bgpreport

Network · data from 2026-11-12

AS51920 VIVACOM

Registry name: vivacom VIVACOM Magyarorszag Kft, HU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS51920, 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.92.116.0/22 No ROA RIR databaseRIPE 673 100% 67
45.9.200.0/22 No ROA RIR databaseRIPE 670 100% 67
45.66.200.0/22 No ROA RIR databaseRIPE 670 100% 67
185.188.56.0/24 No ROA RIR databaseRIPE 670 100% 67
185.188.57.0/24 No ROA RIR databaseRIPE 670 100% 67
185.188.58.0/24 No ROA RIR databaseRIPE 670 100% 67
185.220.188.0/22 No ROA RIR databaseRIPE 670 100% 67
2a03:8c60::/32 No ROA RIR databaseRIPE 636 100% 67
2a03:8c60::/48 No ROA RIR databaseRIPE 636 100% 67
2a03:8c60:1::/48 No ROA RIR databaseRIPE 636 100% 67
2a03:8c60:2::/48 No ROA RIR databaseRIPE 636 100% 67
2a03:8c60:3::/48 No ROA RIR databaseRIPE 636 100% 67
2a0b:b980:1::/48 No ROA RIR databaseRIPE 635 100% 69
2a0b:b980:2::/48 No ROA RIR databaseRIPE 635 100% 69
2a09:6bc0::/29 No ROA RIR databaseRIPE 634 100% 69
2a0b:fac0::/29 No ROA RIR databaseRIPE 634 100% 69
2a0f:6140::/29 No ROA RIR databaseRIPE 634 100% 69
2a0e:9740::/29 No ROA RIR databaseRIPE 1 0%low visibility 1

AS-SET

AS51920's PeeringDB record names no 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 23 are in fix.csv.

  • ROA: none18
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none185.92.116.0/22No ROA covers it. Add a ROA for AS51920, maxLength 22.673 of 673
ROA: none45.9.200.0/22No ROA covers it. Add a ROA for AS51920, maxLength 22.670 of 673
ROA: none45.66.200.0/22No ROA covers it. Add a ROA for AS51920, maxLength 22.670 of 673
ROA: none185.188.56.0/24No ROA covers it. Add a ROA for AS51920, maxLength 24.670 of 673
ROA: none185.188.57.0/24No ROA covers it. Add a ROA for AS51920, maxLength 24.670 of 673
ROA: none185.188.58.0/24No ROA covers it. Add a ROA for AS51920, maxLength 24.670 of 673
ROA: none185.220.188.0/22No ROA covers it. Add a ROA for AS51920, maxLength 22.670 of 673
ROA: none2a03:8c60::/32No ROA covers it. Add a ROA for AS51920, maxLength 32.636 of 636
ROA: none2a03:8c60::/48No ROA covers it. Add a ROA for AS51920, maxLength 48.636 of 636
ROA: none2a03:8c60:1::/48No ROA covers it. Add a ROA for AS51920, maxLength 48.636 of 636
ROA: none2a03:8c60:2::/48No ROA covers it. Add a ROA for AS51920, maxLength 48.636 of 636
ROA: none2a03:8c60:3::/48No ROA covers it. Add a ROA for AS51920, maxLength 48.636 of 636
ROA: none2a0b:b980:1::/48No ROA covers it. Add a ROA for AS51920, maxLength 48.635 of 636
ROA: none2a0b:b980:2::/48No ROA covers it. Add a ROA for AS51920, maxLength 48.635 of 636
ROA: none2a09:6bc0::/29No ROA covers it. Add a ROA for AS51920, maxLength 29.634 of 636
ROA: none2a0b:fac0::/29No ROA covers it. Add a ROA for AS51920, maxLength 29.634 of 636
ROA: none2a0f:6140::/29No ROA covers it. Add a ROA for AS51920, maxLength 29.634 of 636
ROA: none2a0e:9740::/29No ROA covers it. Add a ROA for AS51920, maxLength 29.1 of 636

Route objects not announced

Route objects with origin AS51920 whose prefix no peer sees AS51920 announce. Many are kept on purpose (backup routes, space announced only in some places).

45.136.120.0/22RIPENo ROA
185.92.116.0/24RIPENo ROA
185.92.117.0/24RIPENo ROA
185.92.118.0/24RIPENo ROA
185.92.119.0/24RIPENo 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.