Network · data from 2026-11-12
AS34524 DIGICOM-AS Digital Communications Ltd.
Registry name: DIGICOM-AS Digital Communications Ltd., BG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS34524, 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.
| 185.18.56.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.18.57.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.18.58.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.18.59.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 2a02:d6c0::/29 | No ROA | RIR databaseRIPE | 635 100% |
| 5.104.176.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.104.177.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.104.178.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.104.179.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.104.180.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.104.181.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS34524 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: none5
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 185.18.56.0/24 | No ROA covers it. Add a ROA for AS34524, maxLength 24. |
| ROA: none | 185.18.57.0/24 | No ROA covers it. Add a ROA for AS34524, maxLength 24. |
| ROA: none | 185.18.58.0/24 | No ROA covers it. Add a ROA for AS34524, maxLength 24. |
| ROA: none | 185.18.59.0/24 | No ROA covers it. Add a ROA for AS34524, maxLength 24. |
| ROA: none | 2a02:d6c0::/29 | No ROA covers it. Add a ROA for AS34524, maxLength 29. |
Route objects not announced
Route objects with origin AS34524 whose prefix no peer sees AS34524 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.18.56.0/22 | 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.