Network · data from 2026-11-12
AS204032 UTECH-AS Unity Technologies ApS
Registry name: UTECH-AS Unity Technologies ApS, DK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS204032, 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.
| 185.33.99.0/24 | No ROA | RIR databaseRADB, RIPE | 673 100% |
| 2a03:4be0:b0cc::/48 | No ROA | RIR databaseRIPE | 636 100% |
AS-SET
AS204032 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 12 are in fix.csv.
- ROA: none2
- Route object: not announced10
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.33.99.0/24 | No ROA covers it. Add a ROA for AS204032, maxLength 24. |
| ROA: none | 2a03:4be0:b0cc::/48 | No ROA covers it. Add a ROA for AS204032, maxLength 48. |
Route objects not announced
Route objects with origin AS204032 whose prefix no peer sees AS204032 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.33.96.0/23 | RADB | No ROA |
| 185.33.97.0/24 | RADB | No ROA |
| 185.33.98.0/23 | RADB | No ROA |
| 185.98.36.0/22 | RADB, RIPE | No ROA |
| 185.98.36.0/23 | RIPE | No ROA |
| 185.98.36.0/24 | RIPE | No ROA |
| 185.98.37.0/24 | RADB, RIPE | No ROA |
| 185.98.38.0/23 | RADB | No ROA |
| 185.98.39.0/24 | RADB | No ROA |
| 2a03:4be0::/48 | RIPE | 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.