Network · data from 2026-11-12
AS34916 DIGITAL CONSTRUCTION NETWORK SRL
Registry name: DNET-AS Digital Construction Network SRL, RO · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS34916, 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.
| 86.105.204.0/23 | No ROA | None | 2 0%low visibility |
| 85.204.193.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 86.104.231.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 86.105.226.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 86.106.27.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.44.238.0/23 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
PeeringDB's irr_as_set for AS34916: AS-DCN. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS34916 isn't in the set, or no route object for AS34916 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS34916 in it | Not covered |
|---|---|---|---|---|---|
| AS-DCN | RADB3 member sets in no database: AS-27539, AS-53284, AS-SRT | 45 | 4 | No | 6 |
| RIPE (also) | 5 | 1 | Yes | 1 |
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 7 are in fix.csv.
- ROA: none1
- Route object: none1
- AS-SET: own ASN1
- AS-SET: missing member3
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 86.105.204.0/23 | No ROA covers it. Add a ROA for AS34916, maxLength 23. |
| Route object: none | 86.105.204.0/23 | No route object for it. Add a route object with origin AS34916 in the RIR database for the space. |
| AS-SET: own ASN | AS-DCN | AS34916 isn't in AS-DCN (RADB) once expanded. Add AS34916 to it. |
| AS-SET: missing member | AS-DCN | AS-DCN (RADB) lists AS-27539; no IRR database read has it. |
| AS-SET: missing member | AS-DCN | AS-DCN (RADB) lists AS-53284; no IRR database read has it. |
| AS-SET: missing member | AS-DCN | AS-DCN (RADB) lists AS-SRT; no IRR database read has it. |
Route objects not announced
Route objects with origin AS34916 whose prefix no peer sees AS34916 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a05:cb40:f::/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.