Network · data from 2026-11-12
AS215114 SLBCLOUD
Registry name: PLB-NET Stevan Durand--L'Hours t/a SLBCLOUD, FR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS215114, 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.
| 2a06:5fc0::/29 | Invalid: origin | None | 1 0%low visibility |
| 109.205.8.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 151.240.100.0/24 | Valid | RIR databaseRADB, RIPE | 673 100% |
| 141.11.5.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 96.62.111.0/24 | Valid | RIR databaseRADB, RIPE | 670 100% |
| 151.240.30.0/24 | Valid | RIR databaseRADB, RIPE | 661 98% |
| 139.28.99.0/24 | Valid | RIR databaseRIPE | 658 98% |
| 89.150.49.0/24 | Valid | RIR databaseRIPE | 653 97% |
| 82.26.80.0/24 | Valid | RIR databaseRADB, RIPE | 652 97% |
| 2a12:bec4:1190::/44 | Valid | RIR databaseRIPE | 635 100% |
| 2a13:9500:145::/48 | Valid | RIR databaseRIPE | 635 100% |
| 2a13:bfc2::/32 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS215114: AS215114:AS-SLBCLOUD. 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 (AS215114 isn't in the set, or no route object for AS215114 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 | AS215114 in it | Not covered |
|---|---|---|---|---|---|
| AS215114:AS-SLBCLOUD | RIPElists itself further down3 member sets in no database: AS-PIXOOF, AS-VERSADC, AS199746:AS-NEXTSERV | 841 | 107 | 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 8 are in fix.csv.
- ROA: origin1
- Route object: none1
- AS-SET: missing member3
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2a06:5fc0::/29 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS215114 should announce it, add a ROA for AS215114. |
| Route object: none | 2a06:5fc0::/29 | No route object for it. Add a route object with origin AS215114 in the RIR database for the space. |
| AS-SET: missing member | AS215114:AS-SLBCLOUD | AS215114:AS-SLBCLOUD (RIPE) lists AS-PIXOOF; no IRR database read has it. |
| AS-SET: missing member | AS215114:AS-SLBCLOUD | AS215114:AS-SLBCLOUD (RIPE) lists AS-VERSADC; no IRR database read has it. |
| AS-SET: missing member | AS215114:AS-SLBCLOUD | AS215114:AS-SLBCLOUD (RIPE) lists AS199746:AS-NEXTSERV; no IRR database read has it. |
Route objects not announced
Route objects with origin AS215114 whose prefix no peer sees AS215114 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 82.47.159.0/24 | RADB, RIPE | Valid |
| 164.37.195.0/24 | RADB, RIPE | Valid |
| 2a13:9500:17d::/48 | 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.