Network · data from 2026-11-12
AS31077 UMK LLC Universalna Merezheva Kompaniya
Registry name: UMK LLC Universalna Merezheva Kompaniya, UA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS31077, 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.
| 31.172.138.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 91.192.184.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 92.60.180.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 92.60.182.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 92.60.185.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 92.60.186.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 193.239.217.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.110.132.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.110.137.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 212.110.154.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.20.168.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 217.20.173.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.20.174.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.20.176.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 217.20.182.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 217.20.186.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.20.189.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.20.190.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 80.92.224.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 80.92.226.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 80.92.236.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 128.0.168.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 128.0.171.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS31077 isn't in PeeringDB, where networks name their AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS31077 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.