BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2401:4c20:300::/40
Announced exactly
- 2401:4c20:300::/40AS150436Byteplus Pte. Ltd.RPKI Valid2401:4c20:300::
- Registry
- APNIC · Singapore · Oct 31, 2023
- Delegated block
- 2401:4c20:: – 2401:4c20:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2401:4c20:300::/44AS150436Byteplus Pte. Ltd.RPKI Valid2401:4c20:300::
- 2401:4c20:310::/44AS150436Byteplus Pte. Ltd.RPKI Valid2401:4c20:310::
- 2401:4c20:320::/44AS150436Byteplus Pte. Ltd.RPKI Valid2401:4c20:320::
- 2401:4c20:330::/44AS150436Byteplus Pte. Ltd.RPKI Valid2401:4c20:330::
- 2401:4c20:340::/44AS150436Byteplus Pte. Ltd.RPKI Valid2401:4c20:340::
- 2401:4c20:350::/44AS150436Byteplus Pte. Ltd.RPKI Valid2401:4c20:350::
- 2401:4c20:360::/44AS150436Byteplus Pte. Ltd.RPKI Valid2401:4c20:360::
- 2401:4c20:370::/44AS150436Byteplus Pte. Ltd.RPKI Valid2401:4c20:370::
- 2401:4c20:380::/44AS150436Byteplus Pte. Ltd.RPKI Valid2401:4c20:380::
- 2401:4c20:390::/44AS150436Byteplus Pte. Ltd.RPKI Valid2401:4c20:390::
- 2401:4c20:3a0::/44AS150436Byteplus Pte. Ltd.RPKI Valid2401:4c20:3a0::
- 2401:4c20:3b0::/44AS150436Byteplus Pte. Ltd.RPKI Valid2401:4c20:3b0::
- 2401:4c20:3c0::/44AS150436Byteplus Pte. Ltd.RPKI Valid2401:4c20:3c0::
- 2401:4c20:3d0::/44AS150436Byteplus Pte. Ltd.RPKI Valid2401:4c20:3d0::
- 2401:4c20:3e0::/44AS150436Byteplus Pte. Ltd.RPKI Valid2401:4c20:3e0::
- 2401:4c20:3f0::/44AS150436Byteplus Pte. Ltd.RPKI Valid2401:4c20:3f0::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 90.190.0.0/15 (Telia Eesti, AS3249). 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.