bgpreport

Network · data from 2026-11-12

AS39798 MivoCloud

Registry name: MivoCloud MivoCloud SRL, MD · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS39798, 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.
194.180.174.83/32 Invalid: maxLength Nonecovered by 194.180.174.0/24 1 0%low visibility 1
5.252.176.0/24 Valid RIR databaseRIPE 673 100% 66
5.252.177.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
5.252.179.0/24 Valid RIR databaseRIPE 673 100% 67
94.158.244.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
94.158.247.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
194.180.157.0/24 Valid RIR databaseRIPE 673 100% 67
194.180.158.0/24 Valid RIR databaseRIPE 673 100% 67
194.180.174.0/24 Valid RIR databaseRIPE 673 100% 67
5.181.159.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
5.181.156.0/24 Valid RIR databaseRIPE 671 100% 68
5.181.157.0/24 Valid RIR databaseRIPE 671 100% 68
5.181.158.0/24 Valid RIR databaseRIPE 671 100% 68
5.252.178.0/24 Valid RIR databaseRIPE 671 100% 68
94.158.245.0/24 Valid RIR databaseRIPE 671 100% 68
94.158.246.0/24 Valid RIR databaseRIPE 671 100% 68
185.163.44.0/22 Valid RIR databaseRIPE 671 100% 68
185.225.16.0/24 Valid RIR databaseRIPE 671 100% 68
185.225.17.0/24 Valid RIR databaseRIPE 671 100% 68
185.225.19.0/24 Valid RIR databaseRIPE 671 100% 68
194.180.191.0/24 Valid RIR databaseRIPE 671 100% 68
2a0a:c802:4::/48 Valid RIR databaseRIPE 636 100% 68
2001:67c:2db8::/48 Valid RIR databaseRIPE 635 100% 69
2a0a:c800::/32 Valid RIR databaseRIPE 635 100% 69
2a0a:c801::/32 Valid RIR databaseRIPE 635 100% 69
2a0a:c802::/48 Valid RIR databaseRADB, RIPE 635 100% 67
2a0a:c802:1::/48 Valid RIR databaseRIPE 635 100% 70
2a0a:c802:3::/48 Valid RIR databaseRADB, RIPE 635 100% 67
2a0a:c802:6::/48 Valid RIR databaseRIPE 635 100% 68
2a0a:c802:2::/48 Valid RIR databaseRIPE 634 100% 68
2a0a:c802:5::/48 Valid RIR databaseRIPE 634 100% 67
2a0a:c802:7::/48 Valid RIR databaseRIPE 634 100% 67
185.225.16.0/22 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS39798'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 14 are in fix.csv.

  • ROA: maxLength1
  • Route object: none1
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: maxLength194.180.174.83/32ROA 194.180.174.0/24 AS39798 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 194.180.174.83/32.1 of 673
Route object: none194.180.174.83/32No route object for it. A route object for 194.180.174.0/24 with origin AS39798 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS39798 in the RIR database for the space.1 of 673

Route objects not announced

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

5.181.156.0/22RIPEValid
5.252.176.0/22RIPEValid
94.158.244.0/22RIPEValid
185.163.44.0/24RIPEValid
185.163.45.0/24RIPEValid
185.163.46.0/24RIPEValid
185.163.47.0/24RIPEValid
185.225.18.0/24RIPEValid
2a0a:c800::/29RIPEValid
2a0a:c802::/32RADBValid
2a0e:1980::/29RIPENo ROA
2a0e:3680::/29RIPENo 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.