BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
59.56.0.0/14
Announced exactly
- 59.56.0.0/14AS4134No.31,Jin-rong StreetRPKI Valid59.56.0.0
- Registry
- APNIC · China · Nov 18, 2004
- Delegated block
- 59.56.0.0 – 59.59.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 59.56.16.0/20AS133774FuzhouRPKI Valid59.56.16.0
- 59.56.16.0/24AS133774FuzhouRPKI Valid59.56.16.0
- 59.56.17.0/24AS133774FuzhouRPKI Valid59.56.17.0
- 59.56.18.0/24AS133774FuzhouRPKI Valid59.56.18.0
- 59.56.19.0/24AS133774FuzhouRPKI Valid59.56.19.0
- 59.56.20.0/24AS133774FuzhouRPKI Valid59.56.20.0
- 59.56.21.0/24AS133774FuzhouRPKI Valid59.56.21.0
- 59.56.22.0/24AS133774FuzhouRPKI Valid59.56.22.0
- 59.56.23.0/24AS133774FuzhouRPKI Valid59.56.23.0
- 59.56.24.0/24AS133774FuzhouRPKI Valid59.56.24.0
- 59.56.25.0/24AS133774FuzhouRPKI Valid59.56.25.0
- 59.56.26.0/24AS133774FuzhouRPKI Valid59.56.26.0
- 59.56.27.0/24AS133774FuzhouRPKI Valid59.56.27.0
- 59.56.30.0/24AS133774FuzhouRPKI Valid59.56.30.0
- 59.56.31.0/24AS133774FuzhouRPKI Valid59.56.31.0
- 59.56.64.0/24AS133774FuzhouRPKI Valid59.56.64.0
- 59.56.65.0/24AS133774FuzhouRPKI Valid59.56.65.0
- 59.56.66.0/24AS133774FuzhouRPKI Valid59.56.66.0
- 59.56.67.0/24AS133774FuzhouRPKI Valid59.56.67.0
- 59.56.68.0/24AS133774FuzhouRPKI Valid59.56.68.0
- 59.56.69.0/24AS133774FuzhouRPKI Valid59.56.69.0
- 59.56.70.0/24AS133774FuzhouRPKI Valid59.56.70.0
- 59.56.71.0/24AS133774FuzhouRPKI Valid59.56.71.0
- 59.56.72.0/24AS133774FuzhouRPKI Valid59.56.72.0
- 59.56.73.0/24AS133774FuzhouRPKI Valid59.56.73.0
- 59.56.74.0/24AS133774FuzhouRPKI Valid59.56.74.0
- 59.56.75.0/24AS133774FuzhouRPKI Valid59.56.75.0
- 59.56.76.0/24AS133774FuzhouRPKI Valid59.56.76.0
- 59.56.77.0/24AS133774FuzhouRPKI Valid59.56.77.0
- 59.56.78.0/24AS133774FuzhouRPKI Valid59.56.78.0
- 59.56.79.0/24AS133774FuzhouRPKI Valid59.56.79.0
- 59.56.96.0/24AS133774FuzhouRPKI Valid59.56.96.0
- 59.56.97.0/24AS133774FuzhouRPKI Valid59.56.97.0
- 59.56.98.0/24AS133774FuzhouRPKI Valid59.56.98.0
- 59.56.99.0/24AS133774FuzhouRPKI Valid59.56.99.0
- 59.56.100.0/24AS133774FuzhouRPKI Valid59.56.100.0
- 59.56.101.0/24AS133774FuzhouRPKI Valid59.56.101.0
- 59.56.102.0/24AS133774FuzhouRPKI Valid59.56.102.0
- 59.56.103.0/24AS133774FuzhouRPKI Valid59.56.103.0
- 59.56.104.0/22AS133774FuzhouRPKI Valid59.56.104.0
- 59.56.104.0/24AS133774FuzhouRPKI Valid59.56.104.0
- 59.56.109.0/24AS133774FuzhouRPKI Valid59.56.109.0
- 59.56.110.0/24AS133774FuzhouRPKI Valid59.56.110.0
- 59.56.111.0/24AS133774FuzhouRPKI Valid59.56.111.0
- 59.57.12.0/23AS133776QuanzhouRPKI Valid59.57.12.0
- 59.57.15.0/24AS133776QuanzhouRPKI Valid59.57.15.0
- 59.59.172.0/22AS133774FuzhouRPKI Valid59.59.172.0
- 59.59.176.0/21AS133774FuzhouRPKI Valid59.59.176.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.