BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
206.217.64.0/18
Announced exactly
- 206.217.64.0/18AS3257GTT Communications Inc.RPKI Not found206.217.64.0
- Registry
- ARIN · United States · Aug 18, 2009
- Delegated block
- 206.217.64.0 – 206.217.127.255
Covering routes
No less-specific route covers it.
More-specific routes
- 206.217.64.0/23AS20001Charter Communications IncRPKI Valid206.217.64.0
- 206.217.66.0/24AS5065Bunny CommunicationsRPKI Valid206.217.66.0
- 206.217.68.0/22AS11611Arctic Fox Networks IncRPKI Valid206.217.68.0
- 206.217.72.0/23AS20001Charter Communications IncRPKI Valid206.217.72.0
- 206.217.74.0/24AS14879PARIS ACCESSORIES INC.RPKI Not found206.217.74.0
- 206.217.75.0/24AS2914NTT America, Inc.RPKI Valid206.217.75.0
- 206.217.76.0/23AS20001Charter Communications IncRPKI Valid206.217.76.0
- 206.217.78.0/24AS395793Arisk Communications inc.RPKI Valid206.217.78.0
- 206.217.82.0/23AS20001Charter Communications IncRPKI Valid206.217.82.0
- 206.217.84.0/22AS6079RCNRPKI Valid206.217.84.0
- 206.217.88.0/23AS20001Charter Communications IncRPKI Valid206.217.88.0
- 206.217.91.0/24AS401783TOKALA COMMUNICATIONS INC.RPKI Valid206.217.91.0
- 206.217.92.0/22AS11611Arctic Fox Networks IncRPKI Valid206.217.92.0
- 206.217.96.0/24AS395793Arisk Communications inc.RPKI Valid206.217.96.0
- 206.217.98.0/23AS20001Charter Communications IncRPKI Valid206.217.98.0
- 206.217.100.0/22AS11611Arctic Fox Networks IncRPKI Valid206.217.100.0
- 206.217.104.0/21AS20001Charter Communications IncRPKI Valid206.217.104.0
- 206.217.112.0/20AS20001Charter Communications IncRPKI Valid206.217.112.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 62.103.0.0/16. 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.