Network · data from 2026-11-12
AS41171 Digital-Network DIGITAL NETWORK S.R.L.
Registry name: Digital-Network DIGITAL NETWORK S.R.L., MD · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS41171, 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.
| 143.203.108.0/23 | Valid | Nonecovered by 143.203.108.0/22 | 1 0%low visibility |
| 86.107.166.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 89.35.15.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 93.113.67.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 93.119.150.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 143.203.108.0/22 | Valid | RIR databaseARIN | 671 100% |
| 156.9.92.0/22 | Valid | RIR databaseARIN | 671 100% |
AS-SET
AS41171 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 2 are in fix.csv.
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 143.203.108.0/23 | No route object for it. A route object for 143.203.108.0/22 with origin AS41171 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41171 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS41171 whose prefix no peer sees AS41171 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 109.66.226.0/23 | RADB, 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.