Network · data from 2026-11-12
AS19584 DATACAMO-LOSANGELES - Datacamo, Inc.
Registry name: DATACAMO-LOSANGELES - Datacamo, Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS19584, 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.
| 23.149.96.0/24 | No ROA | RIR databaseARIN, RADB | 2 0%low visibility |
AS-SET
AS19584 isn't in PeeringDB, where networks name their 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 6 are in fix.csv.
- ROA: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 23.149.96.0/24 | No ROA covers it. Add a ROA for AS19584, maxLength 24. |
Route objects not announced
Route objects with origin AS19584 whose prefix no peer sees AS19584 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 216.115.70.0/24 | RADB | No ROA |
| 216.115.77.0/24 | RADB | No ROA |
| 216.115.80.0/24 | RADB | No ROA |
| 216.115.81.0/24 | RADB | No ROA |
| 2604:f640::/36 | ARIN | 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.