BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
173.205.0.0/17
Announced exactly
- 173.205.0.0/17AS3257GTT Communications Inc.RPKI Not found173.205.0.0
- Registry
- ARIN · United States · Oct 15, 2009
- Delegated block
- 173.205.0.0 – 173.205.127.255
Covering routes
No less-specific route covers it.
More-specific routes
- 173.205.1.0/24AS3257GTT Communications Inc.RPKI Invalid173.205.1.0
- 173.205.5.0/24AS3257GTT Communications Inc.RPKI Invalid173.205.5.0
- 173.205.6.0/23AS20001Charter Communications IncRPKI Valid173.205.6.0
- 173.205.8.0/23AS20001Charter Communications IncRPKI Valid173.205.8.0
- 173.205.14.0/23AS20001Charter Communications IncRPKI Valid173.205.14.0
- 173.205.18.0/23AS20001Charter Communications IncRPKI Valid173.205.18.0
- 173.205.21.0/24AS3257GTT Communications Inc.RPKI Invalid173.205.21.0
- 173.205.22.0/23AS20001Charter Communications IncRPKI Valid173.205.22.0
- 173.205.26.0/24AS55470Cyfuture India Pvt. Ltd.RPKI Valid173.205.26.0
- 173.205.28.0/22AS11611Arctic Fox Networks IncRPKI Valid173.205.28.0
- 173.205.34.0/24AS3257GTT Communications Inc.RPKI Invalid173.205.34.0
- 173.205.68.0/24AS55470Cyfuture India Pvt. Ltd.RPKI Valid173.205.68.0
- 173.205.69.0/24AS20940Akamai International B.V.RPKI Not found173.205.69.0
- 173.205.70.0/23AS20001Charter Communications IncRPKI Valid173.205.70.0
- 173.205.73.0/24AS30058FDCservers.netRPKI Valid173.205.73.0
- 173.205.74.0/23AS20001Charter Communications IncRPKI Valid173.205.74.0
- 173.205.76.0/23AS20940Akamai International B.V.RPKI Not found173.205.76.0
- 173.205.78.0/23AS20001Charter Communications IncRPKI Valid173.205.78.0
- 173.205.82.0/23AS207083HOSTSLIM OURPKI Not found173.205.82.0
- 173.205.86.0/23AS35916MULTACOM CORPORATIONRPKI Not found173.205.86.0
- 173.205.89.0/24AS18779EGIHostingRPKI Not found173.205.89.0
- 173.205.98.0/23AS20001Charter Communications IncRPKI Valid173.205.98.0
- 173.205.112.0/24AS55470Cyfuture India Pvt. Ltd.RPKI Valid173.205.112.0
- 173.205.114.0/23AS20001Charter Communications IncRPKI Valid173.205.114.0
- 173.205.120.0/22AS11611Arctic Fox Networks IncRPKI Valid173.205.120.0
- 173.205.124.0/23AS54641InMotion Hosting, Inc.RPKI Not found173.205.124.0
- 173.205.126.0/24AS54641InMotion Hosting, Inc.RPKI Not found173.205.126.0
- 173.205.127.0/24AS54641InMotion Hosting, Inc.RPKI Not found173.205.127.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.