Is OVHcloud down?
Checks passingchecked 9 minutes ago
Our checks of OVHcloud pass from all 10 regions we check.
As of Nov 5, 2026, 3:32 PM UTC, RealUptime's checks of OVHcloud passed in all 10 regions that returned a reading.
Last time our checks failed from two or more distant regions: 1h 55m on Nov 3, 2026 (web surface and Control panel, from Europe, South America, US-East, UK, US-Central, Southeast Asia, US-West, Australia and Canada).
OVHcloud publishes no status feed we can read, so the only reading here is our check reading on the left.
OVHcloud response time, by region
Check your own site while you wait on OVHcloud
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not OVHcloud. It cannot diagnose OVHcloud's own systems.
What we measured, function by function
OVHcloud answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.
- WebUS-East: Awaiting dataUS-West: Checks passingEurope: Awaiting dataAsia-Pacific: Awaiting dataUS-Central: Awaiting dataCanada: Checks passingUK: Awaiting dataSoutheast Asia: Awaiting dataAustralia: Awaiting dataSouth America: Checks passing
- APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- API timeUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- Control panelUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
Get an email when our checks of OVHcloud fail from two or more distant regions, and again when they pass
Get an email when our checks change
We will email you when our checks of OVHcloud fail from two or more distant regions, and again when they pass. No account, no card.
What our checks show, and what people reported
- North AmericaChecks passingUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 1117msstatus code: 401checked: Nov 5, 2026, 3:20 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach OVHcloud normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestChecks passinglatency: 1205msstatus code: 401checked: Nov 5, 2026, 3:20 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach OVHcloud normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralChecks passinglatency: 1266msstatus code: 401checked: Nov 5, 2026, 2:45 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach OVHcloud normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- CanadaChecks passinglatency: 520msstatus code: 401checked: Nov 5, 2026, 2:59 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach OVHcloud normally. We do not have enough reports from Canada to say anything about what people there are seeing.
- South AmericaChecks passinglatency: 1233msstatus code: 401checked: Nov 5, 2026, 3:32 PM UTC0 people in the last 5 minutesNot enough reports to sayOur South America probes reach OVHcloud normally. We do not have enough reports from South America to say anything about what people there are seeing.
- EuropeChecks passingEurope, UK
- EuropeChecks passinglatency: 205msstatus code: 401checked: Nov 5, 2026, 3:30 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach OVHcloud normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKChecks passinglatency: 271msstatus code: 401checked: Nov 5, 2026, 3:19 PM UTC0 people in the last 5 minutesNot enough reports to sayOur UK probes reach OVHcloud normally. We do not have enough reports from UK to say anything about what people there are seeing.
- Asia PacificChecks passingAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 2224msstatus code: 401checked: Nov 5, 2026, 3:08 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach OVHcloud normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaChecks passinglatency: 2342msstatus code: 401checked: Nov 5, 2026, 3:00 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach OVHcloud normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- AustraliaChecks passinglatency: 2324msstatus code: 401checked: Nov 5, 2026, 3:32 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach OVHcloud normally. We do not have enough reports from Australia to say anything about what people there are seeing.
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using OVHcloud, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We started counting reports for OVHcloud on October 2, 2026.
Recent probe events
check entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring OVHcloud since August 22, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for OVHcloud covering any window you pick, with our check readings and OVHcloud's own claim at the time, side by side.
Full check history for OVHcloud: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.
Monitor your own site the same way
This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.
Start monitoring your own serversRun a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter
Put this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/ovhcloud)<a href="https://realuptime.io/outages/ovhcloud"><img src="https://realuptime.io/outages/ovhcloud/badge.svg?days=30" alt="OVHcloud uptime by RealUptime's checks" height="20"></a>Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.
To cite this page: RealUptime, "Is OVHcloud down?", https://realuptime.io/outages/ovhcloud. The readings change with every check, so give the date you read them.
How our checks compare with OVHcloud's stated SLA
Below your target
Our checks of OVHcloud failed for 1h 55m over the last 30 days, which is 99.7332% uptime by our checks. A 99.9% target allows 43 minutes over that period.
That is 1h 12m more than the target allows. The figure above is the pro-rata share of one month's fee for the time our checks failed, an estimate from our checks. OVHclouddecides what counts. Your contract probably uses a tiered credit schedule instead, and we have not read it, so treat this as one common way to reason about a credit rather than the amount they owe.
These figures come from our own checks of one public endpoint per service. They are not the service's real uptime. This is computed from our own checks, not from OVHcloud's SLA instrumentation. Their contract is normally measured against their own systems, with their own exclusions and a claim window, so their figure and ours will differ. Use this to start the conversation and ask for their number. It is not legal advice and it is not a determination of what you are owed.
What we check
What our check can and cannot see
A pass means the service's servers answered with the sign-in refusal they give any request that is not signed in. It does not show that sign-in works or that anything behind the sign-in wall responds.
Host checked: api.ovh.com