BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
42.122.0.0/16
Announced exactly
- 42.122.0.0/16AS17638ASN for TIANJIN Provincial Net of CTRPKI Not found42.122.0.0
- Registry
- APNIC · China · Feb 21, 2011
- Delegated block
- 42.122.0.0 – 42.122.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 42.122.0.0/21AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.0.0
- 42.122.8.0/22AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.8.0
- 42.122.12.0/22AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.12.0
- 42.122.16.0/22AS132536China TelecomRPKI Valid42.122.16.0
- 42.122.20.0/23AS132536China TelecomRPKI Valid42.122.20.0
- 42.122.22.0/24AS132536China TelecomRPKI Valid42.122.22.0
- 42.122.23.0/24AS132536China TelecomRPKI Valid42.122.23.0
- 42.122.40.0/22AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.40.0
- 42.122.44.0/22AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.44.0
- 42.122.48.0/22AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.48.0
- 42.122.52.0/22AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.52.0
- 42.122.63.0/24AS58777ChinaTelecom Cybersecurity TechRPKI Valid42.122.63.0
- 42.122.64.0/18AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.64.0
- 42.122.128.0/22AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.128.0
- 42.122.132.0/22AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.132.0
- 42.122.140.0/22AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.140.0
- 42.122.144.0/21AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.144.0
- 42.122.152.0/22AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.152.0
- 42.122.156.0/22AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.156.0
- 42.122.160.0/21AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.160.0
- 42.122.184.0/22AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.184.0
- 42.122.188.0/22AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.188.0
- 42.122.194.0/24AS132536China TelecomRPKI Not found42.122.194.0
- 42.122.196.0/24AS132536China TelecomRPKI Not found42.122.196.0
- 42.122.200.0/22AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.200.0
- 42.122.204.0/22AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.204.0
- 42.122.208.0/22AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.208.0
- 42.122.212.0/22AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.212.0
- 42.122.216.0/22AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.216.0
- 42.122.220.0/22AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.220.0
- 42.122.225.0/24AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.225.0
- 42.122.226.0/24AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.226.0
- 42.122.228.0/22AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.228.0
- 42.122.232.0/21AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.232.0
- 42.122.240.0/21AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.240.0
- 42.122.248.0/23AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.248.0
- 42.122.250.0/23AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.250.0
- 42.122.252.0/22AS17638ASN for TIANJIN Provincial Net of CTRPKI Valid42.122.252.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.