OVHcloud reported "[GRA9/GRA11][Public Cloud] - Network API incident notification" on its status page at 2026-10-14 14:46 UTC.

When did the incident start and end?

It started at 2026-10-14 14:46 UTC and ended at 2026-10-14 15:24 UTC. It lasted 37 min.

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.

OVHcloudIncident · 2026-10-14 14:46 UTC

[GRA9/GRA11][Public Cloud] - Network API incident notification

Q: What is affected?

OVHcloud lists these components: GRA9, GRA11, Network || Private network (vRack) - GRA9, Network || Private network (vRack) - GRA11, Network || Public network - GRA9, Network || Public network - GRA11.

ResolvedOfficial update

We are pleased to inform you that the incident affecting our Public Cloud offering has been resolved. Start time : 14/10/2026 08:00 UTC End time : 14/10/2026 15:22 UTC Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.

The latest update from OVHcloud.

State

Resolved

Started

18 d ago

2026-10-14 14:46 UTC

Lasted

37 min

until 2026-10-14 15:24 UTC

Worst impact

Partial outage

Timeline

2 updates

14:4614:5615:0515:1415:24

Partial outageUpdate postedTimes in UTC

Investigating

37 min 100%

Updates

Times in UTC

As posted by OVHcloud

Resolved2026-10-14 15:24 UTC

Investigating2026-10-14 14:46 UTC

We are currently experiencing an incident affecting our Public Cloud offering, which is causing temporary latency issues in the GRA9 and GRA11 regions. Please find the details of this incident below : Start time : 14/10/2026 08:00 UTC Impacted Service(s) : The OpenStack Network API in the GRA9 and GRA11 regions is experiencing increased latency. Customers Impact : Customers may experience slowness when performing network operations through the API or Horizon, such as creating or modifying networks, ports, floating IPs or security groups. Ongoing Actions : 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

GRA9GRA11Network || Private network (vRack) - GRA9Network || Private network (vRack) - GRA11Network || Public network - GRA9Network || Public network - GRA11

OVHcloud in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

217

Days with an incident

Median duration

1 h 35 min

This incident

61% 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 35 min

90 days agoToday

Other OVHcloud incidents

All incidents

OVHcloud·[SBG8][Virtual Private Servers] - VPS Incident Notification

Some Virtual Private Servers in the OVHcloud SBG8 region are temporarily unreachable. OVHcloud has identified the incident and states that a network equipment issue causes it. OVHcloud teams are working to restore service.

Partial outageupdated 12 min ago

OVHcloud·[SBG6/8][Virtual Private Servers] - VPS Incident Notification

Some Virtual Private Servers in the SBG5, SBG6 and SBG8 regions were unreachable. OVHcloud reports that the incident is resolved. It lasted from 17:55 UTC to 19:30 UTC.

Resolvedresolved 17 min ago

OVHcloud·[RBX3][Dedicated Servers] - Rack 46E19 Incident Notification

OVHcloud reports that servers in Rack 46E19, RBX3, were not accessible through the IPMI interface. The incident was caused by a network equipment issue. The incident is resolved and it lasted 2 hours and 23 minutes.

Resolvedresolved 3 min ago

OVHcloud·[SBG5/7][Compute - Instance] - Compute Instance Incident Notification

OVHcloud Compute Instance service did not work for some instances in the SBG5 and SBG7 regions. OVHcloud reports that the incident is resolved. The incident lasted from 17:55 UTC to 19:30 UTC.

Resolvedresolved 20 min ago

OVHcloud·[RBX2][Dedicated Servers] - Rack 21D12 Incident Notification

We are pleased to inform you that the incident affecting our Dedicated Servers offering has been resolved. Start time : 31/10/2026 19:38 UTC End time : 31/10/2026 22:10 UTC Root Cause : This incident was caused by an electrical equipment issue. We apologize for any inconvenience caused and appreciate your understanding.

Resolvedresolved 22 h ago

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.cc/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.cc/feed.xml?providers=ovhcloud

Slack

/feed subscribe https://outages.cc/feed.xml?providers=ovhcloud

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane