Skip to content

Outage tracker

OVHcloud: the full evidence record

The last 24 hours in detail, 46 days of measured availability, a 12-month summary, our own incident log, OVHcloud's declared record, and how the two compare.

← Back to OVHcloud's live status

We started measuring OVHcloud on August 22, 2026, which is 46 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.

Email me the next time we see OVHcloud go down

Measured by our own probes from ten regions, not OVHcloud's status page. One email when a measured outage opens and one when it closes, after you confirm the address. No account, no card.

The last 24 hours

What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what OVHcloud's own status page declared. Below it, any public chatter we saw about OVHcloud and the extra probe it triggered.

The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what OVHcloud's own status page declared. Three records side by side; none of them changes another.

Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about OVHcloud in the last 24 hours, which is not evidence that nothing is wrong.
OVHcloud's status pageOVHcloud publishes no status feed we can read, so there is nothing to show here.

Each probe cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused probe is not an outage. Report bars count unverified reports, not people we verified; they never change our reading. The status-page lane is OVHcloud's own declaration, shown as they made it.

Third-party chatter, labeled

Public posts from the last hour that mention OVHcloud next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.

No matching public posts in the last hour from the sources we watch.

Availability by region

Availability is measured probes that succeeded, divided by every probe we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionAvailabilityProbes recorded
US-East97.78%2115
US-West98.06%2111
Europe97.54%2114
Asia-Pacific98.50%2069
US-Central98.51%804
Canada98.01%804
UK97.28%809
Southeast Asia97.51%802
Australia98.00%800
South America97.28%808

Monthly summary

Tracking OVHcloud since Aug 22, 2026. In that time our probes detected 28 outages, 35h 54m in total. Months before that date are not tracked and carry no figure.

MonthUptimeOutagesDowntime
Nov 2025not tracked
Dec 2025not tracked
Jan 2026not tracked
Feb 2026not tracked
Mar 2026not tracked
Apr 2026not tracked
May 2026not tracked
Jun 2026not tracked
Jul 2026not tracked
Aug 2026 from Aug 22, 202698.26%54h 11m
Sep 202695.60%2331h 43m
Oct 2026100%00 min

Uptime here is the share of each month in which our probes had no outage open for OVHcloud: two consecutive failed readings from a region opens one, the first clean reading closes it. Any detected outage counts, including one seen from a single region, and an outage that crosses midnight on the first of a month is counted in both months with its minutes split. User reports, public posts and OVHcloud's own status page contribute nothing to these figures.

Our incident log

Every outage our own probes detected for OVHcloud in the last 90 days, or since we started measuring it if that is more recent. This list is probe-only: OVHcloud's own declared incidents appear further down this page in their own attributed section, never merged with what we measured here. User reports live on the live page, in their own labeled block.

