Is OVHcloud down?
Operationalchecked 1 minute ago
We reached OVHcloud from all 10 regions we check.
Last outage: 1h on Sep 4, 2026 (web surface, from Europe, US-East and Canada).
OVHcloud publishes no status feed we can read, so the only independent reading here is ours on the left.
OVHcloud response time, by region
Is it OVHcloud, or is it you?
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, and what people reported
- North AmericaOperationalUS-East, US-West, US-Central, Canada
- US-EastOperationallatency: 392msstatus code: 200checked: Sep 5, 2026, 2:05 AM 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-WestOperationallatency: 281msstatus code: 200checked: Sep 5, 2026, 1:38 AM 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-CentralOperationallatency: 387msstatus code: 200checked: Sep 5, 2026, 2:02 AM 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.
- CanadaOperationallatency: 363msstatus code: 200checked: Sep 5, 2026, 2:03 AM 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 AmericaOperationallatency: 1130msstatus code: 200checked: Sep 5, 2026, 1:42 AM 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.
- EuropeOperationalEurope, UK
- EuropeOperationallatency: 135msstatus code: 200checked: Sep 5, 2026, 2:06 AM 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.
- UKOperationallatency: 212msstatus code: 200checked: Sep 5, 2026, 1:38 AM 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 PacificOperationalAsia-Pacific, Southeast Asia, Australia
- Asia-PacificOperationallatency: 1204msstatus code: 200checked: Sep 5, 2026, 1:54 AM 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 AsiaOperationallatency: 513msstatus code: 200checked: Sep 5, 2026, 1:47 AM 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.
- AustraliaOperationallatency: 461msstatus code: 200checked: Sep 5, 2026, 1:13 AM 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 have not received any reports for OVHcloud yet, which is not evidence that nothing is wrong.
Recent outages
measured 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 measurements and OVHcloud's own claim at the time, side by side.
Full availability history for OVHcloud: 90-day availability by region, month-by-month uptime, and every incident 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 serversTell me when this goes down
Get told when we measure this
We will tell you when our probes stop reaching OVHcloud, and again when they can reach it again. That is our own measurement from ten regions, not OVHcloud's status page. No account, no card.
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 measured by RealUptime"></a>The badge shows the share of our probes that succeeded over the last 30 days, and the window is printed on it so the number always says what period it covers. If our readings go stale it says stale, and if we have no readings it says so: it will not show green on data we cannot vouch for. Free, no account, and it links back here. See how the badge works for every window and the honesty rules behind it.
What OVHcloud's SLA implies, from our measurement
Below your target
We measured 6h 23m of downtime for OVHcloud over the 338h 7m since we started watching it on 2026-08-22, which is 98.1104% uptime by our reading. A 99.9% target allows 20 minutes over that period.
That is 6h 3m more than the target allows. The figure above is the pro-rata share of one month's fee for the time we could not reach it. 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.
Separately, we measured 3h 4m where only one of our regions was affected. It is excluded above because most SLAs would not credit it, and it is the kind of outage a single-vantage monitor never sees at all.
This is computed from our own probe measurements, 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.