[Global][Domains] - .MG Domains Name incident notification
The .MG domain service does not work for Registration, Renew, Transfer, Restore, and Delete operations. OVHcloud has identified the incident. The cause comes from a provider, and OVHcloud teams work to restore the service.
State
Identified
Started
1 h ago
2026-11-02 09:04 UTC
Ongoing for
1 h 18 min
Worst impact
Partial outage
Timeline
1 updateIdentified
1 h 18 min 100%
Updates
Times in UTCAs posted by OVHcloud
We are currently experiencing an incident affecting our Domains offering. The root cause has been identified. Please find the details of this incident below : Start time : 02/11/2026 08:45 UTC Impacted Service(s) : Multiple operations (Registration, Renew, Transfer, Restore, Delete) are temporarily unavailable for .MG domains. Customers Impact : Customers are temporarily unable to perform specified operations on .MG domains. Root Cause : This incident is caused by our provider. 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
10OVHcloud in the last 90 days
Full historyIncidents in 90 days
221
Days with an incident
90
Median duration
1 h 35 min
This incident
18% shorter than the median
Other OVHcloud incidents
All incidentsOVHcloud·[SBG5][Dedicated Servers] - Rack SBG0505B05B incident notification
Some Dedicated Servers in rack SBG0505B05B in the SBG region are temporarily unavailable, and customers cannot access them. OVHcloud has identified the root cause, which is a maintenance, and teams are working to restore service.
OVHcloud·[Global][Domains] - .CO Domains Name incident notification
The .CO domain registration, renew, transfer, restore, and delete operations do not work for OVHcloud customers. OVHcloud identified the cause as its provider and works with that provider to restore service.
OVHcloud·[ERI1][Dedicated Servers] - Rack E105A01 incident notification
OVHcloud reports that Dedicated Servers in rack E105A01 in the ERI region were temporarily unavailable. The incident is resolved and lasted about 5 minutes.
OVHcloud·[RBX3][Dedicated Servers] - Rack 42C19 incident notification
OVHcloud reports that some Dedicated Servers in rack 42C19 in the RBX region were temporarily unavailable. The incident is resolved. It lasted from 05:48 UTC to 07:18 UTC on 02/11/2026. The cause was an electrical equipment issue.
OVHcloud·[SBG8][Virtual Private Servers] - VPS Incident Notification
Some Virtual Private Servers in the SBG8 region were temporarily unreachable. The incident affected some VPS in the SBG region. OVHcloud identified a network equipment issue as the cause. OVHcloud resolved the incident. The incident started at 17:55 UTC and ended at 19:54 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.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