bgpreport

Network · data from 2026-11-12

AS35012 PICTIME-AS Claranet SAS

Registry name: PICTIME-AS Claranet SAS, FR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS35012, 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.
185.129.167.0/24 Valid Nonecovered by 185.129.164.0/22 672 100% 67
46.17.64.0/21 Valid RIR databaseRIPE 673 100% 66
91.195.164.0/23 Valid RIR databaseRIPE 673 100% 66
185.129.164.0/22 Valid RIR databaseRIPE 673 100% 66
193.238.148.0/22 Valid RIR databaseRIPE 673 100% 66
91.198.159.0/24 Valid RIR databaseRIPE 672 100% 66
193.58.233.0/24 Valid RIR databaseRIPE 672 100% 66
195.238.251.0/24 Valid RIR databaseRIPE 672 100% 66
2a00:6000::/32 Valid RIR databaseRIPE 635 100% 67

AS-SET

AS35012 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 1 are in fix.csv.

  • Route object: none1
ChangePrefix or setDetailFull-table peers
Route object: none185.129.167.0/24No route object for it. A route object for 185.129.164.0/22 with origin AS35012 covers it (filters allowing more-specifics accept it). Add a route object with origin AS35012 in the RIR database for the space.672 of 673

Route objects not announced

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