Network · data from 2026-11-12
AS48090 DMZHOST TECHOFF SRV LIMITED
Registry name: DMZHOST TECHOFF SRV LIMITED, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS48090, 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.
| 195.178.110.204/32 | Invalid: maxLength | Nonecovered by 195.178.110.0/24 | 1 0%low visibility |
| 45.148.10.0/24 | No ROA | RIR databaseRIPE | 663 99% |
| 195.178.110.0/24 | Valid | RIR databaseRIPE | 664 99% |
| 93.123.109.0/24 | Valid | RIR databaseRIPE | 662 98% |
AS-SET
AS48090 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: maxLength1
- ROA: none1
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 195.178.110.204/32 | ROA 195.178.110.0/24 AS48090 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 195.178.110.204/32. |
| Route object: none | 195.178.110.204/32 | No route object for it. A route object for 195.178.110.0/24 with origin AS48090 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS48090 in the RIR database for the space. |
| ROA: none | 45.148.10.0/24 | No ROA covers it. Add a ROA for AS48090, maxLength 24. |
Route objects not announced
Route objects with origin AS48090 whose prefix no peer sees AS48090 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2.57.122.0/24 | RIPE | Valid |
| 80.94.92.0/24 | RIPE | Valid |
| 92.118.39.0/24 | RIPE | Invalid: origin |
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.