Network · data from 2026-11-12
AS2280 OCBHoney Orange S.A.
Registry name: OCBHoney Orange S.A., FR · not in PeeringDB
34IPv4 routes
100.0% RPKI valid · 41.2% with a route object
2IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
20 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
2Route objects not announced
registered with origin AS2280, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS2280, 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.16.0/22 | Valid | Nonecovered by 90.84.16.0/21 | 673 100% |
| 90.84.20.0/22 | Valid | Nonecovered by 90.84.16.0/21 | 673 100% |
| 90.84.40.0/24 | Valid | Nonecovered by 90.84.40.0/21 | 673 100% |
| 90.84.42.0/24 | Valid | Nonecovered by 90.84.40.0/21 | 673 100% |
| 90.84.43.0/24 | Valid | Nonecovered by 90.84.40.0/21 | 673 100% |
| 90.84.44.0/22 | Valid | Nonecovered by 90.84.40.0/21 | 673 100% |
| 90.84.168.0/22 | Valid | Nonecovered by 90.84.168.0/21 | 673 100% |
| 90.84.172.0/22 | Valid | Nonecovered by 90.84.168.0/21 | 673 100% |
| 90.84.176.0/21 | Valid | None | 673 100% |
| 90.84.176.0/22 | Valid | None | 673 100% |
| 90.84.180.0/22 | Valid | None | 673 100% |
| 90.84.184.0/22 | Valid | Nonecovered by 90.84.184.0/21 | 673 100% |
| 90.84.188.0/22 | Valid | Nonecovered by 90.84.184.0/21 | 673 100% |
| 90.84.192.0/22 | Valid | Nonecovered by 90.84.192.0/21 | 673 100% |
| 90.84.196.0/22 | Valid | Nonecovered by 90.84.192.0/21 | 673 100% |
| 90.84.240.0/22 | Valid | Nonecovered by 90.84.240.0/21 | 673 100% |
| 90.84.244.0/22 | Valid | Nonecovered by 90.84.240.0/21 | 673 100% |
| 90.84.14.0/23 | Valid | None | 671 100% |
| 90.84.154.0/23 | Valid | None | 671 100% |
| 90.84.252.0/23 | Valid | None | 671 100% |
| 90.84.11.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 90.84.14.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 90.84.15.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 90.84.16.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 90.84.39.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 90.84.40.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 90.84.154.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 90.84.155.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 90.84.168.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 90.84.184.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 90.84.192.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 90.84.240.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 90.84.251.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 90.84.252.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a01:c9c0:8000::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a01:c9c0:800f::/48 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS2280 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 22 are in fix.csv.
- Route object: none20
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 90.84.16.0/22 | No route object for it. A route object for 90.84.16.0/21 with origin AS2280 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2280 in the RIR database for the space. |
| Route object: none | 90.84.20.0/22 | No route object for it. A route object for 90.84.16.0/21 with origin AS2280 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2280 in the RIR database for the space. |
| Route object: none | 90.84.40.0/24 | No route object for it. A route object for 90.84.40.0/21 with origin AS2280 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2280 in the RIR database for the space. |
| Route object: none | 90.84.42.0/24 | No route object for it. A route object for 90.84.40.0/21 with origin AS2280 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2280 in the RIR database for the space. |
| Route object: none | 90.84.43.0/24 | No route object for it. A route object for 90.84.40.0/21 with origin AS2280 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2280 in the RIR database for the space. |
| Route object: none | 90.84.44.0/22 | No route object for it. A route object for 90.84.40.0/21 with origin AS2280 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2280 in the RIR database for the space. |
| Route object: none | 90.84.168.0/22 | No route object for it. A route object for 90.84.168.0/21 with origin AS2280 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2280 in the RIR database for the space. |
| Route object: none | 90.84.172.0/22 | No route object for it. A route object for 90.84.168.0/21 with origin AS2280 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2280 in the RIR database for the space. |
| Route object: none | 90.84.176.0/21 | No route object for it. Add a route object with origin AS2280 in the RIR database for the space. |
| Route object: none | 90.84.176.0/22 | No route object for it. Add a route object with origin AS2280 in the RIR database for the space. |
| Route object: none | 90.84.180.0/22 | No route object for it. Add a route object with origin AS2280 in the RIR database for the space. |
| Route object: none | 90.84.184.0/22 | No route object for it. A route object for 90.84.184.0/21 with origin AS2280 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2280 in the RIR database for the space. |
| Route object: none | 90.84.188.0/22 | No route object for it. A route object for 90.84.184.0/21 with origin AS2280 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2280 in the RIR database for the space. |
| Route object: none | 90.84.192.0/22 | No route object for it. A route object for 90.84.192.0/21 with origin AS2280 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2280 in the RIR database for the space. |
| Route object: none | 90.84.196.0/22 | No route object for it. A route object for 90.84.192.0/21 with origin AS2280 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2280 in the RIR database for the space. |
| Route object: none | 90.84.240.0/22 | No route object for it. A route object for 90.84.240.0/21 with origin AS2280 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2280 in the RIR database for the space. |
| Route object: none | 90.84.244.0/22 | No route object for it. A route object for 90.84.240.0/21 with origin AS2280 covers it (filters allowing more-specifics accept it). Add a route object with origin AS2280 in the RIR database for the space. |
| Route object: none | 90.84.14.0/23 | No route object for it. Add a route object with origin AS2280 in the RIR database for the space. |
| Route object: none | 90.84.154.0/23 | No route object for it. Add a route object with origin AS2280 in the RIR database for the space. |
| Route object: none | 90.84.252.0/23 | No route object for it. Add a route object with origin AS2280 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS2280 whose prefix no peer sees AS2280 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 90.84.253.0/24 | RIPE | Valid |
| 90.84.254.0/24 | 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.