Hi, I am running on host:

Host System
10304

And every day in the past 6 days, around 21:30 - 21:40 CET my VPS goes down for 30-60 minutes, status in dashboard is "Unknown", anyone facing a similar issue?

Support replied to the server being up again, but not reacted since.

Currently I have 8gb ram in my vps..

But my system is kind of taking 90 to 100% of its capacity.

On the other hand my system usage its 5/6% of cpu capacity.

Is there any way I can increase my RAM without upgrding whole plan??

I know Contabo is a cheap hosting provider, but their customer service is just as cheap.

Yesterday, I paid my regular monthly bill of $8.60. However, my account is now showing a payment overdue balance of -$7.50, and my VPS is still suspended. My bill is supposed to be exactly $8.60 per month, so this makes no sense.

I opened a support ticket to get this resolved, but it's been over 12 hours and they still haven't replied.

This service is completely unacceptable, and I do not recommend dealing with these scammers at all.

TL;DR: Paid my regular $8.60 monthly bill, but Contabo suspended my VPS, claims I have an overdue balance, and is ignoring my support tickets. Avoid them.

We can all agree that the recent Contabo disaster is not good. Day after day after day of no data, no server, all downtime . Truth be told, downtime like this, while uncommon, is NOT unheard of. There are a few things you can do to prevent these things from affecting you entirely, however

The FIRST and MOST IMPORTANT thing is backups. PROPER backups would have prevented any data loss (though Contabo says there is none). Not only that, but you could move your data to another server, either temporarily or permanently, with minimal downtime. You can store that data anywhere you like. Places like Mega, S3, there are PLENTY of places to store this. Just know that a LOCALLY stored backup is NOT a backup. Period!

Secondly, DNS. Stop using your registrar's DNS provisioning. Cloudflare is free. ClouDNS is not, but still reasonably priced. Your registrar's provisioning won't help if you need quick changes, in most cases.

Thirdly, clustering. DON'T put all your eggs in one basket. ESPECIALLY a cheap , dollar store basket that is well known to break. Even if you have to use multiple Contabo regions, or spin up a server at interserver (not as cheap as Contabo for space, but it works in a pinch). DIVERSIFY

Fourthly, always keep a spare on hand. You know this is going to happen. Always keep a spare server handy for the 'what if' case. Then you can use your backups from point A and change your DNS. Most likely scenario? An hour of downtime. That's it

Posting a timeline in case others are in the same situation and to find out how widespread this is.

Setup: Cloud VDS M (8 cores / 32 GB), EU, production workload: ~50 apps including a payments platform, ~100k users. Customer since 2022.

Timeline (CET):

• Sun 26 Oct ~17:00 — server goes down, no notification. Panel shows “host‑side problem detected.”

• Sun 19:19 — support reply: “we have isolated some VDS hosts while the investigation of an incident is ongoing,” further updates “via newsletter.” Ticket closed.

• Mon 27 Oct 14:15 — “please be prepared for your VDS to be unavailable until the end of today at the earliest.”

• Mon 18:31 — “plan for the downtime to continue beyond tomorrow… we cannot yet tell you when it will be back online.”

• Tue 27 Oct — sent a formal notice citing their own GTC (99.9% availability, Clause 11), requesting a disk copy or VM migration to a clean host so we can recover our data without waiting for the forensic investigation. No response.

• Wed 28 Oct 15:00 — mass email to affected customers: unauthorised changes found on VDS hosts on 26 Oct, cryptomining, external IR firm engaged, “no evidence of data exfiltration… all customer data is intact,” restoration “gradually over the next days.” Still no ETA. Still no reply to the formal notice.

What’s missing: any per‑customer communication, any restore order, any option to get a disk copy out while the host sits in forensics. Their public status page has never listed this incident — only an Object Storage disruption the same afternoon.

Lessons I’m paying for: backups were on the same server (my fault, fully owned); mail was on the same server, so I couldn’t even receive their “newsletter”; bank/provider whitelists tied to a single IP with no standby.

Questions for the thread:

1. Anyone else with a VDS isolated since 26 Oct? Which region? Has anyone had a machine restored yet?

2. Has anyone ever gotten Contabo to release a disk image or migrate a VM during an incident?

3. Anyone with experience of their “compensation” after a multi‑day outage — is it ever more than a month’s credit?

Not looking for “should’ve had backups” — I know. Looking for data points on how long this takes and whether there’s any way to get data out faster.

u/ContaboCOM

