Live

[US-WEST-LZ-LAX][LocalZones] - VPS Incident Notification

0

We had an incident on our Virtual Private Servers offer which has now been resolved. Here are some supplementary details : Start time : 20/11/2026 15:59 UTC End time : 20/11/2026 18:53 UTC Impacted Service(s) : Some VPS in the Los Angeles Local Zone experienced partial connectivity issues. Customers Impact : Customers may have experienced connectivity issues when accessing their VPS located in the specified Local Zone. Root Cause : A service disruption occurred due to an unexpected infrastructure malfunction. We thank you for your understanding and patience throughout this incident.

The latest update from OVHcloud.

State

Resolved

Started

Lasted

1 min

Worst impact

Notice

Timeline

1 update
19:4819:4819:4819:4919:49
NoticeUpdate postedTimes in UTC

Resolved

1 min 100%

Updates

Times in UTC

As posted by OVHcloud

Resolved

We had an incident on our Virtual Private Servers offer which has now been resolved. Here are some supplementary details : Start time : 20/11/2026 15:59 UTC End time : 20/11/2026 18:53 UTC Impacted Service(s) : Some VPS in the Los Angeles Local Zone experienced partial connectivity issues. Customers Impact : Customers may have experienced connectivity issues when accessing their VPS located in the specified Local Zone. Root Cause : A service disruption occurred due to an unexpected infrastructure malfunction. We thank you for your understanding and patience throughout this incident.

Affected components

2
US-WEST-LZ-LAXLocalZones || US-WEST - US-WEST-LZ-LAX

OVHcloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

176

Days with an incident

90

Median duration

1 h 46 min

This incident

100% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

7 days
median 1 h 46 min
90 days agoToday

Other OVHcloud incidents

All incidents

OVHcloud·[RBX3][Dedicated Servers] - Rack 46N07 Incident Notification

Some Dedicated Servers in Rack 46N07 in the RBX region do not work. OVHcloud reports that the incident is resolved. The incident lasted 41 minutes, from 17:32 UTC to 18:13 UTC.

Resolved

OVHcloud·[US][Backbone] - Backbone Incident Notification

We had an incident on our Backbone infrastructure which has now been resolved. Here are some supplementary details : Start time : 20/11/2026 14:52 UTC End time : 20/11/2026 15:16 UTC Impacted Service(s) : Packet loss and increased latency occurred on our backbone infrastructure in the US region. Customers Impact : Customers may have experienced packet loss and increased latency when accessing their services in the US region. Root Cause : This incident was caused by our provider. We thank you for your understanding and patience throughout this incident.

Resolved

OVHcloud·[RBX5][Dedicated Servers] - Rack 45D18 incident notification

The vRack network does not work for Dedicated Servers in rack 45D18 in the RBX region. OVHcloud reports that the incident is resolved. It lasted from 08:07 UTC to 11:14 UTC.

Resolved

OVHcloud·[EU/US/APAC][Infrastructure] - Backbone incident notification

OVHcloud reports packet loss on some backbone links between Europe and APAC, and between North America and APAC. The incident is resolved. OVHcloud gives the start time as 08:15 UTC and the end time as 09:15 UTC on 20/11/2026.

Resolved

OVHcloud·[GLOBAL][AI & Machine Learning] - AI Endpoint Incident Notification

The AI Endpoint component of OVHcloud AI & Machine Learning is not available. OVHcloud reports that the incident is resolved. The incident lasted from 06:25 UTC to 07:12 UTC.

Resolved

Follow OVHcloud

Your coding agent knows when OVHcloud is down, and tells you when a failure is theirs, not yours. You can also get OVHcloud incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "ovhcloud" and tell me if OVHcloud has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=ovhcloud
Slack
/feed subscribe https://outages.live/feed.xml?providers=ovhcloud

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane