Skip to main content
OVHcloud logo

Is OVHcloud Down?

No — OVHcloud is up
OVHcloud's status page
Not available · we could not read it
FlareWarden checks
Website reachable · 8 of 8 regions · 520 ms

Right now

We could not read OVHcloud's status page, so the verdict rests on our checks. Check it yourself How we decide

FlareWarden checks

ovhcloud.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable
Regions up
8 of 8
Response
520 ms
Checked

By region

  • Amsterdam reachable, 206 ms
  • Chicago reachable, 708 ms
  • Paris reachable, 178 ms
  • San Jose reachable, 793 ms
  • Singapore reachable, 905 ms
  • Stockholm reachable, 582 ms
  • Sydney reachable, 491 ms
  • Toronto reachable, 303 ms
Timing by region
Connection timing for each region that loaded the page
RegionDNSTCPTLSTTFB
Amsterdam0 ms11 ms16 ms134 ms
Chicago236 ms19 ms23 ms628 ms
Paris0 ms10 ms16 ms113 ms
San Jose203 ms20 ms34 ms725 ms
Singapore0 ms1 ms7 ms884 ms
Stockholm0 ms36 ms42 ms387 ms
Sydney0 ms0 ms7 ms454 ms
Toronto0 ms7 ms14 ms173 ms
We check that ovhcloud.com loads, not every feature behind it. Test it yourself

History

OVHcloud website availability

Measured by FlareWarden · ovhcloud.com

Last 7 days
100%
Last 30 days
100%
Last 90 days
100%
Avg response, 30 days
881ms

Last 30 days

81-day clean streak
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Oct 14: 100.00% uptime, 32 checks
Oct 15: 100.00% uptime, 31 checks
Oct 16: 100.00% uptime, 31 checks
Oct 17: 100.00% uptime, 32 checks
Oct 18: 100.00% uptime, 32 checks
Oct 19: 100.00% uptime, 32 checks
Oct 20: 100.00% uptime, 32 checks
Oct 21: 100.00% uptime, 32 checks
Oct 22: 100.00% uptime, 32 checks
Oct 23: 100.00% uptime, 32 checks
Oct 24: 100.00% uptime, 32 checks
Oct 25: 100.00% uptime, 32 checks
Oct 26: 100.00% uptime, 32 checks
Oct 27: 100.00% uptime, 32 checks
Oct 28: 100.00% uptime, 32 checks
Oct 29: 100.00% uptime, 32 checks
Oct 30: 100.00% uptime, 32 checks
Oct 31: 100.00% uptime, 31 checks
Nov 1: 100.00% uptime, 31 checks
Nov 2: 100.00% uptime, 30 checks
Nov 3: 100.00% uptime, 32 checks
Nov 4: 100.00% uptime, 31 checks
Nov 5: 100.00% uptime, 32 checks
Nov 6: 100.00% uptime, 32 checks
Nov 7: 100.00% uptime, 8 checks
Oct 9 Today
No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of ovhcloud.com from multiple regions every 6 hours. OVHcloud's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 81 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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 17 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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
  • 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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of OVHcloud itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. A reading counts for 45 minutes; we read the feed again within minutes of any change to its incidents. The availability figures above are our measurement alone.

Get alerted when OVHcloud goes down

We check OVHcloud every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required