Ricerca prefisso BGP
Inserisci un prefisso (o un singolo indirizzo). Risposta dalla nostra copia giornaliera della tabella di routing globale.
204.176.0.0/14
Annunciato esattamente
- 204.176.0.0/14AS701Verizon BusinessRPKI Nessun ROA204.176.0.0
- Registro
- ARIN · Stati Uniti · 17 ott 1994
- Blocco assegnato
- 204.176.0.0 – 204.179.255.255
Rotte che lo coprono
Nessuna rotta meno specifica lo copre.
Rotte più specifiche
- 204.176.42.0/24AS15297EPLUS, Inc.RPKI Nessun ROA204.176.42.0
- 204.176.49.0/24AS10982TiVo, Inc.RPKI Nessun ROA204.176.49.0
- 204.176.96.0/24AS22574CocoNet CorporationRPKI Nessun ROA204.176.96.0
- 204.176.194.0/24AS40264Charter Communications LLCRPKI Nessun ROA204.176.194.0
- 204.176.204.0/24AS6220inContact Inc.RPKI Nessun ROA204.176.204.0
- 204.177.96.0/20AS7795LUMOS Networks, Inc.RPKI Nessun ROA204.177.96.0
- 204.177.181.0/24AS13666Verizon BusinessRPKI Nessun ROA204.177.181.0
- 204.177.184.0/21AS4208The Iserv Company, LLCRPKI Nessun ROA204.177.184.0
- 204.178.8.0/21AS6431AT&T Enterprises, LLCRPKI Nessun ROA204.178.8.0
- 204.179.65.0/24AS32806MTNSAT Holdings LLCRPKI Nessun ROA204.179.65.0
- 204.179.96.0/24AS16833Tullett Prebon Americas Corp.RPKI Valida204.179.96.0
- 204.179.168.0/24AS397056AgWorks, LLCRPKI Valida204.179.168.0
- 204.179.192.0/19AS29878Community Hospital of the Monterey PeninsulaRPKI Nessun ROA204.179.192.0
- 204.179.219.0/24AS29878Community Hospital of the Monterey PeninsulaRPKI Nessun ROA204.179.219.0
- 204.179.229.0/24AS12184Forrester ResearchRPKI Nessun ROA204.179.229.0
- 204.179.240.0/24AS10361Bloomberg, LPRPKI Valida204.179.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.