BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
204.4.0.0/14
Announced exactly
- 204.4.0.0/14AS174Cogent Communications, LLCRPKI Not found204.4.0.0
- Registry
- ARIN · United States · May 5, 1994
- Delegated block
- 204.4.0.0 – 204.7.255.255
Covering routes
No less-specific route covers it.
More-specific routes
- 204.4.64.0/24AS54407ArentFox Schiff LLPRPKI Not found204.4.64.0
- 204.4.65.0/24AS54407ArentFox Schiff LLPRPKI Not found204.4.65.0
- 204.4.66.0/24AS54407ArentFox Schiff LLPRPKI Not found204.4.66.0
- 204.4.67.0/24AS54407ArentFox Schiff LLPRPKI Not found204.4.67.0
- 204.4.69.0/24AS54407ArentFox Schiff LLPRPKI Not found204.4.69.0
- 204.4.74.0/24AS54407ArentFox Schiff LLPRPKI Not found204.4.74.0
- 204.4.75.0/24AS54407ArentFox Schiff LLPRPKI Not found204.4.75.0
- 204.4.76.0/24AS54407ArentFox Schiff LLPRPKI Not found204.4.76.0
- 204.4.130.0/24AS9084Goldman Sachs InternationalRPKI Not found204.4.130.0
- 204.4.131.0/24AS9084Goldman Sachs InternationalRPKI Not found204.4.131.0
- 204.4.142.0/24AS9084Goldman Sachs InternationalRPKI Not found204.4.142.0
- 204.4.143.0/24AS9084Goldman Sachs InternationalRPKI Not found204.4.143.0
- 204.4.170.0/24AS9084Goldman Sachs InternationalRPKI Not found204.4.170.0
- 204.4.175.0/24AS9084Goldman Sachs InternationalRPKI Not found204.4.175.0
- 204.4.178.0/24AS33598The Goldman Sachs Group, Inc.RPKI Not found204.4.178.0
- 204.4.182.0/24AS33598The Goldman Sachs Group, Inc.RPKI Not found204.4.182.0
- 204.4.185.0/24AS33598The Goldman Sachs Group, Inc.RPKI Not found204.4.185.0
- 204.4.187.0/24AS6195The Goldman Sachs Group, Inc.RPKI Not found204.4.187.0
- 204.4.235.0/24AS13335Cloudflare, Inc.RPKI Valid204.4.235.0
- 204.4.244.0/24AS31877AccelecomRPKI Not found204.4.244.0
- 204.6.91.0/24AS13372Federated InvestorsRPKI Not found204.6.91.0
- 204.6.160.0/24AS49657Transaction Network Services (UK) LTDRPKI Not found204.6.160.0
- 204.6.162.0/24AS49657Transaction Network Services (UK) LTDRPKI Not found204.6.162.0
- 204.6.164.0/23AS272591TRANSACTION NWRK SVCS DE TECNOLOGIA DO BRASIL LTDARPKI Not found204.6.164.0
- 204.6.166.0/24AS13750Transaction Network Services, Inc.RPKI Not found204.6.166.0
- 204.6.168.0/21AS13750Transaction Network Services, Inc.RPKI Not found204.6.168.0
- 204.6.174.0/24AS13750Transaction Network Services, Inc.RPKI Not found204.6.174.0
- 204.6.192.0/18AS4991Cogent Communications, LLCRPKI Not found204.6.192.0
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.