BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
2400:8800::/32
Announced exactly
- 2400:8800::/32AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800::
- Registry
- APNIC · Hong Kong SAR China · Feb 12, 2009
- Delegated block
- 2400:8800:: – 2400:8800:ffff:ffff:ffff:ffff:ffff:ffff
Covering routes
No less-specific route covers it.
More-specific routes
- 2400:8800::/35AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800::
- 2400:8800:1::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:1::
- 2400:8800:101::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:101::
- 2400:8800:102::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:102::
- 2400:8800:500::/48AS6279PCCW Global (HK) Ltd.RPKI Valid2400:8800:500::
- 2400:8800:501::/48AS6279PCCW Global (HK) Ltd.RPKI Valid2400:8800:501::
- 2400:8800:1000::/37AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:1000::
- 2400:8800:1001::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:1001::
- 2400:8800:1e8f::/48AS7262PCCW Global (HK) Ltd.RPKI Valid2400:8800:1e8f::
- 2400:8800:2000::/35AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:2000::
- 2400:8800:4000::/35AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:4000::
- 2400:8800:4201::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:4201::
- 2400:8800:6000::/35AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:6000::
- 2400:8800:8000::/35AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:8000::
- 2400:8800:a000::/35AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:a000::
- 2400:8800:c000::/35AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:c000::
- 2400:8800:e000::/35AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:e000::
- 2400:8800:f805::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:f805::
- 2400:8800:f806::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:f806::
- 2400:8800:f807::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:f807::
- 2400:8800:f80a::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:f80a::
- 2400:8800:f80d::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:f80d::
- 2400:8800:f80f::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:f80f::
- 2400:8800:f810::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:f810::
- 2400:8800:f811::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:f811::
- 2400:8800:f81f::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:f81f::
- 2400:8800:f821::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:f821::
- 2400:8800:f822::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:f822::
- 2400:8800:f823::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:f823::
- 2400:8800:f828::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:f828::
- 2400:8800:f829::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:f829::
- 2400:8800:f8f0::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:f8f0::
- 2400:8800:f8fa::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:f8fa::
- 2400:8800:fc03::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:fc03::
- 2400:8800:fc05::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:fc05::
- 2400:8800:fc07::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:fc07::
- 2400:8800:fc08::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:fc08::
- 2400:8800:fc09::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:fc09::
- 2400:8800:fc0b::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:fc0b::
- 2400:8800:fc0e::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:fc0e::
- 2400:8800:fc0f::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:fc0f::
- 2400:8800:fc10::/48AS3491PCCW Global (HK) Ltd.RPKI Valid2400:8800:fc10::
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 193.166.0.0/15. 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.