Public Cloud Status: check for Public Cloud outages and issues

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud AI & Machine Learning || AI Dashboard

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud AI & Machine Learning || AI Deploy

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud AI & Machine Learning || AI Endpoint

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud AI & Machine Learning || AI Notebooks

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud AI & Machine Learning || AI Training

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Compute - Instance || BHS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS3

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Compute - Instance || ERI

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

UK1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Compute - Instance || EU-SOUTH-MIL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA2

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL-B

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL-C

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA4

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Compute - Instance || EU-WEST-PAR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-B

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-C

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Compute - Instance || GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Compute-Instance || AP-SOUTH-MUM

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GRA1][Compute - Instance] - Instance incident notification

Started 16 Apr 2026 16:33:54 (3 days ago), resolved 16 Apr 2026 16:33:54 (3 days ago)

Incident without Impact

Resolved

GRA1

We had an incident on Compute - Instance offer which has now been resolved.

Here are some supplementary details :

Start time : 16/04/2026 16:19 UTC End time : 16/04/2026 16:26 UTC Impacted Service(s) : Some instances in the GRA1 region were unreachable. Customers Impact : Customers were temporarily unable to access and use their instances in the GRA1 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.

GRA3

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA9

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA11

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Compute - Instance || India

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[AP-SOUTH-MUM][Public Cloud] - LocalZone / CEPH / Compute Instance / Managed Kubernetes Service incident notification

Started 18 Apr 2026 22:06:46 (7 hours ago), still ongoing

Major Incident

Identified

AP-SOUTH-MUM-1

AP-SOUTH-MUM

AP-SOUTH-MUM-1

LocalZones || AP-SOUTH-MUM

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Public Cloud offering on the specific AP-SOUTH-MUM.

Here are some supplementary details :

Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Some customers are temporarily unable to access or use their compute instances in the AP-SOUTH-MUM-1 region, while actions such as restarting instances in the AP-SOUTH-MUM local zone are currently unavailable, and some Ceph volumes in the region are also impacted. Customers Impact : Some customers are temporarily unable to access or use their compute instances in the AP-SOUTH-MUM-1 region, are unable to perform actions such as restarting instances in the AP-SOUTH-MUM Local Zones, and are also unable to use their Ceph storage services. Root Cause : This incident is linked to : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk 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.

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Some customers using a Managed Kubernetes Service may also be impacted. The management service for instances, volumes, and the load balancer is temporarily unavailable. Customers are currently unable to perform certain actions such as starting, stopping, or restarting resources. Provisioning of these services in this region is also temporarily unavailable. We recommend that customers do not perform any actions on their currently running services. Ongoing Actions : The incident has been identified and our teams and 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.

18 Apr 2026 23:00:12 (6 hours ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Public Cloud offering on the specific AP-SOUTH-MUM.

Here are some supplementary details :

Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Some customers are temporarily unable to access or use their compute instances in the AP-SOUTH-MUM-1 region, while actions such as restarting instances in the AP-SOUTH-MUM local zone are currently unavailable, and some Ceph volumes in the region are also impacted. Customers Impact : Some customers are temporarily unable to access or use their compute instances in the AP-SOUTH-MUM-1 region, are unable to perform actions such as restarting instances in the AP-SOUTH-MUM Local Zones, and are also unable to use their Ceph storage services. Root Cause : This incident is linked to : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk 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.

18 Apr 2026 22:06:46 (7 hours ago)

See all updates

Public Cloud Compute - Instance || LIM

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

DE1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[DE1][Compute - Instance] - Instance incident notification

Started 15 Apr 2026 07:46:19 (4 days ago), resolved 15 Apr 2026 09:01:54 (4 days ago)

Major Incident

Resolved

DE1

We are currently experiencing an event affecting our Compute - Instance offer.

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.

See all updates

Public Cloud Compute - Instance || RBX

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

RBX-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Compute - Instance || SGP

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP2

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Compute - Instance || SBG

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Compute - Instance || SYD

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SYD1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTHEAST-SYD-2

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Compute - Instance || USA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-VA-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-OR-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Compute - Instance || WAW

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Containers & Orchestration || Load Balancer

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

DE1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA9

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA11

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

RBX-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SYD1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

UK1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-VA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-OR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Containers & Orchestration || Managed Kubernetes Service

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[AP-SOUTH-MUM][Public Cloud] - LocalZone / CEPH / Compute Instance / Managed Kubernetes Service incident notification

Started 18 Apr 2026 22:06:46 (7 hours ago), still ongoing

Major Incident

Identified

AP-SOUTH-MUM-1

AP-SOUTH-MUM

AP-SOUTH-MUM-1

LocalZones || AP-SOUTH-MUM

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Public Cloud offering on the specific AP-SOUTH-MUM.

Here are some supplementary details :

Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Some customers are temporarily unable to access or use their compute instances in the AP-SOUTH-MUM-1 region, while actions such as restarting instances in the AP-SOUTH-MUM local zone are currently unavailable, and some Ceph volumes in the region are also impacted. Customers Impact : Some customers are temporarily unable to access or use their compute instances in the AP-SOUTH-MUM-1 region, are unable to perform actions such as restarting instances in the AP-SOUTH-MUM Local Zones, and are also unable to use their Ceph storage services. Root Cause : This incident is linked to : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk 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.

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Some customers using a Managed Kubernetes Service may also be impacted. The management service for instances, volumes, and the load balancer is temporarily unavailable. Customers are currently unable to perform certain actions such as starting, stopping, or restarting resources. Provisioning of these services in this region is also temporarily unavailable. We recommend that customers do not perform any actions on their currently running services. Ongoing Actions : The incident has been identified and our teams and 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.

18 Apr 2026 23:00:12 (6 hours ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Public Cloud offering on the specific AP-SOUTH-MUM.

Here are some supplementary details :

Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Some customers are temporarily unable to access or use their compute instances in the AP-SOUTH-MUM-1 region, while actions such as restarting instances in the AP-SOUTH-MUM local zone are currently unavailable, and some Ceph volumes in the region are also impacted. Customers Impact : Some customers are temporarily unable to access or use their compute instances in the AP-SOUTH-MUM-1 region, are unable to perform actions such as restarting instances in the AP-SOUTH-MUM Local Zones, and are also unable to use their Ceph storage services. Root Cause : This incident is linked to : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk 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.

18 Apr 2026 22:06:46 (7 hours ago)

See all updates

BHS5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-LIM

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

RBX

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA9

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA11

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SYD1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

UK1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-VA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-OR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Containers & Orchestration || Managed Private Registry

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[AP-SOUTH-MUM][Containers & Orchestration] - Managed Private Registry incident notification

Started 18 Apr 2026 20:11:38 (9 hours ago), still ongoing

Major Incident

Identified

AP-SOUTH-MUM

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Containers & Orchestration offer on the specific AP-SOUTH-MUM.

Here are some supplementary details :

Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Service degraded for Registry Product on this DC. Customers Impact : Some of customer may encounter a degraded service on their registries, images push/pull are not available and some UI may be unavailable. 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.

See all updates

BHS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

DE

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

VA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Containers & Orchestration || Managed Rancher Service

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Containers & Orchestration || Workflow Management

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS3

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SYD3

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

DE1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA3

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA9

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA11

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

RBX-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

PAR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP2

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SYD1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Databases || M3 Aggregator

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTHEAST-SYD-2

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

UK1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW2

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-VA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Databases || Cassandra

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-OR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Databases || MongoDB

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Databases || M3DB

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

DE

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[DE/GRA][Databases] - Databases MongoDB incident notification

Started 15 Apr 2026 08:11:20 (4 days ago), resolved 15 Apr 2026 22:15:57 (3 days ago)

Major Incident

Resolved

DE

We are currently experiencing an event affecting our PCI-Databases offer.

Start time : 15/04/2026 04:10 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.

Resolved: We are pleased to inform you that the incident affecting our PCI-Databases has been resolved.

Start time : 15/04/2026 04:10 UTC End time : 15/04/2026 22:10 UTC Root Cause : This incident is related by : https://public-cloud.status-ovhcloud.com/incidents/2v5b4kyjttxj

We apologize for any inconvenience caused and appreciate your understanding.

15 Apr 2026 22:15:57 (3 days ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Some services are available again 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.

15 Apr 2026 15:08:57 (4 days ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Databases offer on the specific DE/GRA regions.

Here are some supplementary details :

Start time : 15/04/2026 07:10 UTC Impacted Service(s) : Some MongoDB databases are temporarily unavailable. Customers Impact : Some customers are temporarily unable to use their MongoDB databases. Root Cause : This incident is related by : https://public-cloud.status-ovhcloud.com/incidents/2v5b4kyjttxj 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.

15 Apr 2026 08:11:20 (4 days ago)

Investigating: We are currently experiencing an event affecting our PCI-Databases offer.

Start time : 15/04/2026 04:10 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.

15 Apr 2026 08:07:13 (4 days ago)

See all updates

GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

UK

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

RBX

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[AP-SOUTH-MUM][PCI-Databases] - Cloud databases incident notification

Started 18 Apr 2026 19:31:44 (10 hours ago), still ongoing

Major Incident

Identified

AP-SOUTH-MUM

More...

We are currently investigating an incident affecting our PCI-Databases offering, which is causing temporary availability issue in the AP-SOUTH-MUM.

Here are some supplementary details :

Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Cloud databases services is unavailable on AP-SOUTH-MUM Customers Impact : Customers may find it difficult to access their services. Orders and service management are also affected. 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.

See all updates

US-EAST-VA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-OR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Databases || MySQL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

DE

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[AP-SOUTH-MUM][PCI-Databases] - Cloud databases incident notification

Started 18 Apr 2026 19:31:44 (10 hours ago), still ongoing

Major Incident

Identified

AP-SOUTH-MUM

More...

We are currently investigating an incident affecting our PCI-Databases offering, which is causing temporary availability issue in the AP-SOUTH-MUM.

Here are some supplementary details :

Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Cloud databases services is unavailable on AP-SOUTH-MUM Customers Impact : Customers may find it difficult to access their services. Orders and service management are also affected. 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.

See all updates

EU-WEST-PAR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

RBX

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-VA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

UK

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-OR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Databases || PostgreSQL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Databases] - PostgreSQL 18 incident notification

Started 30 Mar 2026 12:36:18 (20 days ago), still ongoing

Major Incident

Identified

BHS

DE

GRA

EU-SOUTH-MIL

AP-SOUTH-MUM

More...

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.

See all updates

DE

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Databases] - PostgreSQL 18 incident notification

Started 30 Mar 2026 12:36:18 (20 days ago), still ongoing

Major Incident

Identified

BHS

DE

GRA

EU-SOUTH-MIL

AP-SOUTH-MUM

More...

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.

See all updates

GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Databases] - PostgreSQL 18 incident notification

Started 30 Mar 2026 12:36:18 (20 days ago), still ongoing

Major Incident

Identified

BHS

DE

GRA

EU-SOUTH-MIL

AP-SOUTH-MUM

More...

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.

See all updates

SYD

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Databases] - PostgreSQL 18 incident notification

