bgpreport

Network · data from 2026-11-12

AS199660 Cloudata

Registry name: CLOUDATA LTI NETWORKS SASU, FR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS199660, 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.7.64.0/24 No ROA Nonecovered by 185.7.64.0/22 669 99% 67
185.7.65.0/24 No ROA Nonecovered by 185.7.64.0/22 669 99% 67
185.7.66.0/24 No ROA Nonecovered by 185.7.64.0/22 669 99% 67
185.7.67.0/24 No ROA Nonecovered by 185.7.64.0/22 669 99% 67
185.7.64.0/22 No ROA RIR databaseRIPE 671 100% 67
185.212.96.0/22 No ROA RIR databaseRIPE 671 100% 67
2a03:2440::/32 No ROA RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS199660: AS-CLOUDATA. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS199660 isn't in the set, or no route object for AS199660 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS199660 in itNot covered
AS-CLOUDATA RIPE 2111 Yes 0

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

  • ROA: none7
  • Route object: none4
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none185.7.64.0/24No ROA covers it. Add a ROA for AS199660, maxLength 24.669 of 673
Route object: none185.7.64.0/24No route object for it. A route object for 185.7.64.0/22 with origin AS199660 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199660 in the RIR database for the space.669 of 673
ROA: none185.7.65.0/24No ROA covers it. Add a ROA for AS199660, maxLength 24.669 of 673
Route object: none185.7.65.0/24No route object for it. A route object for 185.7.64.0/22 with origin AS199660 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199660 in the RIR database for the space.669 of 673
ROA: none185.7.66.0/24No ROA covers it. Add a ROA for AS199660, maxLength 24.669 of 673
Route object: none185.7.66.0/24No route object for it. A route object for 185.7.64.0/22 with origin AS199660 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199660 in the RIR database for the space.669 of 673
ROA: none185.7.67.0/24No ROA covers it. Add a ROA for AS199660, maxLength 24.669 of 673
Route object: none185.7.67.0/24No route object for it. A route object for 185.7.64.0/22 with origin AS199660 covers it (filters allowing more-specifics accept it). Add a route object with origin AS199660 in the RIR database for the space.669 of 673
ROA: none185.7.64.0/22No ROA covers it. Add a ROA for AS199660, maxLength 22.671 of 673
ROA: none185.212.96.0/22No ROA covers it. Add a ROA for AS199660, maxLength 22.671 of 673
ROA: none2a03:2440::/32No ROA covers it. Add a ROA for AS199660, maxLength 32.635 of 636

Route objects not announced

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

185.212.96.0/24RIPENo ROA
185.212.97.0/24RIPENo ROA
185.212.98.0/24RIPENo ROA
185.212.99.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.