Data as of Nov 12, 2026

77.123.136.0/22

No anonymizer space · no proxy exits in 30 days

Volia-Cable LLC · space held by Limited Liability Company "KYIVSKI TELEKOMUNIKATSIYNI MEREZHI"

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
77.123.128.0/1816,384UA-VOLIA-20061124Limited Liability Company "KYIVSKI TELEKOMUNIKATSIYNI MEREZHI" (ORG-VI4-RIPE) · UAALLOCATED PAJul 16, 2024abuse@volia.net
└ 77.123.128.0/198,192VOLIA-DCVolia DataCentreLIR-PARTITIONED PAJan 18, 2011abuse@volia.net
via UA-VOLIA-20061124
└ 77.123.136.32/2816DCV-indomusunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.136.48/2816DCV-yukonunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.136.128/2816DCV-smtlogistikunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.137.16/298DCV-pklebaner_1unknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.137.24/298DCV-mistoinformunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.137.48/298DCV-eqviaunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.137.88/298DCV-sun2000unknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.137.96/2816DCV-overseerunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.137.112/298DCV-vid-adminunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.137.128/2816DCV-vsesezonkaunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.137.144/298DCV-teploarmaturaunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.137.152/298DCV-968439unknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.137.160/298DCV-hvostingunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.137.192/298DCV-mgreen2021unknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.137.216/298DCV-sun2000unknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.137.232/298DCV-lux_oknaunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.137.240/298DCV-desireunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.137.248/298DCV-nbchunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.138.8/298DCV-968439unknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.138.16/298DCV-968439unknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.138.24/298DCV-iukraineunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.138.40/298DCV-cityhostunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.138.48/298DCV-952422unknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.138.56/298DCV-sherlunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.138.64/298DCV-hvostingunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.138.88/298DCV-vituaunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.138.120/298DCV-yamkovoyunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.138.128/298DCV-addunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.138.144/298DCV-nutricunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.138.176/298DCV-teploarmaturaunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.138.200/298DCV-tuthost_fopunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.138.216/298DCV-rcstelmunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.138.224/298DCV-globus-serviceunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.138.232/298DCV-ria1unknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.138.240/298DCV-redscloudunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.139.8/298DCV-redscloudunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.139.16/298DCV-rcstelmunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.139.40/298DCV-owlprotectunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.139.64/2816DCV-redscloudunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.139.144/298DCV-jeckyunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.139.160/298DCV-968439unknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.139.176/298DCV-sun2000unknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.139.200/298DCV-968439unknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.139.216/298DCV-sbasatelitunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.139.224/298DCV-yakobchukunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.139.232/298DCV-aroundunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.139.240/298DCV-sbasatelitunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC
└ 77.123.139.248/298DCV-yakobchukunknownASSIGNED PAJul 24, 2023abuse@volia.net
via VOLIA-DC

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Who has announced this prefix

Summary

Routing history

Pattern
Stable
First seen
Jun 2017
Current origin since
Nov 2021 · 5.0 yr
Origin networks
2
Last change of origin
Nov 2021
Recorded history

History

Handoffs
1