Network · data from 2026-11-12
AS49377 YTC-AS ARCTIC TELECOM Limited Liability Company
Registry name: YTC-AS ARCTIC TELECOM Limited Liability Company, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS49377, 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.
| 85.209.212.0/22 | No ROA | RIR databaseRIPE | 673 100% |
| 178.249.56.0/21 | No ROA | RIR databaseRIPE | 673 100% |
| 188.94.48.0/21 | No ROA | RIR databaseRIPE | 672 100% |
| 178.249.61.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.94.54.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.94.55.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 178.249.56.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 178.249.59.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 178.249.60.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 178.249.58.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 188.94.48.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 188.94.49.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 188.94.51.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 188.94.53.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 188.94.50.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 178.249.57.0/24 | Valid | RIR databaseRIPE | 4 1%low visibility |
AS-SET
AS49377 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 9 are in fix.csv.
- ROA: none3
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 85.209.212.0/22 | No ROA covers it. Add a ROA for AS49377, maxLength 22. |
| ROA: none | 178.249.56.0/21 | No ROA covers it. Add a ROA for AS49377, maxLength 21. |
| ROA: none | 188.94.48.0/21 | No ROA covers it. Add a ROA for AS49377, maxLength 21. |
Route objects not announced
Route objects with origin AS49377 whose prefix no peer sees AS49377 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 188.94.48.0/22 | RIPE | No ROA |
| 188.94.48.0/23 | RIPE | No ROA |
| 188.94.52.0/23 | RIPE | No ROA |
| 188.94.52.0/24 | RIPE | No ROA |
| 188.94.55.0/25 | RIPE | Invalid: maxLength |
| 188.94.55.128/25 | RIPE | Invalid: maxLength |
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.