Network · data from 2026-11-12
AS197666 STENCLOUD
Registry name: STENCLOUD STENCLOUD LLC, GE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS197666, 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.
| 2a0f:1500::/48 | No ROA | RIR databaseRIPE | 636 100% |
| 2a0f:1500:1::/48 | No ROA | RIR databaseRIPE | 633 100% |
| 217.60.100.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.58.58.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 132.243.74.0/24 | Valid | RIR databaseRIPE | 655 97% |
AS-SET
AS197666's PeeringDB record names no AS-SET.
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 9 are in fix.csv.
- ROA: none2
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a0f:1500::/48 | No ROA covers it. Add a ROA for AS197666, maxLength 48. |
| ROA: none | 2a0f:1500:1::/48 | No ROA covers it. Add a ROA for AS197666, maxLength 48. |
Route objects not announced
Route objects with origin AS197666 whose prefix no peer sees AS197666 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2.27.61.0/24 | RIPE | Invalid: origin |
| 31.56.12.0/24 | RIPE | Valid |
| 31.59.209.0/24 | RIPE | Valid |
| 31.59.210.0/24 | RIPE | Valid |
| 31.59.222.0/24 | RIPE | Valid |
| 93.89.220.0/24 | RIPE | Valid |
| 2a0f:1500::/29 | 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.