Ricerca prefisso BGP
Inserisci un prefisso (o un singolo indirizzo). Risposta dalla nostra copia giornaliera della tabella di routing globale.
67.63.192.0/18
Annunciato esattamente
- 67.63.192.0/18AS209CenturyLink Communications, LLCRPKI Nessun ROA67.63.192.0
- Registro
- ARIN · Stati Uniti · 30 ago 2004
- Blocco assegnato
- 67.63.192.0 – 67.63.255.255
Rotte che lo coprono
Nessuna rotta meno specifica lo copre.
Rotte più specifiche
- 67.63.192.0/23AS19901BrightspeedRPKI Nessun ROA67.63.192.0
- 67.63.194.0/24AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.194.0
- 67.63.197.0/24AS3356Level 3 Parent, LLCRPKI Nessun ROA67.63.197.0
- 67.63.198.0/24AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.198.0
- 67.63.199.0/24AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.199.0
- 67.63.201.0/24AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.201.0
- 67.63.203.0/24AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.203.0
- 67.63.204.0/24AS398380Driscoll Children's HospitalRPKI Nessun ROA67.63.204.0
- 67.63.207.0/24AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.207.0
- 67.63.208.0/24AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.208.0
- 67.63.209.0/24AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.209.0
- 67.63.210.0/24AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.210.0
- 67.63.220.0/24AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.220.0
- 67.63.221.0/24AS19901BrightspeedRPKI Nessun ROA67.63.221.0
- 67.63.223.0/24AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.223.0
- 67.63.224.0/23AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.224.0
- 67.63.226.0/24AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.226.0
- 67.63.227.0/24AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.227.0
- 67.63.229.0/24AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.229.0
- 67.63.231.0/24AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.231.0
- 67.63.233.0/24AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.233.0
- 67.63.234.0/24AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.234.0
- 67.63.236.0/24AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.236.0
- 67.63.237.0/24AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.237.0
- 67.63.238.0/24AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.238.0
- 67.63.239.0/24AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.239.0
- 67.63.241.0/24AS11211NCIC Operator ServicesRPKI Nessun ROA67.63.241.0
- 67.63.242.0/24AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.242.0
- 67.63.245.0/24AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.245.0
- 67.63.248.0/23AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.248.0
- 67.63.250.0/24AS22561CenturyLink Communications, LLCRPKI Nessun ROA67.63.250.0
- 67.63.252.0/24AS3356Level 3 Parent, LLCRPKI Nessun ROA67.63.252.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.