BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
Examples:
70.41.0.0/16
One collector's view (APNIC). A route filtered before it reaches that collector is not listed.
Announced exactly
- 70.41.0.0/16AS7155ViaSat,Inc.RPKI Valid70.41.0.0
- Registry
- ARIN · United States · Sep 22, 2005
- Delegated block
- 70.41.0.0 – 70.41.255.255
Covering routes
0
No less-specific route covers it.
More-specific routes
254 more-specifics from 3 origin AS(es)
- 70.41.0.0/24AS7155ViaSat,Inc.RPKI Valid70.41.0.0
- 70.41.1.0/24AS7155ViaSat,Inc.RPKI Valid70.41.1.0
- 70.41.2.0/24AS7155ViaSat,Inc.RPKI Valid70.41.2.0
- 70.41.3.0/24AS7155ViaSat,Inc.RPKI Valid70.41.3.0
- 70.41.4.0/24AS7155ViaSat,Inc.RPKI Valid70.41.4.0
- 70.41.5.0/24AS7155ViaSat,Inc.RPKI Valid70.41.5.0
- 70.41.6.0/24AS7155ViaSat,Inc.RPKI Valid70.41.6.0
- 70.41.7.0/24AS7155ViaSat,Inc.RPKI Valid70.41.7.0
- 70.41.8.0/24AS7155ViaSat,Inc.RPKI Valid70.41.8.0
- 70.41.9.0/24AS7155ViaSat,Inc.RPKI Valid70.41.9.0
- 70.41.10.0/24AS7155ViaSat,Inc.RPKI Valid70.41.10.0
- 70.41.11.0/24AS7155ViaSat,Inc.RPKI Valid70.41.11.0
- 70.41.12.0/24AS7155ViaSat,Inc.RPKI Valid70.41.12.0
- 70.41.13.0/24AS7155ViaSat,Inc.RPKI Valid70.41.13.0
- 70.41.14.0/24AS7155ViaSat,Inc.RPKI Valid70.41.14.0
- 70.41.15.0/24AS7155ViaSat,Inc.RPKI Valid70.41.15.0
- 70.41.16.0/24AS7155ViaSat,Inc.RPKI Valid70.41.16.0
- 70.41.17.0/24AS7155ViaSat,Inc.RPKI Valid70.41.17.0
- 70.41.18.0/24AS7155ViaSat,Inc.RPKI Valid70.41.18.0
- 70.41.19.0/24AS7155ViaSat,Inc.RPKI Valid70.41.19.0
- 70.41.20.0/24AS7155ViaSat,Inc.RPKI Valid70.41.20.0
- 70.41.21.0/24AS7155ViaSat,Inc.RPKI Valid70.41.21.0
- 70.41.22.0/24AS7155ViaSat,Inc.RPKI Valid70.41.22.0
- 70.41.23.0/24AS16491ViaSat, Inc.RPKI Valid70.41.23.0
- 70.41.24.0/24AS7155ViaSat,Inc.RPKI Valid70.41.24.0
- 70.41.25.0/24AS7155ViaSat,Inc.RPKI Valid70.41.25.0
- 70.41.26.0/24AS40306ViaSat,Inc.RPKI Valid70.41.26.0
- 70.41.27.0/24AS40306ViaSat,Inc.RPKI Valid70.41.27.0
- 70.41.28.0/24AS40306ViaSat,Inc.RPKI Valid70.41.28.0
- 70.41.29.0/24AS40306ViaSat,Inc.RPKI Valid70.41.29.0
- 70.41.30.0/24AS40306ViaSat,Inc.RPKI Valid70.41.30.0
- 70.41.31.0/24AS40306ViaSat,Inc.RPKI Valid70.41.31.0
- 70.41.32.0/24AS7155ViaSat,Inc.RPKI Valid70.41.32.0
- 70.41.33.0/24AS7155ViaSat,Inc.RPKI Valid70.41.33.0
- 70.41.34.0/24AS7155ViaSat,Inc.RPKI Valid70.41.34.0
- 70.41.35.0/24AS7155ViaSat,Inc.RPKI Valid70.41.35.0
- 70.41.36.0/24AS7155ViaSat,Inc.RPKI Valid70.41.36.0
- 70.41.37.0/24AS7155ViaSat,Inc.RPKI Valid70.41.37.0
- 70.41.38.0/24AS7155ViaSat,Inc.RPKI Valid70.41.38.0
- 70.41.39.0/24AS7155ViaSat,Inc.RPKI Valid70.41.39.0
- 70.41.40.0/24AS7155ViaSat,Inc.RPKI Valid70.41.40.0
- 70.41.41.0/24AS7155ViaSat,Inc.RPKI Valid70.41.41.0
- 70.41.42.0/24AS7155ViaSat,Inc.RPKI Valid70.41.42.0
- 70.41.43.0/24AS7155ViaSat,Inc.RPKI Valid70.41.43.0
- 70.41.44.0/24AS7155ViaSat,Inc.RPKI Valid70.41.44.0
- 70.41.45.0/24AS7155ViaSat,Inc.RPKI Valid70.41.45.0
- 70.41.46.0/24AS7155ViaSat,Inc.RPKI Valid70.41.46.0
- 70.41.47.0/24AS7155ViaSat,Inc.RPKI Valid70.41.47.0
- 70.41.48.0/24AS40306ViaSat,Inc.RPKI Valid70.41.48.0
- 70.41.49.0/24AS40306ViaSat,Inc.RPKI Valid70.41.49.0
- 70.41.50.0/24AS40306ViaSat,Inc.RPKI Valid70.41.50.0
- 70.41.51.0/24AS40306ViaSat,Inc.RPKI Valid70.41.51.0
- 70.41.53.0/24AS7155ViaSat,Inc.RPKI Valid70.41.53.0
- 70.41.54.0/24AS7155ViaSat,Inc.RPKI Valid70.41.54.0
- 70.41.55.0/24AS7155ViaSat,Inc.RPKI Valid70.41.55.0
- 70.41.56.0/24AS40306ViaSat,Inc.RPKI Valid70.41.56.0
- 70.41.57.0/24AS40306ViaSat,Inc.RPKI Valid70.41.57.0
- 70.41.58.0/24AS40306ViaSat,Inc.RPKI Valid70.41.58.0
- 70.41.59.0/24AS40306ViaSat,Inc.RPKI Valid70.41.59.0
- 70.41.60.0/24AS7155ViaSat,Inc.RPKI Valid70.41.60.0
- 70.41.61.0/24AS7155ViaSat,Inc.RPKI Valid70.41.61.0
- 70.41.62.0/24AS7155ViaSat,Inc.RPKI Valid70.41.62.0
- 70.41.63.0/24AS7155ViaSat,Inc.RPKI Valid70.41.63.0
- 70.41.64.0/24AS7155ViaSat,Inc.RPKI Valid70.41.64.0
- 70.41.65.0/24AS7155ViaSat,Inc.RPKI Valid70.41.65.0
- 70.41.66.0/24AS7155ViaSat,Inc.RPKI Valid70.41.66.0
- 70.41.67.0/24AS7155ViaSat,Inc.RPKI Valid70.41.67.0
- 70.41.68.0/24AS7155ViaSat,Inc.RPKI Valid70.41.68.0
- 70.41.69.0/24AS7155ViaSat,Inc.RPKI Valid70.41.69.0
- 70.41.70.0/24AS7155ViaSat,Inc.RPKI Valid70.41.70.0
- 70.41.71.0/24AS7155ViaSat,Inc.RPKI Valid70.41.71.0
- 70.41.72.0/24AS40306ViaSat,Inc.RPKI Valid70.41.72.0
- 70.41.73.0/24AS40306ViaSat,Inc.RPKI Valid70.41.73.0
- 70.41.74.0/24AS40306ViaSat,Inc.RPKI Valid70.41.74.0
- 70.41.75.0/24AS40306ViaSat,Inc.RPKI Valid70.41.75.0
- 70.41.76.0/24AS7155ViaSat,Inc.RPKI Valid70.41.76.0
- 70.41.77.0/24AS7155ViaSat,Inc.RPKI Valid70.41.77.0
- 70.41.78.0/24AS7155ViaSat,Inc.RPKI Valid70.41.78.0
- 70.41.79.0/24AS7155ViaSat,Inc.RPKI Valid70.41.79.0
- 70.41.80.0/24AS7155ViaSat,Inc.RPKI Valid70.41.80.0
- 70.41.81.0/24AS7155ViaSat,Inc.RPKI Valid70.41.81.0
- 70.41.82.0/24AS7155ViaSat,Inc.RPKI Valid70.41.82.0
- 70.41.83.0/24AS7155ViaSat,Inc.RPKI Valid70.41.83.0
- 70.41.84.0/24AS7155ViaSat,Inc.RPKI Valid70.41.84.0
- 70.41.85.0/24AS7155ViaSat,Inc.RPKI Valid70.41.85.0
- 70.41.86.0/24AS7155ViaSat,Inc.RPKI Valid70.41.86.0
- 70.41.87.0/24AS7155ViaSat,Inc.RPKI Valid70.41.87.0
- 70.41.88.0/24AS7155ViaSat,Inc.RPKI Valid70.41.88.0
- 70.41.89.0/24AS7155ViaSat,Inc.RPKI Valid70.41.89.0
- 70.41.90.0/24AS7155ViaSat,Inc.RPKI Valid70.41.90.0
- 70.41.91.0/24AS7155ViaSat,Inc.RPKI Valid70.41.91.0
- 70.41.92.0/24AS7155ViaSat,Inc.RPKI Valid70.41.92.0
- 70.41.93.0/24AS7155ViaSat,Inc.RPKI Valid70.41.93.0
- 70.41.94.0/24AS7155ViaSat,Inc.RPKI Valid70.41.94.0
- 70.41.95.0/24AS7155ViaSat,Inc.RPKI Valid70.41.95.0
- 70.41.96.0/24AS7155ViaSat,Inc.RPKI Valid70.41.96.0
- 70.41.97.0/24AS7155ViaSat,Inc.RPKI Valid70.41.97.0
- 70.41.98.0/24AS7155ViaSat,Inc.RPKI Valid70.41.98.0
- 70.41.99.0/24AS7155ViaSat,Inc.RPKI Valid70.41.99.0
- 70.41.100.0/24AS7155ViaSat,Inc.RPKI Valid70.41.100.0
Showing the first 100.
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.