When did the incident start and end?

It started at 2026-11-09 08:00 UTC. This page shows the end time when OVHcloud marks it resolved.

How do I get alerts for OVHcloud?

Subscribe to the OVHcloud live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of OVHcloud. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

OVHcloudIncident ·

[GLOBAL][Domains] - .DK Domain Names Incident Notification

Q: What happened?

OVHcloud reported "[GLOBAL][Domains] - .DK Domain Names Incident Notification" on its status page at 2026-11-09 08:00 UTC. OVHcloud reports that multiple operations on .DK domain names do not work. Registration, Renew, Transfer, Restore, and Delete are affected for .DK domain names. OVHcloud identified the root cause and teams are working to restore service.

Q: What is affected?

OVHcloud lists these components: Registration, Renew, Transfer, Restore, Delete, Domains || Domains Name - Registration, and 4 more.

Partial outageOfficial update

OVHcloud reports that multiple operations on .DK domain names do not work. Registration, Renew, Transfer, Restore, and Delete are affected for .DK domain names. OVHcloud identified the root cause and teams are working to restore service.

State

Identified

Started

Ongoing for

19 h 42 min

Worst impact

Partial outage

Timeline

1 update

08:0012:5617:5122:4703:42

Partial outageUpdate postedTimes in UTC

Identified

19 h 42 min 100%

Updates

Times in UTC

As posted by OVHcloud

Identified

We are currently experiencing an incident affecting our Domains offering for .DK Domain Names The root cause has been identified. Please find the details of this incident below : Start time : 09/11/2026 07:50 UTC Impacted Service(s) : Multiple operations (Registration, Renew, Transfer, Restore, Delete) are temporarily unavailable for .DK Domain Names. Customers Impact : Customers are temporarily unable to perform specified operations on .DK Domain Names. 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

RegistrationRenewTransferRestoreDeleteDomains || Domains Name - RegistrationDomains || Domains Name - RenewDomains || Domains Name - Transfer

OVHcloud in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

246

Days with an incident

Median duration

1 h 39 min

This incident

12× the median

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

41 days

median 1 h 39 min

90 days agoToday

Other OVHcloud incidents

All incidents

OVHcloud·[BHS1][Dedicated Servers] - Rack T01C28 incident notification

OVHcloud reports a partial outage of Dedicated Servers public network in rack T01C28 in the BHS region. Since 03:15 UTC, the public network in this rack is unavailable. OVHcloud identified a network equipment issue and its teams work to restore service.

Partial outage

OVHcloud·[Global][Collaborative Solutions] - Zimbra incident notification

OVHcloud reports that access to Zimbra mailboxes and webmail was unavailable. The affected components are Web Access and Zimbra Web Access. OVHcloud says the incident is resolved, and it lasted about 53 minutes.

Resolved

OVHcloud·[Global][Collaborative Solutions] - Zimbra Incident Notification

OVHcloud reports slow delivery to some Zimbra mailboxes and webmail accounts. The incident affects the Zimbra Delivery email component. OVHcloud identified the root cause and its teams are working to restore service. Incoming emails are queued.

Partial outage

OVHcloud·[FR][Collaborative Solutions] - Zimbra Incident Notification

OVHcloud Zimbra Web Access, Delivery email, and Operations have a partial outage in France. Access to some mailboxes and webmail is unavailable, and incoming emails are queued. OVHcloud reports the incident resolved. The incident lasted from 07:10 UTC to 16:30 UTC on 09/11/2026.

Resolved · 1 affected

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 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.

Resolved

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