Ricerca prefisso BGP
Inserisci un prefisso (o un singolo indirizzo). Risposta dalla nostra copia giornaliera della tabella di routing globale.
83.124.0.0/14
Annunciato esattamente
- 83.124.0.0/14AS13237euNetworks GmbHRPKI Valida83.124.0.0
- Registro
- RIPE NCC · Germania · 6 ott 2004
- Blocco assegnato
- 83.124.0.0 – 83.127.255.255
Rotte che lo coprono
Nessuna rotta meno specifica lo copre.
Rotte più specifiche
- 83.125.6.0/23AS60380Michael Rottmann trading as Pixel X e.K.RPKI Valida83.125.6.0
- 83.125.8.0/22AS40999dus.net GmbHRPKI Valida83.125.8.0
- 83.125.12.0/22AS31197FNH media KGRPKI Valida83.125.12.0
- 83.125.24.0/24AS200093Deutsche Telekom MMS GmbHRPKI Valida83.125.24.0
- 83.125.25.0/24AS33394JabilRPKI Valida83.125.25.0
- 83.125.36.0/24AS40371PROS, Inc.RPKI Valida83.125.36.0
- 83.125.106.0/23AS1987103U TELECOM GmbHRPKI Valida83.125.106.0
- 83.125.108.0/24AS1987103U TELECOM GmbHRPKI Valida83.125.108.0
- 83.125.118.0/23AS200093Deutsche Telekom MMS GmbHRPKI Valida83.125.118.0
- 83.126.10.0/23AS15479euNetworks GmbHRPKI Valida83.126.10.0
- 83.126.16.0/24AS40123Transaction Network Services, Inc.RPKI Valida83.126.16.0
- 83.126.17.0/24AS40123Transaction Network Services, Inc.RPKI Valida83.126.17.0
- 83.126.22.0/24AS40123Transaction Network Services, Inc.RPKI Valida83.126.22.0
- 83.126.50.0/24AS21734Trading Technologies Intl, Inc.RPKI Valida83.126.50.0
- 83.126.56.0/24AS40123Transaction Network Services, Inc.RPKI Valida83.126.56.0
- 83.126.61.0/24AS14969JANE STREETRPKI Valida83.126.61.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.