Ricerca prefisso BGP
Inserisci un prefisso (o un singolo indirizzo). Risposta dalla nostra copia giornaliera della tabella di routing globale.
121.64.0.0/14
Annunciato esattamente
- 121.64.0.0/14AS3786LG DACOM CorporationRPKI Nessun ROA121.64.0.0
- Registro
- APNIC · Corea del Sud · 9 giu 2006
- Blocco assegnato
- 121.64.0.0 – 121.67.255.255
Rotte che lo coprono
Nessuna rotta meno specifica lo copre.
Rotte più specifiche
- 121.65.186.0/24AS10072Shinhan BankRPKI Nessun ROA121.65.186.0
- 121.65.236.0/24AS38707TosspaymentsRPKI Nessun ROA121.65.236.0
- 121.65.245.0/24AS3786LG DACOM CorporationRPKI Nessun ROA121.65.245.0
- 121.65.247.0/24AS9856WOORI Investment @ SecuritiesRPKI Nessun ROA121.65.247.0
- 121.65.253.0/24AS38707TosspaymentsRPKI Nessun ROA121.65.253.0
- 121.67.12.0/24AS9770LG HelloVision Corp.RPKI Nessun ROA121.67.12.0
- 121.67.13.0/24AS9770LG HelloVision Corp.RPKI Nessun ROA121.67.13.0
- 121.67.14.0/24AS17586LG HelloVision Corp.RPKI Nessun ROA121.67.14.0
- 121.67.15.0/24AS17586LG HelloVision Corp.RPKI Nessun ROA121.67.15.0
- 121.67.34.0/24AS17598LG HelloVision Corp.RPKI Nessun ROA121.67.34.0
- 121.67.35.0/24AS17598LG HelloVision Corp.RPKI Nessun ROA121.67.35.0
- 121.67.39.0/24AS38707TosspaymentsRPKI Nessun ROA121.67.39.0
- 121.67.55.0/24AS38707TosspaymentsRPKI Nessun ROA121.67.55.0
- 121.67.137.0/24AS9631youngsan universityRPKI Nessun ROA121.67.137.0
- 121.67.178.0/24AS131864Firstfire Marine InsuranceRPKI Nessun ROA121.67.178.0
- 121.67.201.0/24AS23555Shinhan BankRPKI Nessun ROA121.67.201.0
- 121.67.240.0/25AS4766Korea TelecomRPKI Nessun ROA121.67.240.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.