[US-WEST-OR][Storage] - Cloud Archive incident notification
The Cloud Archive service in the US-WEST-OR region has an increased error rate. Storing or retrieving archived data may fail. OVHcloud reports the root cause as identified.
State
Identified
Started
Ongoing for
7 h 59 min
Worst impact
Partial outage
Timeline
5 updatesInvestigating
1 h 31 min 19%
Resolved
3 min 1%
Monitoring
33 min 7%
Identified
5 h 51 min 73%
Updates
Times in UTCAs posted by OVHcloud
We are currently experiencing an incident affecting our Cloud Archive offering in the US-WEST-OR region. The root cause has been identified. Please find the details of this incident below : Start time : 19/11/2026 16:30 UTC Impacted Service(s) : The Cloud Archive service is experiencing an increased error rate in the US-WEST-OR region. Customers Impact : Customers may experience errors when storing or retrieving their archived data. Root Cause : This incident is caused by a software issue. Ongoing Actions : Our teams are actively working to restore service as quickly as possible. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
We would like to inform you that our service has been fully restored as of 19/11/2026 21:45 UTC. Monitoring is still in place to ensure long-term stability. Please find the details of this incident below : Start time : 19/11/2026 16:30 UTC Impacted Service(s) : The Cloud Archive service experienced an increased error rate in the US-WEST-OR region. Customers Impact : Customers may have experienced errors when storing or retrieving their archived data. We apologize for any inconvenience caused and appreciate your understanding.
We are currently experiencing an incident affecting our Cloud Archive offering, which is causing temporary availability issues in the US-WEST-OR region. Please find the details of this incident below : Start time : 19/11/2026 16:30 UTC Impacted Service(s) : The Cloud Archive service is experiencing an increased error rate in the US-WEST-OR region. Customers Impact : Customers may experience errors when storing or retrieving their archived data. Ongoing Actions : Our teams are investigating to determine the origin of the incident to fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
We are currently experiencing an incident affecting our Cloud Archive offering, which is causing temporary availability issues in the US-WEST-OR region. Please find the details of this incident below : Start time : 19/11/2026 16:30 UTC Impacted Service(s) : The Cloud Archive service is experiencing an increased error rate in the US-WEST-OR region. Customers Impact : Customers may experience errors when storing or retrieving their archived data. Ongoing Actions : Our teams are investigating to determine the origin of the incident to fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
Affected components
2OVHcloud in the last 90 days
Full historyIncidents in 90 days
184
Days with an incident
90
Median duration
1 h 46 min
This incident
4.5× the median
Other OVHcloud incidents
All incidentsOVHcloud·[Global][Identity, Security & Operations] - Logs Data Platform incident notification
We would like to inform you that the incident affecting our Identity, Security & Operations offering has now been resolved. Please find the details of this incident below : Start time : 19/11/2026 17:31 UTC End time : 19/11/2026 20:50 UTC Impacted Service(s) : The OpenSearch API of the Logs Data Platform service was temporarily unavailable. Customers Impact : Customers were temporarily unable to query or access their logs through the OpenSearch API. Log ingestion remained unaffected. Root Cause : This incident was caused by a network equipment issue. We thank you for your understanding and patience throughout this incident.
OVHcloud·[BHS-CHI][Infrastructure] - Backbone incident notification
OVHcloud reports increased latency on the Backbone link between BHS and CHI. OVHcloud states that the incident is resolved. The incident lasted from 19:41 UTC to 20:38 UTC.
OVHcloud·[Global][Collaborative Solutions] - Zimbra incident notification
OVHcloud Zimbra mailbox access, webmail, email delivery, and operations had a partial outage. OVHcloud reports that the incident is resolved. It lasted 3 hours and 4 minutes, from 14:30 to 17:34 UTC.
OVHcloud·[Global][Web Hosting] - HTTP/2 incident notification
OVHcloud Web Hosting has degraded service on all Web Hosting clusters. HTTP/2 support is temporarily disabled, and sites are served over HTTP/1.1 only. OVHcloud is investigating.
OVHcloud·[GRA2][Dedicated Servers] - Rack G224B17 Incident Notification
Dedicated Servers in Rack G224B17 in the GRA region are unavailable. OVHcloud reports that the incident is resolved and lasted 16 minutes. The cause was a network equipment issue.
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.
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.
https://outages.live/feed.xml?providers=ovhcloud/feed subscribe https://outages.live/feed.xml?providers=ovhcloudFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane