bgpreport

Network · data from 2026-11-12

AS199233 MAIF-AS Mutuelle Assurance Instituteur France STE

Registry name: MAIF-AS Mutuelle Assurance Instituteur France STE, FR · not in PeeringDB

7IPv4 routes 57.1% RPKI valid · 14.3% with a route object
1IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
4No 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 AS199233, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS199233, 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.209.180.0/22 No ROA None 673 100% 67
185.209.180.0/23 No ROA None 673 100% 67
185.209.182.0/23 No ROA None 673 100% 67
2001:67c:10f8::/48 No ROA RIR databaseRIPE 629 99% 67
194.2.130.0/23 Valid None 673 100% 67
194.2.130.0/24 Valid None 673 100% 67
194.2.131.0/24 Valid None 673 100% 67
90.85.39.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

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

  • ROA: none4
  • Route object: none6
ChangePrefix or setDetailFull-table peers
ROA: none185.209.180.0/22No ROA covers it. Add a ROA for AS199233, maxLength 22.673 of 673
Route object: none185.209.180.0/22No route object for it. Add a route object with origin AS199233 in the RIR database for the space.673 of 673
ROA: none185.209.180.0/23No ROA covers it. Add a ROA for AS199233, maxLength 23.673 of 673
Route object: none185.209.180.0/23No route object for it. Add a route object with origin AS199233 in the RIR database for the space.673 of 673
ROA: none185.209.182.0/23No ROA covers it. Add a ROA for AS199233, maxLength 23.673 of 673
Route object: none185.209.182.0/23No route object for it. Add a route object with origin AS199233 in the RIR database for the space.673 of 673
ROA: none2001:67c:10f8::/48No ROA covers it. Add a ROA for AS199233, maxLength 48.629 of 636
Route object: none194.2.130.0/23No route object for it. Add a route object with origin AS199233 in the RIR database for the space.673 of 673
Route object: none194.2.130.0/24No route object for it. Add a route object with origin AS199233 in the RIR database for the space.673 of 673
Route object: none194.2.131.0/24No route object for it. Add a route object with origin AS199233 in the RIR database for the space.673 of 673

Route objects not announced

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