Ricerca prefisso BGP
Inserisci un prefisso (o un singolo indirizzo). Risposta dalla nostra copia giornaliera della tabella di routing globale.
210.108.0.0/16
Annunciato esattamente
- 210.108.0.0/16AS3786LG DACOM CorporationRPKI Nessun ROA210.108.0.0
- Registro
- APNIC · Corea del Sud · 30 apr 1997
- Blocco assegnato
- 210.108.0.0 – 210.108.255.255
Rotte che lo coprono
Nessuna rotta meno specifica lo copre.
Rotte più specifiche
- 210.108.1.0/24AS9638National Agricultural Cooperative federationRPKI Nessun ROA210.108.1.0
- 210.108.26.0/24AS9526KOSCOMRPKI Nessun ROA210.108.26.0
- 210.108.27.0/24AS9526KOSCOMRPKI Nessun ROA210.108.27.0
- 210.108.46.0/24AS10183Korea Culture Information Service AgencyRPKI Nessun ROA210.108.46.0
- 210.108.50.0/24AS18305POSCO DXRPKI Nessun ROA210.108.50.0
- 210.108.60.0/24AS10183Korea Culture Information Service AgencyRPKI Nessun ROA210.108.60.0
- 210.108.75.0/24AS38661abcleRPKI Nessun ROA210.108.75.0
- 210.108.78.0/24AS38661abcleRPKI Nessun ROA210.108.78.0
- 210.108.80.0/22AS9852Samil PwCRPKI Nessun ROA210.108.80.0
- 210.108.84.0/24AS9852Samil PwCRPKI Nessun ROA210.108.84.0
- 210.108.96.0/24AS9767DB Inc.RPKI Nessun ROA210.108.96.0
- 210.108.97.0/24AS9767DB Inc.RPKI Nessun ROA210.108.97.0
- 210.108.137.0/24AS9526KOSCOMRPKI Nessun ROA210.108.137.0
- 210.108.173.0/24AS9776KOOKMIN BANKRPKI Nessun ROA210.108.173.0
- 210.108.199.0/24AS18305POSCO DXRPKI Nessun ROA210.108.199.0
- 210.108.233.0/24AS152288KOSPORPKI Nessun ROA210.108.233.0
- 210.108.234.0/24AS9767DB Inc.RPKI Nessun ROA210.108.234.0
- 210.108.235.0/24AS9767DB Inc.RPKI Nessun ROA210.108.235.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.