Public Cloud quotas are blocking scale
A scaling event that needs more vCPU than the project is allowed, with the increase waiting on a support ticket that nobody filed in advance.
Quotas raised and documented before they bite
Running on OVHcloud?
A Public Cloud project is hitting a vCPU quota that nobody raised during the move from the old datacenter, a bare-metal server at Strasbourg has not pinged since the overnight maintenance window, and the Object Storage bucket in GRA is returning 403s for a role that worked yesterday. We open the OVH API, read the task history on the server, and bring the estate back under control without waiting on a support ticket cycle.
What it is
OVHcloud, originally OVH, is a French cloud provider founded by Octave Klaba in 1999 in Roubaix. It runs more than thirty datacenters across Europe, North America and Asia, builds its own servers, and operates its own backbone. The product line splits across Bare Metal (dedicated servers rented by the month, often at well below hyperscaler prices), Hosted Private Cloud (VMware stacks in OVH facilities), Public Cloud (an OpenStack-based service for VMs, Object Storage, Managed Kubernetes and Managed Databases), and Web Cloud (shared hosting, domains and email).
OVHcloud is the EU-sovereign alternative most regulated procurement departments reach for, and it comes with the operational style of a company that grew from colocation rather than from a developer tooling product. The API is comprehensive, the Terraform provider covers most of the estate, and the manager interface is improving but still surprises people who arrived from AWS or GCP. Trouble in production clusters around quota limits that need formal increases, bare-metal servers that silently fail hardware checks after a reboot, vRack private networking that was not attached to new instances, and scheduled maintenance windows whose timing is announced in CET and read in Pacific time.
The honest version
No technology is all upside. This is where OVHcloud earns its place and where it tends to cause trouble.
Sound familiar?
The OVHcloud problems that bring people to us, and what you have once each one is fixed.
A scaling event that needs more vCPU than the project is allowed, with the increase waiting on a support ticket that nobody filed in advance.
Quotas raised and documented before they bite
A dedicated server that rebooted into a diagnostic state because a RAID controller, a drive or a power supply reported a fault. The box is offline until intervention by OVH staff.
Hardware investigated and recovered
A vRack that was set up for the first wave of resources and not attached to instances created later, so internal services cannot reach each other even though the external IPs work.
vRack attachments documented and enforced
A user whose role or S3 credentials no longer match the bucket policy after a rotation, or a region that was moved from the old Public Cloud to the new Object Storage product without updating the clients.
Credentials and policies aligned
An OVH image that ships without cloud-init or with a stripped version, so Terraform or packer workflows that assume cloud-init silently fall through without running the bootstrap.
Images that execute user-data cleanly
A notice announced in CET that arrived in a mailbox nobody reads, or a window that was accepted months ago and had been forgotten. The reboot interrupts a job that nobody protected.
Maintenance windows calendared and routed
A control plane that timed out during a node pool operation, or a Terraform plan against the cluster that hit the API window. Operations partially succeed and state drifts.
Terraform retries and timeouts tuned
Dedicated servers under personal emails, Public Cloud projects on an ex-employee's login, and billing on a card nobody has. The account works until it does not.
Account recovered, keys rotated
What we do
Reach out for one locked server, or let us look after the whole OVH estate.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
For a very large number of European and global workloads, yes. OVH runs datacenters that have been up for years, operates its own backbone, and has credible network engineering behind the scenes. The 2021 SBG2 fire is the honest counterpoint, and the response was to tighten fire suppression, cross-site replication and backup policies. We treat OVHcloud as a serious production platform and still insist on backups into a second provider or a second region for anything that matters.
Almost always a quota. vCPU, RAM, disk, floating IPs and Managed Kubernetes clusters all have per-project quotas that start low and rise on request. The manager will show the limit, and the increase is a support interaction rather than a self-service toggle, so the usual fix is asking for a raise before the scaling moment arrives rather than during it.
Announcements arrive in CET and in advance, often weeks before the window. We route those notifications into a shared calendar and a Slack channel rather than a personal mailbox, confirm the affected servers in the manager, and either accept the window or request a reschedule where it conflicts with a change freeze. Treating them as planned incidents rather than surprises is the difference.
Yes. The usual driver is cost, sovereignty, or both. We build the OVHcloud side in Terraform, stream the databases across in advance, cut DNS over during a quiet window, and keep the old provider in standby mode for a week or two before decommissioning. Backup into a second region or a second provider is part of the plan from day one, not an afterthought.
Yes. We work through the NIC transfer, rotate every API key and server credential, move billing onto a company card, and inventory what is running across dedicated servers, Public Cloud projects and vRack networks so the handover is clean and nothing goes dark silently.
Quotes are free. Tell us the regions, which products you are running, and what is going wrong, and we return a fixed price before any changes touch the account.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: