Network · data from 2026-11-12
AS12826 Cyllene
Registry name: CYLLENE-ITS CYLLENE ITS SAS, FR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS12826, 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.
| 91.151.74.0/24 | Valid | Nonecovered by 91.151.64.0/20 | 668 99% |
| 91.151.64.0/20 | Valid | RIR databaseRIPE | 670 100% |
| 91.151.64.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.55.164.0/22 | Valid | RIR databaseRIPE | 670 100% |
| 81.80.237.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 185.23.132.0/23 | Valid | RIR databaseRIPE | 669 99% |
| 185.100.193.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 195.101.158.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 91.151.65.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 91.151.66.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 91.151.67.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 91.151.68.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 91.151.69.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 91.151.70.0/23 | Valid | RIR databaseRIPE | 668 99% |
| 91.151.72.0/23 | Valid | RIR databaseRIPE | 668 99% |
| 91.151.76.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 91.151.77.0/24 | Valid | RIR databaseRIPE | 668 99% |
| 2a00:ef60::/32 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS12826: RIPE::AS-CETSI. 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 (AS12826 isn't in the set, or no route object for AS12826 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 | AS12826 in it | Not covered |
|---|---|---|---|---|---|
| RIPE::AS-CETSI | RIPE | 2 | 1 | Yes | 0 |
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 7 are in fix.csv.
- Route object: none1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 91.151.74.0/24 | No route object for it. A route object for 91.151.64.0/20 with origin AS12826 covers it (filters allowing more-specifics accept it). Add a route object with origin AS12826 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS12826 whose prefix no peer sees AS12826 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.151.75.0/24 | RIPE | Invalid: maxLength |
| 91.151.78.0/24 | RIPE | Invalid: maxLength |
| 91.151.79.0/24 | RIPE | Invalid: maxLength |
| 185.23.132.0/24 | RIPE | Valid |
| 185.23.133.0/24 | RIPE | Valid |
| 194.31.195.0/24 | RADB, RIPE | Valid |
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.