bgpreport

Network · data from 2026-11-12

AS12601 CEGEDIM Cegedim.Cloud SASU

Registry name: CEGEDIM Cegedim.Cloud SASU, FR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS12601, 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.
64.126.212.0/24 Valid Nonecovered by 64.126.212.0/22 671 100% 67
195.101.164.0/23 Valid None 671 100% 67
195.101.166.0/23 Valid None 671 100% 67
64.126.196.0/23 Valid Nonecovered by 64.126.196.0/22 670 100% 67
64.126.192.0/23 Valid RIR databaseRIPE 671 100% 67
64.126.194.0/23 Valid RIR databaseRIPE 671 100% 67
64.126.200.0/22 Valid RIR databaseRIPE 671 100% 67
64.126.208.0/24 Valid RIR databaseRIPE 671 100% 67
64.126.209.0/24 Valid RIR databaseRIPE 671 100% 67
64.126.212.0/22 Valid RIR databaseRIPE 671 100% 67
80.94.176.0/22 Valid RIR databaseRIPE 671 100% 67
80.94.182.0/23 Valid RIR databaseRIPE 671 100% 67
80.94.188.0/23 Valid RIR databaseRIPE 671 100% 67
185.113.40.0/22 Valid RIR databaseRIPE 671 100% 67
185.194.80.0/22 Valid RIR databaseRIPE 671 100% 67
185.211.140.0/22 Valid RIR databaseRIPE 671 100% 67
194.5.134.0/24 Valid RIR databaseRIPE 671 100% 67
194.126.236.0/24 Valid RIR databaseRIPE 671 100% 67
213.159.9.0/24 Valid RIR databaseRIPE 671 100% 67
80.94.184.0/24 Valid RIR databaseRIPE 670 100% 67
80.94.185.0/24 Valid RIR databaseRIPE 670 100% 67
2a00:1220:4000::/34 Valid RIR databaseRIPE 634 100% 68
2a00:1220:8000::/34 Valid RIR databaseRIPE 634 100% 68

AS-SET

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

  • Route object: none4
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
Route object: none64.126.212.0/24No route object for it. A route object for 64.126.212.0/22 with origin AS12601 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12601 in the RIR database for the space.671 of 673
Route object: none195.101.164.0/23No route object for it. Add a route object with origin AS12601 in the RIR database for the space.671 of 673
Route object: none195.101.166.0/23No route object for it. Add a route object with origin AS12601 in the RIR database for the space.671 of 673
Route object: none64.126.196.0/23No route object for it. A route object for 64.126.196.0/22 with origin AS12601 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12601 in the RIR database for the space.670 of 673

Route objects not announced

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

64.126.192.0/22RIPENo ROA
64.126.196.0/22RIPENo ROA
80.94.176.0/20RIPENo ROA
80.94.176.0/21RIPENo ROA
80.94.183.0/24RIPEInvalid: maxLength
80.94.184.0/22RIPENo ROA
80.94.184.0/23RIPENo ROA
194.5.133.0/24RIPENo ROA
203.174.28.0/23RADBNo 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.