Network · data from 2026-11-12
AS218810 DATASPACE-ASN Space Web LLC
Registry name: DATASPACE-ASN Space Web LLC, KN · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS218810, 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.
| 2a0e:ad80::/33 | No ROA | RIR databaseRIPE | 635 100% |
| 2a0e:ad81::/33 | Valid | None | 636 100% |
| 136.148.78.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 153.56.255.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS218810 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: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a0e:ad80::/33 | No ROA covers it. Add a ROA for AS218810, maxLength 33. |
| Route object: none | 2a0e:ad81::/33 | No route object for it. Add a route object with origin AS218810 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS218810 whose prefix no peer sees AS218810 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 85.137.181.0/24 | RIPE | Valid |
| 89.39.66.0/24 | RIPE | Valid |
| 188.191.144.0/24 | RIPE | Valid |
| 2a0c:9a40:e040::/48 | RIPE | 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.