BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2001:4c8::/32
Announced exactly
- 2001:4c8::/32AS6461Zayo BandwidthRPKI Valid2001:4c8::
- Registry
- ARIN · United States · Dec 1, 2004
- Delegated block
- 2001:4c8:: – 2001:4c8:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2001:4c8:1008::/48AS25864Latisys-Irvine, LLCRPKI Valid2001:4c8:1008::
- 2001:4c8:1015::/48AS15290Zayo BandwidthRPKI Valid2001:4c8:1015::
- 2001:4c8:101a::/48AS15290Zayo BandwidthRPKI Valid2001:4c8:101a::
- 2001:4c8:101b::/48AS15290Zayo BandwidthRPKI Valid2001:4c8:101b::
- 2001:4c8:101c::/48AS15290Zayo BandwidthRPKI Valid2001:4c8:101c::
- 2001:4c8:101e::/48AS15290Zayo BandwidthRPKI Valid2001:4c8:101e::
- 2001:4c8:1020::/48AS15290Zayo BandwidthRPKI Valid2001:4c8:1020::
- 2001:4c8:1022::/48AS15290Zayo BandwidthRPKI Valid2001:4c8:1022::
- 2001:4c8:1023::/48AS15290Zayo BandwidthRPKI Valid2001:4c8:1023::
- 2001:4c8:1027::/48AS15290Zayo BandwidthRPKI Valid2001:4c8:1027::
- 2001:4c8:102a::/48AS15290Zayo BandwidthRPKI Valid2001:4c8:102a::
- 2001:4c8:1085::/48AS15290Zayo BandwidthRPKI Valid2001:4c8:1085::
- 2001:4c8:1091::/48AS15290Zayo BandwidthRPKI Valid2001:4c8:1091::
- 2001:4c8:1094::/48AS15290Zayo BandwidthRPKI Valid2001:4c8:1094::
- 2001:4c8:1099::/48AS15290Zayo BandwidthRPKI Valid2001:4c8:1099::
- 2001:4c8:109b::/48AS15290Zayo BandwidthRPKI Valid2001:4c8:109b::
- 2001:4c8:109f::/48AS15290Zayo BandwidthRPKI Valid2001:4c8:109f::
- 2001:4c8:10a1::/48AS15290Zayo BandwidthRPKI Valid2001:4c8:10a1::
- 2001:4c8:10fd::/48AS15290Zayo BandwidthRPKI Valid2001:4c8:10fd::
- 2001:4c8:10fe::/48AS15290Zayo BandwidthRPKI Valid2001:4c8:10fe::
- 2001:4c8:1108::/48AS15290Zayo BandwidthRPKI Valid2001:4c8:1108::
- 2001:4c8:110a::/48AS6461Zayo BandwidthRPKI Valid2001:4c8:110a::
- 2001:4c8:1110::/48AS15290Zayo BandwidthRPKI Valid2001:4c8:1110::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 193.166.0.0/15. 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.