OVH.com logo
OVHcloud Public Cloud Status

Current status
Legend
  • Operational
  • Degraded performance
  • Partial Outage
  • Major Outage
  • Under maintenance
[GLOBAL][Databases] - PostgreSQL 18 and PostGIS Compatibility Issue
Update - We have new information regarding the incident that affected your service(s).

Please find below an update on the situation:
Update : PostGIS support for PostgreSQL 18 was introduced in a newer PostGIS version. However, an identified defect carries a risk of data corruption for geospatial data, so we have chosen not to enable it on our offer yet. We are waiting for a PostGIS release that fixes this issue before allowing PostGIS to be used on PostgreSQL 18.
As a reminder, this only affects customers using the PostGIS extension. PostgreSQL instances that do not use PostGIS are not impacted.
In the meantime, we still strongly recommend that PostGIS users postpone any upgrade to PostgreSQL 18 and remain on PostgreSQL 17, which is fully compatible with PostGIS.
Ongoing Actions : We are closely monitoring the situation while the PostGIS team works on a resolution.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.
Jun 11, 2026 - 08:45 UTC
Update - Our provider is still working on resolving the issue affecting our PostgreSQL offering.
To avoid issues with geospatial features, we still strongly recommend postponing any upgrade to PostgreSQL version 18 and continuing to use PostgreSQL version 17, which remains compatible with PostGIS.

For any questions, please contact your usual point of contact or reach out to our support team.

We will keep you updated on the progress and resolution.
Apr 09, 2026 - 14:08 UTC
Identified - We are currently experiencing an ongoing incident and have determined origin of the issue to PostGIS plugin, affecting our PostgreSQL offer when using this specific plugin in version 3.5 and PG18.

Here are some supplementary details :
Start time : 16/03/2026 08:00 UTC
Impacted Service(s) : Customers may experience issues when upgrading to PostgreSQL version 18, as the PostGIS extension is currently not functional on this version, potentially preventing the use of geospatial features.
As a precaution, we strongly recommend postponing any upgrade to PostgreSQL version 18 and continuing to use PostgreSQL version 17, which remains compatible with PostGIS.
Root Cause : This incident is caused by PostGIS extension current version 3.5.
Ongoing Actions : The PostGIS team needs to fix this bug and release a new version of the extension (v3.6). In the meantime, our services remain fully functional without PostGIS.

If you have any questions, please contact your usual point of contact or reach out to our support team.

We will keep you updated on the progress and resolution.
Mar 30, 2026 - 12:36 UTC

About This Site

Welcome to the Public Cloud status page for real-time information on system performance and availability.

