BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
67.0.0.0/13
Announced exactly
- 67.0.0.0/13AS209CenturyLink Communications, LLCRPKI Not found67.0.0.0
- Registry
- ARIN · United States · Jul 26, 2001
- Delegated block
- 67.0.0.0 – 67.7.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 67.0.0.0/16AS209CenturyLink Communications, LLCRPKI Not found67.0.0.0
- 67.1.0.0/16AS209CenturyLink Communications, LLCRPKI Not found67.1.0.0
- 67.2.0.0/16AS209CenturyLink Communications, LLCRPKI Not found67.2.0.0
- 67.3.0.0/17AS209CenturyLink Communications, LLCRPKI Not found67.3.0.0
- 67.3.128.0/17AS209CenturyLink Communications, LLCRPKI Not found67.3.128.0
- 67.4.0.0/16AS209CenturyLink Communications, LLCRPKI Not found67.4.0.0
- 67.4.128.0/17AS209CenturyLink Communications, LLCRPKI Not found67.4.128.0
- 67.4.224.0/20AS209CenturyLink Communications, LLCRPKI Not found67.4.224.0
- 67.5.0.0/16AS209CenturyLink Communications, LLCRPKI Not found67.5.0.0
- 67.5.64.0/23AS209CenturyLink Communications, LLCRPKI Not found67.5.64.0
- 67.5.224.0/19AS209CenturyLink Communications, LLCRPKI Not found67.5.224.0
- 67.6.0.0/16AS19901BrightspeedRPKI Not found67.6.0.0
- 67.7.0.0/19AS19901BrightspeedRPKI Not found67.7.0.0
- 67.7.64.0/19AS209CenturyLink Communications, LLCRPKI Not found67.7.64.0
- 67.7.96.0/20AS19901BrightspeedRPKI Not found67.7.96.0
- 67.7.112.0/20AS19901BrightspeedRPKI Not found67.7.112.0
- 67.7.128.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.128.0
- 67.7.129.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.129.0
- 67.7.130.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.130.0
- 67.7.131.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.131.0
- 67.7.133.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.133.0
- 67.7.134.0/23AS393789CenturyLink Communications, LLCRPKI Not found67.7.134.0
- 67.7.136.0/23AS393789CenturyLink Communications, LLCRPKI Not found67.7.136.0
- 67.7.136.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.136.0
- 67.7.138.0/23AS393789CenturyLink Communications, LLCRPKI Not found67.7.138.0
- 67.7.140.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.140.0
- 67.7.141.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.141.0
- 67.7.142.0/23AS393789CenturyLink Communications, LLCRPKI Not found67.7.142.0
- 67.7.144.0/23AS393789CenturyLink Communications, LLCRPKI Not found67.7.144.0
- 67.7.146.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.146.0
- 67.7.147.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.147.0
- 67.7.149.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.149.0
- 67.7.150.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.150.0
- 67.7.151.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.151.0
- 67.7.152.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.152.0
- 67.7.153.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.153.0
- 67.7.154.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.154.0
- 67.7.156.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.156.0
- 67.7.159.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.159.0
- 67.7.160.0/23AS393789CenturyLink Communications, LLCRPKI Not found67.7.160.0
- 67.7.166.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.166.0
- 67.7.167.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.167.0
- 67.7.168.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.168.0
- 67.7.170.0/23AS393789CenturyLink Communications, LLCRPKI Not found67.7.170.0
- 67.7.172.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.172.0
- 67.7.174.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.174.0
- 67.7.177.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.177.0
- 67.7.178.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.178.0
- 67.7.179.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.179.0
- 67.7.180.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.180.0
- 67.7.181.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.181.0
- 67.7.183.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.183.0
- 67.7.184.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.184.0
- 67.7.185.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.185.0
- 67.7.186.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.186.0
- 67.7.187.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.187.0
- 67.7.188.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.188.0
- 67.7.189.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.189.0
- 67.7.191.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.191.0
- 67.7.192.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.192.0
- 67.7.193.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.193.0
- 67.7.194.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.194.0
- 67.7.196.0/24AS393789CenturyLink Communications, LLCRPKI Not found67.7.196.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.