Network · data from 2026-11-12
AS49893 BITRACE-TELECOM Bitrace telecom Ltd.
Registry name: BITRACE-TELECOM Bitrace telecom Ltd., RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49893, 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.22.128.0/19 | No ROA | RIR databaseRIPE | 673 100% |
| 89.22.128.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 89.22.136.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 89.22.143.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 89.22.144.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 89.22.145.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 89.22.152.0/21 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS49893 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 26 are in fix.csv.
- ROA: none7
- Route object: not announced19
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 89.22.128.0/19 | No ROA covers it. Add a ROA for AS49893, maxLength 19. |
| ROA: none | 89.22.128.0/21 | No ROA covers it. Add a ROA for AS49893, maxLength 21. |
| ROA: none | 89.22.136.0/21 | No ROA covers it. Add a ROA for AS49893, maxLength 21. |
| ROA: none | 89.22.143.0/24 | No ROA covers it. Add a ROA for AS49893, maxLength 24. |
| ROA: none | 89.22.144.0/21 | No ROA covers it. Add a ROA for AS49893, maxLength 21. |
| ROA: none | 89.22.145.0/24 | No ROA covers it. Add a ROA for AS49893, maxLength 24. |
| ROA: none | 89.22.152.0/21 | No ROA covers it. Add a ROA for AS49893, maxLength 21. |
Route objects not announced
Route objects with origin AS49893 whose prefix no peer sees AS49893 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 89.22.128.0/20 | RIPE | No ROA |
| 89.22.129.0/24 | RIPE | No ROA |
| 89.22.130.0/24 | RIPE | No ROA |
| 89.22.131.0/24 | RIPE | No ROA |
| 89.22.132.0/24 | RIPE | No ROA |
| 89.22.135.0/24 | RIPE | No ROA |
| 89.22.136.0/22 | RIPE | No ROA |
| 89.22.142.0/24 | RIPE | No ROA |
| 89.22.144.0/20 | RIPE | No ROA |
| 89.22.146.0/24 | RIPE | No ROA |
| 89.22.147.0/24 | RIPE | No ROA |
| 89.22.148.0/24 | RIPE | No ROA |
| 89.22.149.0/24 | RIPE | No ROA |
| 89.22.150.0/24 | RIPE | No ROA |
| 89.22.151.0/24 | RIPE | No ROA |
| 89.22.152.0/24 | RIPE | No ROA |
| 89.22.154.0/23 | RIPE | No ROA |
| 89.22.156.0/24 | RIPE | No ROA |
| 89.22.157.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.