BGP Prefix Lookup
Enter a prefix (or a single address). Answered from our daily copy of the global routing table.
66.172.0.0/18
Announced exactly
- 66.172.0.0/18AS4213Krypt TechnologiesRPKI Valid66.172.0.0
- Registry
- ARIN · United States · Sep 20, 2001
- Delegated block
- 66.172.0.0 – 66.172.63.255
Covering routes
No less-specific route covers it.
More-specific routes
- 66.172.2.0/24AS4213Krypt TechnologiesRPKI Valid66.172.2.0
- 66.172.3.0/24AS32544FotoKem Industries, IncRPKI Valid66.172.3.0
- 66.172.4.0/24AS4213Krypt TechnologiesRPKI Valid66.172.4.0
- 66.172.7.0/24AS4213Krypt TechnologiesRPKI Valid66.172.7.0
- 66.172.8.0/24AS4213Krypt TechnologiesRPKI Valid66.172.8.0
- 66.172.9.0/24AS4213Krypt TechnologiesRPKI Valid66.172.9.0
- 66.172.10.0/23AS4213Krypt TechnologiesRPKI Valid66.172.10.0
- 66.172.16.0/24AS4213Krypt TechnologiesRPKI Valid66.172.16.0
- 66.172.17.0/24AS4213Krypt TechnologiesRPKI Valid66.172.17.0
- 66.172.26.0/24AS4213Krypt TechnologiesRPKI Valid66.172.26.0
- 66.172.28.0/23AS4213Krypt TechnologiesRPKI Valid66.172.28.0
- 66.172.30.0/24AS4213Krypt TechnologiesRPKI Valid66.172.30.0
- 66.172.31.0/24AS4213Krypt TechnologiesRPKI Valid66.172.31.0
- 66.172.35.0/24AS4213Krypt TechnologiesRPKI Valid66.172.35.0
- 66.172.36.0/23AS4213Krypt TechnologiesRPKI Valid66.172.36.0
- 66.172.40.0/23AS46378FSX HOLDINGS, LLCRPKI Valid66.172.40.0
- 66.172.42.0/23AS4213Krypt TechnologiesRPKI Valid66.172.42.0
- 66.172.44.0/23AS4213Krypt TechnologiesRPKI Valid66.172.44.0
- 66.172.48.0/24AS4213Krypt TechnologiesRPKI Valid66.172.48.0
- 66.172.49.0/24AS4213Krypt TechnologiesRPKI Valid66.172.49.0
- 66.172.50.0/23AS4213Krypt TechnologiesRPKI Valid66.172.50.0
- 66.172.52.0/23AS4213Krypt TechnologiesRPKI Valid66.172.52.0
- 66.172.54.0/23AS4213Krypt TechnologiesRPKI Valid66.172.54.0
- 66.172.56.0/23AS4213Krypt TechnologiesRPKI Valid66.172.56.0
- 66.172.57.0/24AS4213Krypt TechnologiesRPKI Valid66.172.57.0
- 66.172.58.0/23AS4213Krypt TechnologiesRPKI Valid66.172.58.0
- 66.172.63.0/24AS4213Krypt TechnologiesRPKI Valid66.172.63.0
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 158.36.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.