Network · data from 2026-11-12
AS41469 TECOS-AS ZSRCT TECOS Ltd.
Registry name: TECOS-AS ZSRCT TECOS Ltd., RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS41469, 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.
| 89.250.224.0/20 | No ROA | RIR databaseRIPE | 673 100% |
| 89.250.224.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 89.250.225.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 89.250.226.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 89.250.227.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 89.250.228.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 89.250.229.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 89.250.230.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 89.250.231.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 89.250.232.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 89.250.233.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 89.250.234.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 89.250.235.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 89.250.236.0/24 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS41469 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 18 are in fix.csv.
- ROA: none14
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 89.250.224.0/20 | No ROA covers it. Add a ROA for AS41469, maxLength 20. |
| ROA: none | 89.250.224.0/24 | No ROA covers it. Add a ROA for AS41469, maxLength 24. |
| ROA: none | 89.250.225.0/24 | No ROA covers it. Add a ROA for AS41469, maxLength 24. |
| ROA: none | 89.250.226.0/24 | No ROA covers it. Add a ROA for AS41469, maxLength 24. |
| ROA: none | 89.250.227.0/24 | No ROA covers it. Add a ROA for AS41469, maxLength 24. |
| ROA: none | 89.250.228.0/24 | No ROA covers it. Add a ROA for AS41469, maxLength 24. |
| ROA: none | 89.250.229.0/24 | No ROA covers it. Add a ROA for AS41469, maxLength 24. |
| ROA: none | 89.250.230.0/24 | No ROA covers it. Add a ROA for AS41469, maxLength 24. |
| ROA: none | 89.250.231.0/24 | No ROA covers it. Add a ROA for AS41469, maxLength 24. |
| ROA: none | 89.250.232.0/24 | No ROA covers it. Add a ROA for AS41469, maxLength 24. |
| ROA: none | 89.250.233.0/24 | No ROA covers it. Add a ROA for AS41469, maxLength 24. |
| ROA: none | 89.250.234.0/24 | No ROA covers it. Add a ROA for AS41469, maxLength 24. |
| ROA: none | 89.250.235.0/24 | No ROA covers it. Add a ROA for AS41469, maxLength 24. |
| ROA: none | 89.250.236.0/24 | No ROA covers it. Add a ROA for AS41469, maxLength 24. |
Route objects not announced
Route objects with origin AS41469 whose prefix no peer sees AS41469 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.250.224.0/22 | RADB | No ROA |
| 89.250.237.0/24 | RIPE | No ROA |
| 89.250.238.0/24 | RIPE | No ROA |
| 89.250.239.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.