BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2403:e800::/32
Announced exactly
- 2403:e800::/32AS4637Telstra GlobalRPKI Valid2403:e800::
- Registry
- APNIC · Hong Kong SAR China · Sep 4, 2008
- Delegated block
- 2403:e800:: – 2403:e800:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2403:e800:201::/48AS4637Telstra GlobalRPKI Valid2403:e800:201::
- 2403:e800:203::/48AS4637Telstra GlobalRPKI Valid2403:e800:203::
- 2403:e800:601::/48AS4637Telstra GlobalRPKI Valid2403:e800:601::
- 2403:e800:602::/48AS4637Telstra GlobalRPKI Valid2403:e800:602::
- 2403:e800:603::/48AS4637Telstra GlobalRPKI Valid2403:e800:603::
- 2403:e800:609::/48AS4637Telstra GlobalRPKI Valid2403:e800:609::
- 2403:e800:60a::/48AS4637Telstra GlobalRPKI Valid2403:e800:60a::
- 2403:e800:60b::/48AS4637Telstra GlobalRPKI Valid2403:e800:60b::
- 2403:e800:fd00::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd00::
- 2403:e800:fd01::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd01::
- 2403:e800:fd02::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd02::
- 2403:e800:fd05::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd05::
- 2403:e800:fd07::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd07::
- 2403:e800:fd11::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd11::
- 2403:e800:fd12::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd12::
- 2403:e800:fd18::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd18::
- 2403:e800:fd20::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd20::
- 2403:e800:fd28::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd28::
- 2403:e800:fd2b::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd2b::
- 2403:e800:fd34::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd34::
- 2403:e800:fd38::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd38::
- 2403:e800:fd3c::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd3c::
- 2403:e800:fd3d::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd3d::
- 2403:e800:fd3e::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd3e::
- 2403:e800:fd49::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd49::
- 2403:e800:fd4d::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd4d::
- 2403:e800:fd4e::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd4e::
- 2403:e800:fd4f::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd4f::
- 2403:e800:fd5c::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd5c::
- 2403:e800:fd60::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd60::
- 2403:e800:fd70::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd70::
- 2403:e800:fd78::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd78::
- 2403:e800:fd79::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd79::
- 2403:e800:fd81::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd81::
- 2403:e800:fd88::/48AS4637Telstra GlobalRPKI Valid2403:e800:fd88::
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.