Network · data from 2026-11-12
AS205170 TELINNOVA Four Mirror Advisors, S.L.
Registry name: TELINNOVA Four Mirror Advisors, S.L., ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS205170, 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.
| 2001:4030:8000::/33 | No ROA | None | 1 0%low visibility |
| 2001:4030:8000::/34 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
AS205170 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 4 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2001:4030:8000::/33 | No ROA covers it. Add a ROA for AS205170, maxLength 33. |
| Route object: none | 2001:4030:8000::/33 | No route object for it. Add a route object with origin AS205170 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS205170 whose prefix no peer sees AS205170 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.42.122.0/24 | RIPE | Valid |
| 2a03:bc80::/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.