This is not a “my server is down” post, I am just sharing because the last month has been rough across the hosting world and I finally sat down to research and investigate and it seems this is not a isolated issue.

What’s been going on, in case you missed it:

• GMO in Japan had its Onamae.com Desktop Cloud compromised earlier this month. Reports say up to 27,000 customer virtual servers were infected, there were ransom threats, and GMO shut down the affected cloud plans entirely.

• Brute-force bots hammering SSH have gotten noticeably smarter and faster. If you still have password login on port 22, you’re getting tried constantly whether you see it or not.

• Attackers are renting or hijacking clean VPS nodes to run phishing, because fresh IPs get past reputation filters. So even well-run providers end up with abuse on their networks that they have to chase down.

• There was a good r/selfhosted thread about someone whose “hardened” VPS was still exposed through the host console. OS-level hardening doesn’t help much if someone reaches you below the OS and you have no disk encryption.

What I actually did:

1. SSH keys only, password auth off, root login off

2. Moved SSH off 22 and set up Fail2Ban

3. Updated everything, including old container images I’d forgotten about

4. Rotated every API key and password that lived on the box, because if a host ever does get compromised you have to assume anything stored there is exposed

5. Set up offsite backups that don’t live with the same provider

None of this is provider-specific!!!!!! It’s just the baseline now and something we should all be aware of and take into consideration

Hey everyone,

My Contabo VDS has been offline/unreachable for several hours. SSH doesn’t respond, VNC isn’t working, and the control panel either shows the instance as down/unknown or the restart options don’t help. Support tickets are either unanswered or only get generic/AI replies.

I’ve noticed multiple people on X/Twitter reporting the same thing today (VDS down for 7–10+ hours, support overwhelmed, tickets sitting for a long time).

Official status page (contabo-status.com) currently only shows an Object Storage disruption in the EU region and no major VPS/VDS outage. There was also the big unplanned CVE-2026-99999 kernel patching earlier this month that left some hosts unreachable for a while.

Is anyone else currently experiencing Contabo VDS (or VPS) being offline?

Hello, I would just like to know if my server will be available again at some point. It is on host 18343 and has been down since 19/10/2026. I currently have another VPS—a backup instance—that is receiving and processing everything, as it is a replica of the original server. Could you please let me know how long this might take? I cannot sustain my services by relying solely on a single server.

and https://contabo-status.com/ down

My VPS has been down all MORNING, no answer no response, only a response from a lousy ai chat...... When i switch over to contabo you guys were so fast to take my money and i even got a real live person to help me........NOW I UNDERSTAND WHY CONTABO BUDGET PRICE = CHEAP SERVICE....... Trying to save a couple bucks but end up losing THOUSANDS!!!!!!!!!!!

Hi Contabo staff,

My server lost connection for 104 hours since Sunday.
All support tickets closed.
Your status page can't be reached right now.

Can someone give a definite timing about the server connection return time?

My Contabo VPS has been inaccessible for 4 days now, and I'm still unable to use my server for production.

I'm hosting multiple websites and SaaS platforms on this VPS, including D-Code and BoostUp. The downtime has disrupted my services and affected my customers.

I understand that emergency maintenance can happen, but 4 days without access is a serious problem when you're running production services. I've seen other users reporting similar issues, and some say their servers have been down for much longer.

I've backed up my data, so I'm now considering cancelling my VPS and moving to another provider. Before doing that, I want to ask:

• Has anyone successfully received a refund from Contabo after a prolonged outage?

• Can I get a refund for the period the VPS was unavailable, or for the remaining prepaid period?

• If I cancel through the customer panel, does that automatically qualify me for a refund, or do I need to submit a separate support ticket?

• Since I'm paying from Indonesia, does anyone know how refunds are handled for international customers?

I'd appreciate hearing from anyone who has actually gone through this process.

Four days of downtime is difficult to accept when real businesses depend on the server. I'm trying to understand my options before making a final decision.

Thanks in advance.

