bgpreport

Network · data from 2026-11-12

AS199140 ORE-AS Orange S.A.

Registry name: ORE-AS Orange S.A., FR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS199140, 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.
80.12.213.0/24 Valid None 672 100% 67
80.12.241.0/24 Valid None 672 100% 67
80.12.249.0/24 Valid None 672 100% 67
80.12.250.0/24 Valid None 672 100% 67
80.12.253.0/24 Valid None 672 100% 67
80.12.254.0/24 Valid None 672 100% 67
2a01:cb22:4002::/48 Valid None 629 99% 67
2a01:cb22:4003::/48 Valid None 629 99% 67
2a01:cb22:4200::/40 Valid None 629 99% 67
2a01:cb22:4300::/40 Valid None 629 99% 67
2a01:cb22:4fff::/48 Valid None 629 99% 67
80.12.212.0/24 Valid RIR databaseRIPE 672 100% 67
80.12.240.0/24 Valid RIR databaseRIPE 672 100% 67
80.12.243.0/24 Valid RIR databaseRIPE 672 100% 67

AS-SET

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

  • Route object: none11
ChangePrefix or setDetailFull-table peers
Route object: none80.12.213.0/24No route object for it. Add a route object with origin AS199140 in the RIR database for the space.672 of 673
Route object: none80.12.241.0/24No route object for it. Add a route object with origin AS199140 in the RIR database for the space.672 of 673
Route object: none80.12.249.0/24No route object for it. Add a route object with origin AS199140 in the RIR database for the space.672 of 673
Route object: none80.12.250.0/24No route object for it. Add a route object with origin AS199140 in the RIR database for the space.672 of 673
Route object: none80.12.253.0/24No route object for it. Add a route object with origin AS199140 in the RIR database for the space.672 of 673
Route object: none80.12.254.0/24No route object for it. Add a route object with origin AS199140 in the RIR database for the space.672 of 673
Route object: none2a01:cb22:4002::/48No route object for it. Add a route object with origin AS199140 in the RIR database for the space.629 of 636
Route object: none2a01:cb22:4003::/48No route object for it. Add a route object with origin AS199140 in the RIR database for the space.629 of 636
Route object: none2a01:cb22:4200::/40No route object for it. Add a route object with origin AS199140 in the RIR database for the space.629 of 636
Route object: none2a01:cb22:4300::/40No route object for it. Add a route object with origin AS199140 in the RIR database for the space.629 of 636
Route object: none2a01:cb22:4fff::/48No route object for it. Add a route object with origin AS199140 in the RIR database for the space.629 of 636

Route objects not announced

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