Is OVHcloud Down?

No — OVHcloud is up

Reachable from all 8 checked regions

Average response time: 1724ms

Last checked 4 hours ago · checks run every 6 hours

Official status page: https://www.status-ovhcloud.com

OVHcloud uptime

100%

Last 7 days

99.89%

Last 30 days

99.91%

Last 90 days

776ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 35 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

9-day clean streak

Aug 24 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

bom

1838ms

DNS 1ms TCP 55ms TLS 113ms TTFB 1540ms

cdg

339ms

DNS 0ms TCP 13ms TLS 34ms TTFB 254ms

dfw

827ms

DNS 221ms TCP 40ms TLS 56ms TTFB 665ms

ewr

371ms

DNS 60ms TCP 9ms TLS 26ms TTFB 331ms

fra

290ms

DNS 0ms TCP 13ms TLS 24ms TTFB 233ms

gru

2287ms

DNS 0ms TCP 113ms TLS 229ms TTFB 1708ms

iad

413ms

DNS 141ms TCP 2ms TLS 17ms TTFB 396ms

jnb

7428ms

DNS 0ms TCP 173ms TLS 349ms TTFB 6377ms

What OVHcloud does

OVHcloud is a European cloud provider offering dedicated bare metal servers, hosted private cloud, public cloud instances and web hosting from its own datacentres, and says it is trusted by over 1.5 million developers. Businesses that choose it over the American hyperscalers usually do so for cost, or to keep data inside European jurisdiction.

What an outage looks like

Symptoms follow the product line rather than the whole company. Bare metal servers stop answering on their public IPs while the control panel still lists them as running. Public cloud instances lose network reachability, or the API rejects create and delete calls. Web Cloud sites return connection errors, and the OVHcloud manager fails to log in or shows stale state.

What to do about it

status-ovhcloud.com splits into Bare Metal Cloud, Hosted Private Cloud, Public Cloud, Web Cloud, Network and Customer Service, so identify which one your service sits in before reading the incident list. A Network incident can cut off otherwise healthy machines. OVHcloud operates separate datacentre regions, so confirm the incident names the region your servers are in.

Is it down for everyone, or just you?

If this page says OVHcloud is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 18 cities across three regions to find out where it breaks.

Test it yourself

Related services

OVHcloud outage FAQ

Is my server down or is it the network?

Try reaching the server from more than one network, and check whether the OVHcloud manager still reports it as running. Network is its own category on the status page, and a routing or transit incident leaves a perfectly healthy machine unreachable. If the manager shows the server up and console access works, the fault is more likely in the path than in the host.

Does an incident in one datacentre affect my other servers?

Not usually. OVHcloud runs physically separate datacentre regions, and incidents are normally scoped to one site or one network segment within it, so servers elsewhere keep running. The exception is a shared control plane problem, where the manager or API is degraded everywhere while the machines themselves continue serving traffic untouched.

The OVHcloud manager will not load. Are my services affected?

Often not. The manager and the API are the control plane; your running servers, instances and hosted sites are the data plane and keep serving while the console is unavailable. What you lose is the ability to reboot, reinstall or change configuration until it returns. Check your own monitoring or connect to the machines directly before assuming a wider outage.

Which OVHcloud status page should I read?

status-ovhcloud.com is the company's own page and covers every product line in one place. Third-party aggregators often track only one OVHcloud product, which is why they disagree with each other during an incident. Read the category matching your service, and treat the aggregators as a secondary signal rather than the source.

How we measure this

We request OVHcloud's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where OVHcloud publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when OVHcloud goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 18 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required