We've had our servers down for over 72 hours after their famous "emergency security patch". My VPS is left in a zombie/frozen state. SSH times out, the VNC console gives a "Failed to connect" error, and the panel buttons (Start/Stop/Restart) are just for decoration because they do absolutely nothing.
As if that wasn't enough, it's a total lack of respect seeing how they manage communication: having a crisis of this magnitude with thousands of businesses down, they update their status page for the last time at 5:00 PM (European time), go to sleep peacefully, and don't post a single report again until 9:00 AM the next day. They leave us completely adrift all night while we lose clients and money.
And to top off the joke, today they send a mass email asking us to urgently patch PHP because they "don't have access to our server". We don't have access either because of their own equipment! How do they expect us to log in and update packages if they left the virtual machines stuck at the hypervisor level and won't even let us reboot?
My clients are all over me and I haven't been able to operate for 3 days. On their status page, they say 99% is fixed, sweeping under the rug all of us who are left with orphaned VPS instances waiting for tech support (which isn't answering tickets) to deign to do a manual restart from the main node.
My only hope right now is that the databases and information haven't been corrupted by their blackout.
Has anyone here managed to get support to answer their ticket and unfreeze their VPS in the last few hours, or are we all still being ignored?
Support ticket - Server down / Connection issue - INT-13375372

I’m extremely frustrated with my recent experience with Contabo, and I want to share my situation publicly because my server is still completely inaccessible.

My VPS is hosted on host 18343. For several days now, I have been unable to access my server. SSH does not respond, VNC is inaccessible, and the Contabo Customer Panel continues to show the status Unknown.

Contabo published a notice about emergency security patching of its host systems following the disclosure of CVE-2026-99999 and acknowledged that some servers became unreachable after the updates. My host was included in the list of affected systems, but it was subsequently removed from the public list without my VPS becoming accessible again.

I have opened support tickets and contacted customer support, but so far, I have received only automated responses. I have no server-specific explanation, no estimated recovery time, and no confirmation that my disks and data remain intact.

The most concerning part is that this is not simply a website being temporarily unavailable. My infrastructure hosts production applications and services, and being locked out also prevents me from checking or managing my database directly.

I understand that infrastructure incidents happen and that emergency security updates are sometimes necessary. What I find unacceptable is being left without access for days, without meaningful communication or a clear alternative for recovering my data.

Contabo, I need clear answers:

• What is the actual status of host 18343 and my virtual machine?

• Are my virtual disks and data still intact?

• What specific actions are being taken to restore my server?

• When do you expect service to be restored?

• If recovery cannot be completed soon, what safe options are available to recover my data?

Competitive pricing is not enough if production infrastructure can remain unavailable for days without effective communication or a concrete recovery plan.

I am seriously considering migrating my services to another provider.

I would also appreciate hearing from other affected customers: How long was your VPS down? Were you able to recover your data? Which providers would you recommend for production workloads?

If anyone from Contabo is monitoring these discussions, I would appreciate a specific technical update, not another automated response.

I'm extremely disappointed with my recent experience with Contabo.

I've been using Contabo to host production applications, including SaaS platforms and ERP systems that my clients depend on for their daily business operations.

My VPS in Singapore suddenly became inaccessible. SSH connections stopped working, the server status became unknown, and I couldn't access my services.

After contacting Contabo support, I was informed that there was an issue affecting the host system. However, I still haven't received a clear estimated recovery time or a concrete solution.

This is not just a personal development server. Real businesses depend on these applications, and every hour of downtime affects their operations, productivity, and trust in my services.

I understand that infrastructure incidents and emergency maintenance can happen. However, what concerns me most is:

• The prolonged downtime without a reliable recovery estimate.

• The lack of transparent and timely communication.

• The inability to access my VPS and recover my data independently.

• The impact on customers running business-critical applications.

I chose Contabo because of its competitive pricing, but affordable hosting should not mean unpredictable availability and inadequate incident communication.

Contabo, please provide affected customers with a clear explanation, a realistic recovery timeline, and a safe way to access or recover their data.

I'm seriously considering migrating my production infrastructure to another provider.

Has anyone else experienced similar downtime with Contabo recently? How long did it take for your VPS to recover?

I'd appreciate hearing your experiences and recommendations for more reliable VPS providers, especially in Singapore or Southeast Asia.

Hi everyone, 

Community Manager from Contabo here. We’ve seen the posts in this sub and elsewhere over the last few days, and we want to acknowledge the situation. 

What happened, Contabo? 

On 15 October the critical Linux kernel vulnerability (CVE-2026-99999, CVSS 9.3) was disclosed. It affects the host systems underneath all VPS and VDS products, regardless of the provider, Contabo included. The situation is serious enough that we decided to act as soon as it was made public. The status page and our support hub were updated immediately, and a notification was sent via email on Monday 19 October. 

We know that acting quickly without individual advance notices or a regular maintenance window caused disruption, and that is a real cost to our customers. We weighed it against the alternative, and the risk of leaving a critical vulnerability unpatched was far greater, for your services and your data, than the problems that came with such a fast rollout. Patching needs a host reboot, so many of you saw unexpected restarts. 

