Network · data from 2026-11-12

AS29269 CLOUDGLOBAL-AS Cloud Global S.L.

Registry name: CLOUDGLOBAL-AS Cloud Global S.L., ES · not in PeeringDB

1IPv4 routes 100.0% RPKI valid · 100.0% with a route object

10IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No 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 AS29269, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS29269, 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.53.250.0/24	Valid	RIR databaseRIPE	673 100%	66
2a02:6480::/32	Valid	RIR databaseRIPE	599 94%	68
2a12:ca47::/32	Valid	RIR databaseRIPE	570 90%	67
2a12:ca45::/32	Valid	RIR databaseRIPE	569 89%	67
2a12:ca46::/32	Valid	RIR databaseRIPE	569 89%	67
2a12:ca40::/29	Valid	RIR databaseRIPE	567 89%	67
2a12:ca40::/32	Valid	RIR databaseRIPE	566 89%	67
2a12:ca41::/32	Valid	RIR databaseRIPE	566 89%	67
2a12:ca42::/32	Valid	RIR databaseRIPE	566 89%	67
2a12:ca43::/32	Valid	RIR databaseRIPE	566 89%	67
2a12:ca44::/32	Valid	RIR databaseRIPE	566 89%	67

AS-SET

AS29269 isn't in PeeringDB, where networks name their AS-SET.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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