BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
Examples:
67.54.128.0/17
One collector's view (APNIC). A route filtered before it reaches that collector is not listed.
Announced exactly
- 67.54.128.0/17AS7155ViaSat,Inc.RPKI Valid67.54.128.0
- Registry
- ARIN · United States · Jul 15, 2005
- Delegated block
- 67.54.128.0 – 67.54.255.255
Covering routes
0
No less-specific route covers it.
More-specific routes
128 more-specifics from 2 origin AS(es)
- 67.54.128.0/24AS7155ViaSat,Inc.RPKI Valid67.54.128.0
- 67.54.129.0/24AS7155ViaSat,Inc.RPKI Valid67.54.129.0
- 67.54.130.0/24AS7155ViaSat,Inc.RPKI Valid67.54.130.0
- 67.54.131.0/24AS7155ViaSat,Inc.RPKI Valid67.54.131.0
- 67.54.132.0/24AS7155ViaSat,Inc.RPKI Valid67.54.132.0
- 67.54.133.0/24AS7155ViaSat,Inc.RPKI Valid67.54.133.0
- 67.54.134.0/24AS7155ViaSat,Inc.RPKI Valid67.54.134.0
- 67.54.135.0/24AS7155ViaSat,Inc.RPKI Valid67.54.135.0
- 67.54.136.0/24AS7155ViaSat,Inc.RPKI Valid67.54.136.0
- 67.54.137.0/24AS7155ViaSat,Inc.RPKI Valid67.54.137.0
- 67.54.138.0/24AS7155ViaSat,Inc.RPKI Valid67.54.138.0
- 67.54.139.0/24AS7155ViaSat,Inc.RPKI Valid67.54.139.0
- 67.54.140.0/24AS7155ViaSat,Inc.RPKI Valid67.54.140.0
- 67.54.141.0/24AS7155ViaSat,Inc.RPKI Valid67.54.141.0
- 67.54.142.0/24AS7155ViaSat,Inc.RPKI Valid67.54.142.0
- 67.54.143.0/24AS7155ViaSat,Inc.RPKI Valid67.54.143.0
- 67.54.144.0/24AS7155ViaSat,Inc.RPKI Valid67.54.144.0
- 67.54.145.0/24AS7155ViaSat,Inc.RPKI Valid67.54.145.0
- 67.54.146.0/24AS7155ViaSat,Inc.RPKI Valid67.54.146.0
- 67.54.147.0/24AS7155ViaSat,Inc.RPKI Valid67.54.147.0
- 67.54.148.0/24AS7155ViaSat,Inc.RPKI Valid67.54.148.0
- 67.54.149.0/24AS7155ViaSat,Inc.RPKI Valid67.54.149.0
- 67.54.150.0/24AS7155ViaSat,Inc.RPKI Valid67.54.150.0
- 67.54.151.0/24AS7155ViaSat,Inc.RPKI Valid67.54.151.0
- 67.54.152.0/24AS7155ViaSat,Inc.RPKI Valid67.54.152.0
- 67.54.153.0/24AS7155ViaSat,Inc.RPKI Valid67.54.153.0
- 67.54.154.0/24AS7155ViaSat,Inc.RPKI Valid67.54.154.0
- 67.54.155.0/24AS7155ViaSat,Inc.RPKI Valid67.54.155.0
- 67.54.156.0/24AS7155ViaSat,Inc.RPKI Valid67.54.156.0
- 67.54.157.0/24AS7155ViaSat,Inc.RPKI Valid67.54.157.0
- 67.54.158.0/24AS7155ViaSat,Inc.RPKI Valid67.54.158.0
- 67.54.159.0/24AS7155ViaSat,Inc.RPKI Valid67.54.159.0
- 67.54.160.0/24AS7155ViaSat,Inc.RPKI Valid67.54.160.0
- 67.54.161.0/24AS7155ViaSat,Inc.RPKI Valid67.54.161.0
- 67.54.162.0/24AS7155ViaSat,Inc.RPKI Valid67.54.162.0
- 67.54.163.0/24AS7155ViaSat,Inc.RPKI Valid67.54.163.0
- 67.54.164.0/24AS7155ViaSat,Inc.RPKI Valid67.54.164.0
- 67.54.165.0/24AS7155ViaSat,Inc.RPKI Valid67.54.165.0
- 67.54.166.0/24AS7155ViaSat,Inc.RPKI Valid67.54.166.0
- 67.54.167.0/24AS7155ViaSat,Inc.RPKI Valid67.54.167.0
- 67.54.168.0/24AS7155ViaSat,Inc.RPKI Valid67.54.168.0
- 67.54.169.0/24AS7155ViaSat,Inc.RPKI Valid67.54.169.0
- 67.54.170.0/24AS7155ViaSat,Inc.RPKI Valid67.54.170.0
- 67.54.171.0/24AS7155ViaSat,Inc.RPKI Valid67.54.171.0
- 67.54.172.0/24AS7155ViaSat,Inc.RPKI Valid67.54.172.0
- 67.54.173.0/24AS7155ViaSat,Inc.RPKI Valid67.54.173.0
- 67.54.174.0/24AS7155ViaSat,Inc.RPKI Valid67.54.174.0
- 67.54.175.0/24AS7155ViaSat,Inc.RPKI Valid67.54.175.0
- 67.54.176.0/24AS7155ViaSat,Inc.RPKI Valid67.54.176.0
- 67.54.177.0/24AS7155ViaSat,Inc.RPKI Valid67.54.177.0
- 67.54.178.0/24AS7155ViaSat,Inc.RPKI Valid67.54.178.0
- 67.54.179.0/24AS7155ViaSat,Inc.RPKI Valid67.54.179.0
- 67.54.180.0/24AS7155ViaSat,Inc.RPKI Valid67.54.180.0
- 67.54.181.0/24AS7155ViaSat,Inc.RPKI Valid67.54.181.0
- 67.54.182.0/24AS7155ViaSat,Inc.RPKI Valid67.54.182.0
- 67.54.183.0/24AS7155ViaSat,Inc.RPKI Valid67.54.183.0
- 67.54.184.0/24AS7155ViaSat,Inc.RPKI Valid67.54.184.0
- 67.54.185.0/24AS7155ViaSat,Inc.RPKI Valid67.54.185.0
- 67.54.186.0/24AS7155ViaSat,Inc.RPKI Valid67.54.186.0
- 67.54.187.0/24AS7155ViaSat,Inc.RPKI Valid67.54.187.0
- 67.54.188.0/24AS7155ViaSat,Inc.RPKI Valid67.54.188.0
- 67.54.189.0/24AS7155ViaSat,Inc.RPKI Valid67.54.189.0
- 67.54.190.0/24AS7155ViaSat,Inc.RPKI Valid67.54.190.0
- 67.54.191.0/24AS7155ViaSat,Inc.RPKI Valid67.54.191.0
- 67.54.192.0/24AS40306ViaSat,Inc.RPKI Valid67.54.192.0
- 67.54.193.0/24AS7155ViaSat,Inc.RPKI Valid67.54.193.0
- 67.54.194.0/24AS7155ViaSat,Inc.RPKI Valid67.54.194.0
- 67.54.195.0/24AS7155ViaSat,Inc.RPKI Valid67.54.195.0
- 67.54.196.0/24AS7155ViaSat,Inc.RPKI Valid67.54.196.0
- 67.54.197.0/24AS7155ViaSat,Inc.RPKI Valid67.54.197.0
- 67.54.198.0/24AS7155ViaSat,Inc.RPKI Valid67.54.198.0
- 67.54.199.0/24AS7155ViaSat,Inc.RPKI Valid67.54.199.0
- 67.54.200.0/24AS7155ViaSat,Inc.RPKI Valid67.54.200.0
- 67.54.201.0/24AS7155ViaSat,Inc.RPKI Valid67.54.201.0
- 67.54.202.0/24AS7155ViaSat,Inc.RPKI Valid67.54.202.0
- 67.54.203.0/24AS7155ViaSat,Inc.RPKI Valid67.54.203.0
- 67.54.204.0/24AS7155ViaSat,Inc.RPKI Valid67.54.204.0
- 67.54.205.0/24AS7155ViaSat,Inc.RPKI Valid67.54.205.0
- 67.54.206.0/24AS7155ViaSat,Inc.RPKI Valid67.54.206.0
- 67.54.207.0/24AS7155ViaSat,Inc.RPKI Valid67.54.207.0
- 67.54.208.0/24AS7155ViaSat,Inc.RPKI Valid67.54.208.0
- 67.54.209.0/24AS7155ViaSat,Inc.RPKI Valid67.54.209.0
- 67.54.210.0/24AS7155ViaSat,Inc.RPKI Valid67.54.210.0
- 67.54.211.0/24AS7155ViaSat,Inc.RPKI Valid67.54.211.0
- 67.54.212.0/24AS7155ViaSat,Inc.RPKI Valid67.54.212.0
- 67.54.213.0/24AS7155ViaSat,Inc.RPKI Valid67.54.213.0
- 67.54.214.0/24AS7155ViaSat,Inc.RPKI Valid67.54.214.0
- 67.54.215.0/24AS7155ViaSat,Inc.RPKI Valid67.54.215.0
- 67.54.216.0/24AS7155ViaSat,Inc.RPKI Valid67.54.216.0
- 67.54.217.0/24AS7155ViaSat,Inc.RPKI Valid67.54.217.0
- 67.54.218.0/24AS7155ViaSat,Inc.RPKI Valid67.54.218.0
- 67.54.219.0/24AS7155ViaSat,Inc.RPKI Valid67.54.219.0
- 67.54.220.0/24AS7155ViaSat,Inc.RPKI Valid67.54.220.0
- 67.54.221.0/24AS7155ViaSat,Inc.RPKI Valid67.54.221.0
- 67.54.222.0/24AS7155ViaSat,Inc.RPKI Valid67.54.222.0
- 67.54.223.0/24AS7155ViaSat,Inc.RPKI Valid67.54.223.0
- 67.54.224.0/24AS7155ViaSat,Inc.RPKI Valid67.54.224.0
- 67.54.225.0/24AS7155ViaSat,Inc.RPKI Valid67.54.225.0
- 67.54.226.0/24AS7155ViaSat,Inc.RPKI Valid67.54.226.0
- 67.54.227.0/24AS7155ViaSat,Inc.RPKI Valid67.54.227.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.