BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2800:68::/32
Announced exactly
- 2800:68::/32AS61468CEDIARPKI Valid2800:68::
- Registry
- LACNIC · Ecuador · Jul 19, 2006
- Delegated block
- 2800:68:: – 2800:68:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2800:68::/48AS61468CEDIARPKI Valid2800:68::
- 2800:68:1::/48AS61468CEDIARPKI Valid2800:68:1::
- 2800:68:6::/48AS61468CEDIARPKI Valid2800:68:6::
- 2800:68:7::/48AS61468CEDIARPKI Valid2800:68:7::
- 2800:68:9::/48AS61468CEDIARPKI Valid2800:68:9::
- 2800:68:a::/48AS61468CEDIARPKI Valid2800:68:a::
- 2800:68:c::/48AS61468CEDIARPKI Valid2800:68:c::
- 2800:68:10::/48AS61468CEDIARPKI Valid2800:68:10::
- 2800:68:11::/48AS262212Escuela Politecnica NacionalRPKI Valid2800:68:11::
- 2800:68:12::/48AS61468CEDIARPKI Valid2800:68:12::
- 2800:68:13::/48AS61468CEDIARPKI Valid2800:68:13::
- 2800:68:14::/48AS61468CEDIARPKI Valid2800:68:14::
- 2800:68:15::/48AS52343UNIVERSIDAD UTERPKI Valid2800:68:15::
- 2800:68:1d::/48AS27947Telconet S.ARPKI Valid2800:68:1d::
- 2800:68:1f::/48AS61468CEDIARPKI Valid2800:68:1f::
- 2800:68:20::/48AS61468CEDIARPKI Valid2800:68:20::
- 2800:68:22::/48AS27947Telconet S.ARPKI Valid2800:68:22::
- 2800:68:2b::/48AS61468CEDIARPKI Valid2800:68:2b::
- 2800:68:2d::/48AS61468CEDIARPKI Valid2800:68:2d::
- 2800:68:33::/48AS269844UNIVERSIDAD NACIONAL DEL CHIMBORAZORPKI Valid2800:68:33::
- 2800:68:34::/48AS61468CEDIARPKI Valid2800:68:34::
- 2800:68:39::/48AS27947Telconet S.ARPKI Valid2800:68:39::
- 2800:68:3a::/48AS27947Telconet S.ARPKI Valid2800:68:3a::
- 2800:68:3c::/48AS27947Telconet S.ARPKI Valid2800:68:3c::
- 2800:68:3e::/48AS61468CEDIARPKI Valid2800:68:3e::
- 2800:68:40::/48AS27947Telconet S.ARPKI Valid2800:68:40::
- 2800:68:42::/48AS27947Telconet S.ARPKI Valid2800:68:42::
- 2800:68:43::/48AS61468CEDIARPKI Valid2800:68:43::
- 2800:68:44::/48AS61468CEDIARPKI Valid2800:68:44::
- 2800:68:50::/48AS61468CEDIARPKI Valid2800:68:50::
- 2800:68:52::/48AS61468CEDIARPKI Valid2800:68:52::
- 2800:68:54::/48AS27947Telconet S.ARPKI Valid2800:68:54::
- 2800:68:57::/48AS61468CEDIARPKI Valid2800:68:57::
- 2800:68:dc0::/48AS61468CEDIARPKI Valid2800:68:dc0::
- 2800:68:1aa5::/48AS61468CEDIARPKI Valid2800:68:1aa5::
- 2800:68:6000::/48AS61468CEDIARPKI Valid2800:68:6000::
- 2800:68:6001::/48AS61468CEDIARPKI Valid2800:68:6001::
- 2800:68:baca::/48AS61468CEDIARPKI Valid2800:68:baca::
- 2800:68:c0c0::/48AS61468CEDIARPKI Valid2800:68:c0c0::
- 2800:68:dc41::/48AS61468CEDIARPKI Valid2800:68:dc41::
- 2800:68:ffff::/48AS61468CEDIARPKI Valid2800:68:ffff::
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.