Network · data from 2026-11-12
AS16028 Orange S.A.
Registry name: Orange S.A., FR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS16028, 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.
| 193.251.164.0/24 | Invalid: origin | None | 2 0%low visibility |
| 81.52.208.0/22 | Valid | None | 673 100% |
| 193.251.160.0/24 | Valid | None | 673 100% |
| 193.251.162.0/24 | Valid | None | 673 100% |
| 193.251.163.0/24 | Valid | None | 673 100% |
| 81.52.214.0/24 | Valid | None | 672 100% |
| 81.52.215.0/24 | Valid | None | 672 100% |
| 2a01:cde0:40::/48 | Valid | None | 629 99% |
| 2a01:cde0:100::/48 | Valid | None | 629 99% |
| 2a01:cde0:101::/48 | Valid | None | 629 99% |
| 2a01:cde0:102::/48 | Valid | None | 629 99% |
| 2a01:cde0:108::/45 | Valid | None | 629 99% |
| 2a01:cde0:8040::/48 | Valid | None | 629 99% |
| 2a01:cde0:8101::/48 | Valid | None | 629 99% |
| 2a01:cde0:8102::/48 | Valid | None | 629 99% |
| 2a01:cde0:8108::/45 | Valid | None | 629 99% |
AS-SET
AS16028 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 17 are in fix.csv.
- ROA: origin1
- Route object: none16
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 193.251.164.0/24 | ROAs covering it name AS5511, not AS16028. If AS16028 should announce it, add a ROA for AS16028. |
| Route object: none | 193.251.164.0/24 | No route object for it. Add a route object with origin AS16028 in the RIR database for the space. |
| Route object: none | 81.52.208.0/22 | No route object for it. Add a route object with origin AS16028 in the RIR database for the space. |
| Route object: none | 193.251.160.0/24 | No route object for it. Add a route object with origin AS16028 in the RIR database for the space. |
| Route object: none | 193.251.162.0/24 | No route object for it. Add a route object with origin AS16028 in the RIR database for the space. |
| Route object: none | 193.251.163.0/24 | No route object for it. Add a route object with origin AS16028 in the RIR database for the space. |
| Route object: none | 81.52.214.0/24 | No route object for it. Add a route object with origin AS16028 in the RIR database for the space. |
| Route object: none | 81.52.215.0/24 | No route object for it. Add a route object with origin AS16028 in the RIR database for the space. |
| Route object: none | 2a01:cde0:40::/48 | No route object for it. Add a route object with origin AS16028 in the RIR database for the space. |
| Route object: none | 2a01:cde0:100::/48 | No route object for it. Add a route object with origin AS16028 in the RIR database for the space. |
| Route object: none | 2a01:cde0:101::/48 | No route object for it. Add a route object with origin AS16028 in the RIR database for the space. |
| Route object: none | 2a01:cde0:102::/48 | No route object for it. Add a route object with origin AS16028 in the RIR database for the space. |
| Route object: none | 2a01:cde0:108::/45 | No route object for it. Add a route object with origin AS16028 in the RIR database for the space. |
| Route object: none | 2a01:cde0:8040::/48 | No route object for it. Add a route object with origin AS16028 in the RIR database for the space. |
| Route object: none | 2a01:cde0:8101::/48 | No route object for it. Add a route object with origin AS16028 in the RIR database for the space. |
| Route object: none | 2a01:cde0:8102::/48 | No route object for it. Add a route object with origin AS16028 in the RIR database for the space. |
| Route object: none | 2a01:cde0:8108::/45 | No route object for it. Add a route object with origin AS16028 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS16028 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.