BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2408:8000:6000::/36
Announced exactly
- 2408:8000:6000::/36AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8000:6000::
- Registry
- APNIC · China · Jul 7, 2011
- Delegated block
- 2408:8000:: – 2408:83ff:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2408:8000:6001::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8000:6001::
- 2408:8000:6002::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8000:6002::
- 2408:8000:6003::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8000:6003::
- 2408:8000:6004::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8000:6004::
- 2408:8000:6005::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8000:6005::
- 2408:8000:6006::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8000:6006::
- 2408:8000:6007::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8000:6007::
- 2408:8000:6008::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8000:6008::
- 2408:8000:6009::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8000:6009::
- 2408:8000:600a::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8000:600a::
- 2408:8000:600b::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8000:600b::
- 2408:8000:600c::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8000:600c::
- 2408:8000:600d::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8000:600d::
- 2408:8000:600e::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8000:600e::
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.