Network · data from 2026-11-12
AS203596 Celya AS203596
Registry name: CELYA CELYA SAS, FR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS203596, 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.122.100.0/24 | Valid | Nonecovered by 185.122.100.0/22 | 673 100% |
| 185.122.101.0/24 | Valid | Nonecovered by 185.122.100.0/22 | 673 100% |
| 185.122.103.0/24 | Valid | Nonecovered by 185.122.100.0/22 | 673 100% |
| 185.222.90.0/24 | Valid | Nonecovered by 185.222.88.0/22 | 673 100% |
| 185.222.91.0/24 | Valid | Nonecovered by 185.222.88.0/22 | 673 100% |
| 185.122.102.0/24 | Valid | Nonecovered by 185.122.100.0/22 | 672 100% |
| 2a06:a400:13::/48 | Valid | Nonecovered by 2a06:a400::/29 | 635 100% |
| 2a06:a402::/32 | Valid | Nonecovered by 2a06:a400::/29 | 1 0%low visibility |
| 91.213.223.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.216.15.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.14.176.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.14.178.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.222.88.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.222.89.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.108.216.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.109.0.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.109.1.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.109.2.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.109.3.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a06:a400:20::/44 | Valid | RIR databaseRIPE | 636 100% |
| 2a06:a400:22::/48 | Valid | RIR databaseRIPE | 636 100% |
| 2a06:a400:23::/48 | Valid | RIR databaseRIPE | 636 100% |
| 185.122.100.0/22 | Valid | RIR databaseRIPE | 8 1%low visibility |
| 185.222.88.0/22 | Valid | RIR databaseRIPE | 8 1%low visibility |
| 91.216.39.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
| 2a06:a400::/29 | Valid | RIR databaseRIPE | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS203596: AS-CELYA. 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 (AS203596 isn't in the set, or no route object for AS203596 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 | AS203596 in it | Not covered |
|---|---|---|---|---|---|
| AS-CELYA | 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 10 are in fix.csv.
- Route object: none8
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 185.122.100.0/24 | No route object for it. A route object for 185.122.100.0/22 with origin AS203596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203596 in the RIR database for the space. |
| Route object: none | 185.122.101.0/24 | No route object for it. A route object for 185.122.100.0/22 with origin AS203596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203596 in the RIR database for the space. |
| Route object: none | 185.122.103.0/24 | No route object for it. A route object for 185.122.100.0/22 with origin AS203596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203596 in the RIR database for the space. |
| Route object: none | 185.222.90.0/24 | No route object for it. A route object for 185.222.88.0/22 with origin AS203596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203596 in the RIR database for the space. |
| Route object: none | 185.222.91.0/24 | No route object for it. A route object for 185.222.88.0/22 with origin AS203596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203596 in the RIR database for the space. |
| Route object: none | 185.122.102.0/24 | No route object for it. A route object for 185.122.100.0/22 with origin AS203596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203596 in the RIR database for the space. |
| Route object: none | 2a06:a400:13::/48 | No route object for it. A route object for 2a06:a400::/29 with origin AS203596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203596 in the RIR database for the space. |
| Route object: none | 2a06:a402::/32 | No route object for it. A route object for 2a06:a400::/29 with origin AS203596 covers it (filters allowing more-specifics accept it). Add a route object with origin AS203596 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS203596 whose prefix no peer sees AS203596 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 193.109.1.128/25 | RIPE | Invalid: maxLength |
| 2a0d:f000::/29 | RIPE | No ROA |
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.