BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2605:3380:4000::/40
Announced exactly
- 2605:3380:4000::/40AS12025Iron Mountain Data CenterRPKI Not found2605:3380:4000::
- Registry
- ARIN · United States · Jan 8, 2014
- Delegated block
- 2605:3380:: – 2605:3380:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
- 2605:3380:4000::/36AS12025Iron Mountain Data CenterRPKI Not found2605:3380:4000::
- 2605:3380::/32AS12025Iron Mountain Data CenterRPKI Not found2605:3380::
More-specific routes
- 2605:3380:4000::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:4000::
- 2605:3380:4001::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:4001::
- 2605:3380:4002::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:4002::
- 2605:3380:4004::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:4004::
- 2605:3380:4007::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:4007::
- 2605:3380:4008::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:4008::
- 2605:3380:4009::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:4009::
- 2605:3380:400a::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:400a::
- 2605:3380:400b::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:400b::
- 2605:3380:400c::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:400c::
- 2605:3380:400e::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:400e::
- 2605:3380:4010::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:4010::
- 2605:3380:4011::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:4011::
- 2605:3380:4012::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:4012::
- 2605:3380:4013::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:4013::
- 2605:3380:4014::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:4014::
- 2605:3380:4015::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:4015::
- 2605:3380:4017::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:4017::
- 2605:3380:4018::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:4018::
- 2605:3380:4019::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:4019::
- 2605:3380:401a::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:401a::
- 2605:3380:401b::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:401b::
- 2605:3380:401c::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:401c::
- 2605:3380:401d::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:401d::
- 2605:3380:401e::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:401e::
- 2605:3380:402a::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:402a::
- 2605:3380:402d::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:402d::
- 2605:3380:402e::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:402e::
- 2605:3380:4030::/48AS12025Iron Mountain Data CenterRPKI Not found2605:3380:4030::
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.