bgpreport

Network · data from 2026-11-12

AS2287 IOT-CADV-OBS-AS Orange S.A.

Registry name: IOT-CADV-OBS-AS Orange S.A., FR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS2287, 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.

90.84.138.0/24 Valid None 673 100% 67
90.84.139.0/24 Valid None 673 100% 67
90.84.157.0/24 Valid None 673 100% 67
90.84.158.0/24 Valid None 673 100% 67
90.84.166.0/24 Valid None 673 100% 67
90.84.167.0/24 Valid None 673 100% 67
2a01:ceff::/48 Valid None 636 100% 67
2a01:ceff:1::/48 Valid None 636 100% 67
2a01:ceff:2::/48 Valid None 636 100% 67
2a01:ceff:3::/48 Valid None 636 100% 67

AS-SET

AS2287 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.

  • Route object: none10
ChangePrefix or setDetailFull-table peers
Route object: none90.84.138.0/24No route object for it. Add a route object with origin AS2287 in the RIR database for the space.673 of 673
Route object: none90.84.139.0/24No route object for it. Add a route object with origin AS2287 in the RIR database for the space.673 of 673
Route object: none90.84.157.0/24No route object for it. Add a route object with origin AS2287 in the RIR database for the space.673 of 673
Route object: none90.84.158.0/24No route object for it. Add a route object with origin AS2287 in the RIR database for the space.673 of 673
Route object: none90.84.166.0/24No route object for it. Add a route object with origin AS2287 in the RIR database for the space.673 of 673
Route object: none90.84.167.0/24No route object for it. Add a route object with origin AS2287 in the RIR database for the space.673 of 673
Route object: none2a01:ceff::/48No route object for it. Add a route object with origin AS2287 in the RIR database for the space.636 of 636
Route object: none2a01:ceff:1::/48No route object for it. Add a route object with origin AS2287 in the RIR database for the space.636 of 636
Route object: none2a01:ceff:2::/48No route object for it. Add a route object with origin AS2287 in the RIR database for the space.636 of 636
Route object: none2a01:ceff:3::/48No route object for it. Add a route object with origin AS2287 in the RIR database for the space.636 of 636

Route objects not announced

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