BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
61.172.0.0/16
Announced exactly
- 61.172.0.0/16AS4812China Telecom (Group)RPKI Valid61.172.0.0
- Registry
- APNIC · China · Nov 16, 2000
- Delegated block
- 61.172.0.0 – 61.175.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 61.172.168.0/23AS4811China Telecom (Group)RPKI Valid61.172.168.0
- 61.172.170.0/23AS4811China Telecom (Group)RPKI Valid61.172.170.0
- 61.172.178.0/23AS4811China Telecom (Group)RPKI Valid61.172.178.0
- 61.172.180.0/23AS4811China Telecom (Group)RPKI Valid61.172.180.0
- 61.172.182.0/23AS4811China Telecom (Group)RPKI Valid61.172.182.0
- 61.172.184.0/21AS4811China Telecom (Group)RPKI Valid61.172.184.0
- 61.172.192.0/24AS4811China Telecom (Group)RPKI Valid61.172.192.0
- 61.172.194.0/24AS4811China Telecom (Group)RPKI Valid61.172.194.0
- 61.172.196.0/24AS4811China Telecom (Group)RPKI Valid61.172.196.0
- 61.172.198.0/24AS4811China Telecom (Group)RPKI Valid61.172.198.0
- 61.172.200.0/23AS4811China Telecom (Group)RPKI Valid61.172.200.0
- 61.172.200.0/24AS4811China Telecom (Group)RPKI Valid61.172.200.0
- 61.172.201.0/24AS4811China Telecom (Group)RPKI Valid61.172.201.0
- 61.172.202.0/24AS4811China Telecom (Group)RPKI Valid61.172.202.0
- 61.172.203.0/24AS4811China Telecom (Group)RPKI Valid61.172.203.0
- 61.172.204.0/24AS4811China Telecom (Group)RPKI Valid61.172.204.0
- 61.172.207.0/24AS4811China Telecom (Group)RPKI Valid61.172.207.0
- 61.172.227.0/24AS4811China Telecom (Group)RPKI Valid61.172.227.0
- 61.172.229.0/24AS4811China Telecom (Group)RPKI Valid61.172.229.0
- 61.172.230.0/24AS4811China Telecom (Group)RPKI Valid61.172.230.0
- 61.172.231.0/24AS4811China Telecom (Group)RPKI Valid61.172.231.0
- 61.172.232.0/24AS4811China Telecom (Group)RPKI Valid61.172.232.0
- 61.172.233.0/24AS4811China Telecom (Group)RPKI Valid61.172.233.0
- 61.172.235.0/24AS4811China Telecom (Group)RPKI Valid61.172.235.0
- 61.172.236.0/24AS4811China Telecom (Group)RPKI Valid61.172.236.0
- 61.172.244.0/23AS4811China Telecom (Group)RPKI Valid61.172.244.0
- 61.172.244.0/24AS4811China Telecom (Group)RPKI Valid61.172.244.0
- 61.172.245.0/24AS4811China Telecom (Group)RPKI Valid61.172.245.0
- 61.172.255.0/24AS4811China Telecom (Group)RPKI Valid61.172.255.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.