Network · data from 2026-11-12
AS12670 AS-COMPLETEL Completel SAS
Registry name: AS-COMPLETEL Completel SAS, FR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS12670, 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.
| 193.160.131.0/24 | No ROA | RIR databaseRIPE | 672 100% |
| 80.231.9.0/24 | Valid | None | 671 100% |
AS-SET
AS12670 isn't in PeeringDB, where networks name their AS-SET.
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 22 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced20
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 193.160.131.0/24 | No ROA covers it. Add a ROA for AS12670, maxLength 24. |
| Route object: none | 80.231.9.0/24 | No route object for it. Add a route object with origin AS12670 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS12670 whose prefix no peer sees AS12670 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.199.233.0/24 | RIPE | No ROA |
| 91.231.139.0/24 | RIPE | No ROA |
| 148.169.0.0/16 | RIPE | No ROA |
| 148.169.1.0/24 | RIPE | No ROA |
| 171.16.0.0/16 | RIPE | No ROA |
| 171.16.2.0/24 | RIPE | No ROA |
| 171.16.3.0/24 | RIPE | No ROA |
| 171.16.4.0/24 | RIPE | No ROA |
| 171.16.200.0/21 | RIPE | No ROA |
| 171.16.209.0/24 | RIPE | No ROA |
| 171.16.210.0/23 | RIPE | No ROA |
| 171.16.216.0/21 | RIPE | No ROA |
| 171.16.251.0/24 | RIPE | No ROA |
| 171.16.253.0/24 | RIPE | No ROA |
| 185.204.172.0/22 | RIPE | Valid |
| 192.93.7.0/24 | RIPE | No ROA |
| 193.22.92.0/24 | RIPE | No ROA |
| 194.119.98.0/24 | RIPE | No ROA |
| 195.190.156.0/24 | RIPE | No ROA |
| 195.216.242.0/24 | 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.