BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
217.156.128.0/17
Announced exactly
- 217.156.128.0/17AS3549Level 3 Parent, LLCRPKI Not found217.156.128.0
- Registry
- RIPE NCC · United Kingdom · Apr 12, 2001
- Delegated block
- 217.156.128.0 – 217.156.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 217.156.133.0/24AS21267Wavenet LimitedRPKI Not found217.156.133.0
- 217.156.134.0/24AS15641Arqiva Communications LtdRPKI Not found217.156.134.0
- 217.156.151.0/24AS10753Level 3 Parent, LLCRPKI Not found217.156.151.0
- 217.156.156.0/24AS21267Wavenet LimitedRPKI Not found217.156.156.0
- 217.156.160.0/21AS3491PCCW Global (HK) Ltd.RPKI Not found217.156.160.0
- 217.156.160.0/24AS3491PCCW Global (HK) Ltd.RPKI Not found217.156.160.0
- 217.156.163.0/24AS3491PCCW Global (HK) Ltd.RPKI Not found217.156.163.0
- 217.156.174.0/24AS395189BROADRIDGE SECURITIES PROCESSING SOLUTIONS, LLCRPKI Not found217.156.174.0
- 217.156.175.0/24AS3257GTT Communications Inc.RPKI Not found217.156.175.0
- 217.156.181.0/24AS3356Level 3 Parent, LLCRPKI Not found217.156.181.0
- 217.156.209.0/24AS21267Wavenet LimitedRPKI Not found217.156.209.0
- 217.156.249.0/24AS21267Wavenet LimitedRPKI Not found217.156.249.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.