BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2404::/32
Announced exactly
- Registry
- APNIC · Taiwan · Jan 25, 2006
- Delegated block
- 2404:: – 2404:3f:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
More-specific routes
- 2404:0:1000::/40AS17709Asia Pacific TelecomRPKI Valid2404:0:1000::
- 2404:0:10a4::/48AS17709Asia Pacific TelecomRPKI Valid2404:0:10a4::
- 2404:0:10a5::/48AS4780Digital United Inc.RPKI Valid2404:0:10a5::
- 2404:0:10a6::/48AS17709Asia Pacific TelecomRPKI Valid2404:0:10a6::
- 2404:0:2000::/36AS7482Asia Pacific On-line Service Inc.RPKI Valid2404:0:2000::
- 2404:0:4000::/36AS9311HITRON TECHNOLOGY INC.RPKI Valid2404:0:4000::
- 2404:0:5000::/48AS24154Asia Pacific Broadband Fixed Lines Co., Ltd.RPKI Valid2404:0:5000::
- 2404:0:5001::/48AS24154Asia Pacific Broadband Fixed Lines Co., Ltd.RPKI Valid2404:0:5001::
- 2404:0:5002::/48AS24154Asia Pacific Broadband Fixed Lines Co., Ltd.RPKI Valid2404:0:5002::
- 2404:0:5005::/48AS24154Asia Pacific Broadband Fixed Lines Co., Ltd.RPKI Valid2404:0:5005::
- 2404:0:5ffa::/48AS24154Asia Pacific Broadband Fixed Lines Co., Ltd.RPKI Valid2404:0:5ffa::
- 2404:0:5ffb::/48AS24154Asia Pacific Broadband Fixed Lines Co., Ltd.RPKI Valid2404:0:5ffb::
- 2404:0:5ffc::/48AS24154Asia Pacific Broadband Fixed Lines Co., Ltd.RPKI Valid2404:0:5ffc::
- 2404:0:5ffd::/48AS24154Asia Pacific Broadband Fixed Lines Co., Ltd.RPKI Valid2404:0:5ffd::
- 2404:0:5ffe::/48AS24154Asia Pacific Broadband Fixed Lines Co., Ltd.RPKI Valid2404:0:5ffe::
- 2404:0:5fff::/48AS24154Asia Pacific Broadband Fixed Lines Co., Ltd.RPKI Valid2404:0:5fff::
- 2404:0:6000::/36AS24155Asia Pacific Broadband Wireless Communications IncRPKI Valid2404:0:6000::
- 2404:0:7000::/36AS131142Asia Pacific On-Line Service Inc.RPKI Valid2404:0:7000::
- 2404:0:8a00::/48AS17709Asia Pacific TelecomRPKI Valid2404:0:8a00::
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.