Network · data from 2026-11-12

AS201080 SCANI

Registry name: AS-SCANI Societe Cooperative D'amenagement Numerique Icaunaise SCIC, FR · PeeringDB

9IPv4 routes 88.9% RPKI valid · 88.9% with a route object

2IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

1No 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 AS201080, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS201080, 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.239.76.0/22	No ROA	RIR databaseRIPE	672 100%	66
37.60.156.0/24	Valid	Nonecovered by 37.60.156.0/23	672 100%	66
37.60.156.0/23	Valid	RIR databaseRIPE	672 100%	66
185.167.16.0/22	Valid	RIR databaseRIPE	672 100%	66
194.146.205.0/24	Valid	RIR databaseRIPE	672 100%	66
194.146.206.0/23	Valid	RIR databaseRIPE	672 100%	66
37.60.155.0/24	Valid	RIR databaseRIPE	671 100%	66
37.60.157.0/24	Valid	RIR databaseRIPE	671 100%	66
37.60.158.0/24	Valid	RIR databaseRIPE	671 100%	66
2a0b:3200::/30	Valid	RIR databaseRIPE	634 100%	67
2a0b:3200::/31	Valid	RIR databaseRIPE	634 100%	67

AS-SET

PeeringDB's irr_as_set for AS201080: AS-SCANI. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS201080 isn't in the set, or no route object for AS201080 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

Name	Database	ASNs	Sets	Route objects	AS201080 in it	Not covered
AS-SCANI	RIPE	2	1	12	Yes	0

Name

Database

ASNs

Sets

Route objects

AS201080 in it

Not covered

AS-SCANI

RIPE

Yes

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: none1
Route object: none1

Change	Prefix or set	Detail	Full-table peers
ROA: none	193.239.76.0/22	No ROA covers it. Add a ROA for AS201080, maxLength 22.	672 of 673
Route object: none	37.60.156.0/24	No route object for it. A route object for 37.60.156.0/23 with origin AS201080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201080 in the RIR database for the space.	672 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

193.239.76.0/22

No ROA covers it. Add a ROA for AS201080, maxLength 22.

672 of 673

Route object: none

37.60.156.0/24

No route object for it. A route object for 37.60.156.0/23 with origin AS201080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS201080 in the RIR database for the space.

672 of 673

Route objects not announced

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