ASN & BGP prefix lookup
Origin AS, visibility, RPKI validity, upstreams and announced prefixes from the global routing table.
1 warning 2 passed
-
Pass
Announced as 192.172.0.0/19 by AS721.
-
Warning
No ROA covers this route (RPKI not found).
Without a ROA, networks cannot tell your route from a hijack.
Fix: Create a ROA for this prefix and origin at your RIR portal – it takes a few minutes.
-
Pass
Seen by 100% of RIPE RIS peers.
| Announced prefix | 192.172.0.0/19 |
|---|---|
| Origin AS | AS721 |
| RPKI | AS721: unknown |
| Visibility (RIS peers) | 319 / 319 |
| First seen | 2000-08-18T08:00:00 |
| More specifics | 192.172.24.0/23, 192.172.2.0/24, 192.172.12.0/24, 192.172.13.0/24, 192.172.18.0/24, 192.172.27.0/24, 192.172.28.0/24, 192.172.29.0/24, 192.172.30.0/24 |
| Registry (RIR) | ARIN |
|---|---|
| Country | United States (US) |
| Delegated on | 1992-05-29 |
| Status | Allocated |
| Delegated range | 192.172.0.0/24 (192.172.0.0 – 192.172.0.255) |
Source: RIR delegation data, updated daily. The country is where the range was registered, not necessarily where it is used.
Open in RPKI / ROA validator · PeeringDB lookup
Source: RIPEstat (RIPE NCC RIS)