BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
170.202.128.0/17
Announced exactly
- 170.202.128.0/17AS17166Travelers Property Casualty Corp.RPKI Not found170.202.128.0
- Registry
- ARIN · United States · Nov 17, 1994
- Delegated block
- 170.202.0.0 – 170.202.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 170.202.144.0/21AS395180Travelers Property Casualty Corp.RPKI Not found170.202.144.0
- 170.202.152.0/21AS395180Travelers Property Casualty Corp.RPKI Not found170.202.152.0
- 170.202.160.0/22AS17166Travelers Property Casualty Corp.RPKI Not found170.202.160.0
- 170.202.164.0/22AS17166Travelers Property Casualty Corp.RPKI Not found170.202.164.0
- 170.202.168.0/24AS17166Travelers Property Casualty Corp.RPKI Not found170.202.168.0
- 170.202.172.0/23AS17166Travelers Property Casualty Corp.RPKI Not found170.202.172.0
- 170.202.174.0/24AS17166Travelers Property Casualty Corp.RPKI Not found170.202.174.0
- 170.202.176.0/24AS17166Travelers Property Casualty Corp.RPKI Not found170.202.176.0
- 170.202.177.0/24AS395180Travelers Property Casualty Corp.RPKI Not found170.202.177.0
- 170.202.182.0/24AS23381Travelers Property Casualty Corp.RPKI Not found170.202.182.0
- 170.202.183.0/24AS23381Travelers Property Casualty Corp.RPKI Not found170.202.183.0
- 170.202.184.0/24AS23381Travelers Property Casualty Corp.RPKI Not found170.202.184.0
- 170.202.185.0/24AS23381Travelers Property Casualty Corp.RPKI Not found170.202.185.0
- 170.202.187.0/24AS23381Travelers Property Casualty Corp.RPKI Not found170.202.187.0
- 170.202.188.0/24AS23381Travelers Property Casualty Corp.RPKI Not found170.202.188.0
- 170.202.189.0/24AS23381Travelers Property Casualty Corp.RPKI Not found170.202.189.0
- 170.202.191.0/24AS23381Travelers Property Casualty Corp.RPKI Not found170.202.191.0
- 170.202.200.0/24AS14931The St. Paul Travelers Companies, Inc.RPKI Not found170.202.200.0
- 170.202.202.0/24AS17166Travelers Property Casualty Corp.RPKI Not found170.202.202.0
- 170.202.203.0/24AS23381Travelers Property Casualty Corp.RPKI Not found170.202.203.0
- 170.202.206.0/24AS23381Travelers Property Casualty Corp.RPKI Not found170.202.206.0
- 170.202.207.0/24AS23381Travelers Property Casualty Corp.RPKI Not found170.202.207.0
- 170.202.208.0/23AS14931The St. Paul Travelers Companies, Inc.RPKI Not found170.202.208.0
- 170.202.208.0/24AS14931The St. Paul Travelers Companies, Inc.RPKI Not found170.202.208.0
- 170.202.209.0/24AS14931The St. Paul Travelers Companies, Inc.RPKI Not found170.202.209.0
- 170.202.210.0/24AS14931The St. Paul Travelers Companies, Inc.RPKI Not found170.202.210.0
- 170.202.211.0/24AS14931The St. Paul Travelers Companies, Inc.RPKI Not found170.202.211.0
- 170.202.215.0/24AS17166Travelers Property Casualty Corp.RPKI Not found170.202.215.0
- 170.202.216.0/24AS17166Travelers Property Casualty Corp.RPKI Not found170.202.216.0
- 170.202.217.0/24AS17166Travelers Property Casualty Corp.RPKI Not found170.202.217.0
- 170.202.218.0/24AS17166Travelers Property Casualty Corp.RPKI Not found170.202.218.0
- 170.202.219.0/24AS17166Travelers Property Casualty Corp.RPKI Not found170.202.219.0
- 170.202.222.0/24AS17166Travelers Property Casualty Corp.RPKI Not found170.202.222.0
- 170.202.224.0/22AS17166Travelers Property Casualty Corp.RPKI Not found170.202.224.0
- 170.202.228.0/22AS17166Travelers Property Casualty Corp.RPKI Not found170.202.228.0
- 170.202.233.0/24AS17166Travelers Property Casualty Corp.RPKI Not found170.202.233.0
- 170.202.235.0/24AS17166Travelers Property Casualty Corp.RPKI Not found170.202.235.0
- 170.202.236.0/23AS17166Travelers Property Casualty Corp.RPKI Not found170.202.236.0
- 170.202.238.0/23AS17166Travelers Property Casualty Corp.RPKI Not found170.202.238.0
- 170.202.240.0/24AS17166Travelers Property Casualty Corp.RPKI Not found170.202.240.0
- 170.202.241.0/24AS17166Travelers Property Casualty Corp.RPKI Not found170.202.241.0
- 170.202.244.0/24AS17166Travelers Property Casualty Corp.RPKI Not found170.202.244.0
- 170.202.245.0/24AS17166Travelers Property Casualty Corp.RPKI Not found170.202.245.0
- 170.202.246.0/23AS17166Travelers Property Casualty Corp.RPKI Not found170.202.246.0
- 170.202.248.0/22AS17166Travelers Property Casualty Corp.RPKI Not found170.202.248.0
- 170.202.252.0/22AS17166Travelers Property Casualty Corp.RPKI Not found170.202.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, 193.166.0.0/15. 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.