BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
69.174.0.0/17
Announced exactly
- 69.174.0.0/17AS3257GTT Communications Inc.RPKI Not found69.174.0.0
- Registry
- ARIN · United States · Feb 24, 2009
- Delegated block
- 69.174.0.0 – 69.174.127.255
Covering routes
No less-specific route covers it.
More-specific routes
- 69.174.24.0/24AS3257GTT Communications Inc.RPKI Invalid69.174.24.0
- 69.174.25.0/24AS3257GTT Communications Inc.RPKI Invalid69.174.25.0
- 69.174.26.0/24AS397689C1CXRPKI Not found69.174.26.0
- 69.174.32.0/24AS3257GTT Communications Inc.RPKI Invalid69.174.32.0
- 69.174.33.0/24AS3257GTT Communications Inc.RPKI Invalid69.174.33.0
- 69.174.39.0/24AS3257GTT Communications Inc.RPKI Invalid69.174.39.0
- 69.174.47.0/24AS139625Zenlayer (Singapore) PTE. LTDRPKI Valid69.174.47.0
- 69.174.48.0/24AS54641InMotion Hosting, Inc.RPKI Not found69.174.48.0
- 69.174.51.0/24AS36473ContegixRPKI Not found69.174.51.0
- 69.174.52.0/23AS54641InMotion Hosting, Inc.RPKI Not found69.174.52.0
- 69.174.54.0/24AS3257GTT Communications Inc.RPKI Invalid69.174.54.0
- 69.174.58.0/24AS3257GTT Communications Inc.RPKI Valid69.174.58.0
- 69.174.59.0/24AS5065Bunny CommunicationsRPKI Valid69.174.59.0
- 69.174.69.0/24AS20001Charter Communications IncRPKI Valid69.174.69.0
- 69.174.72.0/24AS402063XANTIUM CONTRACTCO LLCRPKI Valid69.174.72.0
- 69.174.73.0/24AS402063XANTIUM CONTRACTCO LLCRPKI Valid69.174.73.0
- 69.174.85.0/24AS3257GTT Communications Inc.RPKI Not found69.174.85.0
- 69.174.87.0/24AS30058FDCservers.netRPKI Valid69.174.87.0
- 69.174.88.0/24AS212238Datacamp LimitedRPKI Valid69.174.88.0
- 69.174.89.0/24AS397686C1CXRPKI Not found69.174.89.0
- 69.174.90.0/24AS3257GTT Communications Inc.RPKI Not found69.174.90.0
- 69.174.94.0/24AS30058FDCservers.netRPKI Valid69.174.94.0
- 69.174.104.0/23AS20001Charter Communications IncRPKI Valid69.174.104.0
- 69.174.107.0/24AS14821Vlan24RPKI Not found69.174.107.0
- 69.174.110.0/23AS30103Zoom Video Communications, IncRPKI Valid69.174.110.0
- 69.174.114.0/23AS54641InMotion Hosting, Inc.RPKI Not found69.174.114.0
- 69.174.117.0/24AS3257GTT Communications Inc.RPKI Not found69.174.117.0
- 69.174.120.0/24AS20001Charter Communications IncRPKI Valid69.174.120.0
- 69.174.121.0/24AS3257GTT Communications Inc.RPKI Not found69.174.121.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.