BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2600:800::/27
Announced exactly
- 2600:800::/27AS701Verizon BusinessRPKI Not found2600:800::
- Registry
- ARIN · United States · Jan 8, 2007
- Delegated block
- 2600:800:: – 2600:81f:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2600:802:430::/48AS13581SHI International Corp.RPKI Not found2600:802:430::
- 2600:803:22c::/48AS7046Verizon BusinessRPKI Not found2600:803:22c::
- 2600:803:418::/48AS13666Verizon BusinessRPKI Not found2600:803:418::
- 2600:803:618::/48AS3495US SenateRPKI Not found2600:803:618::
- 2600:803:638::/48AS32982U.S. Department of EnergyRPKI Not found2600:803:638::
- 2600:803:1200::/48AS15572Verizon UK LimitedRPKI Not found2600:803:1200::
- 2600:805:f04::/48AS703Verizon BusinessRPKI Not found2600:805:f04::
- 2600:809:44a::/48AS41264Google Switzerland GmbHRPKI Not found2600:809:44a::
- 2600:80b:121::/48AS6984Verizon BusinessRPKI Valid2600:80b:121::
- 2600:80b:122::/48AS6984Verizon BusinessRPKI Valid2600:80b:122::
- 2600:80b:1f1::/48AS6984Verizon BusinessRPKI Not found2600:80b:1f1::
- 2600:80b:1f2::/48AS6984Verizon BusinessRPKI Valid2600:80b:1f2::
- 2600:80d::/40AS6984Verizon BusinessRPKI Not found2600:80d::
- 2600:80d::/48AS6984Verizon BusinessRPKI Not found2600:80d::
- 2600:80d:5::/48AS6984Verizon BusinessRPKI Not found2600:80d:5::
- 2600:80e::/32AS3371Verizon BusinessRPKI Not found2600:80e::
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.