Ovhcloud status history
Current state: maintenance — “Planned Maintenance” per https://status.us.ovhcloud.com (Status.io), checked 2026-09-16 12:28 UTC.
15incidents, last 30 days
20incidents, last 90 days
22incidents on record
Status.io only exposes incidents that are open right now, so this history starts on 2026-09-04, the day we first watched Ovhcloud. It fills in from here.
Incidents on record (22)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-09-09 21:19 UTC | PCI host outage in US-EAST-VA-1 | investigating | — | 2 d 15 h (approx.) |
| 2026-09-09 08:48 UTC | PCI host outage in US-EAST-VA-1 | investigating | — | 27 h 27 min (approx.) |
| 2026-09-09 08:29 UTC | VPS host outage in US-EAST-VA-2 | investigating | — | 27 h 46 min (approx.) |
| 2026-09-09 00:48 UTC | PCI host outage in US-EAST-VA-1 | investigating | — | 35 h 27 min (approx.) |
| 2026-09-08 17:26 UTC | PCI host outage in US-EAST-VA-1 | investigating | — | 42 h 48 min (approx.) |
| 2026-09-06 10:11 UTC | VIN - Network Issue - V119G26 - V119G27 | investigating | — | 3 d 2 h (approx.) |
| 2026-09-04 17:50 UTC | PCI host outage in US-WEST-OR-1 | investigating | — | 11 h 29 min (approx.) |
| 2026-09-04 15:00 UTC | Block storage maintenance notification[US-WEST-OR-1] | maintenance | maintenance | 5 d 21 h (approx.) |
| 2026-09-03 18:36 UTC | Delays in Server Delivery due to Backend Processing Issue | investigating | — | 34 h 43 min (approx.) |
| 2026-08-31 17:04 UTC | [BHS8][Cooling System] - Rack BHS0813B01C maintenance notification | maintenance | maintenance | open |
| 2026-08-31 16:49 UTC | [BHS8][Cooling System] - Rack BHS0813B01B maintenance notification | maintenance | maintenance | 15 d 19 h (approx.) |
| 2026-08-31 16:43 UTC | [GRA4][Infrastructure] - Multiple racks maintenance notification | maintenance | maintenance | open |
| 2026-08-31 16:30 UTC | [BHS8][Cooling System] - Rack BHS0813B01A maintenance notification | maintenance | maintenance | 14 d 19 h (approx.) |
| 2026-08-25 14:42 UTC | Service Cancelation issue for VPS Product | investigating | — | 15 d 21 h (approx.) |
| 2026-08-20 04:05 UTC | Maintenance to perform vCSA Minor Upgrade to 8.0U3k | maintenance | maintenance | 23 d 8 h (approx.) |
| 2026-08-07 16:21 UTC | [GRA3][Infrastructure] - Rack GRA0404A01D maintenance notification | maintenance | maintenance | 31 d 20 h (approx.) |
| 2026-08-07 16:19 UTC | [GRA3][Infrastructure] - Rack GRA0404A03D maintenance notification | maintenance | maintenance | 38 d 20 h (approx.) |
| 2026-08-07 16:19 UTC | [GRA4][Infrastructure] - Rack GRA0404A04D maintenance notification | maintenance | maintenance | 39 d 20 h (approx.) |
| 2026-08-07 16:19 UTC | [GRA3][Cooling System] - Rack GRA0404B01D maintenance notification | maintenance | maintenance | open |
| 2026-07-07 15:50 UTC | [GRA/BHS][Identity, Security & Operations] - Logs Data Platform maintenance notification | maintenance | maintenance | open |
| 2026-04-03 14:02 UTC | [VIN1] Server Power Loss VIN0120A02B | investigating | — | open |
| 2026-03-24 19:52 UTC | One VPS host down in VIN | investigating | — | open |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Ovhcloud with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"ovhcloud"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}