Network · data from 2026-11-12
AS206002 Scalair SAS
Registry name: SCALAIR-FR Scalair SAS, FR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS206002, 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.199.103.37/32 | Invalid: maxLength | Nonecovered by 91.199.103.0/24 | 0 0%low visibility |
| 91.199.103.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 95.111.135.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.140.221.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.140.222.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.140.223.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.187.28.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 2a0b:9380::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a14:a580:1::/48 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS206002: AS206002:AS-SCALAIR. 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 (AS206002 isn't in the set, or no route object for AS206002 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 | AS206002 in it | Not covered |
|---|---|---|---|---|---|
| AS206002:AS-SCALAIR | RIPE | 1 | 1 | Yes | 1 |
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 6 are in fix.csv.
- ROA: maxLength1
- Route object: none1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 91.199.103.37/32 | ROA 91.199.103.0/24 AS206002 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 91.199.103.37/32. |
| Route object: none | 91.199.103.37/32 | No route object for it. A route object for 91.199.103.0/24 with origin AS206002 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS206002 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS206002 whose prefix no peer sees AS206002 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.187.28.0/24 | RIPE | Invalid: maxLength |
| 185.187.29.0/24 | RIPE | Invalid: maxLength |
| 185.187.30.0/24 | RIPE | Invalid: maxLength |
| 185.187.31.0/24 | RIPE | Invalid: maxLength |
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.