BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2001:420::/32
Announced exactly
- 2001:420::/32AS109CISCO SYSTEMS, INC.RPKI Valid2001:420::
- Registry
- ARIN · United States · Jun 14, 2000
- Delegated block
- 2001:420:: – 2001:420:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2001:420:88::/48AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:88::
- 2001:420:89::/48AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:89::
- 2001:420:8a::/48AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:8a::
- 2001:420:8b::/48AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:8b::
- 2001:420:8c::/48AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:8c::
- 2001:420:8d::/48AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:8d::
- 2001:420:8e::/48AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:8e::
- 2001:420:8f::/48AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:8f::
- 2001:420:91::/48AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:91::
- 2001:420:92::/48AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:92::
- 2001:420:93::/48AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:93::
- 2001:420:95::/48AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:95::
- 2001:420:96::/48AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:96::
- 2001:420:1000::/40AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:1000::
- 2001:420:1100::/41AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:1100::
- 2001:420:1180::/41AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:1180::
- 2001:420:1200::/41AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:1200::
- 2001:420:2000::/35AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:2000::
- 2001:420:4000::/36AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:4000::
- 2001:420:4000::/40AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:4000::
- 2001:420:4480::/45AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:4480::
- 2001:420:5000::/39AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:5000::
- 2001:420:5200::/39AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:5200::
- 2001:420:5400::/39AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:5400::
- 2001:420:5500::/40AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:5500::
- 2001:420:5600::/39AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:5600::
- 2001:420:5800::/39AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:5800::
- 2001:420:5a00::/39AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:5a00::
- 2001:420:5c00::/39AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:5c00::
- 2001:420:5e00::/39AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:5e00::
- 2001:420:c0c0::/46AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:c0c0::
- 2001:420:c0c4::/46AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:c0c4::
- 2001:420:c0cc::/46AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:c0cc::
- 2001:420:c0d0::/46AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:c0d0::
- 2001:420:c0d4::/46AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:c0d4::
- 2001:420:c0d8::/46AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:c0d8::
- 2001:420:c0dc::/46AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:c0dc::
- 2001:420:c0e0::/46AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:c0e0::
- 2001:420:c0ec::/46AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:c0ec::
- 2001:420:c0f8::/46AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:c0f8::
- 2001:420:c110::/45AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:c110::
- 2001:420:c128::/47AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:c128::
- 2001:420:c130::/46AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:c130::
- 2001:420:c134::/46AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:c134::
- 2001:420:c138::/46AS109CISCO SYSTEMS, INC.RPKI Valid2001:420:c138::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 2.48.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.