Live

[Global][Collaborative Solutions] - Zimbra maintenance notification

MaintenanceOfficial update

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 updates
20:3020:3420:3920:4320:48
MaintenanceUpdate postedTimes in UTC

Scheduled

1 min 2%

In progress

18 min 98%

Updates

Times in UTC

As posted by OVHcloud

In progress

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Scheduled

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

6
Web AccessDelivery emailOperationsCollaborative solutions || Zimbra - Web AccessCollaborative solutions || Zimbra - Delivery emailCollaborative solutions || Zimbra - Operations

OVHcloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

195

Days with an incident

90

Median duration

1 h 42 min

This incident

Not comparable

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

24 days
median 1 h 42 min
90 days agoToday

Other OVHcloud incidents

All incidents

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