BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2001:b010::/28
Announced exactly
- 2001:b010::/28AS3462Data Communication Business GroupRPKI Valid2001:b010::
- Registry
- APNIC · Taiwan · Mar 15, 2006
- Delegated block
- 2001:b000:: – 2001:b7ff:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2001:b011::/37AS3462Data Communication Business GroupRPKI Valid2001:b011::
- 2001:b011:1000::/37AS3462Data Communication Business GroupRPKI Valid2001:b011:1000::
- 2001:b011:2000::/36AS3462Data Communication Business GroupRPKI Valid2001:b011:2000::
- 2001:b011:3000::/37AS3462Data Communication Business GroupRPKI Valid2001:b011:3000::
- 2001:b011:3800::/37AS3462Data Communication Business GroupRPKI Valid2001:b011:3800::
- 2001:b011:4000::/37AS3462Data Communication Business GroupRPKI Valid2001:b011:4000::
- 2001:b011:5c00::/38AS3462Data Communication Business GroupRPKI Valid2001:b011:5c00::
- 2001:b011:6800::/37AS3462Data Communication Business GroupRPKI Valid2001:b011:6800::
- 2001:b011:7000::/37AS3462Data Communication Business GroupRPKI Valid2001:b011:7000::
- 2001:b011:7800::/38AS3462Data Communication Business GroupRPKI Valid2001:b011:7800::
- 2001:b011:7c00::/38AS3462Data Communication Business GroupRPKI Valid2001:b011:7c00::
- 2001:b011:8000::/36AS3462Data Communication Business GroupRPKI Valid2001:b011:8000::
- 2001:b011:9800::/38AS3462Data Communication Business GroupRPKI Valid2001:b011:9800::
- 2001:b011:a400::/38AS3462Data Communication Business GroupRPKI Valid2001:b011:a400::
- 2001:b011:b000::/38AS3462Data Communication Business GroupRPKI Valid2001:b011:b000::
- 2001:b011:b800::/38AS3462Data Communication Business GroupRPKI Valid2001:b011:b800::
- 2001:b011:bc00::/38AS3462Data Communication Business GroupRPKI Valid2001:b011:bc00::
- 2001:b011:c000::/37AS3462Data Communication Business GroupRPKI Valid2001:b011:c000::
- 2001:b011:d000::/38AS3462Data Communication Business GroupRPKI Valid2001:b011:d000::
- 2001:b011:d800::/38AS3462Data Communication Business GroupRPKI Valid2001:b011:d800::
- 2001:b011:e000::/38AS3462Data Communication Business GroupRPKI Valid2001:b011:e000::
- 2001:b011:e600::/39AS3462Data Communication Business GroupRPKI Valid2001:b011:e600::
- 2001:b011:f200::/39AS3462Data Communication Business GroupRPKI Valid2001:b011:f200::
- 2001:b011:fa00::/39AS3462Data Communication Business GroupRPKI Valid2001:b011:fa00::
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.