bgpreport

Network · data from 2026-11-12

AS35779 MCLOUD-AS mCloud doo

Registry name: MCLOUD-AS mCloud doo, RS · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS35779, 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.
188.93.124.0/24 No ROA RIR databaseRIPE 671 100% 66
188.93.125.0/24 No ROA RIR databaseRIPE 671 100% 66
188.93.126.0/24 No ROA RIR databaseRIPE 671 100% 66
188.93.127.0/24 No ROA RIR databaseRIPE 671 100% 66
188.93.124.0/22 No ROA RIR databaseRIPE 670 100% 66
188.93.124.0/23 No ROA RIR databaseRIPE 670 100% 66
188.93.126.0/23 No ROA RIR databaseRIPE 670 100% 66
194.146.56.0/22 No ROA RIR databaseRIPE 670 100% 66
2a07:de80::/29 No ROA RIR databaseRIPE 634 100% 69
46.174.136.0/23 Valid None 673 100% 66

AS-SET

AS35779 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 12 are in fix.csv.

  • ROA: none9
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none188.93.124.0/24No ROA covers it. Add a ROA for AS35779, maxLength 24.671 of 673
ROA: none188.93.125.0/24No ROA covers it. Add a ROA for AS35779, maxLength 24.671 of 673
ROA: none188.93.126.0/24No ROA covers it. Add a ROA for AS35779, maxLength 24.671 of 673
ROA: none188.93.127.0/24No ROA covers it. Add a ROA for AS35779, maxLength 24.671 of 673
ROA: none188.93.124.0/22No ROA covers it. Add a ROA for AS35779, maxLength 22.670 of 673
ROA: none188.93.124.0/23No ROA covers it. Add a ROA for AS35779, maxLength 23.670 of 673
ROA: none188.93.126.0/23No ROA covers it. Add a ROA for AS35779, maxLength 23.670 of 673
ROA: none194.146.56.0/22No ROA covers it. Add a ROA for AS35779, maxLength 22.670 of 673
ROA: none2a07:de80::/29No ROA covers it. Add a ROA for AS35779, maxLength 29.634 of 636
Route object: none46.174.136.0/23No route object for it. Add a route object with origin AS35779 in the RIR database for the space.673 of 673

Route objects not announced

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

46.174.136.0/24RIPEValid
46.174.137.0/24RIPEValid

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.