BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2401:3cc0::/32
Announced exactly
- 2401:3cc0::/32AS7578Global Secure LayerRPKI Not found2401:3cc0::
- Registry
- APNIC · Hong Kong SAR China · Jun 6, 2017
- Delegated block
- 2401:3cc0:: – 2401:3cc0:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2401:3cc0::/48AS7578Global Secure LayerRPKI Not found2401:3cc0::
- 2401:3cc0:3::/48AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:3::
- 2401:3cc0:8::/48AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:8::
- 2401:3cc0:9::/48AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:9::
- 2401:3cc0:10::/48AS7578Global Secure LayerRPKI Not found2401:3cc0:10::
- 2401:3cc0:12::/48AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:12::
- 2401:3cc0:13::/48AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:13::
- 2401:3cc0:19::/48AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:19::
- 2401:3cc0:24::/48AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:24::
- 2401:3cc0:25::/48AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:25::
- 2401:3cc0:27::/48AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:27::
- 2401:3cc0:29::/48AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:29::
- 2401:3cc0:2a::/48AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:2a::
- 2401:3cc0:30::/48AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:30::
- 2401:3cc0:600::/48AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:600::
- 2401:3cc0:700::/48AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:700::
- 2401:3cc0:800::/48AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:800::
- 2401:3cc0:898::/48AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:898::
- 2401:3cc0:900::/48AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:900::
- 2401:3cc0:100c::/48AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:100c::
- 2401:3cc0:100e::/48AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:100e::
- 2401:3cc0:100f::/48AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:100f::
- 2401:3cc0:1011::/48AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:1011::
- 2401:3cc0:1019::/48AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:1019::
- 2401:3cc0:101c::/48AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:101c::
- 2401:3cc0:1800::/44AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:1800::
- 2401:3cc0:4001::/48AS137409GSL Networks Pty LTDRPKI Not found2401:3cc0:4001::
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.