Ricerca prefisso BGP

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

Esempi:

72.58.0.0/15

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

Annunciato esattamente

72.58.0.0/15AS30600MetronetRPKI Nessun ROA72.58.0.0

Registro: ARIN · Stati Uniti · 26 nov 2025
Blocco assegnato: 72.58.0.0 – 72.59.255.255

Rotte che lo coprono

Nessuna rotta meno specifica lo copre.

Rotte più specifiche

31 più specifiche da 13 AS di origine

72.58.0.0/20AS30600MetronetRPKI Valida72.58.0.0
72.58.48.0/20AS30600MetronetRPKI Valida72.58.48.0
72.58.64.0/20AS30600MetronetRPKI Valida72.58.64.0
72.58.80.0/20AS30600MetronetRPKI Valida72.58.80.0
72.58.96.0/20AS30600MetronetRPKI Valida72.58.96.0
72.58.112.0/20AS30600MetronetRPKI Valida72.58.112.0
72.58.144.0/20AS30600MetronetRPKI Valida72.58.144.0
72.58.192.0/20AS30600MetronetRPKI Valida72.58.192.0
72.58.208.0/20AS30600MetronetRPKI Valida72.58.208.0
72.58.224.0/20AS30600MetronetRPKI Valida72.58.224.0
72.58.240.0/20AS30600MetronetRPKI Valida72.58.240.0
72.59.0.0/20AS30600MetronetRPKI Valida72.59.0.0
72.59.172.0/24AS397772Vexus FiberRPKI Valida72.59.172.0
72.59.173.0/24AS397772Vexus FiberRPKI Valida72.59.173.0
72.59.176.0/20AS32898Vexus FiberRPKI Valida72.59.176.0
72.59.200.0/21AS11943Vexus FiberRPKI Valida72.59.200.0
72.59.208.0/21AS54340Vexus FiberRPKI Valida72.59.208.0
72.59.216.0/21AS33507Vexus FiberRPKI Valida72.59.216.0
72.59.224.0/22AS14765Vexus FiberRPKI Valida72.59.224.0
72.59.228.0/22AS63001Vexus FiberRPKI Valida72.59.228.0
72.59.232.0/22AS19734Vexus FiberRPKI Valida72.59.232.0
72.59.236.0/22AS397772Vexus FiberRPKI Valida72.59.236.0
72.59.240.0/22AS398149Vexus FiberRPKI Valida72.59.240.0
72.59.244.0/22AS25798Vexus FiberRPKI Valida72.59.244.0
72.59.244.0/24AS25798Vexus FiberRPKI Valida72.59.244.0
72.59.245.0/24AS25798Vexus FiberRPKI Valida72.59.245.0
72.59.248.0/22AS14791Vexus FiberRPKI Valida72.59.248.0
72.59.252.0/22AS393526Vexus FiberRPKI Valida72.59.252.0
72.59.252.0/24AS393526Vexus FiberRPKI Valida72.59.252.0
72.59.253.0/24AS393526Vexus FiberRPKI Valida72.59.253.0
72.59.254.0/24AS393526Vexus FiberRPKI Valida72.59.254.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