[Global][Collaborative Solutions] - Zimbra maintenance notification
Scheduled maintenance is currently in progress. We will provide updates as necessary.
The latest update from OVHcloud.
State
In progress
Started
Ongoing for
19 min
Worst impact
Maintenance
Timeline
2 updatesScheduled
1 min 2%
In progress
18 min 98%
Updates
Times in UTCAs posted by OVHcloud
Scheduled maintenance is currently in progress. We will provide updates as necessary.
As part of our continuous improvement plan, maintenance is scheduled on our Zimbra offer. Start time : 18/11/2026 20:01 UTC End time : 19/11/2026 10:00 UTC Service impact : During the maintenance, the service will be restarted on the servers hosting the mailboxes. During each restart, the mailboxes hosted on the concerned server will be unreachable for approximately 5 minutes. No emails will be lost. Service improvement : As part of our continuous improvement policy, we will be performing maintenance on our Zimbra infrastructure. Thank you for your understanding.
Affected components
6OVHcloud in the last 90 days
Full historyIncidents in 90 days
195
Days with an incident
90
Median duration
1 h 42 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[GRA][Web Hosting] - Cluster129/Filerz956 incident notification
Web Hosting is slow on Cluster129 in the GRA datacenter. Filerz956 shows latency on Cluster129. OVHcloud reports the status as investigating.
OVHcloud·[GRA][Web Hosting] - Cluster129/Filerz956 incident notification
Web Hosting on Cluster129 and Filerz956 in the GRA datacenter had temporary latency. OVHcloud reports that the incident is resolved. The incident lasted 18 minutes.
OVHcloud·[LIM/FRA][Infrastructure] - Backbone incident notification
The OVHcloud backbone link between LIM and FRA had increased latency and packet loss. OVHcloud reports that the incident is resolved and lasted 50 minutes, from 14:55 to 15:45 UTC. The cause was a network equipment issue.
OVHcloud·[GRA1][Dedicated Servers] - Rack G125A23 incident notification
Some Dedicated Servers in rack G125A23 in the GRA region were temporarily unavailable. OVHcloud reports that the incident is resolved and lasted 3 hours and 55 minutes.
OVHcloud·[SBG5][Dedicated Servers] - Rack SBG0506B04C Incident Notification
The vRack Private Network does not work on Dedicated Servers in rack SBG0506B04C in the SBG region. OVHcloud reports that the incident is resolved and that it lasted from 11:54 UTC to 15:23 UTC.
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