BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
170.101.32.0/19
Announced exactly
- 170.101.32.0/19AS402159Valley FiberComRPKI Valid170.101.32.0
- Registry
- ARIN · United States · May 26, 2026
- Delegated block
- 170.101.32.0 – 170.101.63.255
Covering routes
No less-specific route covers it.
More-specific routes
- 170.101.32.0/22AS402159Valley FiberComRPKI Valid170.101.32.0
- 170.101.36.0/22AS402159Valley FiberComRPKI Valid170.101.36.0
- 170.101.40.0/23AS402159Valley FiberComRPKI Valid170.101.40.0
- 170.101.42.0/23AS402159Valley FiberComRPKI Valid170.101.42.0
- 170.101.44.0/23AS402159Valley FiberComRPKI Valid170.101.44.0
- 170.101.46.0/23AS402159Valley FiberComRPKI Valid170.101.46.0
- 170.101.48.0/23AS402159Valley FiberComRPKI Valid170.101.48.0
- 170.101.50.0/24AS402159Valley FiberComRPKI Valid170.101.50.0
- 170.101.51.0/24AS402159Valley FiberComRPKI Valid170.101.51.0
- 170.101.52.0/24AS402159Valley FiberComRPKI Valid170.101.52.0
- 170.101.53.0/24AS402159Valley FiberComRPKI Valid170.101.53.0
- 170.101.54.0/24AS402159Valley FiberComRPKI Valid170.101.54.0
- 170.101.55.0/24AS402159Valley FiberComRPKI Valid170.101.55.0
- 170.101.56.0/24AS402159Valley FiberComRPKI Valid170.101.56.0
- 170.101.57.0/24AS402159Valley FiberComRPKI Valid170.101.57.0
- 170.101.58.0/24AS402159Valley FiberComRPKI Valid170.101.58.0
- 170.101.59.0/24AS402159Valley FiberComRPKI Valid170.101.59.0
- 170.101.60.0/24AS402159Valley FiberComRPKI Valid170.101.60.0
- 170.101.61.0/24AS402159Valley FiberComRPKI Valid170.101.61.0
- 170.101.62.0/24AS402159Valley FiberComRPKI Valid170.101.62.0
- 170.101.63.0/24AS402159Valley FiberComRPKI Valid170.101.63.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 2.48.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.