Network · data from 2026-11-12
AS61276 EKACOD-AS Vichislitelniy Centr Ltd.
Registry name: EKACOD-AS Vichislitelniy Centr Ltd., RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61276, 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.
| 62.76.31.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 62.76.72.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 185.189.192.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 194.85.218.0/24 | No ROA | RIR databaseRIPE | 673 100% |
| 46.149.172.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 91.190.156.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 93.171.206.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 138.16.137.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 141.101.196.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 193.47.41.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 37.18.21.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 2a11:6380::/32 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
AS61276 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 4 are in fix.csv.
- ROA: none4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 62.76.31.0/24 | No ROA covers it. Add a ROA for AS61276, maxLength 24. |
| ROA: none | 62.76.72.0/24 | No ROA covers it. Add a ROA for AS61276, maxLength 24. |
| ROA: none | 185.189.192.0/24 | No ROA covers it. Add a ROA for AS61276, maxLength 24. |
| ROA: none | 194.85.218.0/24 | No ROA covers it. Add a ROA for AS61276, maxLength 24. |
Route objects not announced
Every route object with origin AS61276 is announced.
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.