Ricerca prefisso BGP
Inserisci un prefisso (o un singolo indirizzo). Risposta dalla nostra copia giornaliera della tabella di routing globale.
2404:b0::/32
Annunciato esattamente
- 2404:b0::/32AS4750CS LOXINFO PUBLIC COMPANY LIMITEDRPKI Valida2404:b0::
- Registro
- APNIC · Thailandia · 4 apr 2006
- Blocco assegnato
- 2404:b0:: – 2404:b0:ffff:ffff:ffff:ffff:ffff:ffff
Rotte che lo coprono
Nessuna rotta meno specifica lo copre.
Rotte più specifiche
- 2404:b0:7::/48AS4750CS LOXINFO PUBLIC COMPANY LIMITEDRPKI Valida2404:b0:7::
- 2404:b0:8::/48AS4750CS LOXINFO PUBLIC COMPANY LIMITEDRPKI Valida2404:b0:8::
- 2404:b0:c::/48AS4750CS LOXINFO PUBLIC COMPANY LIMITEDRPKI Valida2404:b0:c::
- 2404:b0:d::/48AS4750CS LOXINFO PUBLIC COMPANY LIMITEDRPKI Valida2404:b0:d::
- 2404:b0:f::/48AS7568CS LOXINFO Public Company Limited.RPKI Valida2404:b0:f::
- 2404:b0:10::/48AS7568CS LOXINFO Public Company Limited.RPKI Valida2404:b0:10::
- 2404:b0:12::/48AS4750CS LOXINFO PUBLIC COMPANY LIMITEDRPKI Valida2404:b0:12::
- 2404:b0:1001::/48AS4750CS LOXINFO PUBLIC COMPANY LIMITEDRPKI Valida2404:b0:1001::
- 2404:b0:1005::/48AS135586INTERLINK COMMUNICATION PCL.RPKI Valida2404:b0:1005::
- 2404:b0:1008::/48AS4750CS LOXINFO PUBLIC COMPANY LIMITEDRPKI Valida2404:b0:1008::
- 2404:b0:1fff::/48AS4750CS LOXINFO PUBLIC COMPANY LIMITEDRPKI Valida2404:b0:1fff::
- 2404:b0:2000::/48AS9891CS LOXINFO Public Company Limited.RPKI Valida2404:b0:2000::
- 2404:b0:2001::/48AS9891CS LOXINFO Public Company Limited.RPKI Valida2404:b0:2001::
- 2404:b0:5000::/36AS4750CS LOXINFO PUBLIC COMPANY LIMITEDRPKI Valida2404:b0:5000::
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.