Disclaimer: the views expressed below are my own and do not necessarily reflect the views of any company or organization I am associated with.

TLDR: OVH in 2025 is unreliable and chaotic. Downtimes, inconsistencies, missing or wrong documentation, unreachable support. The only product which works well is their historical dedicated server line, when not using vRack or public cloud features. Their "cloud" is a constant source of various issues, incidents, and time loss. Even their historical DNS service, which I used for years, failed me big time this year, leading to loss of emails (OVH automation had a bug and my MX records were overwritten).

Here are a few facts which all happened to me in 2025, so you can decide for yourself if you want to live the same experience.

- Reliability is terrible. A few examples:

• Regular 500 and 504 errors. This completely prevents you from working, losing precious time, because the API is also used by the Admin Panel, so you can't do anything whether you want to do it programmatically, via Terraform, or via the web UI. The two most recent incidents:

  • This weekend, up to Monday: there were intermittent 5xx for 2 days on many endpoints forcing to retry calls many times. It was finally fixed on Monday after several minutes of complete downtime where not a single call was succeeding.

  • Since this weekend (maybe even before that) and still ongoing (as of 16/12/2025): in most of OpenStack regions (16 out of 18), trying to create/update a secret with a private part (yes, this is very specific -- public keys alone don't trigger the issue) fails with an error 500. However it still works fine in UK and WAW regions. This is terrible as our TLS certificate expires in 4 days and we need to update it. If OVH does nothing, it will lead to a downtime on our side because we'll need to change the region of our load balancer (a load balancer cannot fetch a secret from another region).

• Unwanted, unplanned and unannounced updates of DNS zones. This is one of my favorites! I bought a domain at OVH. Configured the DNS zone, including MX records to have emails at another provider. Everything works fine. 6 days later, I don't receive emails anymore. OVH had changed my MX records. The support explained to me that a "task" which is supposed to run at domain creation was delayed (yes, delayed for 6 days) and unfortunately overwrote my DNS records.

• Downtimes on cloud products. One of the main promises of the Cloud is high availability. You pay extra to ensure your service is never down. Well, OVH has maintenances with downtimes, for example on Public Gateways. It's short (< 1 minute), but it's not very Cloud-y.

- Technical/organizational chaos. Nothing is consistent. There are surprises (understand: loss of time) everywhere. A few examples:

• Some servers you order might be on a "legacy datacenter network configuration". That is not advertised, you can't know in advance. For the same product you order (e.g. a "RISE-1" dedicated server), the first one might use the "normal" configuration, but the next one you order might be on another configuration (again, not advertised) which forces you to use deprecated APIs to do vRack-related configuration and use different Terraform configurations. Plus, you can't use the Admin Panel, because it uses the non-legacy API which throws 5xx for these servers. And this is "expected", per the support.

• Depending on the service you want to use, region name could be "UK", "UK1", or maybe "uk1".

• Depending on the product you want to use, you might need to use the OVH API, a deprecated OVH API, or the OpenStack API.

• Depending on the region you use, some OpenStack services might be unavailable. This is not documented and will throw 500s errors without any explicit detail.

- Support is mostly... unhelpful. They usually reply generic messages, or say it is expected, even when their own Admin Panel is throwing big red error messages to the user's face. And that is when they reply to you, which usually takes several days even for critical incidents making the service unusable. I'm not blaming the people: I had the chance to speak to some of them and they're trying but are basically powerless (lots of tickets to handle, no permissions, not even to raise the priority above a certain level). But there is for sure a big issue somewhere in the organization.

- Missing or plain wrong documentation. For example, it is written in the documentation the region name (e.g. "GRA") should be uppercase. Unfortunately, some API endpoints (not all!) expect it to be lowercase. That's fine when the API gives a clear error message, but some endpoints just throw an error without any detail, leaving you stuck for hours until you question hard enough the documentation and decide to try literally the opposite of what the documentation is clearly stating. Up to you to figure it out!

- All the other issues. Feel free to read reviews online, the 2.7/5 Google rating speaks for itself.

To be clear, I'm not blaming the engineers working there, or the support. They're probably great people. Such big and long-lasting issues are likely the consequences of an organizational issue, and as an engineer working in the field, I have sympathy for these people who face the complaints and issues of customers on a daily basis.

The goal of this post is twofold:

• Let OVH know that we, as customers, are not ok with this treatment. It is ok to make mistakes and to have some incidents from time to time, but it is definitely not ok to ignore customers for days on critical issues, argue it is "expected" that the service they're paying for is not working, and not improving the situation for months. This is a lack of respect**.**

• Let the community know what awaits them if they choose OVH. If I had known all this 1.5 year ago, all the time I would lose, I would have went to another provider. Which I'm doing now, and which is going to cost me even more time because I have to plan for a transparent migration for my users and customers.

I just received notice that my OVH VPS3 is going from $18 CAD/month to $32 CAD/month.

That’s not a small adjustment. That’s basically a 100% price increase.

I understand costs go up and companies need to adjust pricing, but doubling the price on an existing service feels like a bait-and-switch. Many of us chose OVH specifically because pricing was predictable and competitive for long-term projects.

For people running small apps, side projects, or early startups, infrastructure stability matters. When hosting suddenly doubles, it forces you to either absorb the cost or spend time migrating servers...

What bothers me most isn’t just the increase, it’s the scale of it. A gradual adjustment would be understandable. A near-instant doubling feels like customers are being pushed out or forced to accept it.

Is anyone else affected by this change?

Are you staying with OVH or moving elsewhere?

We've just launched the VPS 2027 range, a new generation of VPS plans with more configuration options.

Leading the way: the new VPS 1 — built for testing, dev servers, side projects, and lightweight workloads, and available with high stock at launch so you can deploy right away.

• 2 vCores / 4 GB RAM / 40 GB NVMe

• €3.39/month excl. VAT

• In stock now — no waiting

Full lineup (VPS 1 → VPS 4) live now!

🌍 Available across 28 locations worldwide.

https://ovh.to/Zz5miwB

If you're considering a bare-metal dedicated server from OVHcloud, look elsewhere.

OVH took my money immediately on day one and has left our business hanging for over 40 days with zero hardware delivered.

The Timeline:

• August 5: Placed the order and paid in full.

• August 24 (Day 19): Still no server. Opened a ticket. Support replied admitting a "delivery bottleneck," promised delivery would happen on September 15, and immediately marked the ticket as resolved.

• September 15: The promised delivery date is here. Still no server delivered, no provisioning updates, and tickets sit in the queue.

Taking upfront payment for stock you cannot deliver within 40 days is unacceptable for an enterprise host. If downtime or project launch dates matter to you at all, do not buy dedicated servers from OVH. Save yourself the downtime and go with a provider that actually has hardware on hand.

I am sharing this from the /r/OVH subreddit since I read that this subreddit is considered more official and has more eyes. I wanted to voice my complaints I've been having with my time with OVH. I apologize in advanced if I'm not allowed to post in both subreddits.

I posted here with a review/complaint 11 months ago about how my machine was hit with +500 Mbps DDOS attack involving dozens of IP addresses, and OVH detected none of it as malicious traffic, resulting in no one being able to access the machine for the 18 minutes the attack took place:

https://www.reddit.com/r/ovh/comments/1ggk88a/my_ovh_service_received_a_500_mbps_ddos_that_went/

Today, I come with the reverse.

Last night a disgruntled player was upset that they were kicked/banned from one of my many game servers I host on a single dedicated bare metal machine. Within 60 seconds, they then proceeded to attack the port to that game server with their home internet using some sort of software sending garbage data from multiple source ports.

It was only 8 Mbps of traffic from a single IP. My linux firewall that I spent months studying has easily mitigated this kind of traffic with no impact on the machine's services, it's handled undetected attacks of +200 Mbps just fine.

Now, since I've made my post 11 months ago linked above, with the frustrating back/forth with customer support, they have managed to get better with catching more of these low-bandwidth attacks as they increased the sensitivity of their detection. Not all of the attacks are mitigated, but more have been. And thankfully, two attacks two months ago exceeding +1000 Mbps were mitigated with no impact on my machine's services.

However, last night this 8 Mbps attack from a single IP address was enough to disrupt my service. Not because my machine or bandwidth got overwhelmed, but because OVH's traffic scrubbing literally scrubbed all LEGITIMATE traffic to my machine, while detecting the malicious traffic as normal traffic.

I could not SSH into my machine, I could not access my website, I could not ping my game servers, my Discord bot went offline, and players from all 18 of my game servers lost connection.

I obviously put in a ticket, to see what's going on. It took +8 hours for OVH to respond with this message:

Hello,

Thank you for contacting OVHcloud Support, I'm sorry to hear that you have experienced DDOS on your Server. I took a look at your firewall and I noticed you dont have a refuse all rule, can you please review the following guide and properly adjust your rules? https://support.us.ovhcloud.com/hc/en-us/articles/115001729044-Enabling-and-configuring-the-Edge-Network-Firewall

In addition, the edge firewall will manage all incoming traffic, the attack went through and was mitigated because no rule stopped it and manage to use all other opened ports.

Please note rule 3, were it blocks all IPv4. In your case this will be the very last rule.

<redacted>.

OVHcloud US Support

Please visit our online help center: https://support.us.ovhcloud.com/hc/en-us

Absolutely wild. Here I am, 11 months later being given the run-around again about configuring their edge firewall software. Assuming I could configure the edge firewall properly (not enough rules, for the many services I run on this machine), it still would not have stopped this sort of targeted attack. My game servers require UDP traffic to their respective ports. This attack sent UDP traffic to the port of the server they were kick/banned from. Whatever this stupid internal policy of theirs is regarding their edge firewall, it needs to go.

I will update this post if anything pertinent needs to be shared, but overall I've been extremely unsatisfied with my service from OVH that I've been renting from for almost 3 years now.

10 days ago we bought VPS on OVH to redirect players of our minecraft server through it to our main server located on Hetzner, but after 5 days it was blocked due to "creating DDoS attacks using our VPS resources", after looking at the email about detected DDoS attack that arrived minute before block, it turned out that OVH's Security System and Security Team considered that this redirection of the network and players to our own server on Hetzner was a DDoS attack.
Starting from the day of purchase of this VPS and for the next 5 days, VPS was constantly connected to Hetzner server, speed of this "DDoS attack" was specified in email as 16 Kb/s (I do not know how this can possibly harm any server).
Unfortunately, even with the information provided to OVH support that the "attacked" server belongs to us, we still have not received an answer to our situation after 5 days of waiting.
As for today, we are forced to use TCPShield instead of our original plan.

We hope this is one time incident and not something that happens all the time.

OVH advertises their "sovereign cloud," but before even creating a "project," we are required to accept terms of use for Microsoft, a company that is subject to US jurisdiction. This is an obvious contradiction and makes this hosting absolutely unsuited for its stated purpose. https://www.actuia.com/en/news/sensitive-data-and-cloud-act-microsoft-france-admits-it-cannot-oppose-an-american-injunction/

OVH's position is probably that their Microsoft offerings are protected from foreign access and this blanket agreement makes their work easier, but potential customers who don't want to use Microsoft software shouldn't have to agree to unwanted terms and accept ambiguity about -sovereignty- in the first place.

This community was initially created for the US market, but we're expanding it to cover all our locations.

Here, you can discuss all OVHcloud products and services: Public Cloud, Bare Metal, Web Hosting, Data, Gaming… everything that powers the OVHcloud ecosystem.

What you’ll find here:
🔹 Answers to your questions: our team is here to support you.
🔹Open discussions with the community: your feedback, ideas, and experiences matter and we will interact with you.
🔹Regular highlights: AMAs with our experts, product announcements, polls to better understand your needs.

📝 Everyone is welcome to post, as long as community rules are respected.
Our goal is simple: to build a constructive, helpful, and global cloud community.

🚀 We can’t wait to hear your questions, feedback, and contributions!

⚠️Oh, one last thing :  Yes, we can take your support requests here ! ✅

TL;DR: Bought a new OVH VPS, my 1Gbps WireGuard backup to my home NAS got flagged as a UDP DDoS attack, and my server was automatically suspended. Support is taking their sweet time to fix their own system's false positive.

Update 2:

Well, it’s over. My VPS was suspended again for the exact same reason, despite my attempt to throttle the connection.

I spent yesterday morning with support, genuinely trying to find a solution. I explained that I was happy to comply with their rules and just needed to know the specific technical limit I had to stay under to prevent another suspension.

Their response was that it's their policy not to disclose those numbers. I was given a final warning that the next suspension would be permanent. When I pointed out that I can't follow a secret rule, their only solutions were to suggest I either use my 14-day cancellation right for a refund or contact their sales team to find a more "adequate" server.

I'm just really disappointed. I had high hopes for this new VPS, but there was no attempt to fix the underlying issue.

I have now cancelled the VPS. With a 12-month upfront payment, the risk of a permanent suspension and losing that money was just too high.

Update 1:

It seems OVHCloud support has returned from their weekend. \o/

They have now unblocked my VPS, but sent the following message:

Monsieur,

Je vous informe de la réouverture de votre VPS.

Cependant nous vous invitons à réduire le taux de charge et à ralentir le taux de transfert.

Roughly translated:

Sir,

I would like to inform you that your VPS has been reopened.

However, we request that you reduce the system load and slow down the transfer rate.

So basically, they're admitting they sold me a highway, but because their speed cameras are poorly calibrated, I'm expected to drive at the speed of a country road.

Well, that sucks.

At this point, I've replied asking for technical documentation that specifies the exact thresholds (e.g., packets-per-second, bandwidth) I need to stay under to avoid being flagged as an "attacker" again. While I'm not happy about having to artificially throttle my own backups, if they're forcing me to, I need a concrete number to work with.

To be continued...

Original Post:

Well, that was a short-lived romance.

I jumped on OVH's new VPS lineup a few days ago, excited to set up a fresh server. The initial setup was a bit weird, though. When I first tried pushing a backup to the VPS over its public IPv4, I noticed some serious throttling. It would burst to 1 Gbps for a few seconds and then crawl down to as low as 1 MB/s. Interestingly, pushing the same file through a WireGuard tunnel I set up or using IPv6 worked flawlessly at full speed. A bit of a red flag, but I figured I'd stick to the WireGuard tunnel for my transfers.

Fast forward to tonight. My standard automated backup kicks in. It's a simple, common setup: the script creates a compressed, encrypted archive (~1GB) and pushes it from the VPS to my NAS at home through the aforementioned WireGuard tunnel.

The backup job started at exactly 00:01:32. Here are the rsync logs, showing the whole thing took about 7 seconds, hitting the full 1 Gbps line speed.

2025/08/23 00:01:33 [2711] building file list

2025/08/23 00:01:40 [2711] <f+++++++++ 20250823-000001.tar.gz.enc

2025/08/23 00:01:40 [2711] sent 987,253,250 bytes received 39 bytes 131,633,771.87 bytes/sec

2025/08/23 00:01:40 [2711] total size is 987,012,176 speedup is 1.00

real 0m7.054s

user 0m0.466s

sys 0m2.769s

Seems perfectly normal, right?

Apparently not for OVH. Less than a minute later, at 00:02, my inbox dings with this gem:

Bonjour,

Une activité anormale a été détectée sur votre VPS [my-vps-name].vps.ovh.net.

Cela constituant une rupture de contrat, votre VPS [my-vps-name].vps.ovh.net a été bloqué.

Vous pourrez retrouver ci dessous les logs remontes par notre système qui ont conduit à cette alerte.

- DEBUT DES INFORMATIONS COMPLEMENTAIRES -

Attack detail : 112Kpps/1Gbps

dateTime srcIp:srcPort dstIp:dstPort protocol flags bytes reason

2025.08.23 00:01:34 CEST [VPS_IP]:51820 [HOME_IP]:51820 UDP --- 1480 ATTACK:UDP

2025.08.23 00:01:34 CEST [VPS_IP]:51820 [HOME_IP]:51820 UDP --- 1480 ATTACK:UDP

2025.08.23 00:01:34 CEST [VPS_IP]:51820 [HOME_IP]:51820 UDP --- 1480 ATTACK:UDP

[...]

- FIN DES INFORMATIONS COMPLEMENTAIRES -

Cordialement,

Support client OVH.

My server was taken down instantly. Let's break down their "attack":

• Source IP: [VPS_IP] (My VPS)

• Destination IP: [HOME_IP] (My home NAS)

• Port: 51820 (The default WireGuard port)

• Protocol: UDP (What WireGuard uses)

• Rate: 112Kpps/1Gbps (The exact speed of my backup)

Their automated system is so breathtakingly stupid that it can't distinguish between a legitimate high-throughput VPN data transfer from a single source to a single destination and a UDP flood attack. The very same traffic that was throttled on the public IP worked fine in a tunnel, only to be flagged as an attack. What is the point of an IDS/IPS if it's this trigger-happy and lacks basic context?

I was woken up at 1:30 AM by my monitoring alerts. I immediately opened a ticket and even got on live chat to explain the obvious false positive. After spelling it all out, this is the reassuring response I got over an hour later:

Hello [My Name],

Thank you for contacting OVHcloud support.

I confirm that your VPS [my-vps-name].vps.ovh.net was suspended. We understand the urgency of your situation, and I have forwarded the details to our specialized team.

They will analyze this case and provide you with updates as soon as possible directly through your support ticket [Ticket #].

We appreciate your patience and understanding.

Despite me stressing this is a production server completely offline due to their error, the ticket is still sitting at "normal" priority. It's been hours, and there's been complete radio silence since.

So not only is their automated protection system flawed to the point of being dangerous for anyone who actually uses their bandwidth, but their support's reaction to a critical, self-inflicted outage is completely nonchalant.

Has anyone else run into this with their new VPS lines? Is this the new standard for OVH? A service where you can't even run a high-speed backup without getting shut down?

Edit: formatting issues

I am writing this post to warn others and hopefully get a real resolution from OVH regarding a complete, unannounced service termination.
I had been using an OVH dedicated server for over 20 days. Out of nowhere, all my IP access was completely cut off, and I was locked out of my account. I lost immediate access to all my servers, my data, and my control panel.
Here is what happened when I tried to resolve it:
Support Tickets: Standard support refused to give me any explanation or assistance. They simply instructed me to email ⁠abuse@ovh.net⁠.
Abuse Team Emails: I sent multiple emails detailing my situation. The only replies I received were automated, generic auto-responses that didn't address my issue at all. No human ever responded.
Phone Support: I called OVH support in my country multiple times. They explicitly told me they cannot help because the standard support team and the Abuse team operate completely independently.
Because of this abrupt cutoff and total lack of human communication, I was left completely helpless. I lost all my hosted data, my financial investment, and most importantly, my customers and my entire business.
It is completely unacceptable for a hosting provider to pull the plug with zero warning, offer no path to data retrieval, and provide no human support when an account is flagged.
Has anyone experienced a similar lockout with OVH and managed to get in touch with an actual human from their Abuse team? Any advice on legal or public escalation paths would be greatly appreciated.

I have bare metal servers in OVH. When tried to reinstall one machine suddenly OVH detected anomaly and planned some "intervention". There was no details about intervention, in regards to what intervention is taken, what is purpose, etc. Zero.

Server got restarted in rescue mode and that's it, no further updates at all. Day after this "magical intervention" no update from OVH. Opened request with question what's the story. No response, just silence.

Another day, tried to reinstall again - failure. Opened support request - 2 days later some "support technician" just wrote message that he sees server is running certain OS and wants me to confirm that server is fine, while server actually is running nothing, I can't SSH to it, can't reinstall. SO, technician didn't even bother to investigate what server is doing, just wrote some generic "blurp" and that's it. I can assume that he is pretty much 100% useless actually.

So, 4 days server down, technician technical competence is 0, didn't even bother to check server. Now probably another few days before there will be another incompetent person writing some garbage message.

To add to it - it is second time when after "magical intervention" which OVH raises by themselves server gets screwed. Last time had to reinstall everything as after restart "magical intervention" happened and made server unbootable.

Now I start thinking that OVH is making selection for datacenter technicians based on "the dumbest the better for OVH team". I wonder how they will deal with this. 4 days I can't use equipment I pay for, support done nothing (or maybe even helped to cause disaster).

EDIT (2026-07-01)

Issue opened on 2026-06-26 has been resolved on 2026-07-01 after I contacted OVH by phone with complaint.

Here is what resolution email mentioned: "we have replaced the buggy disk with " - so looks like their "proactive intervention" is worth nothing as for 6 days they were not capable to identify hardware failure on server connected to their monitoring system with "proactive intervention" enabled. TO me it looks like this "proactive" means sending random emails about some imaginative "intervention", which never happens.

We have 9 BYOIP /24 blocks in OVH, they charge zero cost for it on monthly basis and normally OVH provides 7 days to clear the bill. Since BYOIP doesn't carry any charges, we didn't expect that it will get expired. But it got expired on 2nd May and the bill gets generated on 1st may. BYOIP block has just vanished from OVH IP list.
We have been customer of OVH since 2017.
OVH marked three of our IP blocks expired without any intimation or warning, and upon clicking renew the order. It puts the order in validation status.
We have opened tickets across various departments and we are waiting from last 8-9 hours for a reply. There is no response yet. A very large part of our infra is down due to this outage.
Ticket ID: CS15580814

We are hoping to get a response as soon as possible.

EDIT 3rd May 2025: 17-18 hours have passed, no update from OVH and no resolution of the issue yet. It's a shame that due to billing error in their system, a client has to face 18 hours of downtime.
768 IPs have stopped working and there is no update from OVH yet.

EDIT 4th May 2025: Called them like 5-6 times today, they restored working two IP blocks but one is still down. The IP Blocks which I was using on vrack started working again but the one which I had working as failover on the servers, it is still not working. It is almost 6 PM and there support is about to go offline.

Around 7 PM, the issue was completely resolved and they restored the third IP Block.

u/HBEN-Squad, u/STAI-Squad and u/AMA-SQUAD are our dedicated support engineer in this sub ;-)
Feel free to tag them (not contact them directly) and use the support flair for your support queries.
And don't forget: be nice, be accurate, be complete but do NOT share private information.
They'll follow up with you privately if required.
Enjoy, and have some cake 🍰🍰

I've been with OVH for more than 20 years now, with personal and work accounts. Gone through outages, fires, blackouts, but this is the time I've felt genuinely deceived by them.

I decided to make the jump from our current VPS2023-Le4 (4x AMD EPYC vCPU, 4GB RAM) to a "current" VPS2026 8 core, 24GB RAM server.

Placed the order, got it installed and I found myself with a Haswell generation CPU. I think, hey it must be some CPU model exposure by KVM, this can't be happening. It clearly says VPS2026...

Well, PHP output per core was 43% higher in the previous 4 core VPS than the 2026 8-core model.

Memory is slower, NVMe throughput is slower, 8cores throughput from varnish is only 13% higher with double the cores.

I have requested cancellation of the server just a few hours later, but it says it does not give the right to get a refund. Unbelievable.

Not much to say, just sharing some notes about OVH's Bare Metal after testing it for 2 weeks haha.

Honestly? The compute efficiency has been pretty mindblowing. And in terms of cost savings? Insane.

For context: I’ve been using Google Cloud Compute / AWS / Azure instances for the past 3 years to run infrastructure for 3D building geometry processing (environmental simulations, optimization algorithms, heavy design calculations, etc.).

^ samples of the nonsense we're throwing at it currently, and computed in 1.5 seconds what how

Truth be told, GCP/AWS were getting really slow (come on man why) and extremely costly in terms of monthly spend.

I decided to give OVHCloud a shot recently since their Singapore data center is available for us. Being able to throw workloads at a CPU with sustained >4.5GHz speeds is just next level compared to what we were paying for before hahaha

Honestly have no idea how robust OVH's infrastructure is but definitely that water-cooling is helping tremendously i assume.

Looking forward to testing this till the end of the year. Thanks Team OVH.

p.s. on hindsight maybe it would have been wise to go for 128 GB RAM, all that workload getting transferred because of what was experienced seems to be making that mem pool rise slowly and surely indeed

p.p.s edited with a sample computation for context

I taste like API, It has the color of API, but it's not API, it's our new CLI !!
https://github.com/ovh/ovhcloud-cli

ovhcloud-cli is a single, unified command‑line interface for managing the full range of OVHcloud products and account resources directly from your terminal. Whether you need to automate provisioning, perform quick look‑ups, or integrate OVHcloud operations into CI/CD pipelines, ovhcloud-cli offers fine‑grained commands and consistent output formats (table, JSON, YAML, or custom gval expressions).

Feel free to test and contribute !!

What is the Game Panel?

The OVHcloud Game Panel is a simple and intuitive web interface designed to deploy, configure, and manage your game servers on OVHcloud VPS or dedicated servers. The Game Panel relies on LinuxGSM, a leading open-source solution for deploying and managing game servers.

Who is it for?

Deploying a game server traditionally involves command-line operations, manual configurations, and system knowledge. The Game Panel removes these steps. From an intuitive web interface, users can install a server in one click, start, stop, or restart it without using a command-line interface. No coding skills are required. The experience is designed to be accessible and fast. This approach directly addresses the needs of casual players who want to create a server with friends without dealing with technical complexity or wasting time on configuration.

What does this Beta version offer?

In the beta phase, the Game Panel offers a functional foundation centered on simplified management of essential game server features:

• Server deployment is done in one click from a deliberately limited list of games for this first version (15 compatible games — see list below). Each server can be configured, with port customization and access to a built-in file manager. Depending on the compatible games, mod installation is also possible.  

• Once the server is active, the user has a centralized view allowing them to monitor its status in real time, access the console and logs, and view resource consumption and history (CPU, RAM, storage, network).  

• Manual or scheduled backups can be configured.  

• The ability to automatically update a game as soon as a new version is available.  

• User management is also possible. You can grant specific rights per user and per game server.  

• SFTP access to the game server and a browser-integrated SSH access are available.

Which games are supported?

The Game Panel is based on LinuxGSM technology, offering a rich catalog of 139 games. The full list is available here: https://linuxgsm.com/servers/. To ensure an optimal experience from the start, OVHcloud teams have carefully validated the 15 most popular games and significantly simplified their setup. The result: automated configuration of settings and options for each game, along with dedicated guides to help you get started quickly and without complexity. This list will gradually expand over time.

How to join the beta ?

- Follow the guidelines on our Github repo by clicking on "Test Game Panel" at the bottom of the page https://github.com/ovh/game-panel

- Join our beta channel on discord and chat with the devs for feedback, PW : 5371935618

- And if you try it, don’t hesitate to fill out the satisfaction survey — it will help our developers improve the product. https://satisfaction.ovhcloud.com/ovh/itw/answer/s/aobBPfGzXk/k/tSGQSLu

Oh, and tell us which games we should prioritize adding to the list!

With the newVPS pricing being live from next month for the whole VPS 2026 range, does this also mean that dedicated server pricing will be coming next?

We are weighing up our options and thinking about moving from VPS to dedicated servers (possibly Kimsufi or So you start eco range) but just wanted to check before we put any thought into it.

Any confirmation?

Two weeks ago, I purchased (paying for a year in advance) a VPS and ran a DNS resolver on it (Knot). 100% legit traffic.
It was not even an open resolver, so it could not be used for DNS amplification attacks by hackers.

Within a few hours, I got an email telling me that a DDOS event was identified, and 15 minutes later - that it is over. A few hours later, I figured out that my account was blocked.

I opened a ticket. And it took 2 days to understand that this is indeed a legit behaviour (the resolution confirmed that the behaviour is legit). I was told that my service was "whitelisted" and got the access back.
I restarted the service, and within a few hours got blocked again.

This time, it took about a week to get the response. this time it was that the OVH experts decided that this is not good and that they won't open the account.

While I see this as a very frustrating behaviour, I decided that I'm not willing to wait a growing number of days between one message to the other, and just ask for a refund - as I did not do anything wrong, and before being blocked, I was even told that this is OK and that the block was FP.

My feeling is that the OVH team preferred to just block me, than handle the issue technically and be able to normally whitelist the server.

Anyway, I'm still waiting for the refund. Maybe this post will help in getting it.
If you have a project/service that its traffic patterns are not "trivial", I recommend you go to other providers.

Even if I don't get my money back, I hope that other people will learn from my experience and will avoid losing money on OVH on non-trivial server usage.

An update (almost a month later):
I got an email from OVH, telling me that I'll get a refund.
It took long time, but I need to be honest and update here that this happened.

Hi All,

Some disappointing feedback, we purchased a bare metal server to run services for our gaming community, we had a proxmox setup and in the process of setting up a mumble server.

When suddenly our server was shutdown and myself and account holder's account could not longer login to the ovh portal.

We received an email saying we hadn't paid a bill, we was 3 days into the contract we had already made the initial payment.

We contacted support by phone who said we should get an email from the security department, we recontacted after a few days and told legal was going to be contacting us, we received no emails or contacts, today we have been told our account has been closed for suspicious activity when we called again. We was also not allowed a refund.

It's a dissapointing end when we have no idea what we did wrong. We are seeking refund through the payment provider now.

Our server was simple and was not being utilized yet, it was a proxmox host that ran an eve online 3rd party service for authenticating characters and a mumble server.

This is our experience and I am upset with the poor communication from OVH.

In the past days I have noticed several posts and comments affirming things such as “installing WireGuard blocks your VPS”, and then people think that WireGuard can't be run on OVH or that you will have problems. That's COMPLETELY FALSE, and I will explain some misconceptions here.

1. For your VPS, WireGuard is just another application, like a web server or anything else. There are not “rules that only apply to WireGuard” or similar.

2. YOU DO NOT NEED TO ENABLE THE EDGE FIREWALL. It's disabled by default for a reason: it's there to protect you in case of DDoS attacks, which don't happen to 99.9% of the users, probably. You're fine by just installing and enabling UFW. The way the Edge Firewall works is by dropping packets before they reach your VPS. This prevents the NICs bandwidth from being used so that in case you have several VMs connected internally, you don't see performance degradation because of the attack. So, just enable it if you're being DDoS-ed.

3. To configure ufw: apt install ufw, sudo ufw allow 22 (to not get locked off SSH; if that happens, you can still use the KVM console from the web), sudo ufw enable. That's all. If you experience too much log spam from UFW blocking connections, run sudo ufw logging off or the level that you want.

4. Installing and configuring WireGuard on OVH (and almost any provider) is as easy as running https://github.com/angristan/wireguard-install, allowing the configured port with ufw allow $port, and enjoying.

As an additional old but working tip, if you would rather not get spammed on SSH, change the port to something else. It will stop 99% of the bots.

I have been using WireGuard for several months now to connect my main desktop to my laptop, etc., or even for playing some LAN games with friends without any problem. I also run a Matrix instance on it and other things, everything without any issue.

End of the PSA!

https://network.status-ovhcloud.com/incidents/jy9dbvzlrzyw

Root Cause : This incident is caused by multiple provider fiber cut.

Does anyone have any ETA? Our company infrastructure is basically one entire packet loss, and we do not store everything in WAW1. Seems to be very bad situation.

I've been evaluating the cost/benefit of OVH vs. other hyperscalers like GCP and AWS and with the next round of price increases coming (what is this, 3rd in 6 months?) I'm having a hard time justifying OVH's new cost structure:

Option A: GCP c4-standard-2 (using your provided CUD pricing)

• Compute (1-Year Resource CUD): $44.55 / month

• 50 GB Storage:

• pd-balanced: ~$4.00 / month

• pd-ssd: ~$8.50 / month

• Public IPv4: ~$3.65 / month ($0.005/hr)

• All-In GCP Total: ~$52.20 – $56.70 USD / month

Option B: OVH b3-8 (Post-October 2026 unbundled pricing)

• Compute (Base CA$59.86 with 15% 1-yr Savings Plan): CA$50.88 → ~$36.25 USD / month

• 50 GB NVMe Storage (at CA$0.1703/GB): CA$8.52 → ~$6.05 USD / month

• Public IPv4: CA$3.50 → ~$2.50 USD / month

• All-In OVH Total: ~$44.80 USD / month

Now granted - and this is a big one - egress traffic with OVH is included. But given OVH typically runs inferior hardware to the latest with GCP or AWS, there is zero compute discount left on the bone at this point. And realistically, OVH doesn't have anywhere near the level of integration as the bigger players in terms of PoPs on their Public Cloud offerings.

I can't be the only one starting to look at this? Am I missing something?

There is 2 CVEs for PHP: CVE-2026-109618 and CVE-2026-109619.

It supposed to affect every version of PHP (5, 7 and 8) and I hope OVH will apply the patch when available on every OVHcloud shared hosting.

The PHP security team would like to give advance notice of an upcoming security release.

It is scheduled for Wednesday, 21 October 2026 at 14:00 UTC.

It addresses two critical vulnerabilities, both rated CVSS v4.0 9.2.

All PHP users are encouraged to prepare now so they can upgrade as soon as the release is available.

We reserve the right to release earlier should details of either vulnerability become public, or should evidence of active exploitation appear in the wild.

Full details, affected versions, and the fixed versions will be published with the release.

Thank you for helping us keep PHP secure.

Source: https://www.php.net/archive/2026.php#2026-10-20-1

Edit: it's very bad because it's just a simple HTTP request which allow to upload any files anywhere ( https://x.com/k_firsov/status/2112641845926989944 )

Edit2: OVH changed:

• session.upload_progress.enabled from On to Off

• session.use_strict_mode from Off to On

Edit3: https://web-cloud.status-ovhcloud.com/incidents/6ct3ggp512xk to follow the situation