BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2408:870c::/32
Announced exactly
- 2408:870c::/32AS17621China Unicom Shanghai networkRPKI Valid2408:870c::
- Registry
- APNIC · China · May 31, 2012
- Delegated block
- 2408:8400:: – 2408:87ff:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2408:870c::/44AS138421China UnicomRPKI Valid2408:870c::
- 2408:870c:20::/44AS138421China UnicomRPKI Valid2408:870c:20::
- 2408:870c:30::/44AS17621China Unicom Shanghai networkRPKI Valid2408:870c:30::
- 2408:870c:40::/44AS17621China Unicom Shanghai networkRPKI Valid2408:870c:40::
- 2408:870c:41::/48AS17621China Unicom Shanghai networkRPKI Valid2408:870c:41::
- 2408:870c:50::/44AS17621China Unicom Shanghai networkRPKI Valid2408:870c:50::
- 2408:870c:80::/44AS17621China Unicom Shanghai networkRPKI Valid2408:870c:80::
- 2408:870c:c0::/44AS17621China Unicom Shanghai networkRPKI Valid2408:870c:c0::
- 2408:870c:d0::/44AS138421China UnicomRPKI Valid2408:870c:d0::
- 2408:870c:e0::/44AS138421China UnicomRPKI Valid2408:870c:e0::
- 2408:870c:f0::/44AS138421China UnicomRPKI Valid2408:870c:f0::
- 2408:870c:130::/44AS17621China Unicom Shanghai networkRPKI Valid2408:870c:130::
- 2408:870c:140::/44AS17621China Unicom Shanghai networkRPKI Valid2408:870c:140::
- 2408:870c:150::/44AS138421China UnicomRPKI Valid2408:870c:150::
- 2408:870c:160::/44AS140979China Unicom Shanghai FuTe IDC networkRPKI Valid2408:870c:160::
- 2408:870c:1000::/44AS17621China Unicom Shanghai networkRPKI Valid2408:870c:1000::
- 2408:870c:1010::/44AS17621China Unicom Shanghai networkRPKI Valid2408:870c:1010::
- 2408:870c:1020::/44AS17621China Unicom Shanghai networkRPKI Valid2408:870c:1020::
- 2408:870c:1030::/44AS17621China Unicom Shanghai networkRPKI Valid2408:870c:1030::
- 2408:870c:1040::/44AS17621China Unicom Shanghai networkRPKI Valid2408:870c:1040::
- 2408:870c:1050::/44AS17621China Unicom Shanghai networkRPKI Valid2408:870c:1050::
- 2408:870c:1060::/44AS17621China Unicom Shanghai networkRPKI Valid2408:870c:1060::
- 2408:870c:1080::/44AS17621China Unicom Shanghai networkRPKI Valid2408:870c:1080::
- 2408:870c:1090::/44AS17621China Unicom Shanghai networkRPKI Valid2408:870c:1090::
- 2408:870c:2020::/44AS138421China UnicomRPKI Valid2408:870c:2020::
- 2408:870c:2030::/44AS138421China UnicomRPKI Valid2408:870c:2030::
- 2408:870c:2040::/44AS138421China UnicomRPKI Valid2408:870c:2040::
- 2408:870c:2050::/44AS138421China UnicomRPKI Valid2408:870c:2050::
- 2408:870c:2070::/44AS138421China UnicomRPKI Valid2408:870c:2070::
- 2408:870c:2080::/44AS138421China UnicomRPKI Valid2408:870c:2080::
- 2408:870c:2090::/44AS138421China UnicomRPKI Valid2408:870c:2090::
- 2408:870c:20a0::/44AS138421China UnicomRPKI Valid2408:870c:20a0::
- 2408:870c:20b0::/44AS138421China UnicomRPKI Valid2408:870c:20b0::
- 2408:870c:20c0::/44AS138421China UnicomRPKI Valid2408:870c:20c0::
- 2408:870c:20d0::/44AS138421China UnicomRPKI Valid2408:870c:20d0::
- 2408:870c:3000::/44AS138421China UnicomRPKI Valid2408:870c:3000::
- 2408:870c:3010::/44AS138421China UnicomRPKI Valid2408:870c:3010::
- 2408:870c:3020::/44AS138421China UnicomRPKI Valid2408:870c:3020::
- 2408:870c:3030::/44AS138421China UnicomRPKI Valid2408:870c:3030::
- 2408:870c:4000::/44AS140979China Unicom Shanghai FuTe IDC networkRPKI Valid2408:870c:4000::
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.