BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
204.180.0.0/14
Announced exactly
- 204.180.0.0/14AS174Cogent Communications, LLCRPKI Not found204.180.0.0
- Registry
- ARIN · United States · Oct 18, 1994
- Delegated block
- 204.180.0.0 – 204.183.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 204.180.0.0/20AS36549WestTel Ltd.RPKI Not found204.180.0.0
- 204.180.130.0/24AS53866Omeda CommunicationsRPKI Not found204.180.130.0
- 204.180.133.0/24AS14162FEDERAL HOME LOAN BANK of PITTSBURGHRPKI Not found204.180.133.0
- 204.180.153.0/24AS174Cogent Communications, LLCRPKI Not found204.180.153.0
- 204.180.228.0/24AS200946EMC Information Systems International PUCRPKI Not found204.180.228.0
- 204.180.232.0/21AS32068UNASSIGNEDRPKI Not found204.180.232.0
- 204.181.0.0/21AS32068UNASSIGNEDRPKI Not found204.181.0.0
- 204.181.52.0/22AS27696LIBERTY NETWORKS HONDURAS, SOCIEDAD DE RESPONSABILIDAD LIMITADARPKI Not found204.181.52.0
- 204.181.152.0/21AS3364Computer Systems Design CompanyRPKI Not found204.181.152.0
- 204.181.192.0/20AS22773Cox Communications Inc.RPKI Not found204.181.192.0
- 204.181.208.0/20AS22773Cox Communications Inc.RPKI Not found204.181.208.0
- 204.181.224.0/20AS22773Cox Communications Inc.RPKI Not found204.181.224.0
- 204.181.240.0/20AS22773Cox Communications Inc.RPKI Not found204.181.240.0
- 204.182.64.0/20AS22773Cox Communications Inc.RPKI Not found204.182.64.0
- 204.182.80.0/20AS22773Cox Communications Inc.RPKI Not found204.182.80.0
- 204.182.96.0/20AS22773Cox Communications Inc.RPKI Not found204.182.96.0
- 204.182.112.0/20AS22773Cox Communications Inc.RPKI Not found204.182.112.0
- 204.182.232.0/24AS46536ViaSat, Inc.RPKI Not found204.182.232.0
- 204.182.233.0/24AS46536ViaSat, Inc.RPKI Not found204.182.233.0
- 204.182.234.0/24AS46536ViaSat, Inc.RPKI Not found204.182.234.0
- 204.182.235.0/24AS46536ViaSat, Inc.RPKI Not found204.182.235.0
- 204.182.236.0/24AS46536ViaSat, Inc.RPKI Not found204.182.236.0
- 204.182.237.0/24AS46536ViaSat, Inc.RPKI Not found204.182.237.0
- 204.182.238.0/24AS46536ViaSat, Inc.RPKI Not found204.182.238.0
- 204.182.239.0/24AS46536ViaSat, Inc.RPKI Not found204.182.239.0
- 204.183.0.0/20AS22773Cox Communications Inc.RPKI Not found204.183.0.0
- 204.183.16.0/20AS22773Cox Communications Inc.RPKI Not found204.183.16.0
- 204.183.32.0/20AS22773Cox Communications Inc.RPKI Not found204.183.32.0
- 204.183.48.0/20AS22773Cox Communications Inc.RPKI Not found204.183.48.0
- 204.183.80.0/20AS174Cogent Communications, LLCRPKI Not found204.183.80.0
- 204.183.80.0/24AS174Cogent Communications, LLCRPKI Not found204.183.80.0
- 204.183.81.0/24AS174Cogent Communications, LLCRPKI Not found204.183.81.0
- 204.183.82.0/24AS174Cogent Communications, LLCRPKI Not found204.183.82.0
- 204.183.83.0/24AS174Cogent Communications, LLCRPKI Not found204.183.83.0
- 204.183.84.0/24AS174Cogent Communications, LLCRPKI Not found204.183.84.0
- 204.183.85.0/24AS174Cogent Communications, LLCRPKI Not found204.183.85.0
- 204.183.86.0/24AS174Cogent Communications, LLCRPKI Not found204.183.86.0
- 204.183.87.0/24AS174Cogent Communications, LLCRPKI Not found204.183.87.0
- 204.183.88.0/24AS174Cogent Communications, LLCRPKI Not found204.183.88.0
- 204.183.89.0/24AS174Cogent Communications, LLCRPKI Not found204.183.89.0
- 204.183.90.0/24AS174Cogent Communications, LLCRPKI Not found204.183.90.0
- 204.183.91.0/24AS174Cogent Communications, LLCRPKI Not found204.183.91.0
- 204.183.92.0/24AS174Cogent Communications, LLCRPKI Not found204.183.92.0
- 204.183.93.0/24AS174Cogent Communications, LLCRPKI Not found204.183.93.0
- 204.183.94.0/24AS174Cogent Communications, LLCRPKI Not found204.183.94.0
- 204.183.95.0/24AS174Cogent Communications, LLCRPKI Not found204.183.95.0
- 204.183.220.0/22AS174Cogent Communications, LLCRPKI Not found204.183.220.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.