BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
205.160.0.0/14
Announced exactly
- 205.160.0.0/14AS174Cogent Communications, LLCRPKI Not found205.160.0.0
- Registry
- ARIN · United States · Mar 8, 1995
- Delegated block
- 205.160.0.0 – 205.163.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 205.160.6.0/24AS19643Network Synergy CorporationRPKI Not found205.160.6.0
- 205.160.168.0/23AS4373Online Computer Library CenterRPKI Not found205.160.168.0
- 205.160.176.0/20AS2379CenturyLink Communications, LLCRPKI Not found205.160.176.0
- 205.160.192.0/24AS2379CenturyLink Communications, LLCRPKI Not found205.160.192.0
- 205.160.198.0/24AS6222CenturyLink Communications, LLCRPKI Not found205.160.198.0
- 205.160.233.0/24AS11139Cable & Wireless DominicaRPKI Not found205.160.233.0
- 205.160.240.0/20AS2379CenturyLink Communications, LLCRPKI Not found205.160.240.0
- 205.160.241.0/24AS12090AAA NationalRPKI Not found205.160.241.0
- 205.161.14.0/24AS9751AMERICAN SAMOA TELECOMMUNICATIONS AUTHORITYRPKI Not found205.161.14.0
- 205.161.15.0/24AS9751AMERICAN SAMOA TELECOMMUNICATIONS AUTHORITYRPKI Not found205.161.15.0
- 205.161.16.0/20AS14174North Central Kansas Community Network Co.RPKI Not found205.161.16.0
- 205.161.16.0/21AS14174North Central Kansas Community Network Co.RPKI Not found205.161.16.0
- 205.161.64.0/19AS174Cogent Communications, LLCRPKI Not found205.161.64.0
- 205.161.64.0/20AS6079RCNRPKI Not found205.161.64.0
- 205.161.64.0/21AS11404Wave BroadbandRPKI Not found205.161.64.0
- 205.161.72.0/21AS11404Wave BroadbandRPKI Not found205.161.72.0
- 205.161.80.0/20AS6079RCNRPKI Not found205.161.80.0
- 205.161.80.0/21AS11404Wave BroadbandRPKI Not found205.161.80.0
- 205.161.88.0/21AS7029Windstream Communications LLCRPKI Not found205.161.88.0
- 205.161.124.0/23AS32182Grange Mutual Casualty Co.RPKI Not found205.161.124.0
- 205.161.188.0/24AS10586OSI de GuatemalaRPKI Not found205.161.188.0
- 205.161.205.0/24AS18593The Goldman Sachs Group, Inc.RPKI Not found205.161.205.0
- 205.161.222.0/24AS174Cogent Communications, LLCRPKI Not found205.161.222.0
- 205.161.224.0/20AS2379CenturyLink Communications, LLCRPKI Not found205.161.224.0
- 205.161.229.0/24AS209CenturyLink Communications, LLCRPKI Not found205.161.229.0
- 205.162.40.0/21AS53866Omeda CommunicationsRPKI Not found205.162.40.0
- 205.162.49.0/24AS19081UNASSIGNEDRPKI Not found205.162.49.0
- 205.162.152.0/23AS174Cogent Communications, LLCRPKI Not found205.162.152.0
- 205.162.160.0/22AS174Cogent Communications, LLCRPKI Not found205.162.160.0
- 205.162.192.0/20AS14921CenturyLink Communications, LLCRPKI Not found205.162.192.0
- 205.162.201.0/24AS11404Wave BroadbandRPKI Not found205.162.201.0
- 205.162.202.0/24AS11404Wave BroadbandRPKI Not found205.162.202.0
- 205.162.209.0/24AS15065Slic Network Solutions, IncRPKI Not found205.162.209.0
- 205.162.224.0/20AS8025BrightNet OklahomaRPKI Not found205.162.224.0
- 205.163.0.0/20AS7029Windstream Communications LLCRPKI Not found205.163.0.0
- 205.163.16.0/20AS3320Deutsche Telekom AGRPKI Not found205.163.16.0
- 205.163.32.0/20AS7029Windstream Communications LLCRPKI Not found205.163.32.0
- 205.163.48.0/20AS7029Windstream Communications LLCRPKI Not found205.163.48.0
- 205.163.64.0/20AS7029Windstream Communications LLCRPKI Not found205.163.64.0
- 205.163.80.0/20AS7029Windstream Communications LLCRPKI Not found205.163.80.0
- 205.163.96.0/20AS7029Windstream Communications LLCRPKI Not found205.163.96.0
- 205.163.112.0/20AS7029Windstream Communications LLCRPKI Not found205.163.112.0
- 205.163.134.0/24AS55139Landry's, Inc.RPKI Not found205.163.134.0
- 205.163.195.0/24AS174Cogent Communications, LLCRPKI Not found205.163.195.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.