Ricerca prefisso BGP
Inserisci un prefisso (o un singolo indirizzo). Risposta dalla nostra copia giornaliera della tabella di routing globale.
66.166.0.0/15
Annunciato esattamente
- 66.166.0.0/15AS3257GTT Communications Inc.RPKI Nessun ROA66.166.0.0
- Registro
- ARIN · Stati Uniti · 10 set 2001
- Blocco assegnato
- 66.166.0.0 – 66.167.255.255
Rotte che lo coprono
Nessuna rotta meno specifica lo copre.
Rotte più specifiche
- 66.166.0.0/20AS22773Cox Communications Inc.RPKI Valida66.166.0.0
- 66.166.16.0/20AS22773Cox Communications Inc.RPKI Valida66.166.16.0
- 66.166.32.0/20AS22773Cox Communications Inc.RPKI Valida66.166.32.0
- 66.166.48.0/20AS22773Cox Communications Inc.RPKI Valida66.166.48.0
- 66.166.64.0/20AS22773Cox Communications Inc.RPKI Valida66.166.64.0
- 66.166.80.0/20AS22773Cox Communications Inc.RPKI Valida66.166.80.0
- 66.166.96.0/20AS22773Cox Communications Inc.RPKI Valida66.166.96.0
- 66.166.112.0/20AS22773Cox Communications Inc.RPKI Valida66.166.112.0
- 66.166.128.0/20AS22773Cox Communications Inc.RPKI Valida66.166.128.0
- 66.166.144.0/20AS22773Cox Communications Inc.RPKI Valida66.166.144.0
- 66.166.160.0/22AS22773Cox Communications Inc.RPKI Valida66.166.160.0
- 66.166.164.0/22AS22773Cox Communications Inc.RPKI Valida66.166.164.0
- 66.166.168.0/22AS22773Cox Communications Inc.RPKI Valida66.166.168.0
- 66.166.172.0/22AS22773Cox Communications Inc.RPKI Valida66.166.172.0
- 66.166.176.0/22AS22773Cox Communications Inc.RPKI Valida66.166.176.0
- 66.166.180.0/22AS22773Cox Communications Inc.RPKI Valida66.166.180.0
- 66.166.184.0/22AS22773Cox Communications Inc.RPKI Valida66.166.184.0
- 66.166.188.0/22AS22773Cox Communications Inc.RPKI Valida66.166.188.0
- 66.166.192.0/22AS22773Cox Communications Inc.RPKI Valida66.166.192.0
- 66.166.196.0/22AS22773Cox Communications Inc.RPKI Valida66.166.196.0
- 66.166.200.0/21AS22773Cox Communications Inc.RPKI Valida66.166.200.0
- 66.166.208.0/20AS22773Cox Communications Inc.RPKI Valida66.166.208.0
- 66.166.224.0/20AS22773Cox Communications Inc.RPKI Valida66.166.224.0
- 66.166.240.0/20AS22773Cox Communications Inc.RPKI Valida66.166.240.0
- 66.167.0.0/23AS401783TOKALA COMMUNICATIONS INC.RPKI Valida66.167.0.0
- 66.167.2.0/23AS9304HGC Global Communications LimitedRPKI Valida66.167.2.0
- 66.167.4.0/23AS402363KEYSTONERPKI Valida66.167.4.0
- 66.167.6.0/23AS3257GTT Communications Inc.RPKI Non valida66.167.6.0
- 66.167.8.0/22AS7459Grande Communications Networks, LLCRPKI Valida66.167.8.0
- 66.167.12.0/23AS20001Charter Communications IncRPKI Valida66.167.12.0
- 66.167.15.0/24AS3257GTT Communications Inc.RPKI Valida66.167.15.0
- 66.167.16.0/20AS11611Arctic Fox Networks IncRPKI Valida66.167.16.0
- 66.167.32.0/20AS22773Cox Communications Inc.RPKI Valida66.167.32.0
- 66.167.48.0/20AS22773Cox Communications Inc.RPKI Valida66.167.48.0
- 66.167.64.0/23AS30058FDCservers.netRPKI Valida66.167.64.0
- 66.167.66.0/23AS55470Cyfuture India Pvt. Ltd.RPKI Valida66.167.66.0
- 66.167.68.0/23AS212238Datacamp LimitedRPKI Valida66.167.68.0
- 66.167.70.0/23AS59711HZ Hosting LtdRPKI Valida66.167.70.0
- 66.167.72.0/23AS59711HZ Hosting LtdRPKI Valida66.167.72.0
- 66.167.74.0/23AS30058FDCservers.netRPKI Valida66.167.74.0
- 66.167.76.0/23AS6762TELECOM ITALIA SPARKLE S.p.A.RPKI Valida66.167.76.0
- 66.167.78.0/23AS30058FDCservers.netRPKI Valida66.167.78.0
- 66.167.80.0/23AS3257GTT Communications Inc.RPKI Non valida66.167.80.0
- 66.167.82.0/23AS9304HGC Global Communications LimitedRPKI Valida66.167.82.0
- 66.167.84.0/23AS401783TOKALA COMMUNICATIONS INC.RPKI Valida66.167.84.0
- 66.167.86.0/23AS401783TOKALA COMMUNICATIONS INC.RPKI Valida66.167.86.0
- 66.167.90.0/24AS3257GTT Communications Inc.RPKI Valida66.167.90.0
- 66.167.92.0/22AS11427Charter Communications IncRPKI Valida66.167.92.0
- 66.167.96.0/20AS22773Cox Communications Inc.RPKI Valida66.167.96.0
- 66.167.112.0/20AS22773Cox Communications Inc.RPKI Valida66.167.112.0
- 66.167.128.0/21AS11427Charter Communications IncRPKI Valida66.167.128.0
- 66.167.136.0/22AS401783TOKALA COMMUNICATIONS INC.RPKI Valida66.167.136.0
- 66.167.140.0/23AS402363KEYSTONERPKI Valida66.167.140.0
- 66.167.142.0/23AS402363KEYSTONERPKI Valida66.167.142.0
- 66.167.144.0/24AS21859Zenlayer IncRPKI Valida66.167.144.0
- 66.167.147.0/24AS3257GTT Communications Inc.RPKI Valida66.167.147.0
- 66.167.151.0/24AS21859Zenlayer IncRPKI Valida66.167.151.0
- 66.167.164.0/24AS26669Headland CommunicationsRPKI Nessun ROA66.167.164.0
- 66.167.166.0/24AS3257GTT Communications Inc.RPKI Valida66.167.166.0
- 66.167.169.0/24AS3257GTT Communications Inc.RPKI Valida66.167.169.0
- 66.167.172.0/22AS7459Grande Communications Networks, LLCRPKI Valida66.167.172.0
- 66.167.201.0/24AS21859Zenlayer IncRPKI Valida66.167.201.0
- 66.167.202.0/23AS3257GTT Communications Inc.RPKI Non valida66.167.202.0
- 66.167.204.0/24AS21859Zenlayer IncRPKI Valida66.167.204.0
- 66.167.206.0/23AS3257GTT Communications Inc.RPKI Valida66.167.206.0
Questo testo non è ancora disponibile in italiano. Viene mostrato in inglese finché non sarà pubblicata una traduzione.
On the internet, routes are announced as prefixes: an autonomous system tells its neighbours via BGP that it can deliver traffic for, say, 144.122.0.0/16 (Middle East Technical University, AS1967). 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.
Domande frequenti
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.
Correlati
- Validatore di rotte RPKIL'AS di origine di una rotta è autorizzato da un ROA?
- Ricerca ASNTitolare, registro e tutti i prefissi annunciati da un AS.
- Ricerca IPASN, provider, route, DNS inverso e posizione di qualsiasi indirizzo.
- Calcolatore CIDRRete, broadcast, maschere e numero di host per qualsiasi prefisso.