bgpreport

Network · data from 2026-11-12

AS51588 SESAN SESAN SERVICE NUMERIQUE DE SANTE GCS

Registry name: SESAN SESAN SERVICE NUMERIQUE DE SANTE GCS, FR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS51588, 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.56.93.0/24 Invalid: maxLength Nonecovered by 194.56.92.0/22 118 18% 41
194.56.92.0/23 Valid Nonecovered by 194.56.92.0/22 673 100% 67
194.56.92.0/24 Valid Nonecovered by 194.56.92.0/22 673 100% 67
194.56.94.0/23 Valid Nonecovered by 194.56.92.0/22 673 100% 67
194.56.94.0/24 Valid Nonecovered by 194.56.92.0/22 673 100% 67
194.56.95.0/24 Valid Nonecovered by 194.56.92.0/22 673 100% 67
194.56.92.0/22 Valid RIR databaseRIPE 673 100% 66
2a06:3100::/29 Valid RIR databaseRIPE 633 100% 70

AS-SET

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

  • ROA: maxLength1
  • Route object: none6
ChangePrefix or setDetailFull-table peers
ROA: maxLength194.56.93.0/24ROA 194.56.92.0/22 AS51588 has maxLength 22; ROA 194.56.92.0/23 AS51588 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 194.56.93.0/24.118 of 673
Route object: none194.56.93.0/24No route object for it. A route object for 194.56.92.0/22 with origin AS51588 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51588 in the RIR database for the space.118 of 673
Route object: none194.56.92.0/23No route object for it. A route object for 194.56.92.0/22 with origin AS51588 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51588 in the RIR database for the space.673 of 673
Route object: none194.56.92.0/24No route object for it. A route object for 194.56.92.0/22 with origin AS51588 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51588 in the RIR database for the space.673 of 673
Route object: none194.56.94.0/23No route object for it. A route object for 194.56.92.0/22 with origin AS51588 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51588 in the RIR database for the space.673 of 673
Route object: none194.56.94.0/24No route object for it. A route object for 194.56.92.0/22 with origin AS51588 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51588 in the RIR database for the space.673 of 673
Route object: none194.56.95.0/24No route object for it. A route object for 194.56.92.0/22 with origin AS51588 covers it (filters allowing more-specifics accept it). Add a route object with origin AS51588 in the RIR database for the space.673 of 673

Route objects not announced

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