Network · data from 2026-11-12
AS2278 OrangeLabs Orange S.A.
Registry name: OrangeLabs Orange S.A., FR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS2278, 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.
| 161.105.128.0/17 | Valid | Nonecovered by 161.105.0.0/16 | 673 100% |
| 2a01:cf00::/42 | Valid | None | 629 99% |
| 161.106.0.0/16 | Valid | RIR databaseRIPE | 673 100% |
| 192.144.77.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS2278 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 4 are in fix.csv.
- Route object: none2
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 161.105.128.0/17 | No route object for it. A route object for 161.105.0.0/16 with origin AS2278 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2278 in the RIR database for the space. |
| Route object: none | 2a01:cf00::/42 | No route object for it. Add a route object with origin AS2278 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS2278 whose prefix no peer sees AS2278 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 161.105.0.0/16 | RIPE | No ROA |
| 2a01:cf00:f::/48 | RIPE | Valid |
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.