Network · data from 2026-11-12
AS47600 RUBIX DATACENTER
Registry name: RUBIXDATACENTER RUBIX DATACENTER SAS, FR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS47600, 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.
| 82.138.75.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 217.71.122.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 80.245.56.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 82.129.65.0/24 | No ROA | RIR databaseRIPE | 670 100% |
| 2a13:cac0::/48 | Valid | Nonecovered by 2a13:cac0::/29 | 421 66% |
| 80.245.58.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 82.138.86.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.45.150.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.71.114.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 80.91.89.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
PeeringDB's irr_as_set for AS47600: AS47600:AS-RUBIX. 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 (AS47600 isn't in the set, or no route object for AS47600 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 | AS47600 in it | Not covered |
|---|---|---|---|---|---|
| AS47600:AS-RUBIX | RIPE | 4 | 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 6 are in fix.csv.
- ROA: none4
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 82.138.75.0/24 | No ROA covers it. Add a ROA for AS47600, maxLength 24. |
| ROA: none | 217.71.122.0/24 | No ROA covers it. Add a ROA for AS47600, maxLength 24. |
| ROA: none | 80.245.56.0/24 | No ROA covers it. Add a ROA for AS47600, maxLength 24. |
| ROA: none | 82.129.65.0/24 | No ROA covers it. Add a ROA for AS47600, maxLength 24. |
| Route object: none | 2a13:cac0::/48 | No route object for it. A route object for 2a13:cac0::/29 with origin AS47600 covers it (filters allowing more-specifics accept it). Add a route object with origin AS47600 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS47600 whose prefix no peer sees AS47600 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a13:cac0::/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.