Ricerca prefisso BGP
Inserisci un prefisso (o un singolo indirizzo). Risposta dalla nostra copia giornaliera della tabella di routing globale.
1.11.0.0/16
Annunciato esattamente
- 1.11.0.0/16AS38091LG HelloVision Corp.RPKI Nessun ROA1.11.0.0
- Registro
- APNIC · Corea del Sud · 16 giu 2010
- Blocco assegnato
- 1.11.0.0 – 1.11.255.255
Rotte che lo coprono
Nessuna rotta meno specifica lo copre.
Rotte più specifiche
- 1.11.0.0/21AS18313LG HelloVision Corp.RPKI Nessun ROA1.11.0.0
- 1.11.8.0/21AS18318LG HelloVision Corp.RPKI Nessun ROA1.11.8.0
- 1.11.16.0/22AS18318LG HelloVision Corp.RPKI Nessun ROA1.11.16.0
- 1.11.20.0/22AS38091LG HelloVision Corp.RPKI Nessun ROA1.11.20.0
- 1.11.24.0/21AS18313LG HelloVision Corp.RPKI Nessun ROA1.11.24.0
- 1.11.33.0/24AS38120LG HelloVision Corp.RPKI Nessun ROA1.11.33.0
- 1.11.34.0/24AS38120LG HelloVision Corp.RPKI Nessun ROA1.11.34.0
- 1.11.35.0/24AS38120LG HelloVision Corp.RPKI Nessun ROA1.11.35.0
- 1.11.36.0/24AS38120LG HelloVision Corp.RPKI Nessun ROA1.11.36.0
- 1.11.37.0/24AS38120LG HelloVision Corp.RPKI Nessun ROA1.11.37.0
- 1.11.38.0/24AS38120LG HelloVision Corp.RPKI Nessun ROA1.11.38.0
- 1.11.39.0/24AS38120LG HelloVision Corp.RPKI Nessun ROA1.11.39.0
- 1.11.40.0/21AS18313LG HelloVision Corp.RPKI Nessun ROA1.11.40.0
- 1.11.48.0/24AS38120LG HelloVision Corp.RPKI Nessun ROA1.11.48.0
- 1.11.49.0/24AS38120LG HelloVision Corp.RPKI Nessun ROA1.11.49.0
- 1.11.50.0/24AS38120LG HelloVision Corp.RPKI Nessun ROA1.11.50.0
- 1.11.51.0/24AS38120LG HelloVision Corp.RPKI Nessun ROA1.11.51.0
- 1.11.52.0/24AS38120LG HelloVision Corp.RPKI Nessun ROA1.11.52.0
- 1.11.53.0/24AS38120LG HelloVision Corp.RPKI Nessun ROA1.11.53.0
- 1.11.54.0/24AS38120LG HelloVision Corp.RPKI Nessun ROA1.11.54.0
- 1.11.55.0/24AS38120LG HelloVision Corp.RPKI Nessun ROA1.11.55.0
- 1.11.56.0/21AS18313LG HelloVision Corp.RPKI Nessun ROA1.11.56.0
- 1.11.64.0/21AS38091LG HelloVision Corp.RPKI Nessun ROA1.11.64.0
- 1.11.71.0/24AS38091LG HelloVision Corp.RPKI Nessun ROA1.11.71.0
- 1.11.72.0/21AS38091LG HelloVision Corp.RPKI Nessun ROA1.11.72.0
- 1.11.80.0/21AS38091LG HelloVision Corp.RPKI Nessun ROA1.11.80.0
- 1.11.82.0/24AS38091LG HelloVision Corp.RPKI Nessun ROA1.11.82.0
- 1.11.88.0/21AS38091LG HelloVision Corp.RPKI Nessun ROA1.11.88.0
- 1.11.92.0/23AS45996DAOU TECHNOLOGYRPKI Nessun ROA1.11.92.0
- 1.11.94.0/24AS45996DAOU TECHNOLOGYRPKI Nessun ROA1.11.94.0
- 1.11.96.0/22AS38669LG HelloVision Corp.RPKI Nessun ROA1.11.96.0
- 1.11.100.0/22AS38669LG HelloVision Corp.RPKI Nessun ROA1.11.100.0
- 1.11.104.0/22AS38669LG HelloVision Corp.RPKI Nessun ROA1.11.104.0
- 1.11.108.0/22AS38669LG HelloVision Corp.RPKI Nessun ROA1.11.108.0
- 1.11.112.0/22AS38669LG HelloVision Corp.RPKI Nessun ROA1.11.112.0
- 1.11.116.0/22AS38669LG HelloVision Corp.RPKI Nessun ROA1.11.116.0
- 1.11.120.0/22AS38669LG HelloVision Corp.RPKI Nessun ROA1.11.120.0
- 1.11.124.0/22AS38669LG HelloVision Corp.RPKI Nessun ROA1.11.124.0
- 1.11.128.0/17AS17839LG HelloVision Corp.RPKI Nessun ROA1.11.128.0
- 1.11.230.0/24AS17839LG HelloVision Corp.RPKI Nessun ROA1.11.230.0
- 1.11.231.0/24AS17839LG HelloVision Corp.RPKI Nessun ROA1.11.231.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.