Network · data from 2026-11-12
AS402447 STREAMWAYS-CORE-ASN - Streamways
Registry name: STREAMWAYS-CORE-ASN - Streamways, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS402447, 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.
| 62.108.48.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 64.40.204.0/22 | Valid | RIR databaseARIN | 673 100% |
| 64.49.0.0/22 | Valid | RIR databaseARIN | 673 100% |
| 84.19.2.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.191.114.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 89.191.120.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 91.123.64.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 66.251.129.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.136.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.137.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.138.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.144.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.150.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.156.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.160.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.161.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.162.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.163.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.165.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.166.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.167.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.172.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.173.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.174.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.175.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.176.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.177.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.178.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.179.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.181.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.183.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.184.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.185.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.186.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.187.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
| 66.251.188.0/24 | Valid | RIR databaseAFRINIC | 670 100% |
AS-SET
AS402447 isn't in PeeringDB, where networks name their AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS402447 is announced.
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.