BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2800:40::/32
Announced exactly
- 2800:40::/32AS16814NSS S.A.RPKI Valid2800:40::
- Registry
- LACNIC · Argentina · Mar 7, 2006
- Delegated block
- 2800:40:: – 2800:40:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2800:40:16::/48AS16814NSS S.A.RPKI Valid2800:40:16::
- 2800:40:2c::/48AS16814NSS S.A.RPKI Valid2800:40:2c::
- 2800:40:33::/48AS16814NSS S.A.RPKI Valid2800:40:33::
- 2800:40:35::/48AS16814NSS S.A.RPKI Valid2800:40:35::
- 2800:40:37::/48AS16814NSS S.A.RPKI Valid2800:40:37::
- 2800:40:38::/48AS16814NSS S.A.RPKI Valid2800:40:38::
- 2800:40:39::/48AS16814NSS S.A.RPKI Valid2800:40:39::
- 2800:40:3a::/48AS16814NSS S.A.RPKI Valid2800:40:3a::
- 2800:40:3b::/48AS16814NSS S.A.RPKI Valid2800:40:3b::
- 2800:40:3c::/48AS16814NSS S.A.RPKI Valid2800:40:3c::
- 2800:40:3d::/48AS16814NSS S.A.RPKI Valid2800:40:3d::
- 2800:40:3e::/48AS16814NSS S.A.RPKI Valid2800:40:3e::
- 2800:40:40::/48AS16814NSS S.A.RPKI Valid2800:40:40::
- 2800:40:41::/48AS16814NSS S.A.RPKI Valid2800:40:41::
- 2800:40:42::/48AS16814NSS S.A.RPKI Valid2800:40:42::
- 2800:40:43::/48AS16814NSS S.A.RPKI Valid2800:40:43::
- 2800:40:44::/48AS16814NSS S.A.RPKI Valid2800:40:44::
- 2800:40:45::/48AS16814NSS S.A.RPKI Valid2800:40:45::
- 2800:40:46::/48AS16814NSS S.A.RPKI Valid2800:40:46::
- 2800:40:47::/48AS16814NSS S.A.RPKI Valid2800:40:47::
- 2800:40:48::/48AS16814NSS S.A.RPKI Valid2800:40:48::
- 2800:40:51::/48AS16814NSS S.A.RPKI Valid2800:40:51::
- 2800:40:52::/48AS16814NSS S.A.RPKI Valid2800:40:52::
- 2800:40:67::/48AS16814NSS S.A.RPKI Valid2800:40:67::
- 2800:40:68::/48AS16814NSS S.A.RPKI Valid2800:40:68::
- 2800:40:69::/48AS16814NSS S.A.RPKI Valid2800:40:69::
- 2800:40:6e::/48AS16814NSS S.A.RPKI Valid2800:40:6e::
- 2800:40:70::/48AS16814NSS S.A.RPKI Valid2800:40:70::
- 2800:40:71::/48AS16814NSS S.A.RPKI Valid2800:40:71::
- 2800:40:72::/48AS16814NSS S.A.RPKI Valid2800:40:72::
- 2800:40:73::/48AS16814NSS S.A.RPKI Valid2800:40:73::
- 2800:40:74::/48AS16814NSS S.A.RPKI Valid2800:40:74::
- 2800:40:75::/48AS16814NSS S.A.RPKI Valid2800:40:75::
- 2800:40:76::/48AS16814NSS S.A.RPKI Valid2800:40:76::
- 2800:40:77::/48AS16814NSS S.A.RPKI Valid2800:40:77::
- 2800:40:79::/48AS16814NSS S.A.RPKI Valid2800:40:79::
- 2800:40:80::/48AS16814NSS S.A.RPKI Valid2800:40:80::
- 2800:40:81::/48AS16814NSS S.A.RPKI Valid2800:40:81::
- 2800:40:82::/48AS16814NSS S.A.RPKI Valid2800:40:82::
- 2800:40:83::/48AS16814NSS S.A.RPKI Valid2800:40:83::
- 2800:40:84::/48AS16814NSS S.A.RPKI Valid2800:40:84::
- 2800:40:85::/48AS16814NSS S.A.RPKI Valid2800:40:85::
- 2800:40:86::/48AS16814NSS S.A.RPKI Valid2800:40:86::
- 2800:40:401::/48AS16814NSS S.A.RPKI Valid2800:40:401::
- 2800:40:402::/48AS16814NSS S.A.RPKI Valid2800:40:402::
- 2800:40:403::/48AS16814NSS S.A.RPKI Valid2800:40:403::
- 2800:40:404::/48AS16814NSS S.A.RPKI Valid2800:40:404::
- 2800:40:405::/48AS16814NSS S.A.RPKI Valid2800:40:405::
- 2800:40:406::/48AS16814NSS S.A.RPKI Valid2800:40:406::
- 2800:40:407::/48AS16814NSS S.A.RPKI Valid2800:40:407::
- 2800:40:408::/48AS16814NSS S.A.RPKI Valid2800:40:408::
- 2800:40:40a::/48AS16814NSS S.A.RPKI Valid2800:40:40a::
- 2800:40:603::/48AS16814NSS S.A.RPKI Valid2800:40:603::
- 2800:40:74c::/48AS16814NSS S.A.RPKI Valid2800:40:74c::
- 2800:40:804::/48AS16814NSS S.A.RPKI Valid2800:40:804::
- 2800:40:fc00::/40AS16814NSS S.A.RPKI Valid2800:40:fc00::
- 2800:40:fd00::/40AS16814NSS S.A.RPKI Valid2800:40:fd00::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 2.48.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.