Sep 30, 2026, 8:48 PM UTC to Sep 30, 2026, 10:49 PM UTC2h 1m
multiple regions
US-East: failing from Sep 30, 2026, 8:56 PM UTC, recovered Sep 30, 2026, 9:55 PM UTCEurope: failing from Sep 30, 2026, 8:56 PM UTC, recovered Sep 30, 2026, 9:56 PM UTCAsia-Pacific: failing from Sep 30, 2026, 8:56 PM UTC, recovered Sep 30, 2026, 9:57 PM UTCUS-Central: failing from Sep 30, 2026, 9:19 PM UTC, recovered Sep 30, 2026, 10:00 PM UTCUK: failing from Sep 30, 2026, 8:54 PM UTC, recovered Sep 30, 2026, 9:53 PM UTCSoutheast Asia: failing from Sep 30, 2026, 9:20 PM UTC, recovered Sep 30, 2026, 10:20 PM UTCAustralia: failing from Sep 30, 2026, 8:48 PM UTC, recovered Sep 30, 2026, 10:49 PM UTC
Permanent record for this incident
Sep 30, 2026, 6:29 AM UTC to Sep 30, 2026, 6:59 AM UTC30 min
single region
US-West: failing from Sep 30, 2026, 6:29 AM UTC, recovered Sep 30, 2026, 6:59 AM UTC
Permanent record for this incident
Sep 27, 2026, 12:52 PM UTC to Sep 27, 2026, 1:52 PM UTC1h
multiple regions
US-East: failing from Sep 27, 2026, 12:53 PM UTC, recovered Sep 27, 2026, 1:23 PM UTCEurope: failing from Sep 27, 2026, 12:52 PM UTC, recovered Sep 27, 2026, 1:22 PM UTCSouth America: failing from Sep 27, 2026, 12:54 PM UTC, recovered Sep 27, 2026, 1:52 PM UTC
Permanent record for this incident
Sep 27, 2026, 12:52 AM UTC to Sep 27, 2026, 1:51 AM UTC59 min
multiple regions
Europe: failing from Sep 27, 2026, 12:52 AM UTC, recovered Sep 27, 2026, 1:22 AM UTCSouth America: failing from Sep 27, 2026, 12:52 AM UTC, recovered Sep 27, 2026, 1:51 AM UTC
Permanent record for this incident
Sep 25, 2026, 7:40 PM UTC to Sep 25, 2026, 8:40 PM UTC1h
single region
Australia: failing from Sep 25, 2026, 7:40 PM UTC, recovered Sep 25, 2026, 8:40 PM UTC
Permanent record for this incident
Sep 25, 2026, 5:40 PM UTC to Sep 25, 2026, 6:40 PM UTC1h
single region
Australia: failing from Sep 25, 2026, 5:40 PM UTC, recovered Sep 25, 2026, 6:40 PM UTC
Permanent record for this incident
Sep 17, 2026, 8:34 AM UTC to Sep 17, 2026, 10:19 AM UTC1h 45m
multiple regions
US-East: failing from Sep 17, 2026, 8:48 AM UTC, recovered Sep 17, 2026, 9:48 AM UTCUS-West: failing from Sep 17, 2026, 8:50 AM UTC, recovered Sep 17, 2026, 9:49 AM UTCEurope: failing from Sep 17, 2026, 8:48 AM UTC, recovered Sep 17, 2026, 9:48 AM UTCCanada: failing from Sep 17, 2026, 9:19 AM UTC, recovered Sep 17, 2026, 10:15 AM UTCUK: failing from Sep 17, 2026, 8:48 AM UTC, recovered Sep 17, 2026, 9:44 AM UTCAustralia: failing from Sep 17, 2026, 8:34 AM UTC, recovered Sep 17, 2026, 10:19 AM UTCSouth America: failing from Sep 17, 2026, 8:51 AM UTC, recovered Sep 17, 2026, 9:48 AM UTC
Permanent record for this incident
Sep 13, 2026, 5:15 PM UTC to Sep 13, 2026, 5:47 PM UTC32 min
multiple regions
US-East: failing from Sep 13, 2026, 5:15 PM UTC, recovered Sep 13, 2026, 5:45 PM UTCEurope: failing from Sep 13, 2026, 5:17 PM UTC, recovered Sep 13, 2026, 5:47 PM UTC
Permanent record for this incident
Sep 9, 2026, 1:12 PM UTC to Sep 9, 2026, 2:10 PM UTC58 min
multiple regions
US-East: failing from Sep 9, 2026, 1:40 PM UTC, recovered Sep 9, 2026, 2:10 PM UTCUS-West: failing from Sep 9, 2026, 1:13 PM UTC, recovered Sep 9, 2026, 1:43 PM UTCEurope: failing from Sep 9, 2026, 1:12 PM UTC, recovered Sep 9, 2026, 1:42 PM UTC
Permanent record for this incident
Sep 9, 2026, 10:08 AM UTC to Sep 9, 2026, 11:41 AM UTC1h 33m
multiple regions
US-East: failing from Sep 9, 2026, 10:40 AM UTC, recovered Sep 9, 2026, 11:10 AM UTCEurope: failing from Sep 9, 2026, 10:41 AM UTC, recovered Sep 9, 2026, 11:11 AM UTCUS-Central: failing from Sep 9, 2026, 10:08 AM UTC, recovered Sep 9, 2026, 11:08 AM UTCUK: failing from Sep 9, 2026, 10:41 AM UTC, recovered Sep 9, 2026, 11:40 AM UTCSouth America: failing from Sep 9, 2026, 10:50 AM UTC, recovered Sep 9, 2026, 11:41 AM UTC
Permanent record for this incident
Sep 8, 2026, 7:13 AM UTC to Sep 8, 2026, 5:41 PM UTC10h 28m
multiple regionsintermittent
US-East: failing from Sep 8, 2026, 7:40 AM UTC, recovered Sep 8, 2026, 5:11 PM UTCUS-West: failing from Sep 8, 2026, 7:13 AM UTC, recovered Sep 8, 2026, 5:12 PM UTCEurope: failing from Sep 8, 2026, 7:41 AM UTC, recovered Sep 8, 2026, 5:11 PM UTCAsia-Pacific: failing from Sep 8, 2026, 7:38 AM UTC, recovered Sep 8, 2026, 5:11 PM UTCUS-Central: failing from Sep 8, 2026, 10:07 AM UTC, recovered Sep 8, 2026, 5:07 PM UTCCanada: failing from Sep 8, 2026, 9:09 AM UTC, recovered Sep 8, 2026, 5:09 PM UTCUK: failing from Sep 8, 2026, 7:41 AM UTC, recovered Sep 8, 2026, 5:41 PM UTCSoutheast Asia: failing from Sep 8, 2026, 8:01 AM UTC, recovered Sep 8, 2026, 5:02 PM UTCAustralia: failing from Sep 8, 2026, 9:24 AM UTC, recovered Sep 8, 2026, 11:09 AM UTCSouth America: failing from Sep 8, 2026, 7:48 AM UTC, recovered Sep 8, 2026, 1:41 PM UTC
Permanent record for this incident
Sep 8, 2026, 3:24 AM UTC to Sep 8, 2026, 4:09 AM UTC45 min
single region
Australia: failing from Sep 8, 2026, 3:24 AM UTC, recovered Sep 8, 2026, 4:09 AM UTC
Permanent record for this incident
Sep 6, 2026, 5:09 AM UTC to Sep 6, 2026, 5:38 AM UTC30 min
single region
Europe: failing from Sep 6, 2026, 5:09 AM UTC, recovered Sep 6, 2026, 5:38 AM UTC
Permanent record for this incident
Sep 5, 2026, 8:56 PM UTC to Sep 5, 2026, 10:24 PM UTC1h 29m
multiple regions
US-East: failing from Sep 5, 2026, 9:37 PM UTC, recovered Sep 5, 2026, 10:07 PM UTCEurope: failing from Sep 5, 2026, 9:39 PM UTC, recovered Sep 5, 2026, 10:09 PM UTCUK: failing from Sep 5, 2026, 9:39 PM UTC, recovered Sep 5, 2026, 10:24 PM UTCSoutheast Asia: failing from Sep 5, 2026, 8:56 PM UTC, recovered Sep 5, 2026, 9:53 PM UTC
Permanent record for this incident
Sep 5, 2026, 11:53 AM UTC to Sep 5, 2026, 12:55 PM UTC1h 1m
single region
Southeast Asia: failing from Sep 5, 2026, 11:53 AM UTC, recovered Sep 5, 2026, 12:55 PM UTC
Permanent record for this incident
Sep 5, 2026, 5:38 AM UTC to Sep 5, 2026, 6:33 AM UTC55 min
multiple regions
US-West: failing from Sep 5, 2026, 5:39 AM UTC, recovered Sep 5, 2026, 6:09 AM UTCUK: failing from Sep 5, 2026, 5:38 AM UTC, recovered Sep 5, 2026, 6:33 AM UTC
Permanent record for this incident
Sep 4, 2026, 6:03 PM UTC to Sep 4, 2026, 7:03 PM UTC1h
multiple regions
US-East: failing from Sep 4, 2026, 6:05 PM UTC, recovered Sep 4, 2026, 6:35 PM UTCEurope: failing from Sep 4, 2026, 6:06 PM UTC, recovered Sep 4, 2026, 6:36 PM UTCCanada: failing from Sep 4, 2026, 6:03 PM UTC, recovered Sep 4, 2026, 7:03 PM UTC
Permanent record for this incident
Sep 4, 2026, 10:42 AM UTC to Sep 4, 2026, 11:38 AM UTC56 min
multiple regions
Europe: failing from Sep 4, 2026, 11:06 AM UTC, recovered Sep 4, 2026, 11:36 AM UTCSouth America: failing from Sep 4, 2026, 10:42 AM UTC, recovered Sep 4, 2026, 11:38 AM UTC
Permanent record for this incident
Sep 4, 2026, 4:33 AM UTC to Sep 4, 2026, 5:03 AM UTC30 min
single region
US-East: failing from Sep 4, 2026, 4:33 AM UTC, recovered Sep 4, 2026, 5:03 AM UTC
Permanent record for this incident
Sep 3, 2026, 11:01 AM UTC to Sep 3, 2026, 12:07 PM UTC1h 6m
multiple regions
US-East: failing from Sep 3, 2026, 11:01 AM UTC, recovered Sep 3, 2026, 12:01 PM UTCEurope: failing from Sep 3, 2026, 11:01 AM UTC, recovered Sep 3, 2026, 12:01 PM UTCAsia-Pacific: failing from Sep 3, 2026, 11:22 AM UTC, recovered Sep 3, 2026, 11:53 AM UTCUS-Central: failing from Sep 3, 2026, 11:03 AM UTC, recovered Sep 3, 2026, 11:33 AM UTCCanada: failing from Sep 3, 2026, 11:03 AM UTC, recovered Sep 3, 2026, 12:03 PM UTCUK: failing from Sep 3, 2026, 11:37 AM UTC, recovered Sep 3, 2026, 12:07 PM UTCSoutheast Asia: failing from Sep 3, 2026, 11:20 AM UTC, recovered Sep 3, 2026, 11:53 AM UTCAustralia: failing from Sep 3, 2026, 11:12 AM UTC, recovered Sep 3, 2026, 11:47 AM UTCSouth America: failing from Sep 3, 2026, 11:28 AM UTC, recovered Sep 3, 2026, 11:59 AM UTC
Permanent record for this incident
Sep 2, 2026, 8:40 AM UTC to Sep 2, 2026, 9:25 AM UTC44 min
multiple regions
US-East: failing from Sep 2, 2026, 8:40 AM UTC, recovered Sep 2, 2026, 9:10 AM UTCUS-West: failing from Sep 2, 2026, 8:53 AM UTC, recovered Sep 2, 2026, 9:25 AM UTCAsia-Pacific: failing from Sep 2, 2026, 8:42 AM UTC, recovered Sep 2, 2026, 9:16 AM UTC
Permanent record for this incident
Sep 1, 2026, 5:09 PM UTC to Sep 1, 2026, 5:39 PM UTC30 min
single region
US-East: failing from Sep 1, 2026, 5:09 PM UTC, recovered Sep 1, 2026, 5:39 PM UTC
Permanent record for this incident
Sep 1, 2026, 2:51 AM UTC to Sep 1, 2026, 3:22 AM UTC31 min
single region
Europe: failing from Sep 1, 2026, 2:51 AM UTC, recovered Sep 1, 2026, 3:22 AM UTC
Permanent record for this incident
Aug 31, 2026, 12:15 PM UTC to Aug 31, 2026, 12:46 PM UTC30 min
single region
US-West: failing from Aug 31, 2026, 12:15 PM UTC, recovered Aug 31, 2026, 12:46 PM UTC
Permanent record for this incident
Aug 30, 2026, 10:13 PM UTC to Aug 30, 2026, 11:14 PM UTC1h
multiple regions
US-West: failing from Aug 30, 2026, 10:13 PM UTC, recovered Aug 30, 2026, 11:14 PM UTCEurope: failing from Aug 30, 2026, 10:15 PM UTC, recovered Aug 30, 2026, 10:45 PM UTC
Permanent record for this incident
Aug 29, 2026, 10:22 PM UTC to Aug 29, 2026, 10:54 PM UTC32 min
single region
Asia-Pacific: failing from Aug 29, 2026, 10:22 PM UTC, recovered Aug 29, 2026, 10:54 PM UTC
Permanent record for this incident
Aug 28, 2026, 1:27 PM UTC to Aug 28, 2026, 3:04 PM UTC1h 37m
multiple regions
US-East: failing from Aug 28, 2026, 1:27 PM UTC, recovered Aug 28, 2026, 2:57 PM UTCUS-West: failing from Aug 28, 2026, 1:33 PM UTC, recovered Aug 28, 2026, 3:04 PM UTCEurope: failing from Aug 28, 2026, 1:47 PM UTC, recovered Aug 28, 2026, 2:47 PM UTCAsia-Pacific: failing from Aug 28, 2026, 1:39 PM UTC, recovered Aug 28, 2026, 2:45 PM UTC
Permanent record for this incident
Aug 28, 2026, 9:10 AM UTC to Aug 28, 2026, 9:42 AM UTC31 min
single region
Europe: failing from Aug 28, 2026, 9:10 AM UTC, recovered Aug 28, 2026, 9:42 AM UTC
Permanent record for this incident

Permanent incident records

Every closed OVHcloud incident RealUptime has ever detected gets its own permanent, citable page: the region-by-region timeline, exactly as measured, that stays up even after the incident log above ages out of this 90-day window.

Full detail on what a probe does and does not prove is in the methodology page.