Host Maintanances

There are 53 replies in this thread, which has been viewed 35,483 times. The last post (October 17, 2026 at 10:45 PM) was by Carbon.

  • Maintenance (FAST DOWNLOAD + MYSQL SERVER)

    Maintenance at backbone connection between Frankfurt - Helsinki


    Status: Investigating
    Affected systems: Backbone
    Start: 2021-11-08 22:00 UTC+0 – Ends on: 2021-11-09 05:00 UTC+0

    • Description

    In the above mentioned period, maintenance will be performed at the backbone connection between Frankfurt and Helsinki. This may lead to brief latency issues. We apologize for any inconvenience. Thank you for your understanding.

  • Hi,

    On September 24 (Saturday), at 02:00-03:00 AM, maintenance work will be carried out. In the mentioned interval, there will be periods when the servers offered will be affected intermittently.

    Greetings

  • NEW MAINTANANCE ANNOUNCEMENT FROM HOST

    RO VERSION :

    Salutare,

    Spuneam ieri de o mentenanta legat de NEO-4. Din ce am observat astazi, consumul de resurse pentru NEO-4 este mult mai mare fata de cat trebuie. Asta se intampla de la ultimul update de panou de control care vine cu versiune noua de wings + docker. Ce inseamna asta? Ca la un timp de 24-30h cat serverul sta offline, cache-ul se aduna (acum a fost dezactivat) si swap limit/memory usage devine atat de mare incat isi da self-shutdown. Problema este rezolvabila (sper sa o fii rezolvat acum), insa nu voiam sa fac mentenante asupra NEO-4 neanuntate. Se pare ca va trebui si clientii de pe NEO-2 nu sunt afectati deloc, NEO-4 fiind dedicatul care nu a fost configurat cum trebuie, fiind la inceput in acel moment cu setarile OVH. Acum 30 minute am dat restart la dedicat si sper ca problema sa fie rezolvata (atentie, tot urmeaza acea mentenanta generala de pe 5 ianuarie).

    Pe scurt: in zilele ce urmeaza, posibil sa fie un downtime la servere de cateva minute, respectiv un restart odata la 24h. Ma uit de 25 minute si pare sa fie okay acum, altfel voi trece la alt workaround. Nu este chiar un major incident, dar poate sa fie un major change.

    * Repet: clientii de pe NEO-2, adica 18 servere nu vor fi afectate de acest impact, acolo totul merge cum trebuie.

    EN VERSION :

    Howdy,

    Yesterday I was talking about a maintenance related to NEO-4. From what I noticed today, the resource consumption for NEO-4 is much higher than it should be. This is happening since the last control panel update that comes with the new version of wings + docker. What this means? As the server is offline for 24-30 hours, the cache accumulates (it has now been disabled) and the swap limit/memory usage becomes so high that it self-shutdowns. The problem is solvable (I hope you've solved it now), but I didn't want to do maintenance on NEO-4 unannounced. It seems that it will have to and the clients on NEO-2 are not affected at all, NEO-4 being the dedicated one that was not configured properly, being at the beginning at that moment with the OVH settings. 30 minutes ago I restarted the dedicated one and I hope that the problem will be solved (attention, that general maintenance from January 5 is still following).

    In short: in the following days, there may be a server downtime of a few minutes, respectively a restart once every 24 hours. I've been watching for 25 minutes and it seems to be okay now, otherwise I'll move on to another workaround. It is not really a major incident, but it can be a major change.

    * I repeat: the clients on NEO-2, i.e. 18 servers will not be affected by this impact, everything is working as it should there.

    For all CSO Players information !

  • Regarding Forum Host : Planned Vital Maintenance

    An important firmware update that will be implemented at our data center, aimed at enhancing the overall performance and reliability of our services.

    The update will take place on July 11, 2023 starting at 09:00 am CET and will be undertaken till 05:00 pm CET, with services possibly intermittent affected.

    Technicians will do everything in their power to complete this maintenance as quickly as possible.

  • Regarding Game Server :

    • Official Post

    Message from forum host :

    Contabo

    Dear Berkay

    we are pleased to inform you that your Servers will soon be migrated to our newly built Hub Europe Data Center at the German-French border:

    *ip redacted*

    (Should you have additional servers not listed here, you will be informed separately about their migration in due time)

    The new data center was designed with N+1 redundancy to reach availability of 99.982% required for Tier 3 data centers. The migration is part of our efforts to enhance reliability of your server.

    The migration will be performed seamlessly without any disruption to ongoing processes on your server. In some cases, a brief restart may occur automatically at the end of the process. Apart from potential restart, your server will remain reachable throughout the process. Your IP address will remain unchanged.

    Please note that if you have servers within the same network subnets, you will need to configure static routes to ensure reachability between these servers after the migration. Please see the following documentation regarding static routes: Creating static routes.

    We kindly ask you to ensure that all services on your servers are configured to be reboot-safe to avoid any issues. Please do not create a snapshot of your server, as this will extend the migration process.

    The migration process, which includes your server, will span several weeks and is set to begin on Monday, May 12th. It is an automated process, so the exact timing of your server migration cannot be precisely determined. Once the host system listed in your customer control panel is updated, you can be certain that your server has been migrated. We appreciate your understanding and kindly ask that you refrain from inquiring about specific migration schedules.

    To learn more about our new data center or about the migration, please visit our Migration FAQ in our Support Hub.

    Thank you for your understanding.

    Best regards

    Jenny

    Contabo Customer Experience

  • Hello,

    The server is back online, it can happen that the server shuts down again due to the host doing stuff this in not us doing it.

  • Planned datacenter maintenance on 21 Oct

    Hello, OVH, the datacenter where our server is hosted, is doing planned work on its cooling system next week. Our server is affected, on:

    • Wednesday 21 October, from 08:00 to about 17:00 (GMT+3)

    The following screenshot describes more about the maintenance, this screenshot comes from the network website we are currently working to better help you get notified about all incidents and issues, maintenance or anything which is going to happen to our infrastructure. We are sharing this informations as fast we got them today with you. As a side note, we are currently working (hard) to improve our infrastructure, on security and network, after last incident. Thank you for understanding,

  • Scheduled — 2026-10-15T09:00:00.000Z

    Our infrastructure provider will carry out cooling maintenance at its LIM3 datacenter (Limburg, Germany) on Tuesday, 20 October 2026 from 05:00 to 14:00 UTC. One of our servers (LIM1) is in the affected rack.

    We do not expect downtime. Services on this server may run with reduced performance during the window, and in a worst-case scenario may restart or shut down briefly. No action is required on your side.

  • Scheduled — 2026-10-15T12:00:00.000Z

    Our infrastructure provider will carry out cooling maintenance at its LIM3 datacenter (Limburg, Germany) starting Wednesday, 21 October 2026 at 05:00 UTC (07:00 CEST). One of our servers (LIM4) is in the affected rack. The provider has not announced an end time; we expect it to finish by about 14:00 UTC and will update this notice.

    We do not expect downtime. Services on this server may run with reduced performance during the window, and in a worst-case scenario may restart or shut down briefly. No action is required on your side.

  • Resolved — 2026-10-15T12:00:00.000Z

    Post-incident summary. On 13 October at 20:39 UTC (23:39 Romania time), an old admin login belonging to a former team member, which we had not removed, was used to shut down LIM1 and LIM4. At 20:53 UTC the same login was used to delete the system configuration on LIM4, so it could not start again. Nobody broke in from outside, and no customer files, game saves or databases were lost.

    Downtime: game servers and databases on LIM4 were down for 1h46m in total (20:39 to 20:46 and 20:53 to 22:33 UTC). Game servers reached through a dedicated IP on LIM4 were down for 2h07m (until 22:54 UTC), and FastDL for 1h50m. Game servers on LIM1 were down for 20 minutes in total (20:39 to 20:46 and 21:31 to 21:44 UTC).

    What we changed: all access held by former team members has been removed from every server, and the shared admin account is locked. Admin logins are key-only and tied to one person each, root passwords have been changed, and the addresses involved are blocked. We're also adding nightly backups of each server's system configuration, permanent alerts on unexpected logins, and VPN-only admin access.

    Resolved — 2026-10-13T22:54:00.000Z

    Game servers reached through a dedicated IP on LIM4 are reachable again. All services on LIM4 and LIM1 are restored.

    Monitoring — 2026-10-13T22:33:21.000Z

    LIM4 is back online. All game servers and their databases are running again, and FastDL followed at 22:37 UTC. Game servers reached through a dedicated IP on LIM4 are still unreachable while we restore their forwarding.

    Identified — 2026-10-13T21:44:18.000Z

    LIM1 is back online and its game servers are running. Work on LIM4 continues.

    Identified — 2026-10-13T21:31:07.000Z

    We are restarting LIM1 into rescue mode to remove the old access. Its game servers will be offline for about 15 minutes.

    Identified — 2026-10-13T21:00:00.000Z

    Both servers were shut down using an old admin login that should have been removed. LIM1 has been back since 20:46 UTC. LIM4 went down again at 20:53 UTC and cannot start, because its system configuration was deleted. We are rebuilding it from rescue mode. Customer files, game saves and databases on LIM4 are intact.

    Investigating — 2026-10-13T20:39:23.000Z

    LIM1 and LIM4 went offline at 20:39 UTC. Game servers on both servers are unreachable. We are investigating.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!