BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
195.228.0.0/16
Announced exactly
- 195.228.0.0/16AS5483Magyar Telekom Plc.RPKI Valid195.228.0.0
- Registry
- RIPE NCC · Hungary · Jul 18, 1996
- Delegated block
- 195.228.0.0 – 195.228.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 195.228.4.0/24AS211595OTP Bank Nyrt. HungaryRPKI Valid195.228.4.0
- 195.228.5.0/24AS197698Concorde Securities Ltd.RPKI Valid195.228.5.0
- 195.228.29.0/24AS203583MBH Bank Nyrt.RPKI Valid195.228.29.0
- 195.228.31.0/24AS211595OTP Bank Nyrt. HungaryRPKI Valid195.228.31.0
- 195.228.45.0/24AS5483Magyar Telekom Plc.RPKI Valid195.228.45.0
- 195.228.58.0/24AS209455GYSEV Zrt.RPKI Valid195.228.58.0
- 195.228.59.0/24AS44277DIGI COMMUNICATION SRLRPKI Valid195.228.59.0
- 195.228.73.0/24AS200940T-Systems Magyarorszag zrtRPKI Valid195.228.73.0
- 195.228.75.0/24AS5483Magyar Telekom Plc.RPKI Valid195.228.75.0
- 195.228.76.0/24AS5483Magyar Telekom Plc.RPKI Valid195.228.76.0
- 195.228.83.0/24AS219151Varosliget Ldc.RPKI Valid195.228.83.0
- 195.228.86.0/24AS5483Magyar Telekom Plc.RPKI Valid195.228.86.0
- 195.228.87.0/24AS5483Magyar Telekom Plc.RPKI Valid195.228.87.0
- 195.228.94.0/24AS200940T-Systems Magyarorszag zrtRPKI Valid195.228.94.0
- 195.228.95.0/24AS200940T-Systems Magyarorszag zrtRPKI Valid195.228.95.0
- 195.228.103.0/24AS200940T-Systems Magyarorszag zrtRPKI Valid195.228.103.0
- 195.228.112.0/24AS211595OTP Bank Nyrt. HungaryRPKI Valid195.228.112.0
- 195.228.135.0/24AS5483Magyar Telekom Plc.RPKI Valid195.228.135.0
- 195.228.152.0/24AS5483Magyar Telekom Plc.RPKI Valid195.228.152.0
- 195.228.155.0/24AS5483Magyar Telekom Plc.RPKI Valid195.228.155.0
- 195.228.156.0/24AS5483Magyar Telekom Plc.RPKI Valid195.228.156.0
- 195.228.180.0/24AS203583MBH Bank Nyrt.RPKI Valid195.228.180.0
- 195.228.224.0/23AS5483Magyar Telekom Plc.RPKI Valid195.228.224.0
- 195.228.240.0/24AS5483Magyar Telekom Plc.RPKI Valid195.228.240.0
- 195.228.244.0/24AS5483Magyar Telekom Plc.RPKI Valid195.228.244.0
- 195.228.248.0/24AS5483Magyar Telekom Plc.RPKI Valid195.228.248.0
- 195.228.249.0/24AS5483Magyar Telekom Plc.RPKI Valid195.228.249.0
- 195.228.250.0/24AS5483Magyar Telekom Plc.RPKI Valid195.228.250.0
- 195.228.251.0/24AS5483Magyar Telekom Plc.RPKI Valid195.228.251.0
- 195.228.254.0/24AS5483Magyar Telekom Plc.RPKI Valid195.228.254.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 49.224.0.0/14. This tool looks a prefix up in our daily copy of the global routing table and shows three things:
- Exact announcements: which AS originates exactly this prefix. More than one origin (a MOAS) is normal for anycast services and some multihomed networks, and suspicious otherwise.
- Covering routes: less-specific announcements that contain it. Traffic follows the most specific route, so a covering route matters if the more-specific one disappears.
- More-specifics: announcements inside it, which may belong to other networks (customers, or a hijack).
Each announced route is also checked against the RPKI: whether a ROA authorises its origin AS.
The table is the view from APNIC’s route collector. Most of the global table is the same from everywhere, but a route that is filtered before it reaches that collector will not appear.
Frequently asked questions
Why is my /24 not listed but a /16 is?
Your addresses are announced as part of the larger block, and no one announces the /24 separately. That is the normal case for most customers of a provider.
What is a more-specific hijack?
Someone announces a longer prefix inside your space. Because routers prefer the most specific route, traffic goes to them. RPKI with a strict max length makes such announcements invalid.
Can I enter a single address?
Yes. The tool then shows the most specific announced route that contains it.