BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2001:c38:9700::/40
Announced exactly
- 2001:c38:9700::/40AS9931National Telecom Public Company LimitedRPKI Valid2001:c38:9700::
- Registry
- APNIC · Thailand · Aug 7, 2002
- Delegated block
- 2001:c38:: – 2001:c38:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
- 2001:c38:9000::/36AS9931National Telecom Public Company LimitedRPKI Valid2001:c38:9000::
More-specific routes
- 2001:c38:9700::/48AS9931National Telecom Public Company LimitedRPKI Valid2001:c38:9700::
- 2001:c38:9703::/48AS9931National Telecom Public Company LimitedRPKI Valid2001:c38:9703::
- 2001:c38:9704::/48AS9931National Telecom Public Company LimitedRPKI Valid2001:c38:9704::
- 2001:c38:9705::/48AS9931National Telecom Public Company LimitedRPKI Valid2001:c38:9705::
- 2001:c38:9706::/48AS9931National Telecom Public Company LimitedRPKI Valid2001:c38:9706::
- 2001:c38:9707::/48AS9931National Telecom Public Company LimitedRPKI Valid2001:c38:9707::
- 2001:c38:9708::/48AS9931National Telecom Public Company LimitedRPKI Valid2001:c38:9708::
- 2001:c38:970a::/48AS9931National Telecom Public Company LimitedRPKI Valid2001:c38:970a::
- 2001:c38:970b::/48AS9931National Telecom Public Company LimitedRPKI Valid2001:c38:970b::
- 2001:c38:970c::/48AS9931National Telecom Public Company LimitedRPKI Valid2001:c38:970c::
- 2001:c38:970d::/48AS9931National Telecom Public Company LimitedRPKI Valid2001:c38:970d::
- 2001:c38:970e::/48AS9931National Telecom Public Company LimitedRPKI Valid2001:c38:970e::
- 2001:c38:970f::/48AS9931National Telecom Public Company LimitedRPKI Valid2001:c38:970f::
- 2001:c38:9710::/48AS9931National Telecom Public Company LimitedRPKI Valid2001:c38:9710::
- 2001:c38:9711::/48AS9931National Telecom Public Company LimitedRPKI Valid2001:c38:9711::
- 2001:c38:9712::/48AS9931National Telecom Public Company LimitedRPKI Valid2001:c38:9712::
- 2001:c38:9713::/48AS9931National Telecom Public Company LimitedRPKI Valid2001:c38:9713::
- 2001:c38:9714::/48AS9931National Telecom Public Company LimitedRPKI Valid2001:c38:9714::
- 2001:c38:9715::/48AS9931National Telecom Public Company LimitedRPKI Valid2001:c38:9715::
- 2001:c38:9716::/48AS9931National Telecom Public Company LimitedRPKI Valid2001:c38:9716::
- 2001:c38:9718::/48AS9464Prince of Songkla University (Sritrang'NET)RPKI Valid2001:c38:9718::
- 2001:c38:9720::/48AS9931National Telecom Public Company LimitedRPKI Valid2001:c38:9720::
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.