Public Cloud Status
Real-time updates of Public Cloud issues and outages
Public Cloud status is Operational
BHS1
BHS3
BHS5
GRA5
GRA7
GRA9
GRA11
You're checking on Public Cloud - but is your own site converting?
Outages aren't the only thing that costs you visitors.
Get a visual audit that shows exactly where your site loses conversions.
Free, takes 2 minutes.
Active Incidents
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PostgreSQL offer.
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 our provider. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
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.
Recently Resolved Incidents
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in the RBX10 region.
Here are some supplementary details :
Start time : 24/04/2026 14:40 UTC Impacted Service(s) : Some instances in the RBX10 region are unreachable. Customers Impact : Customers are temporarily unable to access instances located on the specified 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.
We are currently investigating an incident affecting our Storage offering, which is causing temporary functionality issue in BHS.
Here are some supplementary details :
Start time : 22/04/2026 13:22 UTC Impacted Service(s) : Customers may experience difficulties accessing their services. Customers Impact : Customers may experience 503 errors in BHS 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.
We are currently investigating an incident affecting our Cloud Compute offering, which is causing temporary functionality issue in BHS1 region.
Here are some supplementary details :
Start time : 21/04/2026 11:45 UTC Impacted Service(s) : Some instances in the BHS1, BHS3 and BHS5 regions are unreachable. Customers Impact : Customers are temporarily unable to access instances located on the specified rigion. 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.
We are currently experiencing an incident affecting our Containers & Orchestration - Managed Private Registry offering, which is causing temporary functionality issues in the DE region.
Here is detail for this incident : Start time : 21/04/2026 07:51 UTC Impacted Service(s) : Some Registries are unreachable in the DE 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.
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in the Graveline region.
Here are some supplementary details :
Start time : 20/04/2026 12:27 UTC Impacted Service(s) : Some instances in the Graveline region are unreachable. 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.
We had an incident on Object Storage S3 Standard offer in DE region which has now been resolved.
Here are some supplementary details :
Start time : 20/04/2026 09:55 UTC End time : 20/04/2026 11:06 UTC Impacted Service(s) : Object storage service in DE region was temporarily unavailable for some customers. Customers Impact : Some customers were getting 503 error when trying to connect their object storage located in DE 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.
Public Cloud Outage Survival Guide
Public Cloud Components
Public Cloud AI & Machine Learning || AI Dashboard
Public Cloud AI & Machine Learning || AI Deploy
BHS
GRA
Public Cloud AI & Machine Learning || AI Endpoint
Public Cloud AI & Machine Learning || AI Notebooks
BHS
GRA
Public Cloud AI & Machine Learning || AI Training
BHS
GRA
Public Cloud Compute - Instance || BHS
BHS1
We are currently investigating an incident affecting our Cloud Compute offering, which is causing temporary functionality issue in BHS1 region.
Here are some supplementary details :
Start time : 21/04/2026 11:45 UTC Impacted Service(s) : Some instances in the BHS1, BHS3 and BHS5 regions are unreachable. Customers Impact : Customers are temporarily unable to access instances located on the specified rigion. 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.
BHS3
We are currently investigating an incident affecting our Cloud Compute offering, which is causing temporary functionality issue in BHS1 region.
Here are some supplementary details :
Start time : 21/04/2026 11:45 UTC Impacted Service(s) : Some instances in the BHS1, BHS3 and BHS5 regions are unreachable. Customers Impact : Customers are temporarily unable to access instances located on the specified rigion. 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.
BHS5
We are currently investigating an incident affecting our Cloud Compute offering, which is causing temporary functionality issue in BHS1 region.
Here are some supplementary details :
Start time : 21/04/2026 11:45 UTC Impacted Service(s) : Some instances in the BHS1, BHS3 and BHS5 regions are unreachable. Customers Impact : Customers are temporarily unable to access instances located on the specified rigion. 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.
Public Cloud Compute - Instance || ERI
UK1
Public Cloud Compute - Instance || EU-SOUTH-MIL
GRA2
EU-SOUTH-MIL-A
EU-SOUTH-MIL-B
GRA4
EU-SOUTH-MIL-C
Public Cloud Compute - Instance || EU-WEST-PAR
EU-WEST-PAR-A
EU-WEST-PAR-B
EU-WEST-PAR-C
Public Cloud Compute-Instance || AP-SOUTH-MUM
Public Cloud Compute - Instance || GRA
GRA1
GRA3
GRA5
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in the Graveline region.
Here are some supplementary details :
Start time : 20/04/2026 12:27 UTC Impacted Service(s) : Some instances in the Graveline region are unreachable. 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.
GRA7
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in the Graveline region.
Here are some supplementary details :
Start time : 20/04/2026 12:27 UTC Impacted Service(s) : Some instances in the Graveline region are unreachable. 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.
GRA9
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in the Graveline region.
Here are some supplementary details :
Start time : 20/04/2026 12:27 UTC Impacted Service(s) : Some instances in the Graveline region are unreachable. 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.
GRA11
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in the Graveline region.
Here are some supplementary details :
Start time : 20/04/2026 12:27 UTC Impacted Service(s) : Some instances in the Graveline region are unreachable. 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.
Public Cloud Compute - Instance || India
AP-SOUTH-MUM-1
Public Cloud Compute - Instance || LIM
DE1
Public Cloud Compute - Instance || RBX
RBX-A
We are currently investigating an incident affecting our Compute - Instance offering, which is causing temporary availability issue in the RBX10 region.
Here are some supplementary details :
Start time : 24/04/2026 14:40 UTC Impacted Service(s) : Some instances in the RBX10 region are unreachable. Customers Impact : Customers are temporarily unable to access instances located on the specified 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.
Public Cloud Compute - Instance || SGP
SGP1
SGP2
Public Cloud Compute - Instance || SBG
SBG5
SBG7
Public Cloud Compute - Instance || SYD
SYD1
AP-SOUTHEAST-SYD-2
Public Cloud Compute - Instance || USA
US-EAST-VA-1
US-WEST-OR-1
Public Cloud Compute - Instance || WAW
WAW1
Public Cloud Containers & Orchestration || Load Balancer
AP-SOUTH-MUM
BHS5
DE1
EU-WEST-PAR
GRA5
GRA7
GRA9
GRA11
RBX-A
SBG5
SGP1
SYD1
WAW1
UK1
US-EAST-VA
US-WEST-OR
Public Cloud Containers & Orchestration || Managed Kubernetes Service
AP-SOUTH-MUM
BHS5
EU-WEST-LIM
EU-SOUTH-MIL
EU-WEST-PAR
RBX
GRA5
GRA7
GRA9
GRA11
SBG5
SGP1
SYD1
WAW1
UK1
US-EAST-VA
US-WEST-OR
Public Cloud Containers & Orchestration || Managed Private Registry
AP-SOUTH-MUM
BHS
DE
We are currently experiencing an incident affecting our Containers & Orchestration - Managed Private Registry offering, which is causing temporary functionality issues in the DE region.
Here is detail for this incident : Start time : 21/04/2026 07:51 UTC Impacted Service(s) : Some Registries are unreachable in the DE 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.
EU-SOUTH-MIL
EU-WEST-PAR
GRA
VA
Public Cloud Containers & Orchestration || Managed Rancher Service
Public Cloud Containers & Orchestration || Workflow Management
BHS1
BHS3
BHS5
SYD3
DE1
GRA1
GRA3
GRA5
GRA
GRA7
GRA9
GRA11
RBX-A
SBG5
SBG7
PAR
SGP1
SGP2
SYD1
AP-SOUTHEAST-SYD-2
Public Cloud Databases || M3 Aggregator
UK1
WAW1
WAW2
US-EAST-VA
Public Cloud Databases || Cassandra
US-WEST-OR
AP-SOUTH-MUM
Public Cloud Databases || MongoDB
BHS
Public Cloud Databases || M3DB
DE
GRA
EU-WEST-PAR
SBG
SGP
UK
WAW
EU-SOUTH-MIL
RBX
AP-SOUTH-MUM
US-EAST-VA
US-WEST-OR
Public Cloud Databases || MySQL
BHS
DE
GRA
EU-SOUTH-MIL
AP-SOUTH-MUM
EU-WEST-PAR
RBX
SBG
SGP
US-EAST-VA
UK
US-WEST-OR
WAW
Public Cloud Databases || PostgreSQL
BHS
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PostgreSQL offer.
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 our provider. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
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.
DE
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PostgreSQL offer.
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 our provider. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
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.
SYD
GRA
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PostgreSQL offer.
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 our provider. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
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.
EU-SOUTH-MIL
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PostgreSQL offer.
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 our provider. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
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.
AP-SOUTH-MUM
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PostgreSQL offer.
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 our provider. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
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.
EU-WEST-PAR
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PostgreSQL offer.
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 our provider. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
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.
RBX
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PostgreSQL offer.
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 our provider. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
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.
SBG
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PostgreSQL offer.
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 our provider. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
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.
SGP
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PostgreSQL offer.
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 our provider. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
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.
UK
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PostgreSQL offer.
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 our provider. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
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.
US-EAST-VA
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PostgreSQL offer.
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 our provider. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
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.
US-WEST-OR
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PostgreSQL offer.
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 our provider. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
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.
WAW
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our PostgreSQL offer.
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 our provider. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.
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.
Public Cloud Databases || Valkey
Public Cloud Data & Analytics || Data Processing
BHS
DE
GRA
GRA
EU-SOUTH-MIL
AP-SOUTH-MUM
EU-WEST-PAR
RBX
SBG
SGP
US-EAST-VA
UK
US-WEST-OR
WAW
Public Cloud Data & Analytics || ClickHouse
EU-WEST-PAR
EU-SOUTH-MIL
AP-SOUTH-MUM
Public Cloud Data & Analytics || Data Platform
Public Cloud Data & Analytics || Dashboards
BHS
DE
GRA
EU-WEST-PAR
SBG
SGP
UK
WAW
EU-SOUTH-MIL
AP-SOUTH-MUM
RBX
US-EAST-VA
US-WEST-OR
Public Cloud Data & Analytics || Kafka
BHS
DE
GRA
EU-SOUTH-MIL
AP-SOUTH-MUM
EU-WEST-PAR
RBX
SBG
SGP
UK
AP-SOUTH-MUM-1
US-EAST-VA
US-WEST-OR
MAD
WAW
Public Cloud Data & Analytics || Kafka Connect
BHS
Public Cloud Network || FailoverIP
DE
GRA
EU-WEST-PAR
EU-SOUTH-MIL
AP-SOUTH-MUM
RBX
SBG
SGP
UK
US-EAST-VA
US-WEST-OR
WAW
Public Cloud Data & Analytics || Kafka MirrorMaker
BHS
DE
GRA
EU-SOUTH-MIL
AP-SOUTH-MUM
EU-WEST-PAR
RBX
SBG
Public Cloud Network || Load Balancer
SGP
UK
WAW
US-EAST-VA
US-WEST-OR
Public Cloud Data & Analytics || OpenSearch
BHS
DE
GRA
EU-SOUTH-MIL
AP-SOUTH-MUM
EU-WEST-PAR
RBX
SBG
SGP
US-EAST-VA
UK
US-WEST-OR
WAW
Public Cloud Identity, Security & Operations || Authentication
Public Cloud Identity, Security & Operations || Barbican
AP-SOUTH-MUM
AP-SOUTHEAST-SYD-2
BHS5
DE1
EU-SOUTH-MIL
EU-WEST-PAR
GRA9
RBX-A
SBG7
SGP1
SYD1
UK1
US-WEST-OR
US-EAST-VA
WAW1
Public Cloud Management || Horizon
Public Cloud Identity, Security & Operations || Key Management Service
AP-SOUTHEAST-SGP
AP-SOUTHEAST-SYD
CA-EAST-TOR
CA-EAST-BHS
EU-CENTRAL-WAW
EU-SOUTH-MIL
EU-WEST-ERI
EU-WEST-GRA
EU-WEST-LIM
EU-WEST-PAR
EU-WEST-RBX
EU-WEST-SBG
Public Cloud Identity, Security & Operations || Logs Data Platform
BHS
GRA
Public Cloud LocalZones || AF-CENTRAL
AF-CENTRAL-LZ-ABJ
Public Cloud LocalZones || AF-NORTH
AF-NORTH-LZ-RBA
Public Cloud LocalZones || AP-SOUTH-MUM
Public Cloud LocalZones || EU-CENTRAL
EU-CENTRAL-LZ-BUH
EU-CENTRAL-LZ-PRG
EU-CENTRAL-LZ-SOF
Public Cloud LocalZones || EU-NORTH
AP-SOUTH-MUM-1
EU-NORTH-LZ-CPH
EU-NORTH-LZ-HEL
EU-NORTH-LZ-OSL
EU-NORTH-LZ-STO
Public Cloud LocalZones || EU-SOUTH
EU-SOUTH-LZ-LIS
EU-SOUTH-LZ-MAD
EU-SOUTH-LZ-MIL
Public Cloud LocalZones || EU-WEST
EU-WEST-LZ-AMS
EU-WEST-LZ-BRU
EU-WEST-LZ-DLN
EU-WEST-LZ-LUX
EU-WEST-LZ-MNC
EU-WEST-LZ-MRS
EU-WEST-LZ-VIE
EU-WEST-LZ-ZRH
Public Cloud LocalZones || US-CENTRAL
US-CENTRAL-LZ-SLC
US-CENTRAL-LZ-STL
Public Cloud LocalZones || US-EAST
US-EAST-LZ-ATL
US-EAST-LZ-BOS
US-EAST-LZ-CHI
US-EAST-LZ-DAL
US-EAST-LZ-MIA
US-EAST-LZ-NYC
Public Cloud LocalZones || US-WEST
US-WEST-LZ-DEN
US-WEST-LZ-LAX
US-WEST-LZ-PAO
US-WEST-LZ-PHX
US-WEST-LZ-SEA
Public Cloud Network || Floating IP
BHS1
BHS3
BHS5
DE1
GRA1
GRA3
GRA5
GRA7
GRA9
GRA11
AP-SOUTH-MUM-1
RBX-A
SBG5
SBG7
SGP1
SYD1
AP-SOUTHEAST-SYD-2
UK1
WAW1
US-EAST-VA-1
US-WEST-OR-1
EU-WEST-PAR-A
EU-WEST-PAR-B
EU-WEST-PAR-C
EU-SOUTH-MIL-A
EU-SOUTH-MIL-B
EU-SOUTH-MIL-C
Public Cloud Network || Gateway
BHS1
BHS3
BHS5
DE1
GRA1
GRA3
GRA5
GRA7
GRA9
GRA11
SBG5
SBG7
SGP1
SYD1
AP-SOUTHEAST-SYD-2
UK1
WAW1
Public Cloud UK
US-EAST-VA-1
US-WEST-OR-1
AP-SOUTH-MUM-1
EU-WEST-PAR-A
EU-WEST-PAR-B
EU-WEST-PAR-C
RBX-A
EU-SOUTH-MIL-A
EU-SOUTH-MIL-B
EU-SOUTH-MIL-C
Public Cloud Network || Load Balancer
BHS1
BHS3
BHS5
DE1
GRA1
GRA3
GRA5
GRA7
GRA9
GRA11
SBG5
SBG7
SGP1
SYD1
AP-SOUTHEAST-SYD-2
UK1
WAW1
US-EAST-VA-1
US-WEST-OR-1
EU-WEST-PAR-A
EU-WEST-PAR-B
EU-WEST-PAR-C
AP-SOUTH-MUM-1
RBX-A
EU-SOUTH-MIL-A
EU-SOUTH-MIL-B
EU-SOUTH-MIL-C
Public Cloud Network || Private network (vRack)
BHS1
BHS3
BHS5
DE1
GRA1
GRA3
GRA5
GRA7
GRA9
GRA11
RBX-A
SBG5
SBG7
SGP1
SGP2
SYD1
AP-SOUTHEAST-SYD-2
Public Cloud Compute - Instance || 3AZ
PAR
UK1
WAW1
US-EAST-VA-1
US-WEST-OR-1
EU-WEST-PAR-A
RBX-A
EU-WEST-PAR-B
EU-WEST-PAR-C
AP-SOUTH-MUM-1
RBX-A
EU-SOUTH-MIL-A
EU-SOUTH-MIL-B
EU-SOUTH-MIL-C
Public Cloud Network || Public network
BHS1
BHS3
BHS5
DE1
GRA1
GRA3
GRA5
GRA7
GRA9
GRA11
RBX-A
SBG1
SBG3
SBG5
SBG7
SGP1
SGP2
SYD1
AP-SOUTHEAST-SYD-2
UK1
WAW1
US-EAST-VA-1
US-WEST-OR-1
EU-WEST-PAR-A
EU-WEST-PAR-B
EU-WEST-PAR-C
AP-SOUTH-MUM-1
RBX-A
EU-SOUTH-MIL-A
EU-SOUTH-MIL-B
EU-SOUTH-MIL-C
Public Cloud Quantum || Emulators
BHS
GRA
Public Cloud Quantum || QPUs
BHS
GRA
Public Cloud Storage || Block storage
AP-SOUTHEAST-SYD-2
AP-SOUTH-MUM-1
BHS1
SYD2
BHS3
BHS5
DE1
EU-SOUTH-MIL-A
EU-SOUTH-MIL-B
EU-SOUTH-MIL-C
EU-WEST-PAR-A
EU-WEST-PAR-B
EU-WEST-PAR-C
GRA1
GRA3
GRA5
GRA6
GRA7
GRA9
GRA11
RBX-A
SBG5
SBG7
SGP1
SYD1
UK1
US-EAST-VA-1
US-WEST-OR-1
WAW1
YNM1
Public Cloud Storage || Cloud Archive
DE
GRA
UK
WAW
BHS
We are currently investigating an incident affecting our Storage offering, which is causing temporary functionality issue in BHS.
Here are some supplementary details :
Start time : 22/04/2026 13:22 UTC Impacted Service(s) : Customers may experience difficulties accessing their services. Customers Impact : Customers may experience 503 errors in BHS 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.
SYD
SGP
US-EAST-VA
US-WEST-OR
Public Cloud BHS
Public Cloud Storage || Cold Archive
Public Cloud DE
RBX-ARCHIVE
Public Cloud Storage || Instance Backup
Public Cloud GRA
BHS1
Public Cloud PAR
BHS3
Public Cloud SBG
Public Cloud UK
BHS5
Public Cloud WAW
DE1
GRA1
Public Cloud BHS
Public Cloud DE
GRA3
Public Cloud GRA
GRA5
GRA7
Public Cloud PAR
GRA9
Public Cloud SBG
Public Cloud UK
GRA11
Public Cloud WAW
SBG5
SBG7
SGP1
SYD1
AP-SOUTHEAST-SYD-2
UK1
US-EAST-VA-1
US-WEST-OR-1
WAW1
AP-SOUTH-MUM-1
EU-WEST-PAR-A
EU-WEST-PAR-B
EU-WEST-PAR-C
RBX-A
Public Cloud Storage || Object storage
BHS
GRA
DE
We had an incident on Object Storage S3 Standard offer in DE region which has now been resolved.
Here are some supplementary details :
Start time : 20/04/2026 09:55 UTC End time : 20/04/2026 11:06 UTC Impacted Service(s) : Object storage service in DE region was temporarily unavailable for some customers. Customers Impact : Some customers were getting 503 error when trying to connect their object storage located in DE 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.