Network · data from 2026-11-12
AS207893 DeltaX Labs
Registry name: DELTAX-LABS Tech Futures Interactive Inc., CA · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS207893, 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.88.127.0/24 | Invalid: origin | None | 13 2%low visibility |
| 2a0f:ec80::/32 | Valid | Other IRR onlyRADB | 635 100% |
AS-SET
AS207893'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 5 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: RIR1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 38.88.127.0/24 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS207893 should announce it, add a ROA for AS207893. |
| Route object: none | 38.88.127.0/24 | No route object for it. Add a route object with origin AS207893 in the RIR database for the space. |
| Route object: RIR | 2a0f:ec80::/32 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS207893 whose prefix no peer sees AS207893 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a0f:ec81::/32 | RADB | Valid |
| 2a0f:ec82::/32 | RADB | 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.