Support Notice
Temporary loss of IPv6 connectivity
DNS failure, lost reward - SLA approved with full compensation
Our IaaS is excelent, but nothing is perfect: 3h downtime across all servers
June Compensations for Super and Secure nodes
Lack of IPv6 connectivity - Courtesy credit
Protection fault, 35 nodes off: full compensation + bonus to affected users
Fixing BC Cold Stake with EZ Masternodes
Server upgrade and dadfailed on child bug lead to some reward loss
EZ Masternodes is moving all its nodes from Dual E5-2650v2 128GB SSD servers to Dual E5-2650v2 256GB 3D SSD with Raid 0. During the process we had an IPv6 connectivity issue, after moving the nodes, in the new server, an Ubuntu confirmed bug did not allowed us to attach some IPv6 (dadfailed on child interface error). As result daemons that rely on IPv6 in the range 2602:ffc8:1:2::3:100/64 to 2602:ffc8:1:2::3:154/64 may endure reward loss, but we decide to compensate users.
The SAME Horizen Node goes rougue and claim 80GB of data in 1h
Miss configuration of 15 Horizen Daemons
One of our servers had a fault maintenance in the IO restriction. This lead to an initial lost of sync and later our attempt to solve the problem made it worse.
Some nodes in the range sv1541 to sv1555 will not be able to sync before 1 hour, and some not before 2 hours. So, it may lead to a rewad loss for some users.
Complete refund for endured losses will be performed upon user request.