Skip to content

Outage tracker

OVHcloud: probe event history

The last 24 hours in detail, 63 days of check results, a 12-month summary, our own probe event log, OVHcloud's declared record, and how the two compare.

← Back to OVHcloud's check readings

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

Email me when our checks of OVHcloud fail from two or more distant regions

One email when our checks of OVHcloud fail from two or more distant regions, and one when they pass, after you confirm the address. No account, no card.

This is our own reading from outside. It is not OVHcloud's official status.

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 check 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 check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and 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.

Checks passing by region

Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.

RegionChecks passingProbes recorded
US-East98.40%2933
US-West98.60%2930
Europe98.23%2931
Asia-Pacific98.93%2888
US-Central99.01%1213
Canada98.68%1214
UK98.20%1219
Southeast Asia98.35%1211
Australia98.60%1210
South America97.86%1217

Monthly summary

Tracking OVHcloud since Aug 22, 2026. In that time our checks failed from two or more distant regions in 15 probe events, 17h 35m in total. Months before that date are not tracked and carry no figure.

MonthUptime by our checksProbe eventsTime failing
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.91%22h 37m
Sep 202697.92%1314h 58m
Oct 2026100%00 min

Uptime by our checks is the share of each month in which no probe event was open for OVHcloud. An event opens only when our checks fail from two or more distant regions, meaning regions on different continents. One that nothing else backs stops counting as an outage after 6 hours, and after 48 hours we treat our check as broken. An event that fails these rules is retracted, kept, and listed on the corrections page. An event 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.

These figures come from our own checks of one public endpoint per service. They are not the service's real uptime.

Our probe event log

Every probe event for OVHcloud in the last 90 days, or since we started checking 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 our checks show 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
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
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
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
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
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
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
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
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
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
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
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
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
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
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 probe event records

Every closed OVHcloud probe event gets its own permanent, citable page: the region-by-region timeline of our check results, which stays up even after the event 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.