outages.live
Live
OVHcloudIncident ·

[SYD][Dedicated Servers] - Room S2-5X incident notification

Partial outageOfficial update
0

The public network does not work for Dedicated Servers in several racks of the SYD zone. OVHcloud reports that it identified the state of the incident. The cause is a network equipment issue.

State

Identified

Started

Ongoing for

21 min

Worst impact

Partial outage

Timeline

1 update
07:2707:3207:3707:4307:48
Partial outageUpdate postedTimes in UTC

Identified

21 min 100%

Updates

Times in UTC

As posted by OVHcloud

Identified

We are currently experiencing an incident affecting our Dedicated Servers offering in several racks of the SYD zone. The root cause has been identified. Please find the details of this incident below : Start time : 13/11/2026 07:10 UTC Impacted Service(s) : Public network is temporarily unavailable for servers located in the racks listed below : S2-5X-02-09A S2-5X-02-09B S2-5X-01-08B S2-5X-02-08A S2-5X-02-08B S2-5X-01-04A S2-5X-01-04B Customers Impact : Customers are temporarily unable to access their servers through public network. Root Cause : This incident is caused by a network equipment issue. 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

2
SYDDedicated Servers || Network - SYD

OVHcloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

260

Days with an incident

90

Median duration

1 h 41 min

This incident

79% shorter than the median

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

41 days
median 1 h 41 min
90 days agoToday

Other OVHcloud incidents

All incidents

OVHcloud·[US-EAST-VA][Storage] - Object Storage Incident Notification

OVHcloud Object Storage in the US-EAST-VA region had a partial outage. High Performance and Standard Object Storage had increased latency and 500/503 errors. OVHcloud reports that the incident is resolved. The incident lasted 1 hour and 43 minutes.

Resolved

OVHcloud·[RBX8][Dedicated Servers] - Racks RBX0841A05A and RBX0841A05B incident notification

OVHcloud Dedicated Servers in racks RBX0841A05A and RBX0841A05B were temporarily unavailable in the RBX region. OVHcloud reports that the incident is resolved. The incident lasted from 13:09 UTC to 18:36 UTC on 12/11/2026.

Resolved

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.

Resolved

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.

Resolved

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.

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