[RBX/GRA][Collaborative solutions] - EmailPro Incident Notification
We would like to inform you that the incident affecting our EmailPro offering has now been resolved. Please find the details of this incident below : Start time : 22/10/2026 12:00 UTC End time : 23/10/2026 07:46 UTC Impacted Service(s) : Some EmailPro mailboxes were temporarily unavailable. Customers Impact : Customers were temporarily unable to access their EmailPro mailboxes. Root Cause : This incident was caused by a software issue. We thank you for your understanding and patience throughout this incident.
The latest update from OVHcloud.
State
Resolved
Started
10 d ago
2026-10-22 15:59 UTC
Lasted
15 h 48 min
until 2026-10-23 07:47 UTC
Worst impact
Partial outage
Timeline
3 updatesInvestigating
15 h 48 min 100%
Updates
Times in UTCAs posted by OVHcloud
We would like to inform you that the incident affecting our EmailPro offering has now been resolved. Please find the details of this incident below : Start time : 22/10/2026 12:00 UTC End time : 23/10/2026 07:46 UTC Impacted Service(s) : Some EmailPro mailboxes were temporarily unavailable. Customers Impact : Customers were temporarily unable to access their EmailPro mailboxes. Root Cause : This incident was caused by a software issue. We thank you for your understanding and patience throughout this incident.
Please find an update of this incident below : Update : Some EmailPro mailboxes are progressively becoming accessible again. Ongoing Actions : Our teams are mobilised to restore access to the remaining mailboxes. 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 which is causing temporary availability issue on EmailPro services. Here are some supplementary details : Start time : 22/10/2026 12:00 UTC Impacted Service(s) : Some EmailPro mailboxes are temporarily unavailable. Customers Impact : Customers are temporarily unable to access their EmailPro mailboxes. Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
Affected components
6OVHcloud in the last 90 days
Full historyIncidents in 90 days
217
Days with an incident
90
Median duration
1 h 35 min
This incident
10.0× the median
Other OVHcloud incidents
All incidentsOVHcloud·[SBG8][Virtual Private Servers] - VPS Incident Notification
Some Virtual Private Servers in the OVHcloud SBG8 region are temporarily unreachable. OVHcloud has identified the incident and states that a network equipment issue causes it. OVHcloud teams are working to restore service.
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
Servers in Rack 46E19 in the RBX region are not accessible through the IPMI interface. The Dedicated Servers network in RBX is affected. OVHcloud reports that the incident is identified. The cause is a network equipment issue, and teams work to restore service.
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