29.11.2025 marko server planirana zamena diska u 23:00 bice offline 10-20 min. U 22:30 pokrenut full backup u slucaju kompikacija i kompletiran u 22:53 min. Server je bio offline 9 minuta. Zamena diska uspesna.
8/24/2025 neda server offline at 20:40 - problem solved. The server was offline for 30 min.
7/17/2025 s4rs disk replacement NVMe SSD from the raid at 11:00 p.m. downtime is expected for a couple of minutes.
Disk replacement to s5rs NVMe SSD from raid. 2.7.2025 at 23:10. After booting, it was the second disk that was correct. The server is currently offline. Both disks have crashed without the possibility of recovery. New ones are being installed and new ones are being installed, everything is being restored from the last restore from 18 hours ago.
12.6.2025 s4rs scheduled replacement NVMe SSD from radio 13.6.2025 at 23:30. A few minutes of downtime is expected.
1.6.2025 Completed transfer.
1.6.2025 The server migration from the old s1rs to two new servers was started.
16.5.2025 Preparations have begun for the migration of users from the s1rs server to the new server in order to enable the smooth and reliable operation of the server, considering that the current one has an older version of cPanel that no longer receives new updates.
5/5/2025 Server s9rs offline from 21:22. Unfixed hardware problem where the fuse has blown. Downtime 53 minutes.
28.3.2025 Server s9rs scheduled replacement of the second disk at 11:30 p.m. Downtime 7 min.
3/25/2025 Server s9rs scheduled disk replacement at 11:00 p.m. Downtime was 8 min
25.3.2025 Backup server 2 is offline.
3/17/2025 The data center scheduled the replacement of the motherboard on the s7rs server. Expect downtime from 30 to 40 min. The replacement will be made: 2 April 2025, 08:00 GMT+2 to 12:00 GMT+2
14.3.2025 The announced transfer on 20.2.2025 to the new server s10 with s3net has been completed. An email notification was sent to the clients and the nameservers on the main domains were changed.
On February 21, 2025, s2rs scheduled a disk replacement at 11:00 p.m., a new one was installed and the downtime was 30 min.
20.2.2025 The s10rs server is ready for the transfer of accounts from s3net, an email notification has been sent to users.
November 6, 2024 The NVMe SSD on the s2rs server, which is in software raid, was replaced. It starts at 23:00 CET. Offline lasted 4 minutes, after which the new SSD was synchronized with the old one and there were no further problems and interruptions.
6.11.2024 DNS on s2net was shut down and domains that were not purchased from us and did not change the nameserver or IP address stopped working. The s2net server will remain active until November 14, 2024, when it will be completely shut down.
1/11/2024 All accounts from s2net were transferred to the new s9rs, there were no interruptions in work or offline. All domains that were purchased from us were automatically changed nameservers to new ones.
7/16/2024 MySQL was offline on the s4rs server for 2 hours until 9:30 when the doso server is online. At the beginning, it showed a problem with the database to some clients and later to everyone until the moment of resolution. During the day, the server was unstable in the sense that it used to be slow and on a couple of occasions it was offline for a few minutes to 5 minutes. The reason for this is that the system administrator was checking the server, which is why the CPU was high. At 11 o'clock the server was under a hardware check by the data center at our request to ensure that the server is working properly and there are no unforeseen situations at that moment the server was offline for 4 hours where they found a problem with cooling the CPU which was the cause of the high CPU. The problem was solved and since then the server has been working stably.
23.4.2024 Short offline on server s4 2 min. Apr 23 2024 01:13 PM (EU/Central) to Apr 23 2024 01:15 PM (EU/Central).
While email stopped working since Apr 23 2024 01:13 PM (EU/Central) ie email ports were partially blocked due to DDOS attack until around 9:00PM (EU/Central). Sites work without problems regardless of DDOS attack.
3/17/2024 Due to the upgrade of the mysql database on the s2rs server, the mysql server was offline while the server was online.
11/6/2023 S4 had Switch problem, downtime was 5 minutes.
12.10.2023 Replacement of the NVMe SSD drive that did not work on the s5rs server downtime 1 min.
7.10.2023 MariaDB 10.3 => 10.6 upgrade on s1rs server without downtime
3.10.2023 Big DDOS on server s4rs from 20:15-21:20, downtime was not constant but lasted 1 hour, after which the problem was solved.
18.9.2023. Planning to upgrade MySQL and MariaDB databases from 5.7 and 10.3 to the latest available. The exact date of the upgrade will be highlighted here and clients on which servers will be upgraded will be notified separately.
The servers to be updated are s3rs 5.7 => 8, s2rs 5.7 => 8, s1rs 10.3 => 10.5, s4n 5.7 => 8, s3n 5.7 => 8, s2n 5.7 => 8
6/9/2023 Downtime on server s1 of 2 minutes. from 12:37 to 12:39
12.1.2022 Temporary and short problem with DNS, some sites were offline for a few minutes.
1/1/2023 s3 and s2 Installed Imunify360 and kernelcare as well as software update and reboot, offline less than 1 min.
31.12.2022 s4rs s3rs s2rs s1rs s4 Installed Imunify360 and kernelcare as well as software update and reboot, offline less than 1 min.
20.7.2022 23:30 - 04:00 - s3 The server was offline due to a complete hardware check.
2.4.2022 11:00 - s2 - Jetbackup and restart No downtime