bgpreport

Network · data from 2026-11-12

AS210770 OCTOPUCE-LYON Octopuce s.a.r.l.

Registry name: OCTOPUCE-LYON Octopuce s.a.r.l., FR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS210770, 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.215.171.0/24 No ROA RIR databaseRIPE 672 100% 66
2a00:99a0:f000::/48 No ROA RIR databaseRIPE 635 100% 67

AS-SET

AS210770 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 2 are in fix.csv.

  • ROA: none2
ChangePrefix or setDetailFull-table peers
ROA: none185.215.171.0/24No ROA covers it. Add a ROA for AS210770, maxLength 24.672 of 673
ROA: none2a00:99a0:f000::/48No ROA covers it. Add a ROA for AS210770, maxLength 48.635 of 636

Route objects not announced

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