Network · data from 2026-11-12
AS49173 ASN-TELECABLE Telecable Almonte, S.L.
Registry name: ASN-TELECABLE Telecable Almonte, S.L., ES · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49173, 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.
| 194.146.28.0/24 | Invalid: maxLength | Nonecovered by 194.146.28.0/22 | 80 12% |
| 194.146.29.0/24 | Invalid: maxLength | Nonecovered by 194.146.28.0/22 | 80 12% |
| 194.146.30.0/24 | Invalid: maxLength | Nonecovered by 194.146.28.0/22 | 80 12% |
| 194.146.31.0/24 | Invalid: maxLength | Nonecovered by 194.146.28.0/22 | 80 12% |
| 185.141.242.0/24 | Valid | Nonecovered by 185.141.240.0/22 | 673 100% |
| 194.146.28.0/22 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS49173 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 12 are in fix.csv.
- ROA: maxLength4
- Route object: none5
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 194.146.28.0/24 | ROA 194.146.28.0/22 AS49173 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 194.146.28.0/24. |
| Route object: none | 194.146.28.0/24 | No route object for it. A route object for 194.146.28.0/22 with origin AS49173 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49173 in the RIR database for the space. |
| ROA: maxLength | 194.146.29.0/24 | ROA 194.146.28.0/22 AS49173 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 194.146.29.0/24. |
| Route object: none | 194.146.29.0/24 | No route object for it. A route object for 194.146.28.0/22 with origin AS49173 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49173 in the RIR database for the space. |
| ROA: maxLength | 194.146.30.0/24 | ROA 194.146.28.0/22 AS49173 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 194.146.30.0/24. |
| Route object: none | 194.146.30.0/24 | No route object for it. A route object for 194.146.28.0/22 with origin AS49173 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49173 in the RIR database for the space. |
| ROA: maxLength | 194.146.31.0/24 | ROA 194.146.28.0/22 AS49173 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 194.146.31.0/24. |
| Route object: none | 194.146.31.0/24 | No route object for it. A route object for 194.146.28.0/22 with origin AS49173 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49173 in the RIR database for the space. |
| Route object: none | 185.141.242.0/24 | No route object for it. A route object for 185.141.240.0/22 with origin AS49173 covers it (filters allowing more-specifics accept it). Add a route object with origin AS49173 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS49173 whose prefix no peer sees AS49173 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.26.252.0/22 | RIPE | Valid |
| 185.6.32.0/22 | RIPE | Valid |
| 185.141.240.0/22 | 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.