Started 30 Mar 2026 12:36:18 (20 days ago), still ongoing

Major Incident

Identified

BHS

DE

GRA

EU-SOUTH-MIL

AP-SOUTH-MUM

More...

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.

See all updates

AP-SOUTH-MUM

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[AP-SOUTH-MUM][PCI-Databases] - Cloud databases incident notification

Started 18 Apr 2026 19:31:44 (10 hours ago), still ongoing

Major Incident

Identified

AP-SOUTH-MUM

More...

We are currently investigating an incident affecting our PCI-Databases offering, which is causing temporary availability issue in the AP-SOUTH-MUM.

Here are some supplementary details :

Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Cloud databases services is unavailable on AP-SOUTH-MUM Customers Impact : Customers may find it difficult to access their services. Orders and service management are also affected. 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.

See all updates

[GLOBAL][Databases] - PostgreSQL 18 incident notification

Started 30 Mar 2026 12:36:18 (20 days ago), still ongoing

Major Incident

Identified

BHS

DE

GRA

EU-SOUTH-MIL

AP-SOUTH-MUM

More...

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.

See all updates

EU-WEST-PAR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Databases] - PostgreSQL 18 incident notification

Started 30 Mar 2026 12:36:18 (20 days ago), still ongoing

Major Incident

Identified

BHS

DE

GRA

EU-SOUTH-MIL

AP-SOUTH-MUM

More...

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.

See all updates

RBX

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Databases] - PostgreSQL 18 incident notification

Started 30 Mar 2026 12:36:18 (20 days ago), still ongoing

Major Incident

Identified

BHS

DE

GRA

EU-SOUTH-MIL

AP-SOUTH-MUM

More...

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.

See all updates

SBG

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Databases] - PostgreSQL 18 incident notification

Started 30 Mar 2026 12:36:18 (20 days ago), still ongoing

Major Incident

Identified

BHS

DE

GRA

EU-SOUTH-MIL

AP-SOUTH-MUM

More...

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.

See all updates

SGP

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Databases] - PostgreSQL 18 incident notification

Started 30 Mar 2026 12:36:18 (20 days ago), still ongoing

Major Incident

Identified

BHS

DE

GRA

EU-SOUTH-MIL

AP-SOUTH-MUM

More...

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.

See all updates

UK

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Databases] - PostgreSQL 18 incident notification

Started 30 Mar 2026 12:36:18 (20 days ago), still ongoing

Major Incident

Identified

BHS

DE

GRA

EU-SOUTH-MIL

AP-SOUTH-MUM

More...

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.

See all updates

US-EAST-VA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Databases] - PostgreSQL 18 incident notification

Started 30 Mar 2026 12:36:18 (20 days ago), still ongoing

Major Incident

Identified

BHS

DE

GRA

EU-SOUTH-MIL

AP-SOUTH-MUM

More...

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.

See all updates

US-WEST-OR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Databases] - PostgreSQL 18 incident notification

Started 30 Mar 2026 12:36:18 (20 days ago), still ongoing

Major Incident

Identified

BHS

DE

GRA

EU-SOUTH-MIL

AP-SOUTH-MUM

More...

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.

See all updates

WAW

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Databases] - PostgreSQL 18 incident notification

Started 30 Mar 2026 12:36:18 (20 days ago), still ongoing

Major Incident

Identified

BHS

DE

GRA

EU-SOUTH-MIL

AP-SOUTH-MUM

More...

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.

See all updates

Public Cloud Databases || Valkey

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Data & Analytics || Data Processing

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

DE

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[AP-SOUTH-MUM][PCI-Databases] - Cloud databases incident notification

Started 18 Apr 2026 19:31:44 (10 hours ago), still ongoing

Major Incident

Identified

AP-SOUTH-MUM

More...

We are currently investigating an incident affecting our PCI-Databases offering, which is causing temporary availability issue in the AP-SOUTH-MUM.

Here are some supplementary details :

Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Cloud databases services is unavailable on AP-SOUTH-MUM Customers Impact : Customers may find it difficult to access their services. Orders and service management are also affected. 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.

See all updates

EU-WEST-PAR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

RBX

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-VA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