Uptime over the past 90 days. View historical uptime.
AI & Machine Learning || AI Dashboard Operational
AI & Machine Learning || AI Deploy Operational
BHS Operational
GRA Operational
AI & Machine Learning || AI Endpoint Operational
AI & Machine Learning || AI Notebooks Operational
BHS Operational
GRA Operational
AI & Machine Learning || AI Training Operational
BHS Operational
GRA Operational
Compute - Instance || BHS Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
BHS7 Operational
Compute - Instance || ERI Operational
UK1 Operational
Compute - Instance || EU-SOUTH-MIL Operational
EU-SOUTH-MIL-A Operational
EU-SOUTH-MIL-B Operational
EU-SOUTH-MIL-C Operational
Compute - Instance || EU-WEST-PAR Operational
EU-WEST-PAR-A Operational
EU-WEST-PAR-B Operational
EU-WEST-PAR-C Operational
Compute - Instance || GRA Operational
GRA1 Operational
GRA3 Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
GRA4 Operational
Compute - Instance || India Operational
AP-SOUTH-MUM-1 Operational
Compute - Instance || LIM Operational
DE1 Operational
Compute - Instance || RBX Operational
RBX-A Operational
Compute - Instance || SGP Operational
SGP1 Operational
SGP2 Operational
Compute - Instance || SBG Operational
SBG5 Operational
SBG7 Operational
SBG3 Operational
Compute - Instance || SYD Operational
SYD1 Operational
AP-SOUTHEAST-SYD-2 Operational
Compute - Instance || USA Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
Compute - Instance || WAW Operational
WAW1 Operational
Containers & Orchestration || Load Balancer Operational
AP-SOUTH-MUM Operational
BHS5 Operational
DE1 Operational
EU-WEST-PAR Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
RBX-A Operational
SBG5 Operational
SGP1 Operational
SYD1 Operational
WAW1 Operational
UK1 Operational
US-EAST-VA Operational
US-WEST-OR Operational
Containers & Orchestration || Managed Kubernetes Service Operational
AP-SOUTH-MUM Operational
BHS5 Operational
EU-WEST-LIM Operational
EU-SOUTH-MIL Operational
EU-WEST-PAR Operational
RBX Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
SBG5 Operational
SGP1 Operational
SYD1 Operational
WAW1 Operational
UK1 Operational
US-EAST-VA Operational
US-WEST-OR Operational
DE1 Operational
Containers & Orchestration || Managed Private Registry Operational
AP-SOUTH-MUM Operational
BHS Operational
DE Operational
EU-SOUTH-MIL Operational
EU-WEST-PAR Operational
GRA Operational
VA Operational
Containers & Orchestration || Managed Rancher Service Operational
Containers & Orchestration || Workflow Management Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
DE1 Operational
GRA1 Operational
GRA3 Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
RBX-A Operational
SBG5 Operational
SBG7 Operational
SGP1 Operational
SGP2 Operational
SYD1 Operational
AP-SOUTHEAST-SYD-2 Operational
UK1 Operational
WAW1 Operational
WAW2 Operational
US-EAST-VA Operational
US-WEST-OR Operational
AP-SOUTH-MUM Operational
Databases || MongoDB Operational
90 days ago
100.0 % uptime
Today
BHS Operational
DE Operational
GRA Operational
EU-WEST-PAR Operational
SBG Operational
SGP Operational
UK Operational
WAW Operational
EU-SOUTH-MIL Operational
90 days ago
100.0 % uptime
Today
RBX Operational
AP-SOUTH-MUM Operational
US-EAST-VA Operational
US-WEST-OR Operational
Databases || MySQL Operational
BHS Operational
DE Operational
GRA Operational
EU-SOUTH-MIL Operational
AP-SOUTH-MUM Operational
EU-WEST-PAR Operational
RBX Operational
SBG Operational
SGP Operational
US-EAST-VA Operational
UK Operational
US-WEST-OR Operational
WAW Operational
Databases || PostgreSQL Operational
BHS Operational
DE Operational
GRA Operational
EU-SOUTH-MIL Operational
AP-SOUTH-MUM Operational
EU-WEST-PAR Operational
RBX Operational
SBG Operational
SGP Operational
UK Operational
US-EAST-VA Operational
US-WEST-OR Operational
WAW Operational
Databases || Valkey Operational
BHS Operational
DE Operational
GRA Operational
EU-SOUTH-MIL Operational
AP-SOUTH-MUM Operational
EU-WEST-PAR Operational
RBX Operational
SBG Operational
SGP Operational
US-EAST-VA Operational
UK Operational
US-WEST-OR Operational
WAW Operational
Data & Analytics || ClickHouse Operational
EU-WEST-PAR Operational
EU-SOUTH-MIL Operational
AP-SOUTH-MUM Operational
Data & Analytics || Data Platform Operational
Data & Analytics || Dashboards Operational
BHS Operational
DE Operational
GRA Operational
EU-WEST-PAR Operational
SBG Operational
SGP Operational
UK Operational
WAW Operational
EU-SOUTH-MIL Operational
AP-SOUTH-MUM Operational
RBX Operational
US-EAST-VA Operational
US-WEST-OR Operational
Data & Analytics || Kafka Operational
BHS Operational
DE Operational
GRA Operational
EU-SOUTH-MIL Operational
AP-SOUTH-MUM Operational
EU-WEST-PAR Operational
RBX Operational
SBG Operational
SGP Operational
UK Operational
US-EAST-VA Operational
US-WEST-OR Operational
WAW Operational
Data & Analytics || Kafka Connect Operational
BHS Operational
DE Operational
GRA Operational
EU-WEST-PAR Operational
EU-SOUTH-MIL Operational
AP-SOUTH-MUM Operational
RBX Operational
SBG Operational
SGP Operational
UK Operational
US-EAST-VA Operational
US-WEST-OR Operational
WAW Operational
Data & Analytics || Kafka MirrorMaker Operational
BHS Operational
DE Operational
GRA Operational
EU-SOUTH-MIL Operational
AP-SOUTH-MUM Operational
EU-WEST-PAR Operational
RBX Operational
SBG Operational
SGP Operational
UK Operational
WAW Operational
US-EAST-VA Operational
US-WEST-OR Operational
Data & Analytics || OpenSearch Operational
BHS Operational
DE Operational
GRA Operational
EU-SOUTH-MIL Operational
AP-SOUTH-MUM Operational
EU-WEST-PAR Operational
RBX Operational
SBG Operational
SGP Operational
US-EAST-VA Operational
UK Operational
US-WEST-OR Operational
WAW Operational
Identity, Security & Operations || Authentication Operational
Identity, Security & Operations || Barbican Operational
AP-SOUTH-MUM Operational
AP-SOUTHEAST-SYD-2 Operational
BHS5 Operational
DE1 Operational
EU-SOUTH-MIL Operational
EU-WEST-PAR Operational
GRA9 Operational
RBX-A Operational
SBG7 Operational
SGP1 Operational
SYD1 Operational
UK1 Operational
US-WEST-OR Operational
US-EAST-VA Operational
WAW1 Operational
Management || Horizon Operational
Identity, Security & Operations || Key Management Service Operational
AP-SOUTHEAST-SGP Operational
AP-SOUTHEAST-SYD Operational
CA-EAST-TOR Operational
CA-EAST-BHS Operational
EU-CENTRAL-WAW Operational
EU-SOUTH-MIL Operational
EU-WEST-ERI Operational
EU-WEST-GRA Operational
EU-WEST-LIM Operational
EU-WEST-PAR Operational
EU-WEST-RBX Operational
EU-WEST-SBG Operational
Identity, Security & Operations || Logs Data Platform Operational
BHS Operational
GRA Operational
LocalZones || AF-CENTRAL Operational
AF-CENTRAL-LZ-ABJ Operational
LocalZones || AF-NORTH Operational
AF-NORTH-LZ-RBA Operational
LocalZones || AP-SOUTH-MUM Operational
LocalZones || EU-CENTRAL Operational
EU-CENTRAL-LZ-BUH Operational
EU-CENTRAL-LZ-PRG Operational
EU-CENTRAL-LZ-SOF Operational
LocalZones || EU-NORTH Operational
EU-NORTH-LZ-CPH Operational
EU-NORTH-LZ-HEL Operational
EU-NORTH-LZ-OSL Operational
EU-NORTH-LZ-STO Operational
LocalZones || EU-SOUTH Operational
EU-SOUTH-LZ-LIS Operational
EU-SOUTH-LZ-MAD Operational
EU-SOUTH-LZ-MIL Operational
LocalZones || EU-WEST Operational
EU-WEST-LZ-AMS Operational
EU-WEST-LZ-BRU Operational
EU-WEST-LZ-DLN Operational
EU-WEST-LZ-LUX Operational
EU-WEST-LZ-MNC Operational
EU-WEST-LZ-MRS Operational
EU-WEST-LZ-VIE Operational
EU-WEST-LZ-ZRH Operational
LocalZones || US-CENTRAL Operational
US-CENTRAL-LZ-SLC Operational
US-CENTRAL-LZ-STL Operational
LocalZones || US-EAST Operational
US-EAST-LZ-ATL Operational
US-EAST-LZ-BOS Operational
US-EAST-LZ-CHI Operational
US-EAST-LZ-DAL Operational
US-EAST-LZ-MIA Operational
US-EAST-LZ-NYC Operational
LocalZones || US-WEST Operational
US-WEST-LZ-DEN Operational
US-WEST-LZ-LAX Operational
US-WEST-LZ-PAO Operational
US-WEST-LZ-PHX Operational
US-WEST-LZ-SEA Operational
Network || Floating IP Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
DE1 Operational
GRA1 Operational
GRA3 Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
AP-SOUTH-MUM-1 Operational
RBX-A Operational
SBG5 Operational
SBG7 Operational
SGP1 Operational
SYD1 Operational
AP-SOUTHEAST-SYD-2 Operational
UK1 Operational
WAW1 Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
EU-WEST-PAR-A Operational
EU-WEST-PAR-B Operational
EU-WEST-PAR-C Operational
EU-SOUTH-MIL-A Operational
EU-SOUTH-MIL-B Operational
EU-SOUTH-MIL-C Operational
Network || Gateway Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
DE1 Operational
GRA1 Operational
GRA3 Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
SBG5 Operational
SBG7 Operational
SGP1 Operational
SYD1 Operational
AP-SOUTHEAST-SYD-2 Operational
UK1 Operational
WAW1 Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
AP-SOUTH-MUM-1 Operational
EU-WEST-PAR-A Operational
EU-WEST-PAR-B Operational
EU-WEST-PAR-C Operational
RBX-A Operational
EU-SOUTH-MIL-A Operational
EU-SOUTH-MIL-B Operational
EU-SOUTH-MIL-C Operational
Network || Load Balancer Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
DE1 Operational
GRA1 Operational
GRA3 Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
SBG5 Operational
SBG7 Operational
SGP1 Operational
SYD1 Operational
AP-SOUTHEAST-SYD-2 Operational
UK1 Operational
WAW1 Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
EU-WEST-PAR-A Operational
EU-WEST-PAR-B Operational
EU-WEST-PAR-C Operational
AP-SOUTH-MUM-1 Operational
RBX-A Operational
EU-SOUTH-MIL-A Operational
EU-SOUTH-MIL-B Operational
EU-SOUTH-MIL-C Operational
Network || Private network (vRack) Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
DE1 Operational
GRA1 Operational
GRA3 Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
RBX-A Operational
SBG5 Operational
SBG7 Operational
SGP1 Operational
SGP2 Operational
SYD1 Operational
AP-SOUTHEAST-SYD-2 Operational
UK1 Operational
WAW1 Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
EU-WEST-PAR-A Operational
EU-WEST-PAR-B Operational
EU-WEST-PAR-C Operational
AP-SOUTH-MUM-1 Operational
RBX-A Operational
EU-SOUTH-MIL-A Operational
EU-SOUTH-MIL-B Operational
EU-SOUTH-MIL-C Operational
Network || Public network Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
DE1 Operational
GRA1 Operational
GRA3 Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
RBX-A Operational
SBG1 Operational
SBG3 Operational
SBG5 Operational
SBG7 Operational
SGP1 Operational
SGP2 Operational
SYD1 Operational
AP-SOUTHEAST-SYD-2 Operational
UK1 Operational
WAW1 Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
EU-WEST-PAR-A Operational
EU-WEST-PAR-B Operational
EU-WEST-PAR-C Operational
AP-SOUTH-MUM-1 Operational
RBX-A Operational
EU-SOUTH-MIL-A Operational
EU-SOUTH-MIL-B Operational
EU-SOUTH-MIL-C Operational
Quantum || Emulators Operational
BHS Operational
GRA Operational
Quantum || QPUs Operational
BHS Operational
GRA Operational
Storage || Block storage Operational
AP-SOUTHEAST-SYD-2 Operational
AP-SOUTH-MUM-1 Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
DE1 Operational
EU-SOUTH-MIL-A Operational
EU-SOUTH-MIL-B Operational
EU-SOUTH-MIL-C Operational
EU-WEST-PAR-A Operational
EU-WEST-PAR-B Operational
EU-WEST-PAR-C Operational
GRA1 Operational
GRA3 Operational
GRA5 Operational
GRA6 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
RBX-A Operational
SBG5 Operational
SBG7 Operational
SGP1 Operational
SYD1 Operational
UK1 Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
WAW1 Operational
YNM1 Operational
Storage || Cloud Archive Operational
DE Operational
GRA Operational
UK Operational
WAW Operational
BHS Operational
SYD Operational
SGP Operational
US-EAST-VA Operational
US-WEST-OR Operational
Storage || Cold Archive Operational
RBX-ARCHIVE Operational
Storage || File storage Operational
AP-SOUTH-MUM-1 Operational
BHS3 Operational
BHS5 Operational
DE1 Operational
EU-SOUTH-MIL Operational
EU-WEST-PAR Operational
GRA1 Operational
GRA3 Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
RBX-A Operational
SBG5 Operational
SBG7 Operational
SGP1 Operational
SYD1 Operational
UK1 Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
WAW1 Operational
Storage || Instance Backup Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
DE1 Operational
GRA1 Operational
GRA3 Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
SBG5 Operational
SBG7 Operational
SGP1 Operational
SYD1 Operational
AP-SOUTHEAST-SYD-2 Operational
UK1 Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
WAW1 Operational
AP-SOUTH-MUM-1 Operational
EU-WEST-PAR-A Operational
EU-WEST-PAR-B Operational
EU-WEST-PAR-C Operational
RBX-A Operational
Storage || Object storage Operational
BHS Operational
GRA Operational
DE Operational
RBX Operational
SBG Operational
SGP Operational
SYD Operational
UK Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
WAW Operational
YYZ Operational
LIM Operational
AP-SOUTH-MUM-1 Operational
EU-WEST-PAR-A Operational
EU-WEST-PAR-B Operational
EU-WEST-PAR-C Operational
YNM1 Operational
EU-SOUTH-MIL-B Operational
EU-SOUTH-MIL-A Operational
EU-SOUTH-MIL-C Operational
Storage || Volume Backup Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
DE1 Operational
GRA1 Operational
GRA3 Operational
GRA5 Operational
GRA7 Operational
GRA9 Operational
GRA11 Operational
SBG5 Operational
SBG7 Operational
SGP1 Operational
SYD1 Operational
AP-SOUTHEAST-SYD-2 Operational
UK1 Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
WAW1 Operational
AP-SOUTH-MUM-1 Operational
RBX-A Operational
EU-WEST-PAR-A Operational
EU-WEST-PAR-B Operational
EU-WEST-PAR-C Operational
EU-SOUTH-MIL Operational
Storage || Volume Snapshot (Ceph) Operational
DE1 Operational
GRA1 Operational
GRA2 Operational
GRA3 Operational
GRA5 Operational
GRA6 Operational
GRA4 Operational
GRA7 Operational
GRA8 Operational
GRA9 Operational
GRA11 Operational
RBX-A Operational
SBG5 Operational
SBG6 Operational
SBG7 Operational
SBG8 Operational
SGP1 Operational
SYD1 Operational
AP-SOUTHEAST-SYD-2 Operational
UK1 Operational
UK2 Operational
WAW1 Operational
WAW2 Operational
US-EAST-VA-1 Operational
US-WEST-OR-1 Operational
AP-SOUTH-MUM-1 Operational
EU-WEST-PAR-A Operational
EU-WEST-PAR-B Operational
EU-WEST-PAR-C Operational
EU-SOUTH-MIL Operational
RBX-A Operational
BHS1 Operational
BHS3 Operational
BHS5 Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

[GLOBAL][Containers & Orchestration] - End of Life of Load Balancer for Managed Kubernetes Service notification Jul 9, 2026 08:00-16:00 UTC

As part of the end-of-life of our Containers & Orchestration - Load Balancer (IOLB) offer, a maintenance is scheduled in BHS5 / DE1 / GRA5 / GRA7 / GRA9 / GRA11 / SBG5 / SGP1 / SYD1 / WAW1 / UK1 / US-EAST-VA / US-WEST-OR regions.

Start time : 09/07/2026 08:00 UTC
End time : 09/07/2026 16:00 UTC
Service impact : We're retiring the historical Load Balancer for Managed Kubernetes, now replaced by the Public Cloud Loadbalancer. As part of this change, resources will be deleted and no longer billed.
Note: the migration to Public Cloud Loadbalancer is not automatic and must be performed on your side. (https://docs.ovhcloud.com/en/guides/public-cloud/containers-orchestration/managed-kubernetes/migrate-iolb-to-public-cloud-loadbalancer)
Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our Containers & Orchestration - Load Balancer in the specified regions.

Thank you for your understanding.
Posted on Jun 04, 2026 - 16:27 UTC

[APAC][Identity, Security & Operations] - Authentication maintenance notification Jul 9, 2026 14:00-15:00 UTC

As part of our continuous improvement plan, maintenance is scheduled on our Identity, Security & Operations offer in APAC region.

Start time : 09/07/2026 14:00 UTC
End time : 09/07/2026 15:00 UTC
Service impact : None
Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our Identity, Security & Operations infrastructure.

Thank you for your understanding.
Posted on Jul 02, 2026 - 20:10 UTC

[GRA][Object storage] - Infrastructure maintenance notification Jul 15, 2026 06:00-08:00 UTC

As part of our continuous improvement plan, a maintenance is scheduled on our Object storage infrastructure.

Start time : 15/07/2026 06:00 UTC
End time : 15/07/2026 08:00 UTC
Service impact : Some instances located in GRA region will be temporarily unavailable during the maintenance.
Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our infrastructure in the specified region.

Thank you for your understanding.
Posted on Jun 16, 2026 - 20:30 UTC

[GLOBAL][Storage] - Object Storage S3 maintenance notification Jul 15, 2026 07:00 - Jul 22, 2026 16:00 UTC

As part of our continuous improvement plan, a maintenance is scheduled on our Object Storage offer.

Start time : 15/07/2026 07:00 UTC
End time : 22/07/2026 16:00 UTC
Service impact : S3-compatible Object Storage endpoints will now support IPv6 in dual-stack mode (IPv4 and IPv6), while maintaining unchanged IPv4 connectivity. However, customers with misconfigured IPv6 networking may experience connectivity issues when accessing S3-compatible Object Storage.
Below you can find the table regarding the endpoints and records being added:

RegionDNSnew AAAA record
SBGs3.sbg.perf.cloud.ovh.net
s3.sbg.io.cloud.ovh.net		2001:41d0:404:700::1
 s3-website.sbg.perf.cloud.ovh.net
s3-website.sbg.io.cloud.ovh.net		2001:41d0:404:700::2
GRAs3.gra.perf.cloud.ovh.net
s3.gra.io.cloud.ovh.net		2001:41d0:304:c00::1
 s3-website.gra.perf.cloud.ovh.net
s3-website.gra.io.cloud.ovh.net		2001:41d0:304:c00::2
BHSs3.bhs.perf.cloud.ovh.net
s3.bhs.io.cloud.ovh.net		2607:5300:205:700::1
 s3-website.bhs.perf.cloud.ovh.net
s3-website.bhs.io.cloud.ovh.net		2607:5300:205:700::2
RBXs3.rbx.perf.cloud.ovh.net
s3.rbx.io.cloud.ovh.net		2001:41d0:20a:a00::1
 s3-website.rbx.perf.cloud.ovh.net
s3-website.rbx.io.cloud.ovh.net		2001:41d0:20a:a00::2
UKs3.uk.perf.cloud.ovh.net
s3.uk.io.cloud.ovh.net		2001:41d0:804:100::1
 s3-website.uk.perf.cloud.ovh.net
s3-website.uk.io.cloud.ovh.net		2001:41d0:804:100::2
DEs3.de.perf.cloud.ovh.net
s3.de.io.cloud.ovh.net		2001:41d0:705:4200::1
 s3-website.de.perf.cloud.ovh.net
s3-website.de.io.cloud.ovh.net		2001:41d0:705:4200::2
WAWs3.waw.perf.cloud.ovh.net
s3.waw.io.cloud.ovh.net		2001:41d0:622::1
 s3-website.waw.perf.cloud.ovh.net
s3-website.waw.io.cloud.ovh.net		2001:41d0:622::2
CA-EAST-TORs3.ca-east-tor.perf.cloud.ovh.net
s3.ca-east-tor.io.cloud.ovh.net		2607:5300:304::1
 s3-website.ca-east-tor.perf.cloud.ovh.net
s3-website.ca-east-tor.io.cloud.ovh.net		2607:5300:304::2
SGPs3.sgp.perf.cloud.ovh.net
s3.sgp.io.cloud.ovh.net		2402:1f00:8002:300::1
 s3-website.sgp.perf.cloud.ovh.net
s3-website.sgp.io.cloud.ovh.net		2402:1f00:8002:300::2
AP-SOUTHEAST-SYDs3.ap-southeast-syd.perf.cloud.ovh.net
s3.ap-southeast-syd.io.cloud.ovh.net		2402:1f00:8102:400::1
 s3-website.ap-southeast-syd.perf.cloud.ovh.net
s3-website.ap-southeast-syd.io.cloud.ovh.net		2402:1f00:8102:400::2
AP-SOUTH-MUMs3.ap-south-mum.perf.cloud.ovh.net
s3.ap-south-mum.io.cloud.ovh.net		2402:1f00:8303:200::1
 s3-website.ap-south-mum.perf.cloud.ovh.net
s3-website.ap-south-mum.io.cloud.ovh.net		2402:1f00:8303:200::2
EU-WEST-PARs3.eu-west-par.io.cloud.ovh.net2001:41d0:a0b:500::1
 s3-website.eu-west-par.io.cloud.ovh.net2001:41d0:a0b:500::2
EU-SOUTH-MILs3.eu-south-mil.io.cloud.ovh.net2001:41d0:2005:200::1
 s3-website.eu-south-mil.io.cloud.ovh.net2001:41d0:2005:200::2
EU-EAST-VAs3.us-east-va.perf.cloud.ovh.net
s3.us-east-va.io.cloud.ovh.net		2604:2dc0:101:500::1
 s3-website.us-east-va.perf.cloud.ovh.net
s3-website.us-east-va.io.cloud.ovh.net		2604:2dc0:101:500::2
EU-WEST-ORs3.us-west-or.perf.cloud.ovh.net
s3.us-west-or.io.cloud.ovh.net		2604:2dc0:202:400::1
 s3-website.us-west-or.perf.cloud.ovh.net
s3-website.us-west-or.io.cloud.ovh.net		2604:2dc0:202:400::2

Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our Object Storage S3 infrastructure.

Thank you for your understanding.
Posted on Jun 22, 2026 - 12:19 UTC

[AP-SOUTHEAST-SYD2][Public Cloud] - Planned decommission of the region Aug 15, 2026 06:00-16:00 UTC

Start time : 15/08/2026 06:00 UTC
End time : 15/08/2026 16:00 UTC
Service impact : Public Cloud instances hosted in the AP-SOUTHEAST-SYD-2 region
Service improvement : As part of the continuous evolution of our Public Cloud offering, OVHcloud will progressively phase out the AP-SOUTHEAST-SYD-2 region in Sydney and focus future developments on the SYD1 region.
Services hosted in AP-SOUTHEAST-SYD-2 will enter maintenance mode before a definitive shutdown in the coming months.
Affected customers must manually migrate their workloads and data to the SYD1 region to avoid service disruption.

Required customer actions
Customers are required to:
- Create new instances in the SYD1 region
- Manually migrate applications, services, and data
- Validate workloads on the new infrastructure
- Stop and delete old instances once migration is completed

We strongly recommend performing backups before starting the migration process.
Migration documentation:
https://help.ovhcloud.com/csm/en-ie-public-cloud-compute-migration-between-az?id=kb_article_view&sysparm_article=KB0073126

To compensate for the inconvenience, OVHcloud will automatically apply a credit corresponding to one month of the affected services usage.
Posted on May 28, 2026 - 09:48 UTC

[GRA/BHS][Identity, Security & Operations] - Logs Data Platform maintenance notification Sep 16, 2026 10:30-19:30 UTC

As part of maintenance for the Logs Data Platform, we will replace the certificates for your Data-gathering tools on 16 September 2026, as the current intermediate certificate expires on 20 September 2026.

Start time : 16/09/2026 10:30 UTC
End time : 16/09/2026 19:30 UTC
Service impact : Customers who send their logs directly to the clusters are not affected by this maintenance and can disregard the rest of this message (Customer's log ingestion endpoint looks like gra1.logs.ovh.com:12202, no action is required).
However, customers who use an endpoint such as gra1-65d66a0a68728d746bbebbab.gra1.logs.ovh.com:6514 are affected by this maintenance and we recommend them to follow the relevant action plan below.

Case 1 — The customer's log forwarder agent performs no certificate verification
Customers who keep this behavior will not be impacted by the maintenance. No action is required.

Case 2 — The customer's log forwarder agent validates only the intermediate chain
1. Import the new certificate chain (as soon as possible). The new chain (self-signed, valid for 10 years) is already available in the OVHcloud Manager, on the home page of the customer's Logs Data Platform service. Customers should import it into their configuration before 16 September 2026.
2. Keep the old chain in place temporarily. Until 16 September 2026, customers should leave the old chain in their configuration so the agent accepts both chains (old + new) during the transition window, avoiding any surprise.
3. After 16 September 2026, once the maintenance is complete, customers should remove the old chain and keep only the new one (valid for 10 years).

Case 3 — The customer's log forwarder agent validates the intermediate + Data-gathering-tool certificate chain
1. Create a new Data-gathering tool in the Logs Data Platform project, replicating the exact configuration of the previous one.
2. Import the full certificate chain (intermediate + new self-signed certificate). Customers should go to the Data-gathering tools page, then open the "Useful information" section to obtain it.
3. Update the log forwarder agent configuration to push logs to this new Data-gathering tool.
4. Delete the old Data-gathering tool.
Service improvement : This maintenance renews the certificate chain that secures your log ingestion, ensuring uninterrupted and secure log delivery. The new chain is self-signed and valid for 10 years.

Thank you for your understanding.
Posted on Jul 03, 2026 - 09:47 UTC
Jul 8, 2026
[GRA][Object Storage] - Object Storage Swift Incident Notification
Resolved - We are pleased to inform you that the incident affecting our Object Storage Swift offering has been resolved.

Start time : 06/07/2026 14:00 UTC
End time : 06/07/2026 15:25 UTC
Root Cause : This incident was caused by a software issue.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 8, 12:43 UTC
Monitoring - Service has been fully restored since 06/07/2026 15:25 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 06/07/2026 14:00 UTC
Impacted Service(s) : Slowness and 504 error in response time
Customers Impact : Some customers might have faced slowness or 504 error in response time in specified region.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 6, 15:31 UTC
Investigating - We are currently investigating an incident affecting our Object Storage Swift offering, which is causing temporary functionality issue in GRA region.

Here are some supplementary details :

Start time : 06/07/2026 14:00 UTC
Impacted Service(s) : Slowness and 504 error in response time
Customers Impact : Some customers might face slowness or 504 error in response time in specified region.
Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 6, 14:22 UTC
[GRA5/7/9/11][Containers & Orchestration] - Managed Kubernetes Service Incident Notification
Resolved - We are pleased to inform you that the incident affecting our Containers & Orchestration offering has been resolved.

Start time : 06/07/2026 20:08 UTC
End time : 07/07/2026 01:25 UTC
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 8, 09:34 UTC
Monitoring - Service has been fully restored since 07/07/2026 01:25 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC
Impacted Service(s) : The Managed Kubernetes Service experienced delays in managed node provisioning.
Customers Impact : Customers may have experienced network disruptions when using the load balancer and delays in managed node delivery.
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 7, 01:43 UTC
Investigating - We are currently investigating an incident affecting our Containers & Orchestration offering, which is causing temporary availability issue in the GRA5/7/9/11 regions.

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC
Impacted Service(s) : The Managed Kubernetes Service is experiencing delays in managed node provisioning.
Customers Impact : Customers may experience network disruptions when using the load balancer and delays in managed node delivery.
Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 6, 23:30 UTC
[GRA][Containers & Orchestration] - Managed Private Registry Incident Notification
Resolved - We are pleased to inform you that the incident affecting our Containers & Orchestration offering has been resolved.

Start time : 06/07/2026 20:08 UTC
End time : 07/07/2026 01:25 UTC
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 8, 09:34 UTC
Monitoring - Service has been fully restored since 07/07/2026 01:25 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC
Impacted Service(s) : The Managed Private Registry service experienced intermittent disruptions or temporary unavailability.
Customers Impact : Customers may have experienced issues pushing, pulling, or deploying container images.
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 7, 01:39 UTC
Investigating - We are currently investigating an incident affecting our Containers & Orchestration offering, which is causing temporary availability issue in the GRA region.

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC
Impacted Service(s) : The Managed Private Registry service may experience intermittent disruptions or temporary unavailability.
Customers Impact : Customers may experience issues pushing, pulling, or deploying container images.
Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 6, 22:24 UTC
[GRA1/3/4/5/7/9/11][Compute - Instance] - Some instances incident notification
Resolved - We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved.

Start time : 06/07/2026 20:08 UTC
End time : 07/07/2026 21:34 UTC
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 8, 09:31 UTC
Update - Service has been fully restored since 07/07/2026 21:34 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC
Impacted Service(s) : Public network experienced availability and latency issues.
Customers Impact : Customers experienced temporary service unavailability or increased latency when accessing their services.
Root Cause : This incident was caused by a network equipment issue.
Jul 7, 21:53 UTC
Update - Ongoing Actions: At 20:30 UTC, we will perform an upgrade on the affected network equipment to prevent this issue from recurring.

No customer impact is expected during this maintenance.

Our teams will closely monitor service stability throughout the operation and will remain mobilized until the maintenance has been successfully completed.

We will keep you informed of the progress and notify you once the maintenance has been completed.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 7, 18:33 UTC
Update - Please find the details of this incident below :

Start time : 06/07/2026 20:08 UTC
Impacted Service(s) : Public network experienced availability and latency issues.
Customers Impact : Customers experienced temporary service unavailability or increased latency when accessing their services.
Root Cause : This incident was caused by a network equipment issue.
Ongoing Actions : Our team isolated the affected network equipment to restore service.
The service has been restored since 07/07/2026 01:25 UTC.
Ongoing Actions : Our teams are continuing to investigate the root cause of the incident while closely monitoring system stability to ensure continued stability.

We will keep you updated on the progress of our investigation.
We apologize for any inconvenience caused and appreciate your understanding.
Jul 7, 14:17 UTC
Monitoring - Service has been fully restored since 07/07/2026 01:25 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 06/07/2026 20:08 UTC
Impacted Service(s) : Network perturbation was observed for some instances in the GRA1/3/4/5/7/9/11 regions.
Customers Impact : Some customers were temporarily facing packet loss on their instances located in the specified regions.
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 7, 09:50 UTC
Jul 7, 2026
[GRA][AI & Machine Learning] - AI payload incident notification
Resolved - We are pleased to inform you that the incident affecting our AI payload offering has been resolved.

Start time : 07/07/2026 11:45 UTC
End time : 07/07/2026 11:56 UTC
Root Cause : This incident was caused by a network equipment issue.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 7, 15:10 UTC
Monitoring - Service has been fully restored since 07/07/2026 11:56 UTC. Monitoring remains active to ensure long-term stability.

Here are some supplementary details :

Start time : 07/07/2026 11:45 UTC
Impacted Service(s) : Creation of AI payloads was temporarily unavailable in GRA region.
Customers Impact : Customers were temporarily unable to create AI payloads.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 7, 12:31 UTC
Jul 6, 2026
[GLOBAL][Data & Analytics] - Data Platform Maintenance Notification
Completed - All services are operational.
Jul 6, 17:23 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 6, 12:00 UTC
Scheduled - As part of our continuous improvement plan, a maintenance is scheduled on our Data Platform offer.

Start time : 06/07/2026 12:00 UTC
End time : 06/07/2026 15:00 UTC
Service impact : None
Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our Data Platform infrastructure.

Thank you for your understanding.
Jun 23, 17:24 UTC
Jul 5, 2026

No incidents reported.

Jul 4, 2026

No incidents reported.

Jul 3, 2026
[GRA1/3/9][Compute - Instance] - Some Instances Incident Notification
Resolved - We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved.

Start time : 03/07/2026 12:55 UTC
End time : 03/07/2026 18:20 UTC
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 3, 18:57 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific GRA1/3/9 regions.

Here are some supplementary details :

Start time : 03/07/2026 12:55 UTC
Impacted Service(s) : Some instances in the GRA1/3/9 regions are unreachable.
Customers Impact : Some customers are temporarily unable to access instances located on the specified regions.
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
Ongoing Actions : The incident has been identified and our teams are mobilised 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.
Jul 3, 13:39 UTC
[GLOBAL][AI & Machine Learning] - AI Endpoint Incident Notification
Resolved - We had an incident on AI & Machine Learning offer which has now been resolved.

Here are some supplementary details :

Start time : 02/07/2026 15:00 UTC
End time : 03/07/2026 08:15 UTC
Impacted Service(s) : All models on AI Endpoints have experienced latency and some 503 errors.
Customers Impact : Customers experienced increased latency and intermittent 503 errors across all models on AI Endpoints.
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We thank you for your understanding and patience throughout this incident.
Jul 3, 13:05 UTC
Jul 2, 2026

No incidents reported.

Jul 1, 2026
[GRA7][Compute - Instance] - Some instances incident notification
Resolved - We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved.

Start time : 01/07/2026 17:32 UTC
End time : 01/07/2026 18:54 UTC
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.
Jul 1, 19:21 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific GRA Region.

Here are some supplementary details :

Start time : 01/07/2026 17:32 UTC
Impacted Service(s) : Some instances in the GRA7 region are unreachable.
Customers Impact : Some customers are temporarily unable to access instances located on the specified regions.
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
Ongoing Actions : The incident has been identified and our teams are mobilised 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.
Jul 1, 17:54 UTC
[GRA][Containers & Orchestration] - Managed Private Registry incident notification
Resolved - We are pleased to inform you that the incident affecting our Containers & Orchestration offering has been resolved.

Start time : 01/07/2026 17:32 UTC
End time : 01/07/2026 18:54 UTC
Root Cause : https://web-cloud.status-ovhcloud.com/incidents/0j01r7j5vsky

We apologize for any inconvenience caused and appreciate your understanding.
Jul 1, 19:15 UTC
Identified - We are currently experiencing an incident affecting our Containers & Orchestration - Managed Private Registry offering, which is causing temporary functionality issues in the GRA region.

Here is detail for this incident :
Start time : 01/07/2026 17:32 UTC
Impacted Service(s) : Some Registries are unreachable in the GRA region.
Customers Impact : Some customers are temporarily unable to do management operations on their Registries in the specified region.
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.
Jul 1, 19:14 UTC
[DE1][Containers & Orchestration] - Managed Kubernetes Service incident notification
Resolved - We are pleased to inform you that the incident affecting our Containers & Orchestration offering has been resolved.

Start time : 01/07/2026 17:32 UTC
End time : 01/07/2026 18:54 UTC
Root Cause : https://public-cloud.status-ovhcloud.com/incidents/x3cj8gldm5yx

We apologize for any inconvenience caused and appreciate your understanding.
Jul 1, 18:55 UTC
Update - We are continuing to work on a fix for this issue.
Jul 1, 18:50 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer on the specific DE1 region.

Here are some supplementary details :

Start time : 01/07/2026 17:32 UTC
Impacted Service(s) : Customer may have difficulties to do some cluster action
Customers Impact : Customer may have difficulties to manage their cluster on DE1 region
Root Cause : https://public-cloud.status-ovhcloud.com/incidents/x3cj8gldm5yx
Ongoing Actions : The incident has been identified and our teams are mobilised 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.
Jul 1, 18:32 UTC
[RBX/SBG][Containers & Orchestration] - Managed Rancher Service maintenance notification
Completed - We would like to inform you that the maintenance on our Containers & Orchestration is now completed.

Thank you for your patience throughout this maintenance.
Jul 1, 17:29 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 1, 07:30 UTC
Scheduled - As part of our continuous improvement plan, maintenance is scheduled on our Containers & Orchestration offer.

Start time : 01/07/2026 07:30 UTC
End time : 01/07/2026 16:00 UTC
Service impact : None
Service improvement : As part of our continuous improvement policy, we need to upgrade Ranchers in version 2.11 to version 2.12. You can already manage the upgrade by yourself through OVHcloud Control panel or API.
The Rancher compatibility matrix with downstream clusters will change, indeed K8S version 1.30 will no longer be officially supported.
For more information regarding Managed Rancher Service supported versions and lifecycle policy, you can visit this page: KB0064608

Thank you for your understanding.
Apr 22, 17:38 UTC
[GRA5/79/11][Public Cloud] - Infrastructure maintenance notification
Completed - We would like to inform you that the maintenance on our Public Cloud infrastructure is now completed.
All services are operational.

Thank you for your patience throughout this maintenance.
Jul 1, 13:15 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 1, 07:52 UTC
Scheduled - As part of our continuous improvement plan, a maintenance is scheduled on our Public Cloud infrastructure.

Start time : 01/07/2026 07:30 UTC
End time : 01/07/2026 14:00 UTC
Service impact : None.
Service improvement : As part of our continuous improvement policy, we will be doing a maintenance on our infrastructure in the GRA5/79/11 regions.

Thank you for your understanding.
Jul 1, 07:51 UTC
Jun 30, 2026

No incidents reported.

Jun 29, 2026
[BHS1][Storage] - Block Storage incident notification
Resolved - We are pleased to inform you that the incident affecting our Block Storage offering in BHS1 region has been resolved.

Start time : 29/06/2026 14:07 UTC
End time : 29/06/2026 18:40 UTC
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.
Jun 29, 18:47 UTC
Update - We have new information regarding the incident that affected your service(s).

Please find below an update on the situation:
Impacted Service(s) : The block storage service was again unavailable for some customers in BHS1 region between 29/06/2026 17:00 UTC and 29/06/2026 18:00 UTC.
Ongoing Actions : Our teams are continuing to work on the remaining block storage hosts that were impacted by this incident. As this work is ongoing, customers may experience some temporary degradation in performance.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.
Jun 29, 18:10 UTC
Update - We have new information regarding the incident that affected your service(s).

Please find below an update on the situation:
Update : Customers are now able to access their block storage and normal operations have largely resumed.
Ongoing Actions : Our teams are continuing to work on the remaining block storage hosts that were impacted by this incident. As this work is ongoing, customers may experience some temporary degradation in performance.

We will keep you updated on the progress and full resolution.

We apologize for any inconvenience caused and appreciate your understanding.
Jun 29, 15:46 UTC
Update - We have new information regarding the incident that affected your service(s).

Please find below an update on the situation:
Update : The majority of the block storage hosts in BHS1 region are no longer impacted by this incident.
Ongoing Actions : Our teams are currently working on the last impacted block storage hosts.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.
Jun 29, 14:59 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Block Storage offer on the specific region BHS1.

Here are some supplementary details :

Start time : 29/06/2026 14:07 UTC
Impacted Service(s) : The block storage service is temporarily unavailable for some customers in BHS1 region.
Customers Impact : Some customers are unable to access and use their block storage loacted in the specified region.
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
Ongoing Actions : The incident has been identified and our teams are mobilised 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.
Jun 29, 14:43 UTC
Jun 28, 2026
[GRA1/11][Compute - Instance] - Some instances incident notification
Resolved - We are pleased to inform you that the incident affecting our Compute - Instance offering in GRA1 and GRA11 regions has been resolved.

Start time : 28/06/2026 18:45 UTC
End time : 28/06/2026 20:17 UTC
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.
Jun 28, 20:21 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific regions GRA1 and GRA11.

Here are some supplementary details :

Start time : 28/06/2026 18:45 UTC
Impacted Service(s) : Some instances in GRA1 and GRA11 regions are unreachable.
Customers Impact : Some customers are temporarily unable to access their instances located in GRA1 and GRA11 regions.
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
Ongoing Actions : The incident has been identified and our teams are mobilised 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.
Jun 28, 19:10 UTC
[BHS1/3/5][Compute - Instance] - Some instances incident notification
Resolved - We are pleased to inform you that the incident affecting our Compute - Instance offering in BHS1, BHS3 and BHS5 regions has been resolved.

Start time : 28/06/2026 17:04 UTC
End time : 28/06/2026 17:45 UTC
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.
Jun 28, 17:53 UTC
Investigating - We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in the BHS1, BHS3 and BHS5 regions.

Here are some supplementary details :

Start time : 28/06/2026 17:04 UTC
Impacted Service(s) : Some instances in the BHS1, BHS3 and BHS5 regions are unreachable.
Customers Impact : Some customers are temporarily unable to access their instances located in BHS1, BHS3 and BHS5 regions.
Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.
Jun 28, 17:15 UTC
[DE1][Compute - Instance] - Some instances incident notification
Resolved - We had an incident on Compute - Instance offer in DE1 region which has now been resolved.

Here are some supplementary details :

Start time : 28/06/2026 12:55 UTC
End time : 28/06/2026 13:03 UTC
Impacted Service(s) : Some instances in the DE1 region were unreachable.
Customers Impact : Some customers were temporarily unable to access their instances located in DE1 region.
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We thank you for your understanding and patience throughout this incident.
Jun 28, 13:08 UTC
Jun 27, 2026

No incidents reported.

Jun 26, 2026
[GRA9][File storage] - File storage incident notification
Resolved - We are pleased to inform you that the incident affecting our File storage offering has been resolved.

Start time : 26/06/2026 09:07 UTC
End time : 26/06/2026 19:00 UTC
Root Cause : A service disruption occurred due to an unexpected infrastructure failure.

We apologize for any inconvenience caused and appreciate your understanding.
Jun 26, 19:05 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our File storage offer on the specific GRA9 region.

Here are some supplementary details :

Start time : 26/06/2026 09:07 UTC
Impacted Service(s) : Some File storage are temporarily unavailable.
Customers Impact :Some customers are temporarily unable to access their File storage.
Root Cause : A service disruption occurred due to an unexpected infrastructure failure
Ongoing Actions : The incident has been identified and our teams are mobilised 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.
Jun 26, 10:21 UTC
[UK1][Containers & Orchestration] - Managed Kubernetes Service Incident Notification
Resolved - We are pleased to inform you that the incident affecting our Containers & Orchestration offering has been resolved.

Start time : 25/06/2026 18:49 UTC
End time : 26/06/2026 06:40 UTC
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.
Jun 26, 07:18 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer on the specific UK1 regions.

Here are some supplementary details :

Start time : 25/06/2026 18:49 UTC
Impacted Service(s) : Some instances in the UK1 region are unreachable.
Customers Impact : Management and creation of new Managed Kubernetes Service clusters is temporarily unavailable.
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
Ongoing Actions : The incident has been identified and our teams are mobilised 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.
Jun 25, 19:25 UTC
[UK1][Public Cloud] - API Incident Notification
Resolved - This incident has been resolved.
Jun 26, 06:54 UTC
Update - We are pleased to inform you that the incident affecting our Public Cloud offering has been resolved.

Start time : 22/06/2026 14:25 UTC
End time : 22/06/2026 15:04 UTC
Root Cause : This incident was caused by a software issue.

We apologize for any inconvenience caused and appreciate your understanding.
Jun 26, 06:52 UTC
Update - We are pleased to inform you that the incident affecting our Public Cloud offering has been resolved.

Start time : 22/06/2026 14:25 UTC
End time : 22/06/2026 15:04 UTC
Root Cause : This incident was caused by a software issue.

We apologize for any inconvenience caused and appreciate your understanding.
Jun 22, 15:09 UTC
Investigating - We are currently investigating an incident affecting our Public Cloud offering, which is causing temporary issue in the UK1 region.

Here are some supplementary details :

Start time : 22/06/2026 14:25 UTC
Impacted Service(s) : The API in the UK1 region is temporarily degraded.
Customers Impact : For these regions, you might have issues to create, start, or manage your instances and create or attach new volumes.
Ongoing Actions : Our teams are investigating to determine the origin of the incident and fix it.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.
Jun 22, 14:45 UTC
Jun 25, 2026
[GRA1][Compute - Instance] - Some Instances Incident Notification
Resolved - We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved.

Start time : 25/06/2026 18:05 UTC
End time : 25/06/2026 18:30 UTC
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.
Jun 25, 18:48 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific GRA1 region.

Here are some supplementary details :

Start time : 25/06/2026 18:05 UTC
Impacted Service(s) : Some instances in the GRA1 region are unreachable.
Customers Impact : Some customers are temporarily unable to access instances located on the specified region.
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
Ongoing Actions : The incident has been identified and our teams are mobilised 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.
Jun 25, 18:15 UTC
Jun 24, 2026
[GRA][Compute - Instance] - Some Instances Incident Notification
Resolved - We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved.

Start time : 24/06/2026 20:52 UTC
End time : 24/06/2026 21: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.
Jun 24, 21:23 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific GRA region.

Here are some supplementary details :

Start time : 24/06/2026 20:52 UTC
Impacted Service(s) : Some instances in the GRA region are unreachable.
Customers Impact : Some customers are temporarily unable to access instances located on the specified region.
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
Ongoing Actions : The incident has been identified and our teams are mobilised 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.
Jun 24, 21:03 UTC
[GRA7/GRA9/GRA11][Compute - Instance] - Compute Instance Incident Notification
Resolved - We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved.

Start time : 24/06/2026 06:01 UTC
End time : 24/06/2026 06:20 UTC
Root Cause : A service disruption occurred due to an unexpected infrastructure failure.

We apologize for any inconvenience caused and appreciate your understanding.
Jun 24, 09:30 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer in GRA regions.

Here are some supplementary details :

Start time : 24/06/2026 06:01 UTC
Impacted Service(s) : Some instances in the GRA7/GRA9/GRA11 regions are unreachable.
Customers Impact : Some customers are temporarily unable to access some instances located on the specified regions.
Root Cause : A service disruption occurred due to an unexpected infrastructure failure
Ongoing Actions : The incident has been identified and our teams are mobilised 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.
Jun 24, 06:25 UTC
[GRA3][Compute - Instance] - Some Instances Incident Notification
Resolved - We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved.

Start time : 23/06/2026 13:00 UTC
End time : 24/06/2026 00:34 UTC
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.

We apologize for any inconvenience caused and appreciate your understanding.
Jun 24, 00:35 UTC
Identified - We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific GRA3 region.

Here are some supplementary details :

Start time : 23/06/2026 13:00 UTC
Impacted Service(s) : Some instances in the GRA3 region are unreachable.
Customers Impact : Some customers are temporarily unable to access instances located on the specified region.
Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
Ongoing Actions : The incident has been identified and our teams are mobilised 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.
Jun 23, 16:45 UTC
← Incident History Powered by Atlassian Statuspage