Network · data from 2026-11-12
AS6877 AS6877 JSC "Ukrtelecom"
Registry name: AS6877 JSC "Ukrtelecom", UA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS6877, 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.
| 94.178.0.0/15 | No ROA | Other origin only | 651 97% |
| 213.186.96.0/19 | No ROA | Other origin only | 651 97% |
| 37.52.0.0/14 | No ROA | Other origin only | 650 97% |
AS-SET
AS6877 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.
- ROA: none3
- Route object: none3
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 94.178.0.0/15 | No ROA covers it. Add a ROA for AS6877, maxLength 15. |
| Route object: none | 94.178.0.0/15 | Route objects for it name AS6849. Add a route object with origin AS6877 in the RIR database for the space. |
| ROA: none | 213.186.96.0/19 | No ROA covers it. Add a ROA for AS6877, maxLength 19. |
| Route object: none | 213.186.96.0/19 | Route objects for it name AS6849. Add a route object with origin AS6877 in the RIR database for the space. |
| ROA: none | 37.52.0.0/14 | No ROA covers it. Add a ROA for AS6877, maxLength 14. |
| Route object: none | 37.52.0.0/14 | Route objects for it name AS6849. Add a route object with origin AS6877 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS6877 whose prefix no peer sees AS6877 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 37.52.224.0/20 | RIPE | No ROA |
| 94.178.0.0/17 | RIPE | No ROA |
| 213.186.96.0/20 | RIPE | No ROA |
| 2a02:28d0::/32 | 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.