Network · data from 2026-11-12
AS42748 BYTECITY-AS OOO TRANSTELECOM
Registry name: BYTECITY-AS OOO TRANSTELECOM, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS42748, 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.
| 77.74.8.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 94.199.216.0/21 | No ROA | RIR databaseRIPE | 672 100% |
AS-SET
AS42748 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 16 are in fix.csv.
- ROA: none2
- Route object: not announced14
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 77.74.8.0/21 | No ROA covers it. Add a ROA for AS42748, maxLength 21. |
| ROA: none | 94.199.216.0/21 | No ROA covers it. Add a ROA for AS42748, maxLength 21. |
Route objects not announced
Route objects with origin AS42748 whose prefix no peer sees AS42748 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 77.74.8.0/24 | RIPE | No ROA |
| 77.74.9.0/24 | RIPE | No ROA |
| 77.74.10.0/24 | RIPE | No ROA |
| 77.74.11.0/24 | RIPE | No ROA |
| 77.74.12.0/24 | RIPE | No ROA |
| 77.74.13.0/24 | RIPE | No ROA |
| 77.74.14.0/24 | RIPE | No ROA |
| 77.74.15.0/24 | RIPE | No ROA |
| 94.199.216.0/24 | RIPE | No ROA |
| 94.199.217.0/24 | RIPE | No ROA |
| 94.199.218.0/24 | RIPE | No ROA |
| 94.199.219.0/24 | RIPE | No ROA |
| 94.199.220.0/24 | RIPE | No ROA |
| 94.199.221.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.