Ricerca prefisso BGP
Inserisci un prefisso (o un singolo indirizzo). Risposta dalla nostra copia giornaliera della tabella di routing globale.
67.220.64.0/19
Annunciato esattamente
- 67.220.64.0/19AS33333objx.net, LLCRPKI Valida67.220.64.0
- Registro
- ARIN · Stati Uniti · 8 gen 2008
- Blocco assegnato
- 67.220.64.0 – 67.220.95.255
Rotte che lo coprono
Nessuna rotta meno specifica lo copre.
Rotte più specifiche
- 67.220.64.0/24AS26042FiberState, LLCRPKI Valida67.220.64.0
- 67.220.65.0/24AS33333objx.net, LLCRPKI Valida67.220.65.0
- 67.220.66.0/24AS63023GTHostRPKI Valida67.220.66.0
- 67.220.67.0/24AS63023GTHostRPKI Valida67.220.67.0
- 67.220.69.0/24AS33333objx.net, LLCRPKI Valida67.220.69.0
- 67.220.70.0/24AS63023GTHostRPKI Valida67.220.70.0
- 67.220.71.0/24AS63023GTHostRPKI Valida67.220.71.0
- 67.220.72.0/24AS63023GTHostRPKI Valida67.220.72.0
- 67.220.73.0/24AS63023GTHostRPKI Valida67.220.73.0
- 67.220.74.0/24AS63023GTHostRPKI Valida67.220.74.0
- 67.220.75.0/24AS33333objx.net, LLCRPKI Valida67.220.75.0
- 67.220.79.0/24AS33333objx.net, LLCRPKI Valida67.220.79.0
- 67.220.80.0/24AS63023GTHostRPKI Valida67.220.80.0
- 67.220.81.0/24AS33333objx.net, LLCRPKI Valida67.220.81.0
- 67.220.82.0/24AS63023GTHostRPKI Valida67.220.82.0
- 67.220.85.0/24AS63023GTHostRPKI Valida67.220.85.0
- 67.220.86.0/24AS203380DA International Group Ltd.RPKI Valida67.220.86.0
- 67.220.87.0/24AS63025NOHAVPS LLCRPKI Valida67.220.87.0
- 67.220.88.0/24AS26042FiberState, LLCRPKI Valida67.220.88.0
- 67.220.89.0/24AS54702QuickMeg IncRPKI Valida67.220.89.0
- 67.220.90.0/24AS40065CNSERVERS LLCRPKI Valida67.220.90.0
- 67.220.91.0/24AS40065CNSERVERS LLCRPKI Valida67.220.91.0
- 67.220.92.0/24AS40065CNSERVERS LLCRPKI Valida67.220.92.0
- 67.220.93.0/24AS40065CNSERVERS LLCRPKI Valida67.220.93.0
- 67.220.94.0/24AS62563GLOBALTELEHOST Corp.RPKI Valida67.220.94.0
- 67.220.95.0/24AS63023GTHostRPKI Valida67.220.95.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.