Public Cloud Status
Real-time updates of Public Cloud issues and outages
Public Cloud status is Operational
GRA1
GRA3
GRA5
GRA9
DE1
WAW1
GRA
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 would like to inform you that an incident occurred on our Compute - Instance offering in WAW1. This incident has now been resolved.
Please find the details of this incident below :
Start time : 07/05/2026 07:42 UTC End time : 07/05/2026 07:50 UTC Impacted Service(s) : Some instances in the WAW1 region were unreachable. Customers Impact : Customers were temporarily unable to access and use their instances located on the specified region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
We apologize for any inconvenience caused and appreciate your understanding.
We are currently experiencing an event affecting our Compute - Instance offer.
Start time : 04/05/2026 06:31 UTC
Our teams are fully committed to investigating this issue and working towards a resolution as soon as possible. As investigations are ongoing, we will share any new findings or updates with you as soon as possible.
We apologize for any inconvenience caused and appreciate your understanding.
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific region.
Here are some supplementary details :
Start time : 02/05/2026 12:18 UTC Impacted Service(s) : Some instances in the LIM1 region are unreachable. Customers Impact : Customers are temporarily unable to access instances located on the specified regions and Redis Database. 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.
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
BHS3
BHS5
Public Cloud Compute - Instance || ERI
UK1
Public Cloud Compute - Instance || EU-SOUTH-MIL
EU-SOUTH-MIL-A
GRA2
EU-SOUTH-MIL-B
EU-SOUTH-MIL-C
GRA4
Public Cloud Compute - Instance || EU-WEST-PAR
EU-WEST-PAR-A
EU-WEST-PAR-B
EU-WEST-PAR-C
Public Cloud Compute - Instance || GRA
Public Cloud Compute-Instance || AP-SOUTH-MUM
GRA1
We are currently experiencing an event affecting our Compute - Instance offer.
Start time : 04/05/2026 06:31 UTC
Our teams are fully committed to investigating this issue and working towards a resolution as soon as possible. As investigations are ongoing, we will share any new findings or updates with you as soon as possible.
We apologize for any inconvenience caused and appreciate your understanding.
GRA3
We are currently experiencing an event affecting our Compute - Instance offer.
Start time : 04/05/2026 06:31 UTC
Our teams are fully committed to investigating this issue and working towards a resolution as soon as possible. As investigations are ongoing, we will share any new findings or updates with you as soon as possible.
We apologize for any inconvenience caused and appreciate your understanding.
GRA5
We are currently experiencing an event affecting our Compute - Instance offer.
Start time : 04/05/2026 06:31 UTC
Our teams are fully committed to investigating this issue and working towards a resolution as soon as possible. As investigations are ongoing, we will share any new findings or updates with you as soon as possible.
We apologize for any inconvenience caused and appreciate your understanding.
GRA7
GRA9
We are currently experiencing an event affecting our Compute - Instance offer.
Start time : 04/05/2026 06:31 UTC
Our teams are fully committed to investigating this issue and working towards a resolution as soon as possible. As investigations are ongoing, we will share any new findings or updates with you as soon as possible.
We apologize for any inconvenience caused and appreciate your understanding.
GRA11
Public Cloud Compute - Instance || India
AP-SOUTH-MUM-1
Public Cloud Compute - Instance || LIM
DE1
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific region.
Here are some supplementary details :
Start time : 02/05/2026 12:18 UTC Impacted Service(s) : Some instances in the LIM1 region are unreachable. Customers Impact : Customers are temporarily unable to access instances located on the specified regions and Redis Database. 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.
Public Cloud Compute - Instance || RBX
RBX-A
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
We would like to inform you that an incident occurred on our Compute - Instance offering in WAW1. This incident has now been resolved.
Please find the details of this incident below :
Start time : 07/05/2026 07:42 UTC End time : 07/05/2026 07:50 UTC Impacted Service(s) : Some instances in the WAW1 region were unreachable. Customers Impact : Customers were temporarily unable to access and use their instances located on the specified region. Root Cause : A service disruption occurred due to an unexpected underlying infrastructure malfunction.
We apologize for any inconvenience caused and appreciate your understanding.
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
EU-SOUTH-MIL
EU-WEST-PAR
GRA
We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Compute - Instance offer on the specific region.
Here are some supplementary details :
Start time : 02/05/2026 12:18 UTC Impacted Service(s) : Some instances in the LIM1 region are unreachable. Customers Impact : Customers are temporarily unable to access instances located on the specified regions and Redis Database. 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.
VA
Public Cloud Containers & Orchestration || Managed Rancher Service
Public Cloud Containers & Orchestration || Workflow Management
BHS1
BHS3
BHS5
SYD3
DE1
GRA1
GRA3
GRA5
GRA7
GRA
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
US-WEST-OR
Public Cloud Databases || Cassandra
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.