ASN & BGP prefix lookup
Origin AS, visibility, RPKI validity, upstreams and announced prefixes from the global routing table.
1 problem 1 warning 1 passed
-
Pass
Announced as 91.201.110.0/23 by AS201776.
-
Problem
RPKI invalid for AS201776 – networks that filter will drop this route.
A ROA exists for this space but does not allow this origin or prefix length.
Fix: Fix the ROA (origin AS and max length) at your RIR, or stop announcing the route.
-
Warning
Seen by only 9% of RIPE RIS peers.
Partial visibility points to filtering, a missing IRR route object, or an RPKI problem.
| Announced prefix | 91.201.110.0/23 |
|---|---|
| Origin AS | AS201776 |
| RPKI | AS201776: invalid_length |
| Visibility (RIS peers) | 29 / 321 |
| First seen | 2016-11-24T16:00:00 |
| Covering prefixes | 91.201.108.0/22 |
| More specifics | 91.201.110.0/24, 91.201.111.0/24 |
| Registry (RIR) | RIPE NCC |
|---|---|
| Country | Russia (RU) |
| Delegated on | 2007-11-29 |
| Status | Assigned |
| Delegated range | 91.201.108.0/22 (91.201.108.0 – 91.201.111.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)