Announced routes
Every prefix a peer of the route collectors sees with origin AS59956, 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.
| 94.131.201.254/32 | Invalid: maxLength | Nonecovered by 94.131.201.0/24 | 2 0%low visibility |
| 192.162.198.126/32 | Invalid: maxLength | Nonecovered by 192.162.198.0/24 | 2 0%low visibility |
| 5.53.116.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.235.186.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.145.227.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.131.200.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 94.131.201.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 192.162.198.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.39.240.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.191.200.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 195.191.201.0/24 | Valid | RIR databaseRIPE | 4 1%low visibility |
AS-SET
PeeringDB's irr_as_set for AS59956: RIPE::AS-S3W. 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 (AS59956 isn't in the set, or no route object for AS59956 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 | AS59956 in it | Not covered | |
|---|---|---|---|---|---|---|
| RIPE::AS-S3W | In no IRR database read today. | |||||
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 8 are in fix.csv.
- ROA: maxLength2
- Route object: none2
- AS-SET: not found1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 94.131.201.254/32 | ROA 94.131.201.0/24 AS59956 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 94.131.201.254/32. |
| Route object: none | 94.131.201.254/32 | No route object for it. A route object for 94.131.201.0/24 with origin AS59956 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS59956 in the RIR database for the space. |
| ROA: maxLength | 192.162.198.126/32 | ROA 192.162.198.0/24 AS59956 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 192.162.198.126/32. |
| Route object: none | 192.162.198.126/32 | No route object for it. A route object for 192.162.198.0/24 with origin AS59956 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS59956 in the RIR database for the space. |
| AS-SET: not found | RIPE::AS-S3W | PeeringDB names RIPE::AS-S3W; no IRR database read has it. |
Route objects not announced
Route objects with origin AS59956 whose prefix no peer sees AS59956 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 94.131.202.0/24 | RIPE | Valid |
| 94.131.203.0/24 | RIPE | Valid |
| 195.191.200.0/23 | RIPE | 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.