BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
117.32.0.0/13
Announced exactly
- 117.32.0.0/13AS4134No.31,Jin-rong StreetRPKI Not found117.32.0.0
- Registry
- APNIC · China · Jun 15, 2007
- Delegated block
- 117.32.0.0 – 117.39.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 117.32.233.0/24AS4835China Telecom (Group)RPKI Valid117.32.233.0
- 117.33.128.0/18AS134768CHINANET SHAANXI province Cloud Base networkRPKI Valid117.33.128.0
- 117.33.224.0/19AS134768CHINANET SHAANXI province Cloud Base networkRPKI Valid117.33.224.0
- 117.33.224.0/21AS134768CHINANET SHAANXI province Cloud Base networkRPKI Valid117.33.224.0
- 117.33.232.0/21AS134768CHINANET SHAANXI province Cloud Base networkRPKI Valid117.33.232.0
- 117.33.240.0/21AS134768CHINANET SHAANXI province Cloud Base networkRPKI Valid117.33.240.0
- 117.33.248.0/21AS134768CHINANET SHAANXI province Cloud Base networkRPKI Valid117.33.248.0
- 117.34.0.0/17AS4835China Telecom (Group)RPKI Valid117.34.0.0
- 117.34.7.0/24AS4835China Telecom (Group)RPKI Valid117.34.7.0
- 117.34.9.0/24AS4835China Telecom (Group)RPKI Valid117.34.9.0
- 117.34.35.0/24AS4835China Telecom (Group)RPKI Valid117.34.35.0
- 117.34.41.0/24AS4835China Telecom (Group)RPKI Valid117.34.41.0
- 117.34.42.0/24AS4835China Telecom (Group)RPKI Valid117.34.42.0
- 117.34.43.0/24AS4835China Telecom (Group)RPKI Valid117.34.43.0
- 117.34.49.0/24AS4835China Telecom (Group)RPKI Valid117.34.49.0
- 117.34.50.0/24AS4835China Telecom (Group)RPKI Valid117.34.50.0
- 117.34.51.0/24AS4835China Telecom (Group)RPKI Valid117.34.51.0
- 117.34.52.0/24AS4835China Telecom (Group)RPKI Valid117.34.52.0
- 117.34.55.0/24AS4835China Telecom (Group)RPKI Valid117.34.55.0
- 117.34.58.0/24AS4835China Telecom (Group)RPKI Valid117.34.58.0
- 117.34.82.0/23AS134768CHINANET SHAANXI province Cloud Base networkRPKI Valid117.34.82.0
- 117.34.84.0/23AS134768CHINANET SHAANXI province Cloud Base networkRPKI Valid117.34.84.0
- 117.34.98.0/23AS134768CHINANET SHAANXI province Cloud Base networkRPKI Valid117.34.98.0
- 117.34.100.0/22AS134768CHINANET SHAANXI province Cloud Base networkRPKI Valid117.34.100.0
- 117.34.106.0/23AS134768CHINANET SHAANXI province Cloud Base networkRPKI Valid117.34.106.0
- 117.34.120.0/22AS134768CHINANET SHAANXI province Cloud Base networkRPKI Valid117.34.120.0
- 117.34.124.0/23AS134768CHINANET SHAANXI province Cloud Base networkRPKI Valid117.34.124.0
- 117.34.208.0/21AS134768CHINANET SHAANXI province Cloud Base networkRPKI Valid117.34.208.0
- 117.38.0.0/16AS4809China Telecom Next Generation Carrier NetworkRPKI Valid117.38.0.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.