BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
205.252.0.0/16
Announced exactly
- 205.252.0.0/16AS3491PCCW Global (HK) Ltd.RPKI Valid205.252.0.0
- Registry
- APNIC · Hong Kong SAR China · May 2, 1995
- Delegated block
- 205.252.0.0 – 205.252.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 205.252.8.0/22AS3491PCCW Global (HK) Ltd.RPKI Valid205.252.8.0
- 205.252.10.0/24AS3491PCCW Global (HK) Ltd.RPKI Valid205.252.10.0
- 205.252.14.0/23AS3491PCCW Global (HK) Ltd.RPKI Valid205.252.14.0
- 205.252.16.0/22AS3491PCCW Global (HK) Ltd.RPKI Valid205.252.16.0
- 205.252.40.0/22AS3491PCCW Global (HK) Ltd.RPKI Valid205.252.40.0
- 205.252.56.0/22AS3491PCCW Global (HK) Ltd.RPKI Valid205.252.56.0
- 205.252.80.0/21AS3491PCCW Global (HK) Ltd.RPKI Valid205.252.80.0
- 205.252.108.0/22AS3491PCCW Global (HK) Ltd.RPKI Valid205.252.108.0
- 205.252.114.0/24AS3491PCCW Global (HK) Ltd.RPKI Valid205.252.114.0
- 205.252.118.0/24AS395753KKRRPKI Valid205.252.118.0
- 205.252.124.0/24AS55034IGG.COMRPKI Valid205.252.124.0
- 205.252.125.0/24AS55034IGG.COMRPKI Valid205.252.125.0
- 205.252.126.0/24AS55034IGG.COMRPKI Valid205.252.126.0
- 205.252.127.0/24AS55034IGG.COMRPKI Valid205.252.127.0
- 205.252.129.0/24AS33245JabilRPKI Valid205.252.129.0
- 205.252.130.0/23AS3491PCCW Global (HK) Ltd.RPKI Valid205.252.130.0
- 205.252.134.0/24AS3491PCCW Global (HK) Ltd.RPKI Valid205.252.134.0
- 205.252.135.0/24AS3491PCCW Global (HK) Ltd.RPKI Valid205.252.135.0
- 205.252.136.0/24AS3491PCCW Global (HK) Ltd.RPKI Valid205.252.136.0
- 205.252.137.0/24AS3491PCCW Global (HK) Ltd.RPKI Valid205.252.137.0
- 205.252.138.0/24AS3491PCCW Global (HK) Ltd.RPKI Invalid205.252.138.0
- 205.252.143.0/24AS3491PCCW Global (HK) Ltd.RPKI Valid205.252.143.0
- 205.252.144.0/21AS4760HKT LimitedRPKI Valid205.252.144.0
- 205.252.168.0/21AS3491PCCW Global (HK) Ltd.RPKI Valid205.252.168.0
- 205.252.192.0/24AS3491PCCW Global (HK) Ltd.RPKI Valid205.252.192.0
- 205.252.216.0/21AS3491PCCW Global (HK) Ltd.RPKI Valid205.252.216.0
- 205.252.232.0/21AS3491PCCW Global (HK) Ltd.RPKI Valid205.252.232.0
- 205.252.233.0/24AS30967TP Global Operations LimitedRPKI Valid205.252.233.0
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.