Network · data from 2026-11-12
AS54502 Data Stream
Registry name: DATA-STREAM - Data Stream, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS54502, 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.
| 38.209.80.0/20 | No ROA | Other IRR onlyRADB | 670 100% |
| 38.209.96.0/20 | No ROA | Other IRR onlyRADB | 670 100% |
| 23.247.220.0/22 | Valid | RIR databaseARIN | 670 100% |
| 172.110.192.0/21 | Valid | RIR databaseARIN | 670 100% |
| 2606:7640:4400::/48 | Valid | RIR databaseARIN | 635 100% |
| 2606:7640:4800::/48 | Valid | RIR databaseARIN | 635 100% |
| 2606:7640::/32 | Valid | RIR databaseARIN | 632 99% |
AS-SET
AS54502'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 8 are in fix.csv.
- ROA: none2
- Route object: RIR2
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 38.209.80.0/20 | No ROA covers it. Add a ROA for AS54502, maxLength 20. |
| Route object: RIR | 38.209.80.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.209.96.0/20 | No ROA covers it. Add a ROA for AS54502, maxLength 20. |
| Route object: RIR | 38.209.96.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS54502 whose prefix no peer sees AS54502 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 184.104.234.0/24 | ARIN | Valid |
| 184.105.9.0/24 | ARIN | Valid |
| 184.105.33.0/24 | ARIN | Valid |
| 2001:470:461::/48 | ARIN | Valid |
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.