Network · data from 2026-11-12
AS58282 STATENSIT Statens IT
Registry name: STATENSIT Statens IT, DK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS58282, 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.
| 91.198.204.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 192.66.163.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.153.154.0/23 | Valid | Nonecovered by 185.153.152.0/22 | 673 100% |
| 91.208.157.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.49.252.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.128.228.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.153.152.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 188.64.152.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 192.66.62.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.3.60.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.3.61.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.3.192.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 193.3.234.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 193.162.120.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 193.162.168.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 193.162.176.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 193.163.80.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.163.131.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.163.156.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 194.182.109.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.182.156.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 193.3.246.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 193.163.8.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a03:1500::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a03:1500:ff03::/48 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS58282 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 4 are in fix.csv.
- ROA: none2
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 91.198.204.0/24 | No ROA covers it. Add a ROA for AS58282, maxLength 24. |
| ROA: none | 192.66.163.0/24 | No ROA covers it. Add a ROA for AS58282, maxLength 24. |
| Route object: none | 185.153.154.0/23 | No route object for it. A route object for 185.153.152.0/22 with origin AS58282 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58282 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS58282 whose prefix no peer sees AS58282 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.179.94.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.