Ricerca prefisso BGP
Inserisci un prefisso (o un singolo indirizzo). Risposta dalla nostra copia giornaliera della tabella di routing globale.
2803:e600::/32
Annunciato esattamente
- 2803:e600::/32AS18809Cable OndaRPKI Valida2803:e600::
- Registro
- LACNIC · Panama · 16 ago 2012
- Blocco assegnato
- 2803:e600:: – 2803:e600:ffff:ffff:ffff:ffff:ffff:ffff
Rotte che lo coprono
Nessuna rotta meno specifica lo copre.
Rotte più specifiche
- 2803:e600::/33AS18809Cable OndaRPKI Valida2803:e600::
- 2803:e600::/48AS18809Cable OndaRPKI Valida2803:e600::
- 2803:e600:2::/48AS18809Cable OndaRPKI Valida2803:e600:2::
- 2803:e600:8000::/33AS18809Cable OndaRPKI Valida2803:e600:8000::
- 2803:e600:9999::/48AS18809Cable OndaRPKI Valida2803:e600:9999::
- 2803:e600:aaaa::/48AS18809Cable OndaRPKI Valida2803:e600:aaaa::
- 2803:e600:b000::/48AS18809Cable OndaRPKI Valida2803:e600:b000::
- 2803:e600:c1ff::/48AS18809Cable OndaRPKI Valida2803:e600:c1ff::
- 2803:e600:cac3::/48AS18809Cable OndaRPKI Valida2803:e600:cac3::
- 2803:e600:cace::/48AS18809Cable OndaRPKI Valida2803:e600:cace::
- 2803:e600:facb::/48AS18809Cable OndaRPKI Valida2803:e600:facb::
- 2803:e600:facc::/48AS18809Cable OndaRPKI Valida2803:e600:facc::
- 2803:e600:facd::/48AS18809Cable OndaRPKI Valida2803:e600:facd::
- 2803:e600:face::/48AS18809Cable OndaRPKI Valida2803:e600:face::
- 2803:e600:ff00::/48AS18809Cable OndaRPKI Valida2803:e600:ff00::
- 2803:e600:ffaa::/48AS18809Cable OndaRPKI Valida2803:e600:ffaa::
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.