[Global][Collaborative Solutions] - MX Plan and Zimbra incident notification
We would like to inform you that the incident affecting our MX Plan and Zimbra offerings has now been resolved. Please find the details of this incident below : Start time : 15/10/2026 17:52 UTC End time : 15/10/2026 19:19 UTC Impacted Service(s) : Access to some MX Plan and Zimbra mailboxes was temporarily unavailable. Customers Impact : Customers were temporarily unable to log in to their MX Plan and Zimbra email accounts, whether via webmail or an email client (e.g., Outlook, Thunderbird), and could not send or receive emails. Root Cause : This incident was caused by a hardware issue. We thank you for your understanding and patience throughout this incident.
The latest update from OVHcloud.
State
Resolved
Started
17 d ago
2026-10-15 18:50 UTC
Lasted
31 min
until 2026-10-15 19:22 UTC
Worst impact
Partial outage
Timeline
3 updatesIdentified
31 min 100%
Updates
Times in UTCAs posted by OVHcloud
We would like to inform you that the incident affecting our MX Plan and Zimbra offerings has now been resolved. Please find the details of this incident below : Start time : 15/10/2026 17:52 UTC End time : 15/10/2026 19:19 UTC Impacted Service(s) : Access to some MX Plan and Zimbra mailboxes was temporarily unavailable. Customers Impact : Customers were temporarily unable to log in to their MX Plan and Zimbra email accounts, whether via webmail or an email client (e.g., Outlook, Thunderbird), and could not send or receive emails. Root Cause : This incident was caused by a hardware issue. We thank you for your understanding and patience throughout this incident.
We are currently experiencing an incident affecting our MX Plan and Zimbra offerings. The root cause has been identified. Please find the details of this incident below : Start time : 15/10/2026 17:52 UTC Impacted Service(s) : Access to some MX Plan and Zimbra mailboxes is temporarily unavailable. Customers Impact : Customers are temporarily unable to log in to their MX Plan and Zimbra email accounts, whether via webmail or an email client (e.g., Outlook, Thunderbird). Root Cause : This incident is caused by a hardware 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 are currently experiencing an incident affecting our MX Plan offering. The root cause has been identified. Please find the details of this incident below : Start time : 15/10/2026 17:52 UTC Impacted Service(s) : Access to some MX Plan mailboxes is temporarily unavailable. Customers Impact : Customers are temporarily unable to log in to their MX Plan email accounts, whether via webmail or an email client (e.g., Outlook, Thunderbird), and cannot send or receive emails. Incoming emails are being queued and will be delivered once the incident is resolved. Root Cause : This incident is caused by a hardware 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.
Affected components
4Follow 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