BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
64.93.0.0/18
Announced exactly
- 64.93.0.0/18AS3257GTT Communications Inc.RPKI Not found64.93.0.0
- Registry
- ARIN · United States · May 26, 2000
- Delegated block
- 64.93.0.0 – 64.93.63.255
Covering routes
No less-specific route covers it.
More-specific routes
- 64.93.10.0/24AS3257GTT Communications Inc.RPKI Valid64.93.10.0
- 64.93.11.0/24AS6079RCNRPKI Valid64.93.11.0
- 64.93.12.0/23AS21743Atlas Networks CorporationRPKI Valid64.93.12.0
- 64.93.14.0/23AS5650Frontier Communications of America, Inc.RPKI Valid64.93.14.0
- 64.93.14.0/24AS7029Windstream Communications LLCRPKI Valid64.93.14.0
- 64.93.15.0/24AS7029Windstream Communications LLCRPKI Valid64.93.15.0
- 64.93.16.0/24AS3257GTT Communications Inc.RPKI Valid64.93.16.0
- 64.93.17.0/24AS152726Dream EngineeringRPKI Valid64.93.17.0
- 64.93.18.0/24AS7361DataZone Networks LLCRPKI Valid64.93.18.0
- 64.93.21.0/24AS393446AlphaCore Network LLCRPKI Valid64.93.21.0
- 64.93.24.0/24AS2914NTT America, Inc.RPKI Valid64.93.24.0
- 64.93.25.0/24AS2914NTT America, Inc.RPKI Valid64.93.25.0
- 64.93.26.0/24AS2914NTT America, Inc.RPKI Valid64.93.26.0
- 64.93.27.0/24AS2914NTT America, Inc.RPKI Valid64.93.27.0
- 64.93.28.0/24AS2914NTT America, Inc.RPKI Valid64.93.28.0
- 64.93.29.0/24AS2914NTT America, Inc.RPKI Valid64.93.29.0
- 64.93.30.0/24AS2914NTT America, Inc.RPKI Valid64.93.30.0
- 64.93.31.0/24AS2914NTT America, Inc.RPKI Valid64.93.31.0
- 64.93.32.0/22AS397423Tier.Net Technologies LLCRPKI Valid64.93.32.0
- 64.93.36.0/22AS20115Charter Communications LLCRPKI Valid64.93.36.0
- 64.93.40.0/21AS20115Charter Communications LLCRPKI Valid64.93.40.0
- 64.93.48.0/22AS25369Hydra Communications LtdRPKI Valid64.93.48.0
- 64.93.52.0/22AS3257GTT Communications Inc.RPKI Valid64.93.52.0
- 64.93.56.0/22AS3257GTT Communications Inc.RPKI Valid64.93.56.0
- 64.93.60.0/22AS25369Hydra Communications LtdRPKI Valid64.93.60.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.