Network · data from 2026-11-12
AS28058 AS28058 - Stealth Telecom del Ecuador
Registry name: AS28058 - Stealth Telecom del Ecuador, EC · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS28058, 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.
| 179.60.48.0/23 | Valid | Nonecovered by 179.60.48.0/20 | 672 100% |
| 179.60.50.0/24 | Valid | Nonecovered by 179.60.48.0/20 | 671 100% |
| 200.105.114.0/23 | Valid | Nonecovered by 200.105.112.0/21 | 671 100% |
| 200.105.118.0/23 | Valid | Nonecovered by 200.105.112.0/21 | 671 100% |
| 200.105.112.0/23 | Valid | Nonecovered by 200.105.112.0/21 | 661 98% |
| 200.105.116.0/23 | Valid | Other IRR onlyRADB | 671 100% |
| 200.105.112.0/21 | Valid | RIR databaseLACNIC, RADB | 663 99% |
AS-SET
AS28058 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 10 are in fix.csv.
- Route object: none5
- Route object: RIR1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 179.60.48.0/23 | No route object for it. A route object for 179.60.48.0/20 with origin AS28058 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28058 in the RIR database for the space. |
| Route object: none | 179.60.50.0/24 | No route object for it. A route object for 179.60.48.0/20 with origin AS28058 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28058 in the RIR database for the space. |
| Route object: none | 200.105.114.0/23 | No route object for it. A route object for 200.105.112.0/21 with origin AS28058 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28058 in the RIR database for the space. |
| Route object: none | 200.105.118.0/23 | No route object for it. A route object for 200.105.112.0/21 with origin AS28058 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28058 in the RIR database for the space. |
| Route object: none | 200.105.112.0/23 | No route object for it. A route object for 200.105.112.0/21 with origin AS28058 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28058 in the RIR database for the space. |
| Route object: RIR | 200.105.116.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS28058 whose prefix no peer sees AS28058 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 179.60.48.0/20 | LACNIC, RADB | Valid |
| 2803:4c00::/32 | RADB | No ROA |
| 2803:4c00::/40 | RADB | No ROA |
| 2803:4c00:200::/40 | RADB | 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.