bgpreport

Network · data from 2026-11-12

AS24600 WANADOOPORTAILS-AS Orange S.A.

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS24600, 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.252.121.0/24 Valid None 673 100% 67
2a01:c9c0:b1::/48 Valid None 629 99% 67
2a01:c9c0:b2::/48 Valid None 629 99% 67
2a01:c9c0:b3::/48 Valid None 629 99% 67
2a01:c9c0:b4::/48 Valid None 629 99% 67
2a01:c9c0:b5::/48 Valid None 629 99% 67
2a01:c9c0:b6::/48 Valid None 629 99% 67
2a01:c9c0:b7::/48 Valid None 629 99% 67
2a01:c9c0:bf::/48 Valid None 629 99% 67
193.252.117.0/24 Valid RIR databaseRIPE 673 100% 67
193.252.118.0/24 Valid RIR databaseRIPE 673 100% 67
193.252.122.0/24 Valid RIR databaseRIPE 673 100% 67
193.252.123.0/24 Valid RIR databaseRIPE 673 100% 67

AS-SET

AS24600 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 9 are in fix.csv.

  • Route object: none9
ChangePrefix or setDetailFull-table peers
Route object: none193.252.121.0/24No route object for it. Add a route object with origin AS24600 in the RIR database for the space.673 of 673
Route object: none2a01:c9c0:b1::/48No route object for it. Add a route object with origin AS24600 in the RIR database for the space.629 of 636
Route object: none2a01:c9c0:b2::/48No route object for it. Add a route object with origin AS24600 in the RIR database for the space.629 of 636
Route object: none2a01:c9c0:b3::/48No route object for it. Add a route object with origin AS24600 in the RIR database for the space.629 of 636
Route object: none2a01:c9c0:b4::/48No route object for it. Add a route object with origin AS24600 in the RIR database for the space.629 of 636
Route object: none2a01:c9c0:b5::/48No route object for it. Add a route object with origin AS24600 in the RIR database for the space.629 of 636
Route object: none2a01:c9c0:b6::/48No route object for it. Add a route object with origin AS24600 in the RIR database for the space.629 of 636
Route object: none2a01:c9c0:b7::/48No route object for it. Add a route object with origin AS24600 in the RIR database for the space.629 of 636
Route object: none2a01:c9c0:bf::/48No route object for it. Add a route object with origin AS24600 in the RIR database for the space.629 of 636

Route objects not announced

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