bgpreport

Network · data from 2026-11-12

AS34744 GVM GVM Sistem 2003 SRL

Registry name: GVM GVM Sistem 2003 SRL, RO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS34744, 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.
91.246.172.0/22 Invalid: origin Other origin only 140 21% 46
77.36.0.0/23 Valid RIR databaseRIPE 673 100% 66
77.232.216.0/22 Valid RIR databaseRIPE 673 100% 66
93.120.47.0/24 Valid RIR databaseRIPE 673 100% 66
109.197.232.0/22 Valid RIR databaseRIPE 673 100% 66
176.115.232.0/22 Valid RIR databaseRIPE 673 100% 66
77.36.16.0/21 Valid RIR databaseRIPE 672 100% 67
2a01:7d8::/48 Valid RIR databaseRIPE 636 100% 67
2a01:7d8:1::/48 Valid RIR databaseRIPE 636 100% 67

AS-SET

AS34744 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: origin1
  • Route object: none1
ChangePrefix or setDetailFull-table peers
ROA: origin91.246.172.0/22ROAs covering it name AS19855, not AS34744. If AS34744 should announce it, add a ROA for AS34744.140 of 673
Route object: none91.246.172.0/22Route objects for it name AS19855. Add a route object with origin AS34744 in the RIR database for the space.140 of 673

Route objects not announced

Every route object with origin AS34744 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.