Network · data from 2026-11-12
AS208890 RCK STATE UNITARY ENTERPRISE OF THE LUGANSK PEOPLE'S REPUBLIC "LUGANSK COMMUNICATIONS"
Registry name: RCK STATE UNITARY ENTERPRISE OF THE LUGANSK PEOPLE'S REPUBLIC "LUGANSK COMMUNICATIONS", RU · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS208890, 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.
| 46.16.33.0/24 | Invalid: origin | Other origin only | 127 19% |
| 193.228.163.0/24 | Valid | None | 673 100% |
| 193.228.162.0/24 | Valid | RIR databaseRIPE | 673 100% |
AS-SET
AS208890 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 3 are in fix.csv.
- ROA: origin1
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 46.16.33.0/24 | ROAs covering it name AS43201, not AS208890. If AS208890 should announce it, add a ROA for AS208890. |
| Route object: none | 46.16.33.0/24 | Route objects for it name AS43201. Add a route object with origin AS208890 in the RIR database for the space. |
| Route object: none | 193.228.163.0/24 | No route object for it. Add a route object with origin AS208890 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS208890 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.