UK

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-OR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Data & Analytics || ClickHouse

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Data & Analytics || Data Platform

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GRA][Data & Analytics] - Data Platform incident notification

Started 13 Apr 2026 10:45:35 (6 days ago), resolved 13 Apr 2026 10:45:35 (6 days ago)

Incident without Impact

Resolved

Data & Analytics || Data Platform

We had an incident on Data & Analytics offer which has now been resolved.

Here are some supplementary details :

Start time : 13/04/2026 10:30 UTC End time : 13/04/2026 11:00 UTC Impacted Service(s) : Data Platform projects were temporarily unavailable. Customers Impact : For these regions, you might have faced issues with network connectivity or managing your private networks. Root Cause : This incident was caused by a software issue.

We thank you for your understanding and patience throughout this incident.

Public Cloud Data & Analytics || Dashboards

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

DE

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

UK

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[AP-SOUTH-MUM][PCI-Databases] - Cloud databases incident notification

Started 18 Apr 2026 19:31:44 (10 hours ago), still ongoing

Major Incident

Identified

AP-SOUTH-MUM

More...

We are currently investigating an incident affecting our PCI-Databases offering, which is causing temporary availability issue in the AP-SOUTH-MUM.

Here are some supplementary details :

Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Cloud databases services is unavailable on AP-SOUTH-MUM Customers Impact : Customers may find it difficult to access their services. Orders and service management are also affected. 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.

See all updates

RBX

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-VA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-OR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Data & Analytics || Kafka

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Data & Analytics] - Kafka upgrade version incident notification

Started 30 Oct 2025 16:15:28 (6 months ago), resolved 17 Apr 2026 09:42:53 (2 days ago)

Minor Incident

Resolved

BHS

DE

More...

We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

