[Africa][Support] - Tunisian support number maintenance notification
Scheduled maintenance is currently in progress. We will provide updates as necessary.
The latest update from OVHcloud.
State
In progress
Started
Ongoing for
1 h 46 min
Worst impact
Maintenance
Timeline
5 updatesScheduled
3 min 3%
In progress
1 h 42 min 97%
Updates
Times in UTCAs posted by OVHcloud
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Maintenance will begin as scheduled in 60 minutes.
As part of our continuous improvement plan, maintenance is scheduled on our Tunisian support number +216 71 966 044. Start time : 12/11/2026 14:00 UTC End time : 12/11/2026 18:00 UTC Service impact : The Tunisian support number will not be reachable during the maintenance window. Workaround : The Help Centre, Live Chat and the support number +33 9 72 10 10 07 remain accessible. The customer control panel https://www.ovh.com/manager also remains available, and you can create your support tickets from there. If you have a Business or Enterprise support level, your dedicated phone number remains available to reach your technical advisor in case of emergency. Service improvement : As part of our continuous improvement policy, we will be performing maintenance on our support telephony services. Thank you for your understanding.
Maintenance will begin as scheduled in 60 minutes.
As part of our continuous improvement plan, maintenance is scheduled on our Tunisian support number +216 71 966 044. Start time : 12/11/2026 14:00 UTC End time : 12/11/2026 18:00 UTC Service impact : The Tunisian support number will not be reachable during the maintenance window. Workaround : The Help Centre, Live Chat and the support number +33 9 72 10 10 07 remain accessible. The customer control panel https://www.ovh.com/manager also remains available, and you can create your support tickets from there. If you have a Business or Enterprise support level, your dedicated phone number remains available to reach your technical advisor in case of emergency. Service improvement : As part of our continuous improvement policy, we will be performing maintenance on our support telephony services. Thank you for your understanding.
Affected components
2OVHcloud in the last 90 days
Full historyIncidents in 90 days
258
Days with an incident
90
Median duration
1 h 41 min
This incident
Not comparable
Other OVHcloud incidents
All incidentsOVHcloud·[RBX8][Dedicated Servers] - Racks RBX0841A05A and RBX0841A05B incident notification
OVHcloud reports that some Dedicated Servers in racks RBX0841A05A and RBX0841A05B in the RBX region are unavailable. OVHcloud identified a cooling system issue. All servers in rack RBX0841A05B and many servers in rack RBX0841A05A now work.
OVHcloud·[GRA3][Dedicated Servers] - Rack GRA0326A03B incident notification
OVHcloud reports that the public network did not work in rack GRA0326A03B in the GRA region. This affected Dedicated Servers. The incident is resolved. It lasted from 10:37 UTC to 14:35 UTC.
OVHcloud·[RBX/GRA/SBG][Collaborative Solutions] - EmailPro, Hosted Exchange, Private Exchange, MX Plan incident notification
OVHcloud reports that some management operations, such as password changes and account deletions, did not work on EmailPro, Hosted Exchange, Private Exchange and MX Plan in the RBX, GRA and SBG datacenters. OVHcloud says the incident is resolved. It lasted 1 hour and 41 minutes.
OVHcloud·[Global][Databases & Data Analytics] - API incident notification
OVHcloud reports that the API of PostgreSQL, MySQL, Valkey, ClickHouse, Dashboards, Kafka, Kafka Connect, Kafka MirrorMaker and OpenSearch had slowness and errors in BHS, DE, GRA, EU-WEST-PAR, EU-SOUTH-MIL, AP-SOUTH-MUM, RBX, SBG, SGP, UK and WAW. OVHcloud resolved the incident. The incident lasted 53 minutes, from 09:15 UTC to 10:08 UTC on 12 November 2026.
OVHcloud·[RBX3][Dedicated Servers] - Rack 43N06 incident notification
OVHcloud reports that some Dedicated Servers in rack 43N06 in the RBX region were unavailable. OVHcloud identified an electrical equipment issue. OVHcloud resolved the incident, which lasted about 74 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