BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
59.52.0.0/14
Announced exactly
- 59.52.0.0/14AS4134No.31,Jin-rong StreetRPKI Valid59.52.0.0
- Registry
- APNIC · China · Feb 8, 2005
- Delegated block
- 59.52.0.0 – 59.55.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 59.52.138.0/24AS58777ChinaTelecom Cybersecurity TechRPKI Valid59.52.138.0
- 59.53.48.0/23AS134238CHINANET Jiangx province IDC networkRPKI Valid59.53.48.0
- 59.53.49.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid59.53.49.0
- 59.53.51.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid59.53.51.0
- 59.53.52.0/22AS134238CHINANET Jiangx province IDC networkRPKI Valid59.53.52.0
- 59.53.56.0/21AS134238CHINANET Jiangx province IDC networkRPKI Valid59.53.56.0
- 59.53.60.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid59.53.60.0
- 59.53.64.0/20AS134238CHINANET Jiangx province IDC networkRPKI Valid59.53.64.0
- 59.53.64.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid59.53.64.0
- 59.53.67.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid59.53.67.0
- 59.53.69.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid59.53.69.0
- 59.53.70.0/23AS134238CHINANET Jiangx province IDC networkRPKI Valid59.53.70.0
- 59.53.72.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid59.53.72.0
- 59.53.73.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid59.53.73.0
- 59.53.84.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid59.53.84.0
- 59.53.85.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid59.53.85.0
- 59.53.86.0/23AS139201Jiangxi Jiujiang IDCRPKI Valid59.53.86.0
- 59.53.88.0/24AS139201Jiangxi Jiujiang IDCRPKI Valid59.53.88.0
- 59.53.90.0/23AS134238CHINANET Jiangx province IDC networkRPKI Valid59.53.90.0
- 59.53.92.0/22AS134238CHINANET Jiangx province IDC networkRPKI Valid59.53.92.0
- 59.53.95.0/24AS134238CHINANET Jiangx province IDC networkRPKI Valid59.53.95.0
- 59.54.54.0/24AS139201Jiangxi Jiujiang IDCRPKI Valid59.54.54.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 49.224.0.0/14. 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.