BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2605:a900::/32
Announced exactly
- 2605:a900::/32AS46887Crown Castle Fiber LLCRPKI Not found2605:a900::
- Registry
- ARIN · United States · Aug 9, 2011
- Delegated block
- 2605:a900:: – 2605:a900:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2605:a900::/36AS46887Crown Castle Fiber LLCRPKI Not found2605:a900::
- 2605:a900:3::/48AS46887Crown Castle Fiber LLCRPKI Not found2605:a900:3::
- 2605:a900:7::/48AS46887Crown Castle Fiber LLCRPKI Not found2605:a900:7::
- 2605:a900:8::/48AS26793ICS Advanced TechnologiesRPKI Not found2605:a900:8::
- 2605:a900:9::/48AS46887Crown Castle Fiber LLCRPKI Not found2605:a900:9::
- 2605:a900:e::/48AS46887Crown Castle Fiber LLCRPKI Not found2605:a900:e::
- 2605:a900:1000::/36AS46887Crown Castle Fiber LLCRPKI Not found2605:a900:1000::
- 2605:a900:1003::/48AS46887Crown Castle Fiber LLCRPKI Not found2605:a900:1003::
- 2605:a900:1006::/48AS46887Crown Castle Fiber LLCRPKI Not found2605:a900:1006::
- 2605:a900:2000::/36AS46887Crown Castle Fiber LLCRPKI Not found2605:a900:2000::
- 2605:a900:2007::/48AS46887Crown Castle Fiber LLCRPKI Not found2605:a900:2007::
- 2605:a900:2016::/48AS46887Crown Castle Fiber LLCRPKI Not found2605:a900:2016::
- 2605:a900:3000::/36AS46887Crown Castle Fiber LLCRPKI Not found2605:a900:3000::
- 2605:a900:300f::/48AS46887Crown Castle Fiber LLCRPKI Not found2605:a900:300f::
- 2605:a900:3013::/48AS46887Crown Castle Fiber LLCRPKI Not found2605:a900:3013::
- 2605:a900:3018::/48AS46887Crown Castle Fiber LLCRPKI Not found2605:a900:3018::
- 2605:a900:3019::/48AS46887Crown Castle Fiber LLCRPKI Not found2605:a900:3019::
- 2605:a900:4000::/36AS46887Crown Castle Fiber LLCRPKI Not found2605:a900:4000::
- 2605:a900:4002::/48AS46887Crown Castle Fiber LLCRPKI Not found2605:a900:4002::
- 2605:a900:4006::/48AS46887Crown Castle Fiber LLCRPKI Not found2605:a900:4006::
- 2605:a900:4007::/48AS46887Crown Castle Fiber LLCRPKI Not found2605:a900:4007::
- 2605:a900:4804::/48AS46887Crown Castle Fiber LLCRPKI Not found2605:a900:4804::
- 2605:a900:4805::/48AS46887Crown Castle Fiber LLCRPKI Not found2605:a900:4805::
- 2605:a900:4807::/48AS46887Crown Castle Fiber LLCRPKI Not found2605:a900:4807::
- 2605:a900:5000::/36AS46887Crown Castle Fiber LLCRPKI Not found2605:a900:5000::
- 2605:a900:9000::/48AS46887Crown Castle Fiber LLCRPKI Not found2605:a900:9000::
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.