[Global][Collaborative Solutions] - MX Plan incident notification
OVHcloud reports an MX Plan incident. Sending and receiving emails on MX Plan was temporarily unavailable, and this affected Mail Flow. The incident is resolved. It lasted from 09:00 UTC to 14:47 UTC.
State
Resolved
Started
Lasted
1 h 6 min
Worst impact
Partial outage
Timeline
2 updatesInvestigating
1 h 6 min 100%
Updates
Times in UTCAs posted by OVHcloud
We would like to inform you that the incident affecting our MX Plan offering has now been resolved. Please find the details of this incident below : Start time : 07/11/2026 09:00 UTC End time : 07/11/2026 14:47 UTC Impacted Service(s) : Sending and receiving emails on MX Plan was temporarily unavailable. Customers Impact : Customers were temporarily unable to send or receive emails on their MX Plan email accounts. Incoming emails were queued and have been delivered following the resolution of the incident. Root Cause : This incident was caused by a software issue. We thank you for your understanding and patience throughout this incident.
We are currently experiencing an incident affecting our MX Plan offering, which is causing temporary availability issues. Please find the details of this incident below : Start time : 07/11/2026 09:00 UTC Impacted Service(s) : Sending and receiving emails on MX Plan is temporarily unavailable. Customers Impact : Customers are temporarily unable to send or receive emails on their MX Plan email accounts. Incoming emails are being queued and will be delivered once the incident is resolved. Ongoing Actions : Our teams are investigating to determine the origin of the incident to fix it. We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.
Affected components
2OVHcloud in the last 90 days
Full historyIncidents in 90 days
242
Days with an incident
90
Median duration
1 h 39 min
This incident
33% shorter than the median
Other OVHcloud incidents
All incidentsOVHcloud·[GRA2][Dedicated Servers] - Rack G243A16 incident notification
We had an incident on Dedicated Servers offer which has now been resolved. Here are some supplementary details : Start time : 07/11/2026 10:32 UTC End time : 07/11/2026 13:50 UTC Impacted Service(s) : Servers in the rack were no longer able to access the vRack network. Customers Impact : Customers were temporarily unable to access their servers via public and vRack networks located on the specified rack. Root Cause : This incident was caused by a network equipment issue. We thank you for your understanding and patience throughout this incident.
OVHcloud·[GRA2][Dedicated Servers] - Rack G243A16 incident notification
We had an incident on Dedicated Servers offer which has now been resolved. Here are some supplementary details : Start time : 07/11/2026 10:32 UTC End time : 07/11/2026 10:36 UTC Impacted Service(s) : Servers in the rack were no longer able to access the vRack network. Customers Impact : Customers were temporarily unable to access their servers via public and vRack networks located on the specified rack. Root Cause : This incident was caused by a network equipment issue. We thank you for your understanding and patience throughout this incident.
OVHcloud·[EU/CA/US][Control panel & API] - Control Panel incident notification
OVHcloud reports that the Control Panel was unavailable in the CA, EU, and US regions. Customers had errors when they accessed the Control Panel to order or manage services. Existing services were not affected. The incident is resolved and lasted 29 minutes.
OVHcloud·[GRA][Storage and Backups] - NasHA incident notification
OVHcloud reports that the NAS HA service in the GRA region had a temporary availability problem in Cluster614. OVHcloud states that the incident is resolved and lasted from 06/11/2026 06:48 UTC to 06/11/2026 11:03 UTC. OVHcloud reports that a hardware issue caused the incident.
OVHcloud·[BHS6][Dedicated Servers] - Rack T06F27 incident notification
OVHcloud reports that the vRack network did not work in rack T06F27 in the BHS region. This affected Dedicated Servers. OVHcloud identified a network equipment issue. OVHcloud replaced the faulty equipment. The incident is resolved and lasted about 3 hours and 10 minutes.
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