BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2408:8001:3000::/36
Announced exactly
- 2408:8001:3000::/36AS17816China Unicom IP network China169 Guangdong provinceRPKI Valid2408:8001:3000::
- 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:8001:3002::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8001:3002::
- 2408:8001:3010::/44AS17622China Unicom Guangzhou networkRPKI Valid2408:8001:3010::
- 2408:8001:3012::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8001:3012::
- 2408:8001:3022::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8001:3022::
- 2408:8001:3032::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8001:3032::
- 2408:8001:3042::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8001:3042::
- 2408:8001:3052::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8001:3052::
- 2408:8001:3062::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8001:3062::
- 2408:8001:3070::/44AS17623China Unicom Shenzen networkRPKI Valid2408:8001:3070::
- 2408:8001:3072::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8001:3072::
- 2408:8001:3082::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8001:3082::
- 2408:8001:3092::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8001:3092::
- 2408:8001:30a2::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8001:30a2::
- 2408:8001:30b2::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8001:30b2::
- 2408:8001:30c2::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8001:30c2::
- 2408:8001:30d2::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8001:30d2::
- 2408:8001:30e2::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8001:30e2::
- 2408:8001:30f2::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8001:30f2::
- 2408:8001:3102::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8001:3102::
- 2408:8001:3112::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8001:3112::
- 2408:8001:3122::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8001:3122::
- 2408:8001:3132::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8001:3132::
- 2408:8001:3142::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8001:3142::
- 2408:8001:3152::/48AS4837CHINA UNICOM China169 BackboneRPKI Valid2408:8001:3152::
- 2408:8001:3160::/44AS136958China Unicom Guangdong IP networkRPKI Valid2408:8001:3160::
- 2408:8001:3170::/44AS135061China Unicom Guangdong IP networkRPKI Valid2408:8001:3170::
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.