[GLOBAL][Collaborative solutions] - Mail incident notification
We are pleased to inform you that the incident affecting our MX Plan and Zimbra offering has been resolved. Start time : 15/10/2026 08:30 UTC End time : 18/10/2026 13:30 UTC Root Cause : This incident was caused by a software issue issue. We apologize for any inconvenience caused and appreciate your understanding.
The latest update from OVHcloud.
State
Resolved
Started
17 d ago
2026-10-15 10:15 UTC
Lasted
5 days
until 2026-10-20 07:09 UTC
Worst impact
Partial outage
Timeline
7 updatesIdentified
3 days 64%
Monitoring
41 h 36 min 36%
Updates
Times in UTCAs posted by OVHcloud
We are pleased to inform you that the incident affecting our MX Plan and Zimbra offering has been resolved. Start time : 15/10/2026 08:30 UTC End time : 18/10/2026 13:30 UTC Root Cause : This incident was caused by a software issue issue. We apologize for any inconvenience caused and appreciate your understanding.
We would like to inform you that a workaround has been implemented and our service has been fully restored as of 18/10/2026 13:30 UTC. Monitoring is still in place to ensure long-term stability. Please find the details of this incident below : Start time : 15/10/2026 08:30 UTC Impacted Service(s) : EmailPro, Trusted Exchange, Hosted Exchange, Private Exchange, Zimbra and MX Plan Canada services were temporarily unavailable. Customers Impact : Customers using EmailPro, Trusted Exchange, Hosted Exchange, Private Exchange, Zimbra and MX Plan Canada were temporarily unable to send and receive emails. Root Cause : This incident was caused by our provider. We apologize for any inconvenience caused and appreciate your understanding.
Please find an update of this incident below : Update : EmailPro, Trusted Exchange, Hosted Exchange, Private Exchange, Zimbra and MX Plan Canada services are still impacted by this incident. Following a faulty software update from our provider, an issue is affecting mail queues and some emails may not be sent or received. Ongoing Actions : Our teams remain fully mobilised and are awaiting a fix from our provider 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.
Please find an update of this incident below : Update : In coordination with our provider, our teams have identified a potential fix to restore mail flow. A new configuration is currently being applied and the affected servers are being restarted. Ongoing Actions : Our teams are mobilised to deploy this corrective action and are closely monitoring its effect on the service. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
We have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : The incident originates from one of our providers. Ongoing Actions : Our teams are working closely with the provider 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 have new information regarding the incident that affected your service(s). Please find below an update on the situation: Update : From 15/10/2026 12:50 UTC till 16/10/2026 08:50 UTC, no impact was observed on the services. Since 16/10/2026 08:50 UTC, customers using EmailPro, Trusted Exchange and Hosted Exchange, MXplan Canada are again temporarily unable to send and receive mails. Ongoing Actions : The incident has been identified and our teams are mobilised 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 are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Collaborative solutions offer on the specific GLOBAL region. Here are some supplementary details : Start time : 15/10/2026 08:30 UTC Impacted Service(s) : EmailPro, Trusted Exchange and Hosted Exchange, MX Plan Canada Customers Impact : Customers using EmailPro, Trusted Exchange and Hosted Exchange, MXplan Canada are temporarily unable to send and receive mails. Root Cause : This incident is caused by a software issue. Ongoing Actions : The incident has been identified and our teams are mobilised 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.
Affected components
5OVHcloud in the last 90 days
Full historyIncidents in 90 days
217
Days with an incident
90
Median duration
1 h 35 min
This incident
74× the median
Other OVHcloud incidents
All incidentsOVHcloud·[SBG8][Virtual Private Servers] - VPS Incident Notification
Some Virtual Private Servers in the SBG8 region were temporarily unreachable. The incident affected some VPS in the SBG region. OVHcloud identified a network equipment issue as the cause. OVHcloud resolved the incident. The incident started at 17:55 UTC and ended at 19:54 UTC.
OVHcloud·[SBG6/8][Virtual Private Servers] - VPS Incident Notification
Some Virtual Private Servers in the SBG5, SBG6 and SBG8 regions were unreachable. OVHcloud reports that the incident is resolved. It lasted from 17:55 UTC to 19:30 UTC.
OVHcloud·[RBX3][Dedicated Servers] - Rack 46E19 Incident Notification
OVHcloud reports that servers in Rack 46E19, RBX3, were not accessible through the IPMI interface. The incident was caused by a network equipment issue. The incident is resolved and it lasted 2 hours and 23 minutes.
OVHcloud·[SBG5/7][Compute - Instance] - Compute Instance Incident Notification
OVHcloud Compute Instance service did not work for some instances in the SBG5 and SBG7 regions. OVHcloud reports that the incident is resolved. The incident lasted from 17:55 UTC to 19:30 UTC.
OVHcloud·[RBX2][Dedicated Servers] - Rack 21D12 Incident Notification
We are pleased to inform you that the incident affecting our Dedicated Servers offering has been resolved. Start time : 31/10/2026 19:38 UTC End time : 31/10/2026 22:10 UTC Root Cause : This incident was caused by an electrical equipment issue. We apologize for any inconvenience caused and appreciate your understanding.
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.cc/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.cc/feed.xml?providers=ovhcloud/feed subscribe https://outages.cc/feed.xml?providers=ovhcloudFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane