Announced routes
Every prefix a peer of the route collectors sees with origin AS5577, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 195.28.160.0/23 | No ROA | Other IRR onlyRADB | 673 100% |
| 83.243.8.0/21 | No ROA | RIR databaseRADB, RIPE | 673 100% |
| 195.24.72.0/21 | No ROA | RIR databaseRADB, RIPE | 673 100% |
| 195.26.4.0/23 | No ROA | RIR databaseRADB, RIPE | 673 100% |
| 2001:67c:15a3::/48 | No ROA | RIR databaseRADB, RIPE | 635 100% |
| 2a01:608::/32 | No ROA | RIR databaseRADB, RIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS5577: AS-ROOT. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS5577 isn't in the set, or no route object for AS5577 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS5577 in it | Not covered |
|---|---|---|---|---|---|
| AS-ROOT | RADB | 17 | 1 | Yes | 0 |
| RIPE (also)lists itself further down2 member sets in no database: AS-BITNAMES, AS-HELIACAL | 70 | 23 | Yes | 0 |
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 19 are in fix.csv.
- ROA: none6
- Route object: RIR1
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 195.28.160.0/23 | No ROA covers it. Add a ROA for AS5577, maxLength 23. |
| Route object: RIR | 195.28.160.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 83.243.8.0/21 | No ROA covers it. Add a ROA for AS5577, maxLength 21. |
| ROA: none | 195.24.72.0/21 | No ROA covers it. Add a ROA for AS5577, maxLength 21. |
| ROA: none | 195.26.4.0/23 | No ROA covers it. Add a ROA for AS5577, maxLength 23. |
| ROA: none | 2001:67c:15a3::/48 | No ROA covers it. Add a ROA for AS5577, maxLength 48. |
| ROA: none | 2a01:608::/32 | No ROA covers it. Add a ROA for AS5577, maxLength 32. |
Route objects not announced
Route objects with origin AS5577 whose prefix no peer sees AS5577 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 83.243.8.0/24 | RADB | No ROA |
| 83.243.9.0/24 | RADB | No ROA |
| 83.243.10.0/24 | RADB | No ROA |
| 83.243.11.0/24 | RADB | No ROA |
| 83.243.12.0/24 | RADB | No ROA |
| 83.243.13.0/24 | RADB | No ROA |
| 83.243.14.0/24 | RADB | No ROA |
| 83.243.15.0/24 | RADB | No ROA |
| 185.5.45.0/24 | RIPE | Valid |
| 194.68.32.0/24 | RADB | No ROA |
| 198.175.15.0/24 | RADB | No ROA |
| 2a0e:1b40::/29 | RADB | No ROA |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.