bgpreport

Network · data from 2026-11-12

AS44277 DIGI-AS DIGI COMMUNICATION SRL

Registry name: DIGI-AS DIGI COMMUNICATION SRL, RO · not in PeeringDB

13IPv4 routes 84.6% RPKI valid · 100.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
2No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS44277, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS44277, 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.
217.156.31.0/24 No ROA RIR databaseRIPE 671 100% 67
80.97.26.0/24 No ROA RIR databaseRIPE 670 100% 67
85.204.23.0/24 Valid RIR databaseRIPE 671 100% 67
86.106.99.0/24 Valid RIR databaseRIPE 671 100% 67
86.107.180.0/24 Valid RIR databaseRIPE 671 100% 67
89.35.115.0/24 Valid RIR databaseRIPE 671 100% 67
89.43.61.0/24 Valid RIR databaseRIPE 671 100% 67
93.118.39.0/24 Valid RIR databaseRIPE 671 100% 67
188.213.51.0/24 Valid RIR databaseRIPE 671 100% 67
188.214.226.0/24 Valid RIR databaseRIPE 671 100% 67
188.240.198.0/23 Valid RIR databaseRIPE 671 100% 67
188.241.108.0/24 Valid RIR databaseRIPE 671 100% 67
195.228.59.0/24 Valid RIR databaseRIPE 671 100% 67

AS-SET

AS44277 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.

  • ROA: none2
ChangePrefix or setDetailFull-table peers
ROA: none217.156.31.0/24No ROA covers it. Add a ROA for AS44277, maxLength 24.671 of 673
ROA: none80.97.26.0/24No ROA covers it. Add a ROA for AS44277, maxLength 24.670 of 673

Route objects not announced

Every route object with origin AS44277 is announced.

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.