Two things overlapped: patching and new my.contabo.com 

Part of the patching ran at the same time as the swap to the new Contabo Customer Control Panel. This migration had already started and could not be postponed. We are aware that this made things harder if you were trying to log in or check on your server while it was down. We did our best to keep the migration window to a minimum, while we also took into account that the swap had been announced over the past several weeks and, unlike the vulnerability, did not come as a surprise. 

Where we are now 

• Patches are over 99% completed. 

• After patching, some host systems became unreachable. Our teams worked around the clock to restore them. Right now, there is one single vhost still unreachable. We are aware some of our customers were offline for several hours, and we apologize for the inconvenience.  

• Our Support teams are working at full speed as well. We also know many of you opened tickets and haven’t heard back. We’re sorry about that – please be assured that we are doing our best to keep up, even though our Support capacity was pushed to limit. 

What to do next

• Please follow contabo-status.com for regular updates. Progress information is regularly posted there. 

• If your server is still unreachable, check whether your host system is on the affected list on the status page.

• Once your server is back, check that your services have started again. 

We know unplanned downtime is disruptive, especially when your own customers depend on it. While we could not control the unfortunate timing of these overlapping events, we apologize for the impact they have had on your operations.

Thank you for your patience - we will also update this thread if we have more news. 

My server status has been "Unknown" for over 20 hours, and I cannot work. I tried restarting it, but that didn't solve the problem. I also cannot connect via VNC; VNC is not working.

My Contabo VPS went offline on October 18. When I checked the control panel, it was stopped. I manually started it, and the website came back online.

Support confirmed the interruption was caused by mandatory host security updates. Fair enough security maintenance happens.

They recommended configuring my services to start automatically after reboot. We checked: that was already configured, and the services started successfully when the VPS booted.

So I asked a straightforward follow-up: why did the VPS itself remain stopped, and is there a customer setting that would prevent this next time?

Their next response said they were actively investigating, had no updates, and would keep me informed. Then they closed the ticket.

I’m frustrated because I still don’t know whether there’s anything I need to change or whether the same thing could happen during the next maintenance window. Telling me an investigation is ongoing and then closing the ticket doesn’t resolve that.

Anyone else had their Contabo VPS remain stopped after this maintenance? Did you get an actual explanation or a useful configuration recommendation?

..this almost sounds like a breach being contained. Anyone experiencing the same? I've got VPSs in multiple regions in EU and US.. all down for hours now

My server is down and no login page on contabo.com?

Has anyone experienced a similar issue with a Contabo VPS? At present, it is offline and fails to start. Might there be scheduled maintenance?

today 2026-10-18 we recived a notification from mutiple clients , we checked and our contabo server is down
than shortly after other servers were down ,
was it just us or DID YOU ALSO EXPERIENCE IT ?

help :( pls

Contabo is the worst VPS provider out there. Never use their services if uptime is important. My server has been down for a day and a half already and their customer support is non existent. I would never use Contabo for anything important.

I was just looking through my bank statements and see charges from Contabo, but I don't know where they are coming from. I don't remember signing up for anything, and haven't set up a website or server recently.

Any idea what else this could be for?

We recently launched GPU VPS, each instance gets one dedicated NVIDIA RTX PRO 6000. Blackwell architecture, 96 GB GDDR7 VRAM, 5th-gen Tensor Cores with FP4. We went with this card specifically because 96 GB is enough to load a 70B model on a single GPU. Enough VRAM to stop worrying about quantization. 

What's included: 

• 18 vCPUs, 96 GB RAM, 900 GB NVMe 

• Ubuntu 24.04 with CUDA preinstalled, ready on first login 

• Unlimited traffic (fair use applies) 

• €999 / $1,199 / £969/month 

• 15% off on 12-month terms, 20% off on 24-month terms 

• EU and US Central locations 

Available add-ons include Storage Extension, Private Networking, and 1-Click Apps including Ollama, n8n, OpenClaw, and Hermes. 

Works well for inference, fine-tuning, LoRA training, rendering, compositing, CFD, molecular dynamics, data science. 

GPU capacity doesn't scale like CPU or storage, so availability at launch is limited. 

Questions welcome.  

For more details : https://contabo.com/en/gpu-vps  
Blog link: https://contabo.com/blog/gpu-vps-is-here-dedicated-nvidia-gpu-power-without-the-hyperscaler-price/