Network · data from 2026-11-12
AS210771 Setel_Conecta SETEL CONECTA S.L.
Registry name: Setel_Conecta SETEL CONECTA S.L., ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS210771, 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.208.147.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.252.5.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.208.144.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.208.145.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.252.6.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.208.146.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS210771 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 1 are in fix.csv.
- Route object: not announced1
Route objects not announced
Route objects with origin AS210771 whose prefix no peer sees AS210771 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.252.7.0/24 | 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.