BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2403:2c00::/32
Announced exactly
- 2403:2c00::/32AS4058CITIC Telecom International CPC LimitedRPKI Not found2403:2c00::
- Registry
- APNIC · Hong Kong SAR China · Dec 1, 2009
- Delegated block
- 2403:2c00:: – 2403:2c00:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2403:2c00:3::/48AS4058CITIC Telecom International CPC LimitedRPKI Not found2403:2c00:3::
- 2403:2c00:4::/48AS4058CITIC Telecom International CPC LimitedRPKI Not found2403:2c00:4::
- 2403:2c00:5::/48AS9918TAI FU INTERNATIONAL NETWORK CO., LTD.RPKI Not found2403:2c00:5::
- 2403:2c00:7::/48AS4058CITIC Telecom International CPC LimitedRPKI Not found2403:2c00:7::
- 2403:2c00:9::/48AS4058CITIC Telecom International CPC LimitedRPKI Not found2403:2c00:9::
- 2403:2c00:a::/48AS4058CITIC Telecom International CPC LimitedRPKI Not found2403:2c00:a::
- 2403:2c00:b::/48AS4058CITIC Telecom International CPC LimitedRPKI Not found2403:2c00:b::
- 2403:2c00:8000::/36AS4058CITIC Telecom International CPC LimitedRPKI Not found2403:2c00:8000::
- 2403:2c00:9000::/36AS4058CITIC Telecom International CPC LimitedRPKI Not found2403:2c00:9000::
- 2403:2c00:a000::/36AS4058CITIC Telecom International CPC LimitedRPKI Not found2403:2c00:a000::
- 2403:2c00:c000::/36AS4058CITIC Telecom International CPC LimitedRPKI Not found2403:2c00:c000::
- 2403:2c00:d000::/36AS9918TAI FU INTERNATIONAL NETWORK CO., LTD.RPKI Not found2403:2c00:d000::
- 2403:2c00:e000::/36AS4058CITIC Telecom International CPC LimitedRPKI Not found2403:2c00:e000::
- 2403:2c00:f01f::/48AS4058CITIC Telecom International CPC LimitedRPKI Not found2403:2c00:f01f::
- 2403:2c00:f02b::/48AS198949Radware LtdRPKI Not found2403:2c00:f02b::
- 2403:2c00:fffb::/48AS4058CITIC Telecom International CPC LimitedRPKI Not found2403:2c00:fffb::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 85.240.0.0/13. 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.