Network · data from 2026-11-12
AS48158 DIGITALONE-AS DigitalOne AG
Registry name: DIGITALONE-AS DigitalOne AG, CH · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS48158, 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.
| 146.255.212.0/23 | Valid | None | 67 10%low visibility |
| 146.255.208.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.255.209.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.255.210.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.255.212.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.255.213.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.255.216.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.255.217.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.255.218.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.255.219.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.255.220.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.255.221.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.255.222.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 146.255.223.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.58.38.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.58.39.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.58.40.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.58.41.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.58.42.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.58.43.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.58.45.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.58.50.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.58.52.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.58.54.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.58.56.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.58.46.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 176.58.48.0/23 | Valid | RIR databaseRIPE | 671 100% |
| 176.58.53.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 176.58.47.0/24 | Valid | RIR databaseRIPE | 668 99% |
AS-SET
AS48158 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 14 are in fix.csv.
- Route object: none1
- Route object: not announced13
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 146.255.212.0/23 | No route object for it. Add a route object with origin AS48158 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS48158 whose prefix no peer sees AS48158 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.12.4.0/24 | RIPE | No ROA |
| 45.12.5.0/24 | RIPE | No ROA |
| 45.12.6.0/24 | RIPE | No ROA |
| 146.255.211.0/24 | RIPE | Valid |
| 146.255.214.0/24 | RIPE | Valid |
| 146.255.215.0/24 | RIPE | Valid |
| 176.58.44.0/24 | RIPE | Invalid: origin |
| 176.58.51.0/24 | RIPE | Invalid: origin |
| 176.58.55.0/24 | RIPE | Valid |
| 176.58.57.0/24 | RIPE | Valid |
| 185.190.190.0/24 | RIPE | Valid |
| 185.190.191.0/24 | RIPE | No ROA |
| 212.124.96.0/22 | 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.