Ricerca prefisso BGP

Inserisci un prefisso (o un singolo indirizzo). Risposta dalla nostra copia giornaliera della tabella di routing globale.

Esempi:

121.78.0.0/18

La vista di un solo collector (APNIC). Una rotta filtrata prima di raggiungerlo non è elencata.

Annunciato esattamente

121.78.0.0/18AS9286KINXRPKI Nessun ROA121.78.0.0

Registro: APNIC · Corea del Sud · 20 giu 2006
Blocco assegnato: 121.78.0.0 – 121.78.255.255

Rotte che lo coprono

Nessuna rotta meno specifica lo copre.

Rotte più specifiche

21 più specifiche da 7 AS di origine

121.78.0.0/24AS9957KINXRPKI Nessun ROA121.78.0.0
121.78.1.0/24AS9957KINXRPKI Nessun ROA121.78.1.0
121.78.2.0/24AS9957KINXRPKI Nessun ROA121.78.2.0
121.78.3.0/24AS9957KINXRPKI Nessun ROA121.78.3.0
121.78.5.0/24AS9957KINXRPKI Nessun ROA121.78.5.0
121.78.21.0/24AS9286KINXRPKI Nessun ROA121.78.21.0
121.78.23.0/24AS17497Liasail Global Hongkong LimitedRPKI Nessun ROA121.78.23.0
121.78.27.0/24AS131094HYUNDAI MOTOR CORPKI Nessun ROA121.78.27.0
121.78.28.0/24AS21859Zenlayer IncRPKI Nessun ROA121.78.28.0
121.78.31.0/24AS9286KINXRPKI Nessun ROA121.78.31.0
121.78.35.0/24AS9286KINXRPKI Valida121.78.35.0
121.78.38.0/24AS9286KINXRPKI Nessun ROA121.78.38.0
121.78.40.0/24AS9286KINXRPKI Nessun ROA121.78.40.0
121.78.42.0/24AS9957KINXRPKI Nessun ROA121.78.42.0
121.78.46.0/24AS20940Akamai International B.V.RPKI Nessun ROA121.78.46.0
121.78.48.0/24AS46003CONNECTWAVERPKI Nessun ROA121.78.48.0
121.78.54.0/24AS9957KINXRPKI Nessun ROA121.78.54.0
121.78.55.0/24AS9286KINXRPKI Nessun ROA121.78.55.0
121.78.56.0/24AS9286KINXRPKI Nessun ROA121.78.56.0
121.78.59.0/24AS9286KINXRPKI Nessun ROA121.78.59.0
121.78.62.0/24AS9286KINXRPKI Nessun ROA121.78.62.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.

Domande frequenti

Correlati