[Global][DNS] - .TN DNS Hosting incident notification
The ns1.tn.ovh.net DNS server is temporarily unavailable. This affects the OVHcloud .TN DNS hosting service. Domains that use ns1.tn.ovh.net alone can have DNS resolution failures. OVHcloud reports that the incident is under investigation.
State
Investigating
Started
Ongoing for
36 min
Worst impact
Partial outage
Timeline
2 updatesInvestigating
36 min 100%
Updates
Times in UTCAs posted by OVHcloud
We are currently experiencing an incident affecting our .TN DNS offering, which is causing temporary availability issues. Please find the details of this incident below : Start time : 15/11/2026 01:19 UTC Impacted Service(s) : The ns1.tn.ovh.net DNS server is temporarily unavailable. Customers Impact : Customers whose .tn domains rely only on ns1.tn.ovh.net may experience DNS resolution failures. Domains using both ns1.tn.ovh.net and dns1.tn.ovh.net are not expected to be impacted. Ongoing Actions : In coordination with our provider, 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.
We are currently experiencing an incident affecting our DNS offering, which is causing temporary availability issues. Please find the details of this incident below : Start time : 15/11/2026 01:19 UTC Impacted Service(s) : The ns1.tn.ovh.net DNS server is temporarily unavailable. Customers Impact : Customers whose .tn domains rely only on ns1.tn.ovh.net may experience DNS resolution failures. Domains using both ns1.tn.ovh.net and dns1.tn.ovh.net are not expected to be impacted. Ongoing Actions : In coordination with our provider, 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
260
Days with an incident
90
Median duration
1 h 41 min
This incident
64% shorter than the median
Other OVHcloud incidents
All incidentsOVHcloud·[SGP1][Storage] - Block Storage incident notification
OVHcloud Block Storage volumes in the SGP1 region had degraded performance. OVHcloud reports that the incident is resolved. The incident lasted 58 minutes.
OVHcloud·[GRA][Web Hosting] - Cluster128 SSH/FTP services incident notification
We would like to inform you that an incident affected our Web Hosting offering on Cluster128. This incident has since been resolved. Please find the details of this incident below : Start time : 14/11/2026 08:18 UTC End time : 14/11/2026 09:30 UTC Impacted Service(s) : SSH and FTP services on Web Hosting Cluster128 were temporarily unavailable. Customers Impact : Customers were temporarily unable to access their files via SSH or FTP. Root Cause : This incident was caused by a software issue. We thank you for your understanding and patience throughout
OVHcloud·[GRA1][Dedicated Servers] - Rack G127A24 incident notification
OVHcloud reports that the vRack network did not work for Dedicated Servers in rack G127A24 in the GRA region. The incident is resolved, and it lasted about 57 minutes. OVHcloud states that a network equipment issue caused the incident.
OVHcloud·[BHS5][Dedicated Servers] - Rack T05G37 incident notification
OVHcloud reports that some Dedicated Servers in rack T05G37 in the BHS region were unavailable. The incident was caused by a cooling system issue. OVHcloud resolved the incident, which lasted 2 hours and 52 minutes.
OVHcloud·[GRA3][Dedicated Servers] - Rack GRA0325B05A incident notification
OVHcloud reports that the vRack network did not work for Dedicated Servers in rack GRA0325B05A in the GRA region. OVHcloud identified a cooling system issue as the cause. OVHcloud resolved the incident, which lasted from 06:15 UTC to 08:00 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.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