17 Apr 2026 09:42:53 (2 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

3 Apr 2026 14:06:47 (16 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

24 Feb 2026 13:41:33 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

18 Feb 2026 13:46:59 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

7 Jan 2026 19:22:16 (3 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

26 Dec 2025 12:58:39 (4 months ago)

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

19 Dec 2025 08:32:51 (4 months ago)

Identified: We are continuing to work on a fix for this issue.

15 Dec 2025 14:36:10 (4 months ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

3 Nov 2025 14:50:39 (6 months ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

31 Oct 2025 12:18:06 (6 months ago)

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

30 Oct 2025 16:15:28 (6 months ago)

See all updates

DE

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Data & Analytics] - Kafka upgrade version incident notification

Started 30 Oct 2025 16:15:28 (6 months ago), resolved 17 Apr 2026 09:42:53 (2 days ago)

Minor Incident

Resolved

BHS

DE

More...

We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

17 Apr 2026 09:42:53 (2 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

3 Apr 2026 14:06:47 (16 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

24 Feb 2026 13:41:33 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

18 Feb 2026 13:46:59 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

7 Jan 2026 19:22:16 (3 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

26 Dec 2025 12:58:39 (4 months ago)

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

19 Dec 2025 08:32:51 (4 months ago)

Identified: We are continuing to work on a fix for this issue.

15 Dec 2025 14:36:10 (4 months ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

3 Nov 2025 14:50:39 (6 months ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

31 Oct 2025 12:18:06 (6 months ago)

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

30 Oct 2025 16:15:28 (6 months ago)

See all updates

GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Data & Analytics] - Kafka upgrade version incident notification

Started 30 Oct 2025 16:15:28 (6 months ago), resolved 17 Apr 2026 09:42:53 (2 days ago)

Minor Incident

Resolved

BHS

DE

More...

We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

17 Apr 2026 09:42:53 (2 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

3 Apr 2026 14:06:47 (16 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

24 Feb 2026 13:41:33 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

18 Feb 2026 13:46:59 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

7 Jan 2026 19:22:16 (3 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

26 Dec 2025 12:58:39 (4 months ago)

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

19 Dec 2025 08:32:51 (4 months ago)

Identified: We are continuing to work on a fix for this issue.

15 Dec 2025 14:36:10 (4 months ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

3 Nov 2025 14:50:39 (6 months ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

31 Oct 2025 12:18:06 (6 months ago)

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

30 Oct 2025 16:15:28 (6 months ago)

See all updates

EU-SOUTH-MIL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[AP-SOUTH-MUM][PCI-Databases] - Cloud databases incident notification

Started 18 Apr 2026 19:31:44 (10 hours ago), still ongoing

Major Incident

Identified

AP-SOUTH-MUM

More...

We are currently investigating an incident affecting our PCI-Databases offering, which is causing temporary availability issue in the AP-SOUTH-MUM.

Here are some supplementary details :

Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Cloud databases services is unavailable on AP-SOUTH-MUM Customers Impact : Customers may find it difficult to access their services. Orders and service management are also affected. 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.

See all updates

EU-WEST-PAR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Data & Analytics] - Kafka upgrade version incident notification

Started 30 Oct 2025 16:15:28 (6 months ago), resolved 17 Apr 2026 09:42:53 (2 days ago)

Minor Incident

Resolved

BHS

DE

More...

We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

17 Apr 2026 09:42:53 (2 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

3 Apr 2026 14:06:47 (16 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

24 Feb 2026 13:41:33 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

18 Feb 2026 13:46:59 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

7 Jan 2026 19:22:16 (3 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

26 Dec 2025 12:58:39 (4 months ago)

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

19 Dec 2025 08:32:51 (4 months ago)

Identified: We are continuing to work on a fix for this issue.

15 Dec 2025 14:36:10 (4 months ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

3 Nov 2025 14:50:39 (6 months ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

31 Oct 2025 12:18:06 (6 months ago)

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

30 Oct 2025 16:15:28 (6 months ago)

See all updates

RBX

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Data & Analytics] - Kafka upgrade version incident notification

Started 30 Oct 2025 16:15:28 (6 months ago), resolved 17 Apr 2026 09:42:53 (2 days ago)

Minor Incident

Resolved

BHS

DE

More...

We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

17 Apr 2026 09:42:53 (2 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

3 Apr 2026 14:06:47 (16 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

24 Feb 2026 13:41:33 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

18 Feb 2026 13:46:59 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

7 Jan 2026 19:22:16 (3 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

26 Dec 2025 12:58:39 (4 months ago)

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

19 Dec 2025 08:32:51 (4 months ago)

Identified: We are continuing to work on a fix for this issue.

15 Dec 2025 14:36:10 (4 months ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

3 Nov 2025 14:50:39 (6 months ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

31 Oct 2025 12:18:06 (6 months ago)

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

30 Oct 2025 16:15:28 (6 months ago)

See all updates

SGP

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Data & Analytics] - Kafka upgrade version incident notification

Started 30 Oct 2025 16:15:28 (6 months ago), resolved 17 Apr 2026 09:42:53 (2 days ago)

Minor Incident

Resolved

BHS

DE

More...

We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

17 Apr 2026 09:42:53 (2 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

3 Apr 2026 14:06:47 (16 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

24 Feb 2026 13:41:33 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

18 Feb 2026 13:46:59 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

7 Jan 2026 19:22:16 (3 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

26 Dec 2025 12:58:39 (4 months ago)

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

19 Dec 2025 08:32:51 (4 months ago)

Identified: We are continuing to work on a fix for this issue.

15 Dec 2025 14:36:10 (4 months ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

3 Nov 2025 14:50:39 (6 months ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

31 Oct 2025 12:18:06 (6 months ago)

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

30 Oct 2025 16:15:28 (6 months ago)

See all updates

UK

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Data & Analytics] - Kafka upgrade version incident notification

Started 30 Oct 2025 16:15:28 (6 months ago), resolved 17 Apr 2026 09:42:53 (2 days ago)

Minor Incident

Resolved

BHS

DE

More...

We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

17 Apr 2026 09:42:53 (2 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

3 Apr 2026 14:06:47 (16 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

24 Feb 2026 13:41:33 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

18 Feb 2026 13:46:59 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

7 Jan 2026 19:22:16 (3 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

26 Dec 2025 12:58:39 (4 months ago)

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

19 Dec 2025 08:32:51 (4 months ago)

Identified: We are continuing to work on a fix for this issue.

15 Dec 2025 14:36:10 (4 months ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

3 Nov 2025 14:50:39 (6 months ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

31 Oct 2025 12:18:06 (6 months ago)

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

30 Oct 2025 16:15:28 (6 months ago)

See all updates

US-EAST-VA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-OR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Data & Analytics] - Kafka upgrade version incident notification

Started 30 Oct 2025 16:15:28 (6 months ago), resolved 17 Apr 2026 09:42:53 (2 days ago)

Minor Incident

Resolved

BHS

DE

More...

We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

17 Apr 2026 09:42:53 (2 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

3 Apr 2026 14:06:47 (16 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

24 Feb 2026 13:41:33 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

18 Feb 2026 13:46:59 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

7 Jan 2026 19:22:16 (3 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

26 Dec 2025 12:58:39 (4 months ago)

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

19 Dec 2025 08:32:51 (4 months ago)

Identified: We are continuing to work on a fix for this issue.

15 Dec 2025 14:36:10 (4 months ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

3 Nov 2025 14:50:39 (6 months ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

31 Oct 2025 12:18:06 (6 months ago)

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

30 Oct 2025 16:15:28 (6 months ago)

See all updates

MAD

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Data & Analytics || Kafka Connect

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Data & Analytics] - Kafka upgrade version incident notification

Started 30 Oct 2025 16:15:28 (6 months ago), resolved 17 Apr 2026 09:42:53 (2 days ago)

Minor Incident

Resolved

BHS

DE

More...

We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

17 Apr 2026 09:42:53 (2 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

3 Apr 2026 14:06:47 (16 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

24 Feb 2026 13:41:33 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

18 Feb 2026 13:46:59 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

7 Jan 2026 19:22:16 (3 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

26 Dec 2025 12:58:39 (4 months ago)

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

19 Dec 2025 08:32:51 (4 months ago)

Identified: We are continuing to work on a fix for this issue.

15 Dec 2025 14:36:10 (4 months ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

3 Nov 2025 14:50:39 (6 months ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

31 Oct 2025 12:18:06 (6 months ago)

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

30 Oct 2025 16:15:28 (6 months ago)

See all updates

DE

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Data & Analytics] - Kafka upgrade version incident notification

Started 30 Oct 2025 16:15:28 (6 months ago), resolved 17 Apr 2026 09:42:53 (2 days ago)

Minor Incident

Resolved

BHS

DE

More...

We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

17 Apr 2026 09:42:53 (2 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

3 Apr 2026 14:06:47 (16 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

24 Feb 2026 13:41:33 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

18 Feb 2026 13:46:59 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

7 Jan 2026 19:22:16 (3 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

26 Dec 2025 12:58:39 (4 months ago)

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

19 Dec 2025 08:32:51 (4 months ago)

Identified: We are continuing to work on a fix for this issue.

15 Dec 2025 14:36:10 (4 months ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

3 Nov 2025 14:50:39 (6 months ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

31 Oct 2025 12:18:06 (6 months ago)

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

30 Oct 2025 16:15:28 (6 months ago)

See all updates

Public Cloud Network || FailoverIP

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Data & Analytics] - Kafka upgrade version incident notification

Started 30 Oct 2025 16:15:28 (6 months ago), resolved 17 Apr 2026 09:42:53 (2 days ago)

Minor Incident

Resolved

BHS

DE

More...

We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

17 Apr 2026 09:42:53 (2 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

3 Apr 2026 14:06:47 (16 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

24 Feb 2026 13:41:33 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

18 Feb 2026 13:46:59 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

7 Jan 2026 19:22:16 (3 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

26 Dec 2025 12:58:39 (4 months ago)

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

19 Dec 2025 08:32:51 (4 months ago)

Identified: We are continuing to work on a fix for this issue.

15 Dec 2025 14:36:10 (4 months ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

3 Nov 2025 14:50:39 (6 months ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

31 Oct 2025 12:18:06 (6 months ago)

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

30 Oct 2025 16:15:28 (6 months ago)

See all updates

EU-WEST-PAR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Data & Analytics] - Kafka upgrade version incident notification

Started 30 Oct 2025 16:15:28 (6 months ago), resolved 17 Apr 2026 09:42:53 (2 days ago)

Minor Incident

Resolved

BHS

DE

More...

We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

17 Apr 2026 09:42:53 (2 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

3 Apr 2026 14:06:47 (16 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

24 Feb 2026 13:41:33 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

18 Feb 2026 13:46:59 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

7 Jan 2026 19:22:16 (3 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

26 Dec 2025 12:58:39 (4 months ago)

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

19 Dec 2025 08:32:51 (4 months ago)

Identified: We are continuing to work on a fix for this issue.

15 Dec 2025 14:36:10 (4 months ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

3 Nov 2025 14:50:39 (6 months ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

31 Oct 2025 12:18:06 (6 months ago)

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

30 Oct 2025 16:15:28 (6 months ago)

See all updates

EU-SOUTH-MIL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[AP-SOUTH-MUM][PCI-Databases] - Cloud databases incident notification

Started 18 Apr 2026 19:31:44 (10 hours ago), still ongoing

Major Incident

Identified

AP-SOUTH-MUM

More...

We are currently investigating an incident affecting our PCI-Databases offering, which is causing temporary availability issue in the AP-SOUTH-MUM.

Here are some supplementary details :

Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Cloud databases services is unavailable on AP-SOUTH-MUM Customers Impact : Customers may find it difficult to access their services. Orders and service management are also affected. 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.

See all updates

RBX

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Data & Analytics] - Kafka upgrade version incident notification

Started 30 Oct 2025 16:15:28 (6 months ago), resolved 17 Apr 2026 09:42:53 (2 days ago)

Minor Incident

Resolved

BHS

DE

More...

We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

17 Apr 2026 09:42:53 (2 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

3 Apr 2026 14:06:47 (16 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

24 Feb 2026 13:41:33 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

18 Feb 2026 13:46:59 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

7 Jan 2026 19:22:16 (3 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

26 Dec 2025 12:58:39 (4 months ago)

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

19 Dec 2025 08:32:51 (4 months ago)

Identified: We are continuing to work on a fix for this issue.

15 Dec 2025 14:36:10 (4 months ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

3 Nov 2025 14:50:39 (6 months ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

31 Oct 2025 12:18:06 (6 months ago)

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

30 Oct 2025 16:15:28 (6 months ago)

See all updates

SGP

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Data & Analytics] - Kafka upgrade version incident notification

Started 30 Oct 2025 16:15:28 (6 months ago), resolved 17 Apr 2026 09:42:53 (2 days ago)

Minor Incident

Resolved

BHS

DE

More...

We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

17 Apr 2026 09:42:53 (2 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

3 Apr 2026 14:06:47 (16 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

24 Feb 2026 13:41:33 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

18 Feb 2026 13:46:59 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

7 Jan 2026 19:22:16 (3 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

26 Dec 2025 12:58:39 (4 months ago)

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

19 Dec 2025 08:32:51 (4 months ago)

Identified: We are continuing to work on a fix for this issue.

15 Dec 2025 14:36:10 (4 months ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

3 Nov 2025 14:50:39 (6 months ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

31 Oct 2025 12:18:06 (6 months ago)

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

30 Oct 2025 16:15:28 (6 months ago)

See all updates

UK

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Data & Analytics] - Kafka upgrade version incident notification

Started 30 Oct 2025 16:15:28 (6 months ago), resolved 17 Apr 2026 09:42:53 (2 days ago)

Minor Incident

Resolved

BHS

DE

More...

We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

17 Apr 2026 09:42:53 (2 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

3 Apr 2026 14:06:47 (16 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

24 Feb 2026 13:41:33 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

18 Feb 2026 13:46:59 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

7 Jan 2026 19:22:16 (3 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

26 Dec 2025 12:58:39 (4 months ago)

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

19 Dec 2025 08:32:51 (4 months ago)

Identified: We are continuing to work on a fix for this issue.

15 Dec 2025 14:36:10 (4 months ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

3 Nov 2025 14:50:39 (6 months ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

31 Oct 2025 12:18:06 (6 months ago)

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

30 Oct 2025 16:15:28 (6 months ago)

See all updates

US-EAST-VA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-OR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Data & Analytics] - Kafka upgrade version incident notification

Started 30 Oct 2025 16:15:28 (6 months ago), resolved 17 Apr 2026 09:42:53 (2 days ago)

Minor Incident

Resolved

BHS

DE

More...

We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

17 Apr 2026 09:42:53 (2 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

3 Apr 2026 14:06:47 (16 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

24 Feb 2026 13:41:33 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

18 Feb 2026 13:46:59 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

7 Jan 2026 19:22:16 (3 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

26 Dec 2025 12:58:39 (4 months ago)

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

19 Dec 2025 08:32:51 (4 months ago)

Identified: We are continuing to work on a fix for this issue.

15 Dec 2025 14:36:10 (4 months ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

3 Nov 2025 14:50:39 (6 months ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

31 Oct 2025 12:18:06 (6 months ago)

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

30 Oct 2025 16:15:28 (6 months ago)

See all updates

Public Cloud Data & Analytics || Kafka MirrorMaker

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Data & Analytics] - Kafka upgrade version incident notification

Started 30 Oct 2025 16:15:28 (6 months ago), resolved 17 Apr 2026 09:42:53 (2 days ago)

Minor Incident

Resolved

BHS

DE

More...

We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

17 Apr 2026 09:42:53 (2 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

3 Apr 2026 14:06:47 (16 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

24 Feb 2026 13:41:33 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

18 Feb 2026 13:46:59 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

7 Jan 2026 19:22:16 (3 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

26 Dec 2025 12:58:39 (4 months ago)

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

19 Dec 2025 08:32:51 (4 months ago)

Identified: We are continuing to work on a fix for this issue.

15 Dec 2025 14:36:10 (4 months ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

3 Nov 2025 14:50:39 (6 months ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

31 Oct 2025 12:18:06 (6 months ago)

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

30 Oct 2025 16:15:28 (6 months ago)

See all updates

DE

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Data & Analytics] - Kafka upgrade version incident notification

Started 30 Oct 2025 16:15:28 (6 months ago), resolved 17 Apr 2026 09:42:53 (2 days ago)

Minor Incident

Resolved

BHS

DE

More...

We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

17 Apr 2026 09:42:53 (2 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

3 Apr 2026 14:06:47 (16 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

24 Feb 2026 13:41:33 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

18 Feb 2026 13:46:59 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

7 Jan 2026 19:22:16 (3 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

26 Dec 2025 12:58:39 (4 months ago)

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

19 Dec 2025 08:32:51 (4 months ago)

Identified: We are continuing to work on a fix for this issue.

15 Dec 2025 14:36:10 (4 months ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

3 Nov 2025 14:50:39 (6 months ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

31 Oct 2025 12:18:06 (6 months ago)

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

30 Oct 2025 16:15:28 (6 months ago)

See all updates

GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Data & Analytics] - Kafka upgrade version incident notification

Started 30 Oct 2025 16:15:28 (6 months ago), resolved 17 Apr 2026 09:42:53 (2 days ago)

Minor Incident

Resolved

BHS

DE

More...

We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

17 Apr 2026 09:42:53 (2 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

3 Apr 2026 14:06:47 (16 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

24 Feb 2026 13:41:33 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

18 Feb 2026 13:46:59 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

7 Jan 2026 19:22:16 (3 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

26 Dec 2025 12:58:39 (4 months ago)

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

19 Dec 2025 08:32:51 (4 months ago)

Identified: We are continuing to work on a fix for this issue.

15 Dec 2025 14:36:10 (4 months ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

3 Nov 2025 14:50:39 (6 months ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

31 Oct 2025 12:18:06 (6 months ago)

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

30 Oct 2025 16:15:28 (6 months ago)

See all updates

EU-SOUTH-MIL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[AP-SOUTH-MUM][PCI-Databases] - Cloud databases incident notification

Started 18 Apr 2026 19:31:44 (10 hours ago), still ongoing

Major Incident

Identified

AP-SOUTH-MUM

More...

We are currently investigating an incident affecting our PCI-Databases offering, which is causing temporary availability issue in the AP-SOUTH-MUM.

Here are some supplementary details :

Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Cloud databases services is unavailable on AP-SOUTH-MUM Customers Impact : Customers may find it difficult to access their services. Orders and service management are also affected. 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.

See all updates

EU-WEST-PAR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Data & Analytics] - Kafka upgrade version incident notification

Started 30 Oct 2025 16:15:28 (6 months ago), resolved 17 Apr 2026 09:42:53 (2 days ago)

Minor Incident

Resolved

BHS

DE

More...

We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

17 Apr 2026 09:42:53 (2 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

3 Apr 2026 14:06:47 (16 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

24 Feb 2026 13:41:33 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

18 Feb 2026 13:46:59 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

7 Jan 2026 19:22:16 (3 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

26 Dec 2025 12:58:39 (4 months ago)

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

19 Dec 2025 08:32:51 (4 months ago)

Identified: We are continuing to work on a fix for this issue.

15 Dec 2025 14:36:10 (4 months ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

3 Nov 2025 14:50:39 (6 months ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

31 Oct 2025 12:18:06 (6 months ago)

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

30 Oct 2025 16:15:28 (6 months ago)

See all updates

RBX

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Data & Analytics] - Kafka upgrade version incident notification

Started 30 Oct 2025 16:15:28 (6 months ago), resolved 17 Apr 2026 09:42:53 (2 days ago)

Minor Incident

Resolved

BHS

DE

More...

We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

17 Apr 2026 09:42:53 (2 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

3 Apr 2026 14:06:47 (16 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

24 Feb 2026 13:41:33 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

18 Feb 2026 13:46:59 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

7 Jan 2026 19:22:16 (3 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

26 Dec 2025 12:58:39 (4 months ago)

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

19 Dec 2025 08:32:51 (4 months ago)

Identified: We are continuing to work on a fix for this issue.

15 Dec 2025 14:36:10 (4 months ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

3 Nov 2025 14:50:39 (6 months ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

31 Oct 2025 12:18:06 (6 months ago)

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

30 Oct 2025 16:15:28 (6 months ago)

See all updates

SGP

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Data & Analytics] - Kafka upgrade version incident notification

Started 30 Oct 2025 16:15:28 (6 months ago), resolved 17 Apr 2026 09:42:53 (2 days ago)

Minor Incident

Resolved

BHS

DE

More...

We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

17 Apr 2026 09:42:53 (2 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

3 Apr 2026 14:06:47 (16 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

24 Feb 2026 13:41:33 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

18 Feb 2026 13:46:59 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

7 Jan 2026 19:22:16 (3 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

26 Dec 2025 12:58:39 (4 months ago)

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

19 Dec 2025 08:32:51 (4 months ago)

Identified: We are continuing to work on a fix for this issue.

15 Dec 2025 14:36:10 (4 months ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

3 Nov 2025 14:50:39 (6 months ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

31 Oct 2025 12:18:06 (6 months ago)

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

30 Oct 2025 16:15:28 (6 months ago)

See all updates

UK

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Data & Analytics] - Kafka upgrade version incident notification

Started 30 Oct 2025 16:15:28 (6 months ago), resolved 17 Apr 2026 09:42:53 (2 days ago)

Minor Incident

Resolved

BHS

DE

More...

We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

17 Apr 2026 09:42:53 (2 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

3 Apr 2026 14:06:47 (16 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

24 Feb 2026 13:41:33 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

18 Feb 2026 13:46:59 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

7 Jan 2026 19:22:16 (3 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

26 Dec 2025 12:58:39 (4 months ago)

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

19 Dec 2025 08:32:51 (4 months ago)

Identified: We are continuing to work on a fix for this issue.

15 Dec 2025 14:36:10 (4 months ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

3 Nov 2025 14:50:39 (6 months ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

31 Oct 2025 12:18:06 (6 months ago)

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

30 Oct 2025 16:15:28 (6 months ago)

See all updates

Public Cloud Network || Load Balancer

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GLOBAL][Data & Analytics] - Kafka upgrade version incident notification

Started 30 Oct 2025 16:15:28 (6 months ago), resolved 17 Apr 2026 09:42:53 (2 days ago)

Minor Incident

Resolved

BHS

DE

More...

We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

Resolved: We are pleased to inform you that the incident affecting our Data & Analytics has been resolved.

Start time : 28/10/2025 12:00 UTC End time : 17/04/2026 09:28 UTC Root Cause : This incident was caused by our provider.

We apologize for any inconvenience caused and appreciate your understanding.

17 Apr 2026 09:42:53 (2 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by mid April. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

3 Apr 2026 14:06:47 (16 days ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Update : Our provider is still working to restore the service as quickly as possible. Based on our current assessment, we estimate that the incident is expected to be resolved by early March. We will keep you informed as soon as possible.

We apologize for any inconvenience caused and appreciate your understanding.

24 Feb 2026 13:41:33 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our teams are still working closely with our provider to solve the incident. 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.

18 Feb 2026 13:46:59 (2 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : We continue to work with our provider on the incident. 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.

7 Jan 2026 19:22:16 (3 months ago)

Monitoring: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : The incident originated on 28/10/2025 12:00 UTC when attempts to upgrade Kafka from version 3.8 to the target x.y release began returning an error. The problem is limited to the upgrade path; existing Kafka clusters continue to operate normally, and no other functionality of the Data & Analytics platform is impacted. Actions in progress : Our teams are working closely with the provider to diagnose the root cause of the upgrade failure. We are monitoring the provider's remediation work in real time and have prepared a fallback path that allows customers to deploy alternative supported versions (e.g., 3.9 or 4.0) in parallel while the primary upgrade path is being restored. Key guidance for customers : No immediate action is required from customers. If you need a newer Kafka version before the official migration is available, you may provision a parallel cluster running version 3.9 or 4.0. We will continue to provide updates as the investigation progresses and will notify you when the upgrade path is fully restored. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and corrected. It is being closely monitored to ensure long-term stability.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding

26 Dec 2025 12:58:39 (4 months ago)

Monitoring: Monitoring remains active for this incident.

Update : Our provider is still working to restore the service as quickly as possible. The migration from 3.8 to x.y version is expected to be available by the end of January 2026.

We apologize for any inconvenience caused and appreciate your understanding.

19 Dec 2025 08:32:51 (4 months ago)

Identified: We are continuing to work on a fix for this issue.

15 Dec 2025 14:36:10 (4 months ago)

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Our provider has informed us that the migration from 3.8 to x.y version is more complex than initially anticipated, which is the reason why this feature is currently unavailable. However, customers can deploy Kafka version 3.9 or 4.0 in parallel if they need. Upgrade possibility is expected to be available by end January 2026.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

3 Nov 2025 14:50:39 (6 months ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Data & Analytics offer on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). Customers Impact : Customers are temporarily unable to upgrade their Kafka version from 3.8 to x.y. Root Cause : This incident is caused by our provider. Ongoing Actions : The incident has been identified and our teams are working with our provider to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

31 Oct 2025 12:18:06 (6 months ago)

Investigating: We are currently investigating an incident affecting our Data & Analytics offering, which is causing temporary functionality issue on Kafka services.

Here are some supplementary details :

Start time : 28/10/2025 12:00 UTC Impacted Service(s) : Upgrading version trigger an error ("cannot upgrade from version 3.8 to x.y"). 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.

30 Oct 2025 16:15:28 (6 months ago)

See all updates

US-EAST-VA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-OR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Data & Analytics || OpenSearch

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

DE

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[AP-SOUTH-MUM][PCI-Databases] - Cloud databases incident notification

Started 18 Apr 2026 19:31:44 (10 hours ago), still ongoing

Major Incident

Identified

AP-SOUTH-MUM

More...

We are currently investigating an incident affecting our PCI-Databases offering, which is causing temporary availability issue in the AP-SOUTH-MUM.

Here are some supplementary details :

Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Cloud databases services is unavailable on AP-SOUTH-MUM Customers Impact : Customers may find it difficult to access their services. Orders and service management are also affected. 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.

See all updates

EU-WEST-PAR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

RBX

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-VA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

UK

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-OR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Identity, Security & Operations || Authentication

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Identity, Security & Operations || Barbican

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTHEAST-SYD-2

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

DE1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA9

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

RBX-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SYD1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

UK1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-OR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-VA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Management || Horizon

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Identity, Security & Operations || Key Management Service

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTHEAST-SGP

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTHEAST-SYD

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

CA-EAST-TOR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

CA-EAST-BHS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-CENTRAL-WAW

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-ERI

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-LIM

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-RBX

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-SBG

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Identity, Security & Operations || Logs Data Platform

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud LocalZones || AF-CENTRAL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AF-CENTRAL-LZ-ABJ

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud LocalZones || AF-NORTH

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AF-NORTH-LZ-RBA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud LocalZones || AP-SOUTH-MUM

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[AP-SOUTH-MUM][Public Cloud] - LocalZone / CEPH / Compute Instance / Managed Kubernetes Service incident notification

Started 18 Apr 2026 22:06:46 (7 hours ago), still ongoing

Major Incident

Identified

AP-SOUTH-MUM-1

AP-SOUTH-MUM

AP-SOUTH-MUM-1

LocalZones || AP-SOUTH-MUM

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Public Cloud offering on the specific AP-SOUTH-MUM.

Here are some supplementary details :

Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Some customers are temporarily unable to access or use their compute instances in the AP-SOUTH-MUM-1 region, while actions such as restarting instances in the AP-SOUTH-MUM local zone are currently unavailable, and some Ceph volumes in the region are also impacted. Customers Impact : Some customers are temporarily unable to access or use their compute instances in the AP-SOUTH-MUM-1 region, are unable to perform actions such as restarting instances in the AP-SOUTH-MUM Local Zones, and are also unable to use their Ceph storage services. Root Cause : This incident is linked to : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk 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.

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Some customers using a Managed Kubernetes Service may also be impacted. The management service for instances, volumes, and the load balancer is temporarily unavailable. Customers are currently unable to perform certain actions such as starting, stopping, or restarting resources. Provisioning of these services in this region is also temporarily unavailable. We recommend that customers do not perform any actions on their currently running services. Ongoing Actions : The incident has been identified and our teams and 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.

18 Apr 2026 23:00:12 (6 hours ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Public Cloud offering on the specific AP-SOUTH-MUM.

Here are some supplementary details :

Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Some customers are temporarily unable to access or use their compute instances in the AP-SOUTH-MUM-1 region, while actions such as restarting instances in the AP-SOUTH-MUM local zone are currently unavailable, and some Ceph volumes in the region are also impacted. Customers Impact : Some customers are temporarily unable to access or use their compute instances in the AP-SOUTH-MUM-1 region, are unable to perform actions such as restarting instances in the AP-SOUTH-MUM Local Zones, and are also unable to use their Ceph storage services. Root Cause : This incident is linked to : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk 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.

18 Apr 2026 22:06:46 (7 hours ago)

See all updates

Public Cloud LocalZones || EU-CENTRAL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-CENTRAL-LZ-BUH

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-CENTRAL-LZ-PRG

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-CENTRAL-LZ-SOF

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud LocalZones || EU-NORTH

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-NORTH-LZ-CPH

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-NORTH-LZ-HEL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-NORTH-LZ-OSL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-NORTH-LZ-STO

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud LocalZones || EU-SOUTH

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-LZ-LIS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-LZ-MAD

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-LZ-MIL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud LocalZones || EU-WEST

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-LZ-AMS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-LZ-BRU

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-LZ-DLN

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-LZ-LUX

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-LZ-MNC

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-LZ-MRS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-LZ-VIE

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-LZ-ZRH

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud LocalZones || US-CENTRAL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-CENTRAL-LZ-SLC

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-CENTRAL-LZ-STL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud LocalZones || US-EAST

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-LZ-ATL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-LZ-BOS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-LZ-CHI

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-LZ-DAL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-LZ-MIA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-LZ-NYC

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud LocalZones || US-WEST

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-LZ-DEN

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-LZ-LAX

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-LZ-PAO

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-LZ-PHX

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-LZ-SEA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Network || Floating IP

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS3

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

DE1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA3

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA9

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA11

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

RBX-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SYD1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTHEAST-SYD-2

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

UK1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-VA-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-OR-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-B

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-C

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL-B

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL-C

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Network || Gateway

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS3

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

DE1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA3

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA9

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA11

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SYD1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTHEAST-SYD-2

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

UK1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-VA-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud UK

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-OR-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-B

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-C

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

RBX-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL-B

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL-C

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Network || Load Balancer

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS3

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

DE1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA3

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA9

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA11

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SYD1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTHEAST-SYD-2

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

UK1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-VA-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-OR-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-B

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-C

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

RBX-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL-B

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL-C

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Network || Private network (vRack)

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS3

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

DE1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA3

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA9

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA11

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

RBX-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP2

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SYD1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTHEAST-SYD-2

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Compute - Instance || 3AZ

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

UK1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

PAR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-VA-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-OR-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

RBX-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-B

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-C

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

RBX-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL-B

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL-C

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Network || Public network

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS3

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

DE1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GRA][Network] - Network incident notification

Started 13 Apr 2026 09:30:40 (6 days ago), resolved 13 Apr 2026 11:58:40 (6 days ago)

Major Incident

Resolved

GRA1

GRA3

GRA5

GRA7

GRA9

More...

We are currently investigating an incident affecting our Network offering, which is causing temporary availability issue in the GRA region.

Here are some supplementary details :

Start time : 13/04/2026 09:25 UTC Impacted Service(s) : For these regions, you might have issues with network connectivity or managing your Public networks. Your existing network configurations remain active. 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.

See all updates

GRA3

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GRA][Network] - Network incident notification

Started 13 Apr 2026 09:30:40 (6 days ago), resolved 13 Apr 2026 11:58:40 (6 days ago)

Major Incident

Resolved

GRA1

GRA3

GRA5

GRA7

GRA9

More...

We are currently investigating an incident affecting our Network offering, which is causing temporary availability issue in the GRA region.

Here are some supplementary details :

Start time : 13/04/2026 09:25 UTC Impacted Service(s) : For these regions, you might have issues with network connectivity or managing your Public networks. Your existing network configurations remain active. 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.

See all updates

GRA5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GRA][Network] - Network incident notification

Started 13 Apr 2026 09:30:40 (6 days ago), resolved 13 Apr 2026 11:58:40 (6 days ago)

Major Incident

Resolved

GRA1

GRA3

GRA5

GRA7

GRA9

More...

We are currently investigating an incident affecting our Network offering, which is causing temporary availability issue in the GRA region.

Here are some supplementary details :

Start time : 13/04/2026 09:25 UTC Impacted Service(s) : For these regions, you might have issues with network connectivity or managing your Public networks. Your existing network configurations remain active. 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.

See all updates

GRA7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GRA][Network] - Network incident notification

Started 13 Apr 2026 09:30:40 (6 days ago), resolved 13 Apr 2026 11:58:40 (6 days ago)

Major Incident

Resolved

GRA1

GRA3

GRA5

GRA7

GRA9

More...

We are currently investigating an incident affecting our Network offering, which is causing temporary availability issue in the GRA region.

Here are some supplementary details :

Start time : 13/04/2026 09:25 UTC Impacted Service(s) : For these regions, you might have issues with network connectivity or managing your Public networks. Your existing network configurations remain active. 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.

See all updates

GRA9

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GRA][Network] - Network incident notification

Started 13 Apr 2026 09:30:40 (6 days ago), resolved 13 Apr 2026 11:58:40 (6 days ago)

Major Incident

Resolved

GRA1

GRA3

GRA5

GRA7

GRA9

More...

We are currently investigating an incident affecting our Network offering, which is causing temporary availability issue in the GRA region.

Here are some supplementary details :

Start time : 13/04/2026 09:25 UTC Impacted Service(s) : For these regions, you might have issues with network connectivity or managing your Public networks. Your existing network configurations remain active. 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.

See all updates

GRA11

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[GRA][Network] - Network incident notification

Started 13 Apr 2026 09:30:40 (6 days ago), resolved 13 Apr 2026 11:58:40 (6 days ago)

Major Incident

Resolved

GRA1

GRA3

GRA5

GRA7

GRA9

More...

We are currently investigating an incident affecting our Network offering, which is causing temporary availability issue in the GRA region.

Here are some supplementary details :

Start time : 13/04/2026 09:25 UTC Impacted Service(s) : For these regions, you might have issues with network connectivity or managing your Public networks. Your existing network configurations remain active. 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.

See all updates

RBX-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG3

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP2

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SYD1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTHEAST-SYD-2

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

UK1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-VA-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-OR-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-B

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-C

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

RBX-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL-B

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL-C

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Quantum || Emulators

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Quantum || QPUs

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Storage || Block storage

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTHEAST-SYD-2

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS3

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SYD2

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

DE1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL-B

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL-C

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-B

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-C

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA3

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA6

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA9

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA11

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

RBX-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SYD1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

UK1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-VA-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-OR-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

YNM1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Storage || Cloud Archive

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

DE

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

UK

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SYD

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-VA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-OR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Storage || Cold Archive

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

RBX-ARCHIVE

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud BHS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Storage || Instance Backup

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud DE

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud PAR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS3

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud SBG

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

DE1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud UK

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud WAW

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA3

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud BHS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud DE

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA9

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud PAR

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA11

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud SBG

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud UK

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud WAW

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SYD1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTHEAST-SYD-2

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

UK1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-VA-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-OR-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-B

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-C

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

RBX-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Storage || Object storage

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

DE

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

RBX

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SYD

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

UK

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[ERI1][Storage] - Object Storage Incident Notification

Started 15 Apr 2026 07:38:01 (4 days ago), resolved 15 Apr 2026 07:38:01 (4 days ago)

Incident without Impact

Resolved

UK

We had an incident on Storage offer which has now been resolved.

Here are some supplementary details :

Start time : 15/04/2026 05:00 UTC End time : 15/04/2026 07:16 UTC Impacted Service(s) : The block storage service was temporarily unavailable for some customers. Customers Impact : Some customers were temporarily unable to access their storage located in ERI1. Root Cause : A service disruption occurred due to an unexpected infrastructure failure.

We thank you for your understanding and patience throughout this incident.

US-EAST-VA-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-OR-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

YYZ

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

LIM

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[AP-SOUTH-MUM][Storage] - Object Storage S3 incident notification

Started 18 Apr 2026 18:01:08 (11 hours ago), still ongoing

Major Incident

Identified

AP-SOUTH-MUM-1

We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the AP-SOUTH-MUM region .

Here are some supplementary details :

Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Issues to access on S3 objects on this region Customers Impact : Customers may experience issues downloading or uploading their objects due to 500/503 errors. 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.

See all updates

EU-WEST-PAR-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[EU-WEST-PAR][Storage] - Object Storage Incident Notification

Started 16 Apr 2026 12:56:01 (3 days ago), resolved 16 Apr 2026 15:08:51 (3 days ago)

Major Incident

Resolved

EU-WEST-PAR-A

EU-WEST-PAR-B

EU-WEST-PAR-C

We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the PAR region.

Here are some supplementary details :

Start time : 16/04/2026 11:35 UTC Impacted Service(s) : The object storage service is temporarily unavailable. Customers Impact : Customers in the EU-WEST-PAR region may temporarily encounter 503 errors on their object storage. 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.

See all updates

EU-WEST-PAR-B

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[EU-WEST-PAR][Storage] - Object Storage Incident Notification

Started 16 Apr 2026 12:56:01 (3 days ago), resolved 16 Apr 2026 15:08:51 (3 days ago)

Major Incident

Resolved

EU-WEST-PAR-A

EU-WEST-PAR-B

EU-WEST-PAR-C

We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the PAR region.

Here are some supplementary details :

Start time : 16/04/2026 11:35 UTC Impacted Service(s) : The object storage service is temporarily unavailable. Customers Impact : Customers in the EU-WEST-PAR region may temporarily encounter 503 errors on their object storage. 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.

See all updates

EU-WEST-PAR-C

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[EU-WEST-PAR][Storage] - Object Storage Incident Notification

Started 16 Apr 2026 12:56:01 (3 days ago), resolved 16 Apr 2026 15:08:51 (3 days ago)

Major Incident

Resolved

EU-WEST-PAR-A

EU-WEST-PAR-B

EU-WEST-PAR-C

We are currently investigating an incident affecting our Storage offering, which is causing temporary availability issue in the PAR region.

Here are some supplementary details :

Start time : 16/04/2026 11:35 UTC Impacted Service(s) : The object storage service is temporarily unavailable. Customers Impact : Customers in the EU-WEST-PAR region may temporarily encounter 503 errors on their object storage. 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.

See all updates

YNM1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL-B

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL-C

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Storage || Volume Backup

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS3

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

DE1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA3

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA9

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA11

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SYD1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTHEAST-SYD-2

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

UK1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-VA-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-OR-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

RBX-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-B

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-C

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Storage || Volume Snapshot (Ceph)

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

DE1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA2

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA3

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA6

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA4

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA8

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA9

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

GRA11

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

RBX-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG6

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG7

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SBG8

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SGP1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

SYD1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTHEAST-SYD-2

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

UK1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

UK2

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

WAW2

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-EAST-VA-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

US-WEST-OR-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

AP-SOUTH-MUM-1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

[AP-SOUTH-MUM][Public Cloud] - LocalZone / CEPH / Compute Instance / Managed Kubernetes Service incident notification

Started 18 Apr 2026 22:06:46 (7 hours ago), still ongoing

Major Incident

Identified

AP-SOUTH-MUM-1

AP-SOUTH-MUM

AP-SOUTH-MUM-1

LocalZones || AP-SOUTH-MUM

We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Public Cloud offering on the specific AP-SOUTH-MUM.

Here are some supplementary details :

Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Some customers are temporarily unable to access or use their compute instances in the AP-SOUTH-MUM-1 region, while actions such as restarting instances in the AP-SOUTH-MUM local zone are currently unavailable, and some Ceph volumes in the region are also impacted. Customers Impact : Some customers are temporarily unable to access or use their compute instances in the AP-SOUTH-MUM-1 region, are unable to perform actions such as restarting instances in the AP-SOUTH-MUM Local Zones, and are also unable to use their Ceph storage services. Root Cause : This incident is linked to : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk 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.

Identified: We have new information regarding the incident that affected your service(s).

Please find below an update on the situation: Update : Some customers using a Managed Kubernetes Service may also be impacted. The management service for instances, volumes, and the load balancer is temporarily unavailable. Customers are currently unable to perform certain actions such as starting, stopping, or restarting resources. Provisioning of these services in this region is also temporarily unavailable. We recommend that customers do not perform any actions on their currently running services. Ongoing Actions : The incident has been identified and our teams and 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.

18 Apr 2026 23:00:12 (6 hours ago)

Identified: We are currently experiencing an ongoing incident. We have determined the origin of the issue affecting our Public Cloud offering on the specific AP-SOUTH-MUM.

Here are some supplementary details :

Start time : 18/04/2026 17:06 UTC Impacted Service(s) : Some customers are temporarily unable to access or use their compute instances in the AP-SOUTH-MUM-1 region, while actions such as restarting instances in the AP-SOUTH-MUM local zone are currently unavailable, and some Ceph volumes in the region are also impacted. Customers Impact : Some customers are temporarily unable to access or use their compute instances in the AP-SOUTH-MUM-1 region, are unable to perform actions such as restarting instances in the AP-SOUTH-MUM Local Zones, and are also unable to use their Ceph storage services. Root Cause : This incident is linked to : https://network.status-ovhcloud.com/incidents/lycx4vgc89jk 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.

18 Apr 2026 22:06:46 (7 hours ago)

See all updates

EU-WEST-PAR-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-B

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-WEST-PAR-C

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

EU-SOUTH-MIL

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

RBX-A

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS1

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS3

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

BHS5

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud GRA

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud SBG

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud BHS

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud SGP

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud UK

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud DE

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud MUM

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud WAW

Sun 12

Mon 13

Tue 14

Wed 15

Thu 16

Fri 17

Sat 18

now

Public Cloud Status

Real-time updates of Public Cloud issues and outages

Public Cloud status is Minor Service Outage

GRA1

Public Cloud Compute - Instance || India

AP-SOUTH-MUM-1

DE1

Public Cloud Containers & Orchestration || Managed Kubernetes Service

AP-SOUTH-MUM

Public Cloud Containers & Orchestration || Managed Private Registry

You're checking on Public Cloud - but is your own site converting?

Active Incidents

Recently Resolved Incidents

Public Cloud Outage Survival Guide

Public Cloud Components

Public Cloud

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

GRA2

EU-SOUTH-MIL-A

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

GRA3

GRA5

GRA7

GRA9

GRA11

Public Cloud Compute - Instance || India

AP-SOUTH-MUM-1

Public Cloud Compute - Instance || LIM

DE1

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

Public Cloud Containers & Orchestration || Load Balancer

AP-SOUTH-MUM

BHS5

DE1

EU-WEST-PAR

GRA5

GRA7

GRA9

GRA11