Live

[Global][Identity, Security & Operations] - Logs Data Platform incident notification

0

We would like to inform you that the incident affecting our Identity, Security & Operations offering has now been resolved. Please find the details of this incident below : Start time : 19/11/2026 17:31 UTC End time : 19/11/2026 20:50 UTC Impacted Service(s) : The OpenSearch API of the Logs Data Platform service was temporarily unavailable. Customers Impact : Customers were temporarily unable to query or access their logs through the OpenSearch API. Log ingestion remained unaffected. Root Cause : This incident was caused by a network equipment issue. We thank you for your understanding and patience throughout this incident.

The latest update from OVHcloud.

State

Resolved

Started

Lasted

1 min

Worst impact

Partial outage

Timeline

2 updates
20:5420:5420:5520:5520:55
Partial outageUpdate postedTimes in UTC

Identified

1 min 100%

Updates

Times in UTC

As posted by OVHcloud

Resolved

We would like to inform you that the incident affecting our Identity, Security & Operations offering has now been resolved. Please find the details of this incident below : Start time : 19/11/2026 17:31 UTC End time : 19/11/2026 20:50 UTC Impacted Service(s) : The OpenSearch API of the Logs Data Platform service was temporarily unavailable. Customers Impact : Customers were temporarily unable to query or access their logs through the OpenSearch API. Log ingestion remained unaffected. Root Cause : This incident was caused by a network equipment issue. We thank you for your understanding and patience throughout this incident.

Identified

We are currently experiencing an incident affecting our Identity, Security & Operations offering. The root cause has been identified. Please find the details of this incident below : Start time : 19/11/2026 17:31 UTC Impacted Service(s) : The OpenSearch API of the Logs Data Platform service is temporarily unavailable. Customers Impact : Customers are temporarily unable to query or access their logs through the OpenSearch API. Log ingestion remains unaffected. Root Cause : This incident is caused by a security mitigation applied on our load balancing infrastructure. 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

4
GRABHSIdentity, Security & Operations || Logs Data Platform - GRAIdentity, Security & Operations || Logs Data Platform - BHS

OVHcloud in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

184

Days with an incident

90

Median duration

1 h 46 min

This incident

99% shorter than the median

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

24 days
median 1 h 46 min
90 days agoToday

Other OVHcloud incidents

All incidents

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