Network · data from 2026-11-12
AS42773 INTELCOM-UPSTREAM Nemerov Evgeniy Vladimirovish PE
Registry name: INTELCOM-UPSTREAM Nemerov Evgeniy Vladimirovish PE, RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS42773, 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.
| 164.215.64.0/24 | No ROA | RIR databaseRIPE | 673 100% |
AS-SET
AS42773 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 13 are in fix.csv.
- ROA: none1
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 164.215.64.0/24 | No ROA covers it. Add a ROA for AS42773, maxLength 24. |
Route objects not announced
Route objects with origin AS42773 whose prefix no peer sees AS42773 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.197.20.0/22 | RIPE | No ROA |
| 93.157.240.0/22 | RIPE | No ROA |
| 164.215.64.0/21 | RIPE | No ROA |
| 164.215.64.0/22 | RIPE | No ROA |
| 164.215.65.0/24 | RIPE | No ROA |
| 164.215.66.0/24 | RIPE | No ROA |
| 164.215.67.0/24 | RIPE | No ROA |
| 164.215.68.0/24 | RIPE | No ROA |
| 164.215.69.0/24 | RIPE | No ROA |
| 164.215.70.0/23 | RIPE | No ROA |
| 164.215.70.0/24 | RIPE | No ROA |
| 164.215.71.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.