Network · data from 2026-11-12
AS41106 teltel My Telecom Ltd.
Registry name: teltel My Telecom Ltd., RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS41106, 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.200.180.0/24 | No ROA | Nonecovered by 89.200.180.0/23 | 671 100% |
| 89.200.181.0/24 | No ROA | Nonecovered by 89.200.180.0/23 | 671 100% |
| 89.200.182.0/24 | No ROA | Nonecovered by 89.200.182.0/23 | 671 100% |
| 89.200.183.0/24 | No ROA | Nonecovered by 89.200.182.0/23 | 671 100% |
| 89.200.176.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 89.200.177.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 89.200.178.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 89.200.179.0/24 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS41106 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 14 are in fix.csv.
- ROA: none8
- Route object: none4
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 89.200.180.0/24 | No ROA covers it. Add a ROA for AS41106, maxLength 24. |
| Route object: none | 89.200.180.0/24 | No route object for it. A route object for 89.200.180.0/23 with origin AS41106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41106 in the RIR database for the space. |
| ROA: none | 89.200.181.0/24 | No ROA covers it. Add a ROA for AS41106, maxLength 24. |
| Route object: none | 89.200.181.0/24 | No route object for it. A route object for 89.200.180.0/23 with origin AS41106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41106 in the RIR database for the space. |
| ROA: none | 89.200.182.0/24 | No ROA covers it. Add a ROA for AS41106, maxLength 24. |
| Route object: none | 89.200.182.0/24 | No route object for it. A route object for 89.200.182.0/23 with origin AS41106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41106 in the RIR database for the space. |
| ROA: none | 89.200.183.0/24 | No ROA covers it. Add a ROA for AS41106, maxLength 24. |
| Route object: none | 89.200.183.0/24 | No route object for it. A route object for 89.200.182.0/23 with origin AS41106 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41106 in the RIR database for the space. |
| ROA: none | 89.200.176.0/24 | No ROA covers it. Add a ROA for AS41106, maxLength 24. |
| ROA: none | 89.200.177.0/24 | No ROA covers it. Add a ROA for AS41106, maxLength 24. |
| ROA: none | 89.200.178.0/24 | No ROA covers it. Add a ROA for AS41106, maxLength 24. |
| ROA: none | 89.200.179.0/24 | No ROA covers it. Add a ROA for AS41106, maxLength 24. |
Route objects not announced
Route objects with origin AS41106 whose prefix no peer sees AS41106 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.200.180.0/23 | RIPE | No ROA |
| 89.200.182.0/23 | 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.