Public Cloud Status: check for Public Cloud outages and issues

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud AI & Machine Learning || AI Dashboard

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud AI & Machine Learning || AI Deploy

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud AI & Machine Learning || AI Endpoint

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud AI & Machine Learning || AI Notebooks

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud AI & Machine Learning || AI Training

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Compute - Instance || BHS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Compute - Instance || ERI

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

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

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA2

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-A

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-B

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA4

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GRA4][Compute] - Instances incident notification

Started 14 Oct 2024 18:22:13 (8 months ago), still ongoing

Major Incident

Investigating

GRA4

An incident is in progress on our public cloud offer.

Please be aware that this is currently affecting the availability.

Here is detail for this incident : Start time : 14/10/2024 17:10 UTC Service impact : Some instances are temporarily unreachable. Ongoing actions : Investigating Our teams are fully mobilized and we will keep you informed of developments and the resolution of the incident.

We apologize for the inconvenience and thank you for your understanding.

EU-WEST-PAR-C

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Compute - Instance || GRA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GRA1][Compute] Instances unreachable

Started 14 Dec 2024 08:43:57 (6 months ago), still ongoing

Major Incident

Investigating

GRA1

An incident is in progress on our Compute-Instance offer.

Please be aware that this is currently affecting the Functionality.

Here is detail for this incident :

Start time : 14/12/2024 08:18 UTC Service impact : Some instances in the GRA1 region are unreachable. Ongoing actions : Investigating

Our teams are fully mobilized and we will keep you informed of developments and the resolution of the incident.

We apologize for the inconvenience and thank you for your understanding.

See all updates

GRA3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GRA11/GRA7/GRA5][Compute - Instance] - Instance incident notification

Started 30 May 2025 12:37:03 (2 days ago), resolved 30 May 2025 16:44:45 (2 days ago)

Major Incident

Resolved

GRA5

GRA7

GRA5

More...

We are currently experiencing an event affecting our Compute Instance offer in the specific regions GRA11 GRA7 GRA5. Start time : 30/05/2025 12:20 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 would like to inform you that the incident on our Compute Instance offer in the specific regions GRA11 GRA7 GRA5 has now been resolved.

Here is detail for this incident :

Start time : 30/05/2025 12:20 UTC End time : 30/05/2025 16:30 UTC Root cause : A service disruption occurred due to an unexpected infrastructure failure.

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

30 May 2025 16:44:45 (2 days ago)

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

Please find below an update on the situation: Update : The incident is still ongoing. We would like to assure you that we are doing our utmost to resolve this situation as quickly as possible.

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.

30 May 2025 14:44:58 (2 days ago)

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

30 May 2025 13:30:49 (2 days ago)

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

30 May 2025 13:28:05 (2 days ago)

Identified: We have determined the origin of the incident affecting our Compute - Instance offer on the specific region GRA11 GRA7 GRA5.

Here are some supplementary details :

Start time : 30/05/2025 12:20 UTC Impacted Service(s) : Some instances in the GRA11 GRA7 GRA5 regions are unreachable. Customers impact : Some customers cannot use their services in these Gra regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

30 May 2025 12:46:03 (2 days ago)

Investigating: We are currently experiencing an event affecting our Compute Instance offer in the specific regions GRA11 GRA7 GRA5. Start time : 30/05/2025 12:20 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.

30 May 2025 12:37:03 (2 days ago)

See all updates

GRA7

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GRA11/GRA7/GRA5][Compute - Instance] - Instance incident notification

Started 30 May 2025 12:37:03 (2 days ago), resolved 30 May 2025 16:44:45 (2 days ago)

Major Incident

Resolved

GRA5

GRA7

GRA5

More...

We are currently experiencing an event affecting our Compute Instance offer in the specific regions GRA11 GRA7 GRA5. Start time : 30/05/2025 12:20 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 would like to inform you that the incident on our Compute Instance offer in the specific regions GRA11 GRA7 GRA5 has now been resolved.

Here is detail for this incident :

Start time : 30/05/2025 12:20 UTC End time : 30/05/2025 16:30 UTC Root cause : A service disruption occurred due to an unexpected infrastructure failure.

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

30 May 2025 16:44:45 (2 days ago)

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

Please find below an update on the situation: Update : The incident is still ongoing. We would like to assure you that we are doing our utmost to resolve this situation as quickly as possible.

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.

30 May 2025 14:44:58 (2 days ago)

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

30 May 2025 13:30:49 (2 days ago)

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

30 May 2025 13:28:05 (2 days ago)

Identified: We have determined the origin of the incident affecting our Compute - Instance offer on the specific region GRA11 GRA7 GRA5.

Here are some supplementary details :

Start time : 30/05/2025 12:20 UTC Impacted Service(s) : Some instances in the GRA11 GRA7 GRA5 regions are unreachable. Customers impact : Some customers cannot use their services in these Gra regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

30 May 2025 12:46:03 (2 days ago)

Investigating: We are currently experiencing an event affecting our Compute Instance offer in the specific regions GRA11 GRA7 GRA5. Start time : 30/05/2025 12:20 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.

30 May 2025 12:37:03 (2 days ago)

See all updates

GRA9

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA11

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GRA11/GRA7/GRA5][Compute - Instance] - Instance incident notification

Started 30 May 2025 12:37:03 (2 days ago), resolved 30 May 2025 16:44:45 (2 days ago)

Major Incident

Resolved

GRA5

GRA7

GRA5

More...

We are currently experiencing an event affecting our Compute Instance offer in the specific regions GRA11 GRA7 GRA5. Start time : 30/05/2025 12:20 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 would like to inform you that the incident on our Compute Instance offer in the specific regions GRA11 GRA7 GRA5 has now been resolved.

Here is detail for this incident :

Start time : 30/05/2025 12:20 UTC End time : 30/05/2025 16:30 UTC Root cause : A service disruption occurred due to an unexpected infrastructure failure.

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

30 May 2025 16:44:45 (2 days ago)

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

Please find below an update on the situation: Update : The incident is still ongoing. We would like to assure you that we are doing our utmost to resolve this situation as quickly as possible.

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.

30 May 2025 14:44:58 (2 days ago)

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

30 May 2025 13:30:49 (2 days ago)

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

30 May 2025 13:28:05 (2 days ago)

Identified: We have determined the origin of the incident affecting our Compute - Instance offer on the specific region GRA11 GRA7 GRA5.

Here are some supplementary details :

Start time : 30/05/2025 12:20 UTC Impacted Service(s) : Some instances in the GRA11 GRA7 GRA5 regions are unreachable. Customers impact : Some customers cannot use their services in these Gra regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

30 May 2025 12:46:03 (2 days ago)

Investigating: We are currently experiencing an event affecting our Compute Instance offer in the specific regions GRA11 GRA7 GRA5. Start time : 30/05/2025 12:20 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.

30 May 2025 12:37:03 (2 days ago)

See all updates

Public Cloud Compute - Instance || India

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

AP-SOUTH-MUM-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Compute - Instance || LIM

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Compute - Instance || RBX

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

RBX-A

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Compute - Instance || SGP

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SGP1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SGP2

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Compute - Instance || SBG

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG7

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Compute - Instance || SYD

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

AP-SOUTHEAST-SYD-2

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Compute - Instance || USA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-EAST-VA-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-WEST-OR-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Compute - Instance || WAW

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Containers & Orchestration || Load Balancer

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GRA11/GRA7/GRA5][Compute - Instance] - Instance incident notification

Started 30 May 2025 12:37:03 (2 days ago), resolved 30 May 2025 16:44:45 (2 days ago)

Major Incident

Resolved

GRA5

GRA7

GRA5

More...

We are currently experiencing an event affecting our Compute Instance offer in the specific regions GRA11 GRA7 GRA5. Start time : 30/05/2025 12:20 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 would like to inform you that the incident on our Compute Instance offer in the specific regions GRA11 GRA7 GRA5 has now been resolved.

Here is detail for this incident :

Start time : 30/05/2025 12:20 UTC End time : 30/05/2025 16:30 UTC Root cause : A service disruption occurred due to an unexpected infrastructure failure.

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

30 May 2025 16:44:45 (2 days ago)

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

Please find below an update on the situation: Update : The incident is still ongoing. We would like to assure you that we are doing our utmost to resolve this situation as quickly as possible.

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.

30 May 2025 14:44:58 (2 days ago)

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

30 May 2025 13:30:49 (2 days ago)

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

30 May 2025 13:28:05 (2 days ago)

Identified: We have determined the origin of the incident affecting our Compute - Instance offer on the specific region GRA11 GRA7 GRA5.

Here are some supplementary details :

Start time : 30/05/2025 12:20 UTC Impacted Service(s) : Some instances in the GRA11 GRA7 GRA5 regions are unreachable. Customers impact : Some customers cannot use their services in these Gra regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

30 May 2025 12:46:03 (2 days ago)

Investigating: We are currently experiencing an event affecting our Compute Instance offer in the specific regions GRA11 GRA7 GRA5. Start time : 30/05/2025 12:20 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.

30 May 2025 12:37:03 (2 days ago)

See all updates

GRA7

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GRA11/GRA7/GRA5][Compute - Instance] - Instance incident notification

Started 30 May 2025 12:37:03 (2 days ago), resolved 30 May 2025 16:44:45 (2 days ago)

Major Incident

Resolved

GRA5

GRA7

GRA5

More...

We are currently experiencing an event affecting our Compute Instance offer in the specific regions GRA11 GRA7 GRA5. Start time : 30/05/2025 12:20 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 would like to inform you that the incident on our Compute Instance offer in the specific regions GRA11 GRA7 GRA5 has now been resolved.

Here is detail for this incident :

Start time : 30/05/2025 12:20 UTC End time : 30/05/2025 16:30 UTC Root cause : A service disruption occurred due to an unexpected infrastructure failure.

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

30 May 2025 16:44:45 (2 days ago)

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

Please find below an update on the situation: Update : The incident is still ongoing. We would like to assure you that we are doing our utmost to resolve this situation as quickly as possible.

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.

30 May 2025 14:44:58 (2 days ago)

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

30 May 2025 13:30:49 (2 days ago)

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

30 May 2025 13:28:05 (2 days ago)

Identified: We have determined the origin of the incident affecting our Compute - Instance offer on the specific region GRA11 GRA7 GRA5.

Here are some supplementary details :

Start time : 30/05/2025 12:20 UTC Impacted Service(s) : Some instances in the GRA11 GRA7 GRA5 regions are unreachable. Customers impact : Some customers cannot use their services in these Gra regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

30 May 2025 12:46:03 (2 days ago)

Investigating: We are currently experiencing an event affecting our Compute Instance offer in the specific regions GRA11 GRA7 GRA5. Start time : 30/05/2025 12:20 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.

30 May 2025 12:37:03 (2 days ago)

See all updates

GRA9

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA11

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GRA11/GRA7/GRA5][Compute - Instance] - Instance incident notification

Started 30 May 2025 12:37:03 (2 days ago), resolved 30 May 2025 16:44:45 (2 days ago)

Major Incident

Resolved

GRA5

GRA7

GRA5

More...

We are currently experiencing an event affecting our Compute Instance offer in the specific regions GRA11 GRA7 GRA5. Start time : 30/05/2025 12:20 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 would like to inform you that the incident on our Compute Instance offer in the specific regions GRA11 GRA7 GRA5 has now been resolved.

Here is detail for this incident :

Start time : 30/05/2025 12:20 UTC End time : 30/05/2025 16:30 UTC Root cause : A service disruption occurred due to an unexpected infrastructure failure.

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

30 May 2025 16:44:45 (2 days ago)

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

Please find below an update on the situation: Update : The incident is still ongoing. We would like to assure you that we are doing our utmost to resolve this situation as quickly as possible.

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.

30 May 2025 14:44:58 (2 days ago)

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

30 May 2025 13:30:49 (2 days ago)

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

30 May 2025 13:28:05 (2 days ago)

Identified: We have determined the origin of the incident affecting our Compute - Instance offer on the specific region GRA11 GRA7 GRA5.

Here are some supplementary details :

Start time : 30/05/2025 12:20 UTC Impacted Service(s) : Some instances in the GRA11 GRA7 GRA5 regions are unreachable. Customers impact : Some customers cannot use their services in these Gra regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

30 May 2025 12:46:03 (2 days ago)

Investigating: We are currently experiencing an event affecting our Compute Instance offer in the specific regions GRA11 GRA7 GRA5. Start time : 30/05/2025 12:20 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.

30 May 2025 12:37:03 (2 days ago)

See all updates

SBG5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SGP1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-EAST-VA-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-WEST-OR-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Containers & Orchestration || Managed Kubernetes Service

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GRA11/GRA7/GRA5][Compute - Instance] - Instance incident notification

Started 30 May 2025 12:37:03 (2 days ago), resolved 30 May 2025 16:44:45 (2 days ago)

Major Incident

Resolved

GRA5

GRA7

GRA5

More...

We are currently experiencing an event affecting our Compute Instance offer in the specific regions GRA11 GRA7 GRA5. Start time : 30/05/2025 12:20 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 would like to inform you that the incident on our Compute Instance offer in the specific regions GRA11 GRA7 GRA5 has now been resolved.

Here is detail for this incident :

Start time : 30/05/2025 12:20 UTC End time : 30/05/2025 16:30 UTC Root cause : A service disruption occurred due to an unexpected infrastructure failure.

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

30 May 2025 16:44:45 (2 days ago)

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

Please find below an update on the situation: Update : The incident is still ongoing. We would like to assure you that we are doing our utmost to resolve this situation as quickly as possible.

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.

30 May 2025 14:44:58 (2 days ago)

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

30 May 2025 13:30:49 (2 days ago)

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

30 May 2025 13:28:05 (2 days ago)

Identified: We have determined the origin of the incident affecting our Compute - Instance offer on the specific region GRA11 GRA7 GRA5.

Here are some supplementary details :

Start time : 30/05/2025 12:20 UTC Impacted Service(s) : Some instances in the GRA11 GRA7 GRA5 regions are unreachable. Customers impact : Some customers cannot use their services in these Gra regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

30 May 2025 12:46:03 (2 days ago)

Investigating: We are currently experiencing an event affecting our Compute Instance offer in the specific regions GRA11 GRA7 GRA5. Start time : 30/05/2025 12:20 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.

30 May 2025 12:37:03 (2 days ago)

See all updates

GRA7

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GRA11/GRA7/GRA5][Compute - Instance] - Instance incident notification

Started 30 May 2025 12:37:03 (2 days ago), resolved 30 May 2025 16:44:45 (2 days ago)

Major Incident

Resolved

GRA5

GRA7

GRA5

More...

We are currently experiencing an event affecting our Compute Instance offer in the specific regions GRA11 GRA7 GRA5. Start time : 30/05/2025 12:20 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 would like to inform you that the incident on our Compute Instance offer in the specific regions GRA11 GRA7 GRA5 has now been resolved.

Here is detail for this incident :

Start time : 30/05/2025 12:20 UTC End time : 30/05/2025 16:30 UTC Root cause : A service disruption occurred due to an unexpected infrastructure failure.

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

30 May 2025 16:44:45 (2 days ago)

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

Please find below an update on the situation: Update : The incident is still ongoing. We would like to assure you that we are doing our utmost to resolve this situation as quickly as possible.

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.

30 May 2025 14:44:58 (2 days ago)

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

30 May 2025 13:30:49 (2 days ago)

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

30 May 2025 13:28:05 (2 days ago)

Identified: We have determined the origin of the incident affecting our Compute - Instance offer on the specific region GRA11 GRA7 GRA5.

Here are some supplementary details :

Start time : 30/05/2025 12:20 UTC Impacted Service(s) : Some instances in the GRA11 GRA7 GRA5 regions are unreachable. Customers impact : Some customers cannot use their services in these Gra regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

30 May 2025 12:46:03 (2 days ago)

Investigating: We are currently experiencing an event affecting our Compute Instance offer in the specific regions GRA11 GRA7 GRA5. Start time : 30/05/2025 12:20 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.

30 May 2025 12:37:03 (2 days ago)

See all updates

GRA9

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA11

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GRA11/GRA7/GRA5][Compute - Instance] - Instance incident notification

Started 30 May 2025 12:37:03 (2 days ago), resolved 30 May 2025 16:44:45 (2 days ago)

Major Incident

Resolved

GRA5

GRA7

GRA5

More...

We are currently experiencing an event affecting our Compute Instance offer in the specific regions GRA11 GRA7 GRA5. Start time : 30/05/2025 12:20 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 would like to inform you that the incident on our Compute Instance offer in the specific regions GRA11 GRA7 GRA5 has now been resolved.

Here is detail for this incident :

Start time : 30/05/2025 12:20 UTC End time : 30/05/2025 16:30 UTC Root cause : A service disruption occurred due to an unexpected infrastructure failure.

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

30 May 2025 16:44:45 (2 days ago)

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

Please find below an update on the situation: Update : The incident is still ongoing. We would like to assure you that we are doing our utmost to resolve this situation as quickly as possible.

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.

30 May 2025 14:44:58 (2 days ago)

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

30 May 2025 13:30:49 (2 days ago)

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

30 May 2025 13:28:05 (2 days ago)

Identified: We have determined the origin of the incident affecting our Compute - Instance offer on the specific region GRA11 GRA7 GRA5.

Here are some supplementary details :

Start time : 30/05/2025 12:20 UTC Impacted Service(s) : Some instances in the GRA11 GRA7 GRA5 regions are unreachable. Customers impact : Some customers cannot use their services in these Gra regions. Root Cause : A service disruption occurred due to an unexpected infrastructure failure. Ongoing Actions : The incident has been identified and our teams are mobilised to restore service as quickly as possible.

We will keep you updated on the progress and resolution.

We apologize for any inconvenience caused and appreciate your understanding.

30 May 2025 12:46:03 (2 days ago)

Investigating: We are currently experiencing an event affecting our Compute Instance offer in the specific regions GRA11 GRA7 GRA5. Start time : 30/05/2025 12:20 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.

30 May 2025 12:37:03 (2 days ago)

See all updates

SBG5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SGP1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-EAST-VA-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-WEST-OR-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Containers & Orchestration || Managed Private Registry

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

VA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Containers & Orchestration || Managed Rancher Service

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Containers & Orchestration || Workflow Management

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA7

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA9

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA11

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG7

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SGP1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SGP2

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD2

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW2

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-EAST-VA-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-WEST-OR-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Databases || Cassandra

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

PAR

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Databases || M3 Aggregator

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

PAR

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Databases || M3DB

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

PAR

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Databases || MongoDB

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

PAR

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Databases || MySQL

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

PAR

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Databases || PostgreSQL

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

PAR

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SGP

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Databases || Caching

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

PAR

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Data & Analytics || Data Processing

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Data & Analytics || Data Platform

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Data & Analytics || Grafana

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

PAR

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Data & Analytics || Kafka

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

PAR

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Data & Analytics || Kafka Connect

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

PAR

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Data & Analytics || Kafka MirrorMaker

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

PAR

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Data & Analytics || Logs Data Platform

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Data & Analytics || OpenSearch

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

PAR

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

MAD

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Identity, Security & Operations || Key Management Service

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

RBX

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Network || FailoverIP

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

YYZ

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud LocalZones || AF-NORTH

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

AF-NORTH-LZ-RBA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud LocalZones || EU-CENTRAL

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-CENTRAL-LZ-PRG

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud LocalZones || EU-NORTH

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-NORTH-LZ-OSL

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-NORTH-LZ-STO

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud LocalZones || EU-SOUTH

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-SOUTH-LZ-LIS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-SOUTH-LZ-MAD

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-SOUTH-LZ-MIL

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud LocalZones || EU-WEST

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-LZ-AMS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-LZ-BRU

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-LZ-DLN

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-LZ-LUX

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-LZ-MNC

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-LZ-MRS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Network || Load Balancer

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-LZ-VIE

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-LZ-ZRH

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud LocalZones || US-EAST

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-EAST-LZ-ATL

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-EAST-LZ-BOS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-EAST-LZ-CHI

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-EAST-LZ-DAL

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-EAST-LZ-MIA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-EAST-LZ-NYC

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud LocalZones || US-WEST

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-WEST-LZ-DEN

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-WEST-LZ-LAX

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-WEST-LZ-PAO

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-WEST-LZ-SEA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Management || Horizon

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Network || Floating IP

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA7

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA9

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA11

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG7

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SGP1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-EAST-VA-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-WEST-OR-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-A

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-B

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-C

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

AP-SOUTH-MUM-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Network || Gateway

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA7

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA9

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GRA9][Network] - Routers

Started 28 May 2025 09:47:30 (4 days ago), resolved 28 May 2025 13:02:40 (4 days ago)

Minor Incident

Resolved

GRA9

We are currently experiencing an event affecting our Network Gateway offer in the GRA9 region.

Start time : 28/05/2025 08:00 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.

See all updates

GRA11

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG7

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SGP1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-EAST-VA-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-WEST-OR-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

AP-SOUTH-MUM-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-A

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-B

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-C

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

AP-SOUTH-MUM-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Network || Load Balancer

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA7

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA9

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA11

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG7

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SGP1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-EAST-VA-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-WEST-OR-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-A

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-B

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-C

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

AP-SOUTH-MUM-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Network || Private network (vRack)

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA7

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA9

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA11

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

RBX-A

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG7

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SGP1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SGP2

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-EAST-VA-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-WEST-OR-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-A

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-B

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-C

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

AP-SOUTH-MUM-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Network || Public network

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA7

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA9

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA11

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

RBX-A

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG7

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SGP1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SGP2

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-EAST-VA-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-WEST-OR-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-A

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-B

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-C

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

AP-SOUTH-MUM-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Storage || Block storage

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud UK

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA6

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GRA6][Storage] - Block Storage Notifcation Incident

Started 19 Dec 2024 14:59:18 (5 months ago), still ongoing

Major Incident

Investigating

GRA6

An incident is in progress on our Block Storage offer.

Please be aware that this is currently affecting the Availability.

Here is detail for this incident :

Start time : 19/12/2024 14:40 UTC Service impact : Customers cannot access the Block Storage service. Ongoing actions : Investigating

Our teams are fully mobilized and we will keep you informed of developments and the resolution of the incident.

We apologize for the inconvenience and thank you for your understanding.

GRA7

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA9

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA11

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG7

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SGP1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-EAST-VA-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-WEST-OR-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

AP-SOUTH-MUM-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-A

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-B

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-C

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Storage || Cloud Archive

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SGP

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-EAST-VA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-WEST-OR

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Storage || Cold Archive

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

RBX-ARCHIVE

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[RBX][Storage] - Object Storage S3 Standard/High Perf/Cold Archive

Started 1 Jun 2025 00:43:11 (8 hours ago), resolved 1 Jun 2025 00:43:11 (8 hours ago)

Incident without Impact

Resolved

RBX-ARCHIVE

We would like to inform you that an incident on Object Storage S3 Standard/High Perf/Cold Archive happened and has now been resolved.

Here is detail for this incident : Start time : 31/05/2025 22:35 UTC End time : 01/06/2025 00:30 UTC Service impact: Some servers were unreachable. Customers impact : Customers may have experienced 503 errors when they wanted to use their services. Root Cause : This incident was caused by a malfunction on some hardwares.

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

[RBX][Storage] - Object Storage S3 Standard/High Perf/Cold Archive

Started 1 Jun 2025 00:01:28 (8 hours ago), resolved 1 Jun 2025 00:01:28 (8 hours ago)

Incident without Impact

Resolved

RBX-ARCHIVE

We would like to inform you that an incident on Object Storage S3 Standard/High Perf/Cold Archive happened and has now been resolved.

Here is detail for this incident : Start time : 31/05/2025 22:35 UTC End time : 31/05/2025 23:00 UTC Service impact: Some servers were unreachable. Customers impact : Customers may have experienced 503 errors when they wanted to use their services. Root Cause : This incident was caused by a malfunction on some hardwares.

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

Public Cloud Storage || Instance Backup

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA7

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA9

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA11

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG7

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SGP1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-EAST-VA-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-WEST-OR-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Compute - Instance || 3AZ

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

PAR

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

AP-SOUTH-MUM-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-A

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-B

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-C

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Storage || Object storage

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GLOBAL][Object Storage] - Amazon S3 SDK compatibility inconsistencies with Object Storage Standard/High Performance

Started 23 Jan 2025 14:51:30 (4 months ago), still ongoing

Major Incident

Identified

BHS

GRA

DE

RBX

SBG

More...

We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

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

Please find below an update on the situation: Update : We have completed our development and the fix is currently being tested in our Q&A process. Testing process is especially long to prevent any regression while fixing the issue. 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.

10 Apr 2025 08:46:04 (2 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 teams are still working on fix.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

3 Mar 2025 12:37:50 (3 months ago)

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

6 Feb 2025 19:10:34 (4 months ago)

Identified: We have determined the origin of the incident affecting our Object Storage S3 offer.

Here are some supplementary details : Start time : 01/01/2025 00:00 UTC Impacted Service(s) : Object Storage S3 Customers Impact : Requests to our Object Storage endpoint could return the error "InvalidArgument", on different Object operations. Root Cause : Following a recent AWS SDK upgrade, this issue is due to a new checksum enforcement in those SDKs. Unsupported headers are:

x-amz-content-sha256 with value STREAMING-UNSIGNED-PAYLOAD-TRAILER
x-amz-sdk-checksum-algorithm with value CRC32 Workaround A workaround is to downgrade the version, until the feature is implemented on our side. Max supported versions:
boto3 1.35.99
legacy aws cli 1.36.40
aws cli 2.22.35
aws-sdk-go 1.72.3
aws-sdk-java 2.29.52
aws-sdk-js-v3 3.726.1
aws-sdk-net 3.7.962.0
aws-sdk-php 3.336.15
aws-sdk-ruby 1.177.0 Ongoing Actions : The incident has been identified and our teams are mobilized 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.

23 Jan 2025 15:11:08 (4 months ago)

Investigating: We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

23 Jan 2025 14:51:30 (4 months ago)

See all updates

[GLOBAL][Storage] - Object storage incident notification

Started 25 Apr 2025 08:47:08 (1 month ago), resolved 31 May 2025 00:50:52 (1 day ago)

Minor Incident

Resolved

BHS

GRA

DE

RBX

SBG

More...

We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

Resolved: We would like to inform you that the incident on our Object Storage offer, have been resolved Start Time : 25/03/2025 09:00 UTC End Time : 31/05/2025 00:45 UTC Root cause : This incident is caused by a software issue.

We thank you for your understanding and patience throughout this incident

31 May 2025 00:50:52 (1 day ago)

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

Please find below an update on the situation:
Update : Treatments are still ongoing and have already been completed for some customers. Refunds are also being processed. However, treatments vary in length depending on the customer. Please be assured that refunds will be issued upon completion of treatment, with a start date of March 25, 2025.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.

21 May 2025 10:06:07 (11 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 customers are still experiencing a discrepancy between the actual size of their bucket and the size displayed in the Manager, due to undeleted parts that should have been removed. To address this issue, affected customers will receive an informational email and a credit note on their invoice, compensating for excess consumption, with credits applied as of April 18, 2025. Ongoing Actions : The incident has been identified and our technical teams are working on the storage size of the impacted customers between those 2 dates.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

14 May 2025 12:32:18 (18 days ago)

Identified: We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

25 Apr 2025 08:47:09 (1 month ago)

See all updates

GRA

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GLOBAL][Object Storage] - Amazon S3 SDK compatibility inconsistencies with Object Storage Standard/High Performance

Started 23 Jan 2025 14:51:30 (4 months ago), still ongoing

Major Incident

Identified

BHS

GRA

DE

RBX

SBG

More...

We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

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

Please find below an update on the situation: Update : We have completed our development and the fix is currently being tested in our Q&A process. Testing process is especially long to prevent any regression while fixing the issue. 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.

10 Apr 2025 08:46:04 (2 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 teams are still working on fix.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

3 Mar 2025 12:37:50 (3 months ago)

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

6 Feb 2025 19:10:34 (4 months ago)

Identified: We have determined the origin of the incident affecting our Object Storage S3 offer.

Here are some supplementary details : Start time : 01/01/2025 00:00 UTC Impacted Service(s) : Object Storage S3 Customers Impact : Requests to our Object Storage endpoint could return the error "InvalidArgument", on different Object operations. Root Cause : Following a recent AWS SDK upgrade, this issue is due to a new checksum enforcement in those SDKs. Unsupported headers are:

x-amz-content-sha256 with value STREAMING-UNSIGNED-PAYLOAD-TRAILER
x-amz-sdk-checksum-algorithm with value CRC32 Workaround A workaround is to downgrade the version, until the feature is implemented on our side. Max supported versions:
boto3 1.35.99
legacy aws cli 1.36.40
aws cli 2.22.35
aws-sdk-go 1.72.3
aws-sdk-java 2.29.52
aws-sdk-js-v3 3.726.1
aws-sdk-net 3.7.962.0
aws-sdk-php 3.336.15
aws-sdk-ruby 1.177.0 Ongoing Actions : The incident has been identified and our teams are mobilized 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.

23 Jan 2025 15:11:08 (4 months ago)

Investigating: We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

23 Jan 2025 14:51:30 (4 months ago)

See all updates

[GLOBAL][Storage] - Object storage incident notification

Started 25 Apr 2025 08:47:08 (1 month ago), resolved 31 May 2025 00:50:52 (1 day ago)

Minor Incident

Resolved

BHS

GRA

DE

RBX

SBG

More...

We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

Resolved: We would like to inform you that the incident on our Object Storage offer, have been resolved Start Time : 25/03/2025 09:00 UTC End Time : 31/05/2025 00:45 UTC Root cause : This incident is caused by a software issue.

We thank you for your understanding and patience throughout this incident

31 May 2025 00:50:52 (1 day ago)

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

Please find below an update on the situation:
Update : Treatments are still ongoing and have already been completed for some customers. Refunds are also being processed. However, treatments vary in length depending on the customer. Please be assured that refunds will be issued upon completion of treatment, with a start date of March 25, 2025.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.

21 May 2025 10:06:07 (11 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 customers are still experiencing a discrepancy between the actual size of their bucket and the size displayed in the Manager, due to undeleted parts that should have been removed. To address this issue, affected customers will receive an informational email and a credit note on their invoice, compensating for excess consumption, with credits applied as of April 18, 2025. Ongoing Actions : The incident has been identified and our technical teams are working on the storage size of the impacted customers between those 2 dates.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

14 May 2025 12:32:18 (18 days ago)

Identified: We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

25 Apr 2025 08:47:09 (1 month ago)

See all updates

[EU][Storage] - Object Storage S3 Standard/High Perf

Started 27 May 2025 20:31:00 (4 days ago), resolved 27 May 2025 21:31:20 (4 days ago)

Major Incident

Resolved

GRA

DE

RBX

SBG

UK

We are currently experiencing an incident affecting our Object Storage offer. Start time : 27/05/2025 20:00 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.

See all updates

DE

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GLOBAL][Object Storage] - Amazon S3 SDK compatibility inconsistencies with Object Storage Standard/High Performance

Started 23 Jan 2025 14:51:30 (4 months ago), still ongoing

Major Incident

Identified

BHS

GRA

DE

RBX

SBG

More...

We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

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

Please find below an update on the situation: Update : We have completed our development and the fix is currently being tested in our Q&A process. Testing process is especially long to prevent any regression while fixing the issue. 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.

10 Apr 2025 08:46:04 (2 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 teams are still working on fix.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

3 Mar 2025 12:37:50 (3 months ago)

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

6 Feb 2025 19:10:34 (4 months ago)

Identified: We have determined the origin of the incident affecting our Object Storage S3 offer.

Here are some supplementary details : Start time : 01/01/2025 00:00 UTC Impacted Service(s) : Object Storage S3 Customers Impact : Requests to our Object Storage endpoint could return the error "InvalidArgument", on different Object operations. Root Cause : Following a recent AWS SDK upgrade, this issue is due to a new checksum enforcement in those SDKs. Unsupported headers are:

x-amz-content-sha256 with value STREAMING-UNSIGNED-PAYLOAD-TRAILER
x-amz-sdk-checksum-algorithm with value CRC32 Workaround A workaround is to downgrade the version, until the feature is implemented on our side. Max supported versions:
boto3 1.35.99
legacy aws cli 1.36.40
aws cli 2.22.35
aws-sdk-go 1.72.3
aws-sdk-java 2.29.52
aws-sdk-js-v3 3.726.1
aws-sdk-net 3.7.962.0
aws-sdk-php 3.336.15
aws-sdk-ruby 1.177.0 Ongoing Actions : The incident has been identified and our teams are mobilized 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.

23 Jan 2025 15:11:08 (4 months ago)

Investigating: We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

23 Jan 2025 14:51:30 (4 months ago)

See all updates

[GLOBAL][Storage] - Object storage incident notification

Started 25 Apr 2025 08:47:08 (1 month ago), resolved 31 May 2025 00:50:52 (1 day ago)

Minor Incident

Resolved

BHS

GRA

DE

RBX

SBG

More...

We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

Resolved: We would like to inform you that the incident on our Object Storage offer, have been resolved Start Time : 25/03/2025 09:00 UTC End Time : 31/05/2025 00:45 UTC Root cause : This incident is caused by a software issue.

We thank you for your understanding and patience throughout this incident

31 May 2025 00:50:52 (1 day ago)

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

Please find below an update on the situation:
Update : Treatments are still ongoing and have already been completed for some customers. Refunds are also being processed. However, treatments vary in length depending on the customer. Please be assured that refunds will be issued upon completion of treatment, with a start date of March 25, 2025.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.

21 May 2025 10:06:07 (11 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 customers are still experiencing a discrepancy between the actual size of their bucket and the size displayed in the Manager, due to undeleted parts that should have been removed. To address this issue, affected customers will receive an informational email and a credit note on their invoice, compensating for excess consumption, with credits applied as of April 18, 2025. Ongoing Actions : The incident has been identified and our technical teams are working on the storage size of the impacted customers between those 2 dates.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

14 May 2025 12:32:18 (18 days ago)

Identified: We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

25 Apr 2025 08:47:09 (1 month ago)

See all updates

[EU][Storage] - Object Storage S3 Standard/High Perf

Started 27 May 2025 20:31:00 (4 days ago), resolved 27 May 2025 21:31:20 (4 days ago)

Major Incident

Resolved

GRA

DE

RBX

SBG

UK

We are currently experiencing an incident affecting our Object Storage offer. Start time : 27/05/2025 20:00 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.

See all updates

RBX

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GLOBAL][Object Storage] - Amazon S3 SDK compatibility inconsistencies with Object Storage Standard/High Performance

Started 23 Jan 2025 14:51:30 (4 months ago), still ongoing

Major Incident

Identified

BHS

GRA

DE

RBX

SBG

More...

We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

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

Please find below an update on the situation: Update : We have completed our development and the fix is currently being tested in our Q&A process. Testing process is especially long to prevent any regression while fixing the issue. 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.

10 Apr 2025 08:46:04 (2 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 teams are still working on fix.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

3 Mar 2025 12:37:50 (3 months ago)

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

6 Feb 2025 19:10:34 (4 months ago)

Identified: We have determined the origin of the incident affecting our Object Storage S3 offer.

Here are some supplementary details : Start time : 01/01/2025 00:00 UTC Impacted Service(s) : Object Storage S3 Customers Impact : Requests to our Object Storage endpoint could return the error "InvalidArgument", on different Object operations. Root Cause : Following a recent AWS SDK upgrade, this issue is due to a new checksum enforcement in those SDKs. Unsupported headers are:

x-amz-content-sha256 with value STREAMING-UNSIGNED-PAYLOAD-TRAILER
x-amz-sdk-checksum-algorithm with value CRC32 Workaround A workaround is to downgrade the version, until the feature is implemented on our side. Max supported versions:
boto3 1.35.99
legacy aws cli 1.36.40
aws cli 2.22.35
aws-sdk-go 1.72.3
aws-sdk-java 2.29.52
aws-sdk-js-v3 3.726.1
aws-sdk-net 3.7.962.0
aws-sdk-php 3.336.15
aws-sdk-ruby 1.177.0 Ongoing Actions : The incident has been identified and our teams are mobilized 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.

23 Jan 2025 15:11:08 (4 months ago)

Investigating: We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

23 Jan 2025 14:51:30 (4 months ago)

See all updates

[GLOBAL][Storage] - Object storage incident notification

Started 25 Apr 2025 08:47:08 (1 month ago), resolved 31 May 2025 00:50:52 (1 day ago)

Minor Incident

Resolved

BHS

GRA

DE

RBX

SBG

More...

We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

Resolved: We would like to inform you that the incident on our Object Storage offer, have been resolved Start Time : 25/03/2025 09:00 UTC End Time : 31/05/2025 00:45 UTC Root cause : This incident is caused by a software issue.

We thank you for your understanding and patience throughout this incident

31 May 2025 00:50:52 (1 day ago)

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

Please find below an update on the situation:
Update : Treatments are still ongoing and have already been completed for some customers. Refunds are also being processed. However, treatments vary in length depending on the customer. Please be assured that refunds will be issued upon completion of treatment, with a start date of March 25, 2025.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.

21 May 2025 10:06:07 (11 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 customers are still experiencing a discrepancy between the actual size of their bucket and the size displayed in the Manager, due to undeleted parts that should have been removed. To address this issue, affected customers will receive an informational email and a credit note on their invoice, compensating for excess consumption, with credits applied as of April 18, 2025. Ongoing Actions : The incident has been identified and our technical teams are working on the storage size of the impacted customers between those 2 dates.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

14 May 2025 12:32:18 (18 days ago)

Identified: We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

25 Apr 2025 08:47:09 (1 month ago)

See all updates

[EU][Storage] - Object Storage S3 Standard/High Perf

Started 27 May 2025 20:31:00 (4 days ago), resolved 27 May 2025 21:31:20 (4 days ago)

Major Incident

Resolved

GRA

DE

RBX

SBG

UK

We are currently experiencing an incident affecting our Object Storage offer. Start time : 27/05/2025 20:00 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.

See all updates

SBG

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GLOBAL][Object Storage] - Amazon S3 SDK compatibility inconsistencies with Object Storage Standard/High Performance

Started 23 Jan 2025 14:51:30 (4 months ago), still ongoing

Major Incident

Identified

BHS

GRA

DE

RBX

SBG

More...

We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

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

Please find below an update on the situation: Update : We have completed our development and the fix is currently being tested in our Q&A process. Testing process is especially long to prevent any regression while fixing the issue. 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.

10 Apr 2025 08:46:04 (2 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 teams are still working on fix.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

3 Mar 2025 12:37:50 (3 months ago)

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

6 Feb 2025 19:10:34 (4 months ago)

Identified: We have determined the origin of the incident affecting our Object Storage S3 offer.

Here are some supplementary details : Start time : 01/01/2025 00:00 UTC Impacted Service(s) : Object Storage S3 Customers Impact : Requests to our Object Storage endpoint could return the error "InvalidArgument", on different Object operations. Root Cause : Following a recent AWS SDK upgrade, this issue is due to a new checksum enforcement in those SDKs. Unsupported headers are:

x-amz-content-sha256 with value STREAMING-UNSIGNED-PAYLOAD-TRAILER
x-amz-sdk-checksum-algorithm with value CRC32 Workaround A workaround is to downgrade the version, until the feature is implemented on our side. Max supported versions:
boto3 1.35.99
legacy aws cli 1.36.40
aws cli 2.22.35
aws-sdk-go 1.72.3
aws-sdk-java 2.29.52
aws-sdk-js-v3 3.726.1
aws-sdk-net 3.7.962.0
aws-sdk-php 3.336.15
aws-sdk-ruby 1.177.0 Ongoing Actions : The incident has been identified and our teams are mobilized 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.

23 Jan 2025 15:11:08 (4 months ago)

Investigating: We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

23 Jan 2025 14:51:30 (4 months ago)

See all updates

[GLOBAL][Storage] - Object storage incident notification

Started 25 Apr 2025 08:47:08 (1 month ago), resolved 31 May 2025 00:50:52 (1 day ago)

Minor Incident

Resolved

BHS

GRA

DE

RBX

SBG

More...

We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

Resolved: We would like to inform you that the incident on our Object Storage offer, have been resolved Start Time : 25/03/2025 09:00 UTC End Time : 31/05/2025 00:45 UTC Root cause : This incident is caused by a software issue.

We thank you for your understanding and patience throughout this incident

31 May 2025 00:50:52 (1 day ago)

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

Please find below an update on the situation:
Update : Treatments are still ongoing and have already been completed for some customers. Refunds are also being processed. However, treatments vary in length depending on the customer. Please be assured that refunds will be issued upon completion of treatment, with a start date of March 25, 2025.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.

21 May 2025 10:06:07 (11 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 customers are still experiencing a discrepancy between the actual size of their bucket and the size displayed in the Manager, due to undeleted parts that should have been removed. To address this issue, affected customers will receive an informational email and a credit note on their invoice, compensating for excess consumption, with credits applied as of April 18, 2025. Ongoing Actions : The incident has been identified and our technical teams are working on the storage size of the impacted customers between those 2 dates.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

14 May 2025 12:32:18 (18 days ago)

Identified: We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

25 Apr 2025 08:47:09 (1 month ago)

See all updates

[EU][Storage] - Object Storage S3 Standard/High Perf

Started 27 May 2025 20:31:00 (4 days ago), resolved 27 May 2025 21:31:20 (4 days ago)

Major Incident

Resolved

GRA

DE

RBX

SBG

UK

We are currently experiencing an incident affecting our Object Storage offer. Start time : 27/05/2025 20:00 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.

See all updates

SGP

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GLOBAL][Object Storage] - Amazon S3 SDK compatibility inconsistencies with Object Storage Standard/High Performance

Started 23 Jan 2025 14:51:30 (4 months ago), still ongoing

Major Incident

Identified

BHS

GRA

DE

RBX

SBG

More...

We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

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

Please find below an update on the situation: Update : We have completed our development and the fix is currently being tested in our Q&A process. Testing process is especially long to prevent any regression while fixing the issue. 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.

10 Apr 2025 08:46:04 (2 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 teams are still working on fix.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

3 Mar 2025 12:37:50 (3 months ago)

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

6 Feb 2025 19:10:34 (4 months ago)

Identified: We have determined the origin of the incident affecting our Object Storage S3 offer.

Here are some supplementary details : Start time : 01/01/2025 00:00 UTC Impacted Service(s) : Object Storage S3 Customers Impact : Requests to our Object Storage endpoint could return the error "InvalidArgument", on different Object operations. Root Cause : Following a recent AWS SDK upgrade, this issue is due to a new checksum enforcement in those SDKs. Unsupported headers are:

x-amz-content-sha256 with value STREAMING-UNSIGNED-PAYLOAD-TRAILER
x-amz-sdk-checksum-algorithm with value CRC32 Workaround A workaround is to downgrade the version, until the feature is implemented on our side. Max supported versions:
boto3 1.35.99
legacy aws cli 1.36.40
aws cli 2.22.35
aws-sdk-go 1.72.3
aws-sdk-java 2.29.52
aws-sdk-js-v3 3.726.1
aws-sdk-net 3.7.962.0
aws-sdk-php 3.336.15
aws-sdk-ruby 1.177.0 Ongoing Actions : The incident has been identified and our teams are mobilized 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.

23 Jan 2025 15:11:08 (4 months ago)

Investigating: We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

23 Jan 2025 14:51:30 (4 months ago)

See all updates

[GLOBAL][Storage] - Object storage incident notification

Started 25 Apr 2025 08:47:08 (1 month ago), resolved 31 May 2025 00:50:52 (1 day ago)

Minor Incident

Resolved

BHS

GRA

DE

RBX

SBG

More...

We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

Resolved: We would like to inform you that the incident on our Object Storage offer, have been resolved Start Time : 25/03/2025 09:00 UTC End Time : 31/05/2025 00:45 UTC Root cause : This incident is caused by a software issue.

We thank you for your understanding and patience throughout this incident

31 May 2025 00:50:52 (1 day ago)

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

Please find below an update on the situation:
Update : Treatments are still ongoing and have already been completed for some customers. Refunds are also being processed. However, treatments vary in length depending on the customer. Please be assured that refunds will be issued upon completion of treatment, with a start date of March 25, 2025.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.

21 May 2025 10:06:07 (11 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 customers are still experiencing a discrepancy between the actual size of their bucket and the size displayed in the Manager, due to undeleted parts that should have been removed. To address this issue, affected customers will receive an informational email and a credit note on their invoice, compensating for excess consumption, with credits applied as of April 18, 2025. Ongoing Actions : The incident has been identified and our technical teams are working on the storage size of the impacted customers between those 2 dates.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

14 May 2025 12:32:18 (18 days ago)

Identified: We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

25 Apr 2025 08:47:09 (1 month ago)

See all updates

SYD

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GLOBAL][Object Storage] - Amazon S3 SDK compatibility inconsistencies with Object Storage Standard/High Performance

Started 23 Jan 2025 14:51:30 (4 months ago), still ongoing

Major Incident

Identified

BHS

GRA

DE

RBX

SBG

More...

We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

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

Please find below an update on the situation: Update : We have completed our development and the fix is currently being tested in our Q&A process. Testing process is especially long to prevent any regression while fixing the issue. 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.

10 Apr 2025 08:46:04 (2 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 teams are still working on fix.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

3 Mar 2025 12:37:50 (3 months ago)

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

6 Feb 2025 19:10:34 (4 months ago)

Identified: We have determined the origin of the incident affecting our Object Storage S3 offer.

Here are some supplementary details : Start time : 01/01/2025 00:00 UTC Impacted Service(s) : Object Storage S3 Customers Impact : Requests to our Object Storage endpoint could return the error "InvalidArgument", on different Object operations. Root Cause : Following a recent AWS SDK upgrade, this issue is due to a new checksum enforcement in those SDKs. Unsupported headers are:

x-amz-content-sha256 with value STREAMING-UNSIGNED-PAYLOAD-TRAILER
x-amz-sdk-checksum-algorithm with value CRC32 Workaround A workaround is to downgrade the version, until the feature is implemented on our side. Max supported versions:
boto3 1.35.99
legacy aws cli 1.36.40
aws cli 2.22.35
aws-sdk-go 1.72.3
aws-sdk-java 2.29.52
aws-sdk-js-v3 3.726.1
aws-sdk-net 3.7.962.0
aws-sdk-php 3.336.15
aws-sdk-ruby 1.177.0 Ongoing Actions : The incident has been identified and our teams are mobilized 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.

23 Jan 2025 15:11:08 (4 months ago)

Investigating: We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

23 Jan 2025 14:51:30 (4 months ago)

See all updates

[GLOBAL][Storage] - Object storage incident notification

Started 25 Apr 2025 08:47:08 (1 month ago), resolved 31 May 2025 00:50:52 (1 day ago)

Minor Incident

Resolved

BHS

GRA

DE

RBX

SBG

More...

We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

Resolved: We would like to inform you that the incident on our Object Storage offer, have been resolved Start Time : 25/03/2025 09:00 UTC End Time : 31/05/2025 00:45 UTC Root cause : This incident is caused by a software issue.

We thank you for your understanding and patience throughout this incident

31 May 2025 00:50:52 (1 day ago)

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

Please find below an update on the situation:
Update : Treatments are still ongoing and have already been completed for some customers. Refunds are also being processed. However, treatments vary in length depending on the customer. Please be assured that refunds will be issued upon completion of treatment, with a start date of March 25, 2025.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.

21 May 2025 10:06:07 (11 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 customers are still experiencing a discrepancy between the actual size of their bucket and the size displayed in the Manager, due to undeleted parts that should have been removed. To address this issue, affected customers will receive an informational email and a credit note on their invoice, compensating for excess consumption, with credits applied as of April 18, 2025. Ongoing Actions : The incident has been identified and our technical teams are working on the storage size of the impacted customers between those 2 dates.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

14 May 2025 12:32:18 (18 days ago)

Identified: We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

25 Apr 2025 08:47:09 (1 month ago)

See all updates

UK

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GLOBAL][Object Storage] - Amazon S3 SDK compatibility inconsistencies with Object Storage Standard/High Performance

Started 23 Jan 2025 14:51:30 (4 months ago), still ongoing

Major Incident

Identified

BHS

GRA

DE

RBX

SBG

More...

We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

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

Please find below an update on the situation: Update : We have completed our development and the fix is currently being tested in our Q&A process. Testing process is especially long to prevent any regression while fixing the issue. 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.

10 Apr 2025 08:46:04 (2 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 teams are still working on fix.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

3 Mar 2025 12:37:50 (3 months ago)

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

6 Feb 2025 19:10:34 (4 months ago)

Identified: We have determined the origin of the incident affecting our Object Storage S3 offer.

Here are some supplementary details : Start time : 01/01/2025 00:00 UTC Impacted Service(s) : Object Storage S3 Customers Impact : Requests to our Object Storage endpoint could return the error "InvalidArgument", on different Object operations. Root Cause : Following a recent AWS SDK upgrade, this issue is due to a new checksum enforcement in those SDKs. Unsupported headers are:

x-amz-content-sha256 with value STREAMING-UNSIGNED-PAYLOAD-TRAILER
x-amz-sdk-checksum-algorithm with value CRC32 Workaround A workaround is to downgrade the version, until the feature is implemented on our side. Max supported versions:
boto3 1.35.99
legacy aws cli 1.36.40
aws cli 2.22.35
aws-sdk-go 1.72.3
aws-sdk-java 2.29.52
aws-sdk-js-v3 3.726.1
aws-sdk-net 3.7.962.0
aws-sdk-php 3.336.15
aws-sdk-ruby 1.177.0 Ongoing Actions : The incident has been identified and our teams are mobilized 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.

23 Jan 2025 15:11:08 (4 months ago)

Investigating: We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

23 Jan 2025 14:51:30 (4 months ago)

See all updates

[GLOBAL][Storage] - Object storage incident notification

Started 25 Apr 2025 08:47:08 (1 month ago), resolved 31 May 2025 00:50:52 (1 day ago)

Minor Incident

Resolved

BHS

GRA

DE

RBX

SBG

More...

We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

Resolved: We would like to inform you that the incident on our Object Storage offer, have been resolved Start Time : 25/03/2025 09:00 UTC End Time : 31/05/2025 00:45 UTC Root cause : This incident is caused by a software issue.

We thank you for your understanding and patience throughout this incident

31 May 2025 00:50:52 (1 day ago)

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

Please find below an update on the situation:
Update : Treatments are still ongoing and have already been completed for some customers. Refunds are also being processed. However, treatments vary in length depending on the customer. Please be assured that refunds will be issued upon completion of treatment, with a start date of March 25, 2025.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.

21 May 2025 10:06:07 (11 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 customers are still experiencing a discrepancy between the actual size of their bucket and the size displayed in the Manager, due to undeleted parts that should have been removed. To address this issue, affected customers will receive an informational email and a credit note on their invoice, compensating for excess consumption, with credits applied as of April 18, 2025. Ongoing Actions : The incident has been identified and our technical teams are working on the storage size of the impacted customers between those 2 dates.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

14 May 2025 12:32:18 (18 days ago)

Identified: We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

25 Apr 2025 08:47:09 (1 month ago)

See all updates

[EU][Storage] - Object Storage S3 Standard/High Perf

Started 27 May 2025 20:31:00 (4 days ago), resolved 27 May 2025 21:31:20 (4 days ago)

Major Incident

Resolved

GRA

DE

RBX

SBG

UK

We are currently experiencing an incident affecting our Object Storage offer. Start time : 27/05/2025 20:00 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.

See all updates

US-EAST-VA-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GLOBAL][Object Storage] - Amazon S3 SDK compatibility inconsistencies with Object Storage Standard/High Performance

Started 23 Jan 2025 14:51:30 (4 months ago), still ongoing

Major Incident

Identified

BHS

GRA

DE

RBX

SBG

More...

We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

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

Please find below an update on the situation: Update : We have completed our development and the fix is currently being tested in our Q&A process. Testing process is especially long to prevent any regression while fixing the issue. 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.

10 Apr 2025 08:46:04 (2 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 teams are still working on fix.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

3 Mar 2025 12:37:50 (3 months ago)

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

6 Feb 2025 19:10:34 (4 months ago)

Identified: We have determined the origin of the incident affecting our Object Storage S3 offer.

Here are some supplementary details : Start time : 01/01/2025 00:00 UTC Impacted Service(s) : Object Storage S3 Customers Impact : Requests to our Object Storage endpoint could return the error "InvalidArgument", on different Object operations. Root Cause : Following a recent AWS SDK upgrade, this issue is due to a new checksum enforcement in those SDKs. Unsupported headers are:

x-amz-content-sha256 with value STREAMING-UNSIGNED-PAYLOAD-TRAILER
x-amz-sdk-checksum-algorithm with value CRC32 Workaround A workaround is to downgrade the version, until the feature is implemented on our side. Max supported versions:
boto3 1.35.99
legacy aws cli 1.36.40
aws cli 2.22.35
aws-sdk-go 1.72.3
aws-sdk-java 2.29.52
aws-sdk-js-v3 3.726.1
aws-sdk-net 3.7.962.0
aws-sdk-php 3.336.15
aws-sdk-ruby 1.177.0 Ongoing Actions : The incident has been identified and our teams are mobilized 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.

23 Jan 2025 15:11:08 (4 months ago)

Investigating: We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

23 Jan 2025 14:51:30 (4 months ago)

See all updates

[GLOBAL][Storage] - Object storage incident notification

Started 25 Apr 2025 08:47:08 (1 month ago), resolved 31 May 2025 00:50:52 (1 day ago)

Minor Incident

Resolved

BHS

GRA

DE

RBX

SBG

More...

We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

Resolved: We would like to inform you that the incident on our Object Storage offer, have been resolved Start Time : 25/03/2025 09:00 UTC End Time : 31/05/2025 00:45 UTC Root cause : This incident is caused by a software issue.

We thank you for your understanding and patience throughout this incident

31 May 2025 00:50:52 (1 day ago)

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

Please find below an update on the situation:
Update : Treatments are still ongoing and have already been completed for some customers. Refunds are also being processed. However, treatments vary in length depending on the customer. Please be assured that refunds will be issued upon completion of treatment, with a start date of March 25, 2025.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.

21 May 2025 10:06:07 (11 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 customers are still experiencing a discrepancy between the actual size of their bucket and the size displayed in the Manager, due to undeleted parts that should have been removed. To address this issue, affected customers will receive an informational email and a credit note on their invoice, compensating for excess consumption, with credits applied as of April 18, 2025. Ongoing Actions : The incident has been identified and our technical teams are working on the storage size of the impacted customers between those 2 dates.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

14 May 2025 12:32:18 (18 days ago)

Identified: We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

25 Apr 2025 08:47:09 (1 month ago)

See all updates

US-WEST-OR-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GLOBAL][Object Storage] - Amazon S3 SDK compatibility inconsistencies with Object Storage Standard/High Performance

Started 23 Jan 2025 14:51:30 (4 months ago), still ongoing

Major Incident

Identified

BHS

GRA

DE

RBX

SBG

More...

We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

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

Please find below an update on the situation: Update : We have completed our development and the fix is currently being tested in our Q&A process. Testing process is especially long to prevent any regression while fixing the issue. 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.

10 Apr 2025 08:46:04 (2 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 teams are still working on fix.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

3 Mar 2025 12:37:50 (3 months ago)

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

6 Feb 2025 19:10:34 (4 months ago)

Identified: We have determined the origin of the incident affecting our Object Storage S3 offer.

Here are some supplementary details : Start time : 01/01/2025 00:00 UTC Impacted Service(s) : Object Storage S3 Customers Impact : Requests to our Object Storage endpoint could return the error "InvalidArgument", on different Object operations. Root Cause : Following a recent AWS SDK upgrade, this issue is due to a new checksum enforcement in those SDKs. Unsupported headers are:

x-amz-content-sha256 with value STREAMING-UNSIGNED-PAYLOAD-TRAILER
x-amz-sdk-checksum-algorithm with value CRC32 Workaround A workaround is to downgrade the version, until the feature is implemented on our side. Max supported versions:
boto3 1.35.99
legacy aws cli 1.36.40
aws cli 2.22.35
aws-sdk-go 1.72.3
aws-sdk-java 2.29.52
aws-sdk-js-v3 3.726.1
aws-sdk-net 3.7.962.0
aws-sdk-php 3.336.15
aws-sdk-ruby 1.177.0 Ongoing Actions : The incident has been identified and our teams are mobilized 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.

23 Jan 2025 15:11:08 (4 months ago)

Investigating: We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

23 Jan 2025 14:51:30 (4 months ago)

See all updates

[GLOBAL][Storage] - Object storage incident notification

Started 25 Apr 2025 08:47:08 (1 month ago), resolved 31 May 2025 00:50:52 (1 day ago)

Minor Incident

Resolved

BHS

GRA

DE

RBX

SBG

More...

We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

Resolved: We would like to inform you that the incident on our Object Storage offer, have been resolved Start Time : 25/03/2025 09:00 UTC End Time : 31/05/2025 00:45 UTC Root cause : This incident is caused by a software issue.

We thank you for your understanding and patience throughout this incident

31 May 2025 00:50:52 (1 day ago)

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

Please find below an update on the situation:
Update : Treatments are still ongoing and have already been completed for some customers. Refunds are also being processed. However, treatments vary in length depending on the customer. Please be assured that refunds will be issued upon completion of treatment, with a start date of March 25, 2025.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.

21 May 2025 10:06:07 (11 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 customers are still experiencing a discrepancy between the actual size of their bucket and the size displayed in the Manager, due to undeleted parts that should have been removed. To address this issue, affected customers will receive an informational email and a credit note on their invoice, compensating for excess consumption, with credits applied as of April 18, 2025. Ongoing Actions : The incident has been identified and our technical teams are working on the storage size of the impacted customers between those 2 dates.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

14 May 2025 12:32:18 (18 days ago)

Identified: We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

25 Apr 2025 08:47:09 (1 month ago)

See all updates

WAW

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GLOBAL][Object Storage] - Amazon S3 SDK compatibility inconsistencies with Object Storage Standard/High Performance

Started 23 Jan 2025 14:51:30 (4 months ago), still ongoing

Major Incident

Identified

BHS

GRA

DE

RBX

SBG

More...

We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

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

Please find below an update on the situation: Update : We have completed our development and the fix is currently being tested in our Q&A process. Testing process is especially long to prevent any regression while fixing the issue. 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.

10 Apr 2025 08:46:04 (2 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 teams are still working on fix.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

3 Mar 2025 12:37:50 (3 months ago)

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

6 Feb 2025 19:10:34 (4 months ago)

Identified: We have determined the origin of the incident affecting our Object Storage S3 offer.

Here are some supplementary details : Start time : 01/01/2025 00:00 UTC Impacted Service(s) : Object Storage S3 Customers Impact : Requests to our Object Storage endpoint could return the error "InvalidArgument", on different Object operations. Root Cause : Following a recent AWS SDK upgrade, this issue is due to a new checksum enforcement in those SDKs. Unsupported headers are:

x-amz-content-sha256 with value STREAMING-UNSIGNED-PAYLOAD-TRAILER
x-amz-sdk-checksum-algorithm with value CRC32 Workaround A workaround is to downgrade the version, until the feature is implemented on our side. Max supported versions:
boto3 1.35.99
legacy aws cli 1.36.40
aws cli 2.22.35
aws-sdk-go 1.72.3
aws-sdk-java 2.29.52
aws-sdk-js-v3 3.726.1
aws-sdk-net 3.7.962.0
aws-sdk-php 3.336.15
aws-sdk-ruby 1.177.0 Ongoing Actions : The incident has been identified and our teams are mobilized 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.

23 Jan 2025 15:11:08 (4 months ago)

Investigating: We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

23 Jan 2025 14:51:30 (4 months ago)

See all updates

[GLOBAL][Storage] - Object storage incident notification

Started 25 Apr 2025 08:47:08 (1 month ago), resolved 31 May 2025 00:50:52 (1 day ago)

Minor Incident

Resolved

BHS

GRA

DE

RBX

SBG

More...

We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

Resolved: We would like to inform you that the incident on our Object Storage offer, have been resolved Start Time : 25/03/2025 09:00 UTC End Time : 31/05/2025 00:45 UTC Root cause : This incident is caused by a software issue.

We thank you for your understanding and patience throughout this incident

31 May 2025 00:50:52 (1 day ago)

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

Please find below an update on the situation:
Update : Treatments are still ongoing and have already been completed for some customers. Refunds are also being processed. However, treatments vary in length depending on the customer. Please be assured that refunds will be issued upon completion of treatment, with a start date of March 25, 2025.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.

21 May 2025 10:06:07 (11 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 customers are still experiencing a discrepancy between the actual size of their bucket and the size displayed in the Manager, due to undeleted parts that should have been removed. To address this issue, affected customers will receive an informational email and a credit note on their invoice, compensating for excess consumption, with credits applied as of April 18, 2025. Ongoing Actions : The incident has been identified and our technical teams are working on the storage size of the impacted customers between those 2 dates.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

14 May 2025 12:32:18 (18 days ago)

Identified: We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

25 Apr 2025 08:47:09 (1 month ago)

See all updates

YYZ

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GLOBAL][Object Storage] - Amazon S3 SDK compatibility inconsistencies with Object Storage Standard/High Performance

Started 23 Jan 2025 14:51:30 (4 months ago), still ongoing

Major Incident

Identified

BHS

GRA

DE

RBX

SBG

More...

We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

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

Please find below an update on the situation: Update : We have completed our development and the fix is currently being tested in our Q&A process. Testing process is especially long to prevent any regression while fixing the issue. 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.

10 Apr 2025 08:46:04 (2 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 teams are still working on fix.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

3 Mar 2025 12:37:50 (3 months ago)

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

6 Feb 2025 19:10:34 (4 months ago)

Identified: We have determined the origin of the incident affecting our Object Storage S3 offer.

Here are some supplementary details : Start time : 01/01/2025 00:00 UTC Impacted Service(s) : Object Storage S3 Customers Impact : Requests to our Object Storage endpoint could return the error "InvalidArgument", on different Object operations. Root Cause : Following a recent AWS SDK upgrade, this issue is due to a new checksum enforcement in those SDKs. Unsupported headers are:

x-amz-content-sha256 with value STREAMING-UNSIGNED-PAYLOAD-TRAILER
x-amz-sdk-checksum-algorithm with value CRC32 Workaround A workaround is to downgrade the version, until the feature is implemented on our side. Max supported versions:
boto3 1.35.99
legacy aws cli 1.36.40
aws cli 2.22.35
aws-sdk-go 1.72.3
aws-sdk-java 2.29.52
aws-sdk-js-v3 3.726.1
aws-sdk-net 3.7.962.0
aws-sdk-php 3.336.15
aws-sdk-ruby 1.177.0 Ongoing Actions : The incident has been identified and our teams are mobilized 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.

23 Jan 2025 15:11:08 (4 months ago)

Investigating: We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

23 Jan 2025 14:51:30 (4 months ago)

See all updates

[GLOBAL][Storage] - Object storage incident notification

Started 25 Apr 2025 08:47:08 (1 month ago), resolved 31 May 2025 00:50:52 (1 day ago)

Minor Incident

Resolved

BHS

GRA

DE

RBX

SBG

More...

We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

Resolved: We would like to inform you that the incident on our Object Storage offer, have been resolved Start Time : 25/03/2025 09:00 UTC End Time : 31/05/2025 00:45 UTC Root cause : This incident is caused by a software issue.

We thank you for your understanding and patience throughout this incident

31 May 2025 00:50:52 (1 day ago)

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

Please find below an update on the situation:
Update : Treatments are still ongoing and have already been completed for some customers. Refunds are also being processed. However, treatments vary in length depending on the customer. Please be assured that refunds will be issued upon completion of treatment, with a start date of March 25, 2025.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.

21 May 2025 10:06:07 (11 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 customers are still experiencing a discrepancy between the actual size of their bucket and the size displayed in the Manager, due to undeleted parts that should have been removed. To address this issue, affected customers will receive an informational email and a credit note on their invoice, compensating for excess consumption, with credits applied as of April 18, 2025. Ongoing Actions : The incident has been identified and our technical teams are working on the storage size of the impacted customers between those 2 dates.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

14 May 2025 12:32:18 (18 days ago)

Identified: We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

25 Apr 2025 08:47:09 (1 month ago)

See all updates

LIM

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GLOBAL][Object Storage] - Amazon S3 SDK compatibility inconsistencies with Object Storage Standard/High Performance

Started 23 Jan 2025 14:51:30 (4 months ago), still ongoing

Major Incident

Identified

BHS

GRA

DE

RBX

SBG

More...

We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

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

Please find below an update on the situation: Update : We have completed our development and the fix is currently being tested in our Q&A process. Testing process is especially long to prevent any regression while fixing the issue. 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.

10 Apr 2025 08:46:04 (2 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 teams are still working on fix.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

3 Mar 2025 12:37:50 (3 months ago)

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

6 Feb 2025 19:10:34 (4 months ago)

Identified: We have determined the origin of the incident affecting our Object Storage S3 offer.

Here are some supplementary details : Start time : 01/01/2025 00:00 UTC Impacted Service(s) : Object Storage S3 Customers Impact : Requests to our Object Storage endpoint could return the error "InvalidArgument", on different Object operations. Root Cause : Following a recent AWS SDK upgrade, this issue is due to a new checksum enforcement in those SDKs. Unsupported headers are:

x-amz-content-sha256 with value STREAMING-UNSIGNED-PAYLOAD-TRAILER
x-amz-sdk-checksum-algorithm with value CRC32 Workaround A workaround is to downgrade the version, until the feature is implemented on our side. Max supported versions:
boto3 1.35.99
legacy aws cli 1.36.40
aws cli 2.22.35
aws-sdk-go 1.72.3
aws-sdk-java 2.29.52
aws-sdk-js-v3 3.726.1
aws-sdk-net 3.7.962.0
aws-sdk-php 3.336.15
aws-sdk-ruby 1.177.0 Ongoing Actions : The incident has been identified and our teams are mobilized 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.

23 Jan 2025 15:11:08 (4 months ago)

Investigating: We are currently experiencing an event affecting our Object Storage S3 offer. Start time : 01/01/2025 00:00 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.

23 Jan 2025 14:51:30 (4 months ago)

See all updates

[GLOBAL][Storage] - Object storage incident notification

Started 25 Apr 2025 08:47:08 (1 month ago), resolved 31 May 2025 00:50:52 (1 day ago)

Minor Incident

Resolved

BHS

GRA

DE

RBX

SBG

More...

We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

Resolved: We would like to inform you that the incident on our Object Storage offer, have been resolved Start Time : 25/03/2025 09:00 UTC End Time : 31/05/2025 00:45 UTC Root cause : This incident is caused by a software issue.

We thank you for your understanding and patience throughout this incident

31 May 2025 00:50:52 (1 day ago)

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

Please find below an update on the situation:
Update : Treatments are still ongoing and have already been completed for some customers. Refunds are also being processed. However, treatments vary in length depending on the customer. Please be assured that refunds will be issued upon completion of treatment, with a start date of March 25, 2025.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.

21 May 2025 10:06:07 (11 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 customers are still experiencing a discrepancy between the actual size of their bucket and the size displayed in the Manager, due to undeleted parts that should have been removed. To address this issue, affected customers will receive an informational email and a credit note on their invoice, compensating for excess consumption, with credits applied as of April 18, 2025. Ongoing Actions : The incident has been identified and our technical teams are working on the storage size of the impacted customers between those 2 dates.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

14 May 2025 12:32:18 (18 days ago)

Identified: We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

25 Apr 2025 08:47:09 (1 month ago)

See all updates

AP-SOUTH-MUM-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GLOBAL][Storage] - Object storage incident notification

Started 25 Apr 2025 08:47:08 (1 month ago), resolved 31 May 2025 00:50:52 (1 day ago)

Minor Incident

Resolved

BHS

GRA

DE

RBX

SBG

More...

We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

Resolved: We would like to inform you that the incident on our Object Storage offer, have been resolved Start Time : 25/03/2025 09:00 UTC End Time : 31/05/2025 00:45 UTC Root cause : This incident is caused by a software issue.

We thank you for your understanding and patience throughout this incident

31 May 2025 00:50:52 (1 day ago)

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

Please find below an update on the situation:
Update : Treatments are still ongoing and have already been completed for some customers. Refunds are also being processed. However, treatments vary in length depending on the customer. Please be assured that refunds will be issued upon completion of treatment, with a start date of March 25, 2025.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.

21 May 2025 10:06:07 (11 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 customers are still experiencing a discrepancy between the actual size of their bucket and the size displayed in the Manager, due to undeleted parts that should have been removed. To address this issue, affected customers will receive an informational email and a credit note on their invoice, compensating for excess consumption, with credits applied as of April 18, 2025. Ongoing Actions : The incident has been identified and our technical teams are working on the storage size of the impacted customers between those 2 dates.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

14 May 2025 12:32:18 (18 days ago)

Identified: We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

25 Apr 2025 08:47:09 (1 month ago)

See all updates

EU-WEST-PAR-A

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GLOBAL][Storage] - Object storage incident notification

Started 25 Apr 2025 08:47:08 (1 month ago), resolved 31 May 2025 00:50:52 (1 day ago)

Minor Incident

Resolved

BHS

GRA

DE

RBX

SBG

More...

We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

Resolved: We would like to inform you that the incident on our Object Storage offer, have been resolved Start Time : 25/03/2025 09:00 UTC End Time : 31/05/2025 00:45 UTC Root cause : This incident is caused by a software issue.

We thank you for your understanding and patience throughout this incident

31 May 2025 00:50:52 (1 day ago)

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

Please find below an update on the situation:
Update : Treatments are still ongoing and have already been completed for some customers. Refunds are also being processed. However, treatments vary in length depending on the customer. Please be assured that refunds will be issued upon completion of treatment, with a start date of March 25, 2025.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.

21 May 2025 10:06:07 (11 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 customers are still experiencing a discrepancy between the actual size of their bucket and the size displayed in the Manager, due to undeleted parts that should have been removed. To address this issue, affected customers will receive an informational email and a credit note on their invoice, compensating for excess consumption, with credits applied as of April 18, 2025. Ongoing Actions : The incident has been identified and our technical teams are working on the storage size of the impacted customers between those 2 dates.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

14 May 2025 12:32:18 (18 days ago)

Identified: We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

25 Apr 2025 08:47:09 (1 month ago)

See all updates

EU-WEST-PAR-B

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GLOBAL][Storage] - Object storage incident notification

Started 25 Apr 2025 08:47:08 (1 month ago), resolved 31 May 2025 00:50:52 (1 day ago)

Minor Incident

Resolved

BHS

GRA

DE

RBX

SBG

More...

We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

Resolved: We would like to inform you that the incident on our Object Storage offer, have been resolved Start Time : 25/03/2025 09:00 UTC End Time : 31/05/2025 00:45 UTC Root cause : This incident is caused by a software issue.

We thank you for your understanding and patience throughout this incident

31 May 2025 00:50:52 (1 day ago)

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

Please find below an update on the situation:
Update : Treatments are still ongoing and have already been completed for some customers. Refunds are also being processed. However, treatments vary in length depending on the customer. Please be assured that refunds will be issued upon completion of treatment, with a start date of March 25, 2025.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.

21 May 2025 10:06:07 (11 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 customers are still experiencing a discrepancy between the actual size of their bucket and the size displayed in the Manager, due to undeleted parts that should have been removed. To address this issue, affected customers will receive an informational email and a credit note on their invoice, compensating for excess consumption, with credits applied as of April 18, 2025. Ongoing Actions : The incident has been identified and our technical teams are working on the storage size of the impacted customers between those 2 dates.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

14 May 2025 12:32:18 (18 days ago)

Identified: We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

25 Apr 2025 08:47:09 (1 month ago)

See all updates

EU-WEST-PAR-C

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

[GLOBAL][Storage] - Object storage incident notification

Started 25 Apr 2025 08:47:08 (1 month ago), resolved 31 May 2025 00:50:52 (1 day ago)

Minor Incident

Resolved

BHS

GRA

DE

RBX

SBG

More...

We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

Resolved: We would like to inform you that the incident on our Object Storage offer, have been resolved Start Time : 25/03/2025 09:00 UTC End Time : 31/05/2025 00:45 UTC Root cause : This incident is caused by a software issue.

We thank you for your understanding and patience throughout this incident

31 May 2025 00:50:52 (1 day ago)

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

Please find below an update on the situation:
Update : Treatments are still ongoing and have already been completed for some customers. Refunds are also being processed. However, treatments vary in length depending on the customer. Please be assured that refunds will be issued upon completion of treatment, with a start date of March 25, 2025.

We will keep you updated on the progress and resolution.
We apologize for any inconvenience caused and appreciate your understanding.

21 May 2025 10:06:07 (11 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 customers are still experiencing a discrepancy between the actual size of their bucket and the size displayed in the Manager, due to undeleted parts that should have been removed. To address this issue, affected customers will receive an informational email and a credit note on their invoice, compensating for excess consumption, with credits applied as of April 18, 2025. Ongoing Actions : The incident has been identified and our technical teams are working on the storage size of the impacted customers between those 2 dates.

We will keep you updated on the progress and resolution. We apologize for any inconvenience caused and appreciate your understanding.

14 May 2025 12:32:18 (18 days ago)

Identified: We have determined the origin of the incident affecting our Object Storage offer.

Here are some supplementary details : Start time : 25/03/2025 09:00 UTC Impacted Service(s) : Object storage offer Customers Impact : Between 25/03/2025 09:00 UTC and 18/04/2025 16:00 UTC, when customers deleting an object with MPU (only objects with more than 100 parts), only the first 100 parts were deleted. Since 18/04/2025 16:00 UTC, the bug is fixed and all parts are now correctly deleted. Because of this bug, customers will have a discrepancy between the actual bucket size and the size displayed in the Manager because of parts that not have been deleted but should have been. In the meantime, our technical teams are working on the storage size of the impacted customers between those 2 dates. Root Cause : This incident is caused by a software issue. 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.

25 Apr 2025 08:47:09 (1 month ago)

See all updates

Public Cloud Storage || Volume Backup

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

BHS5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA7

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA9

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA11

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG7

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SGP1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD2

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-EAST-VA-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-WEST-OR-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Storage || Volume Snapshot (Ceph)

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

DE1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA2

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA6

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA7

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA9

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

GRA11

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG5

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SBG7

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SGP1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

SYD3

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

UK1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

WAW1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-EAST-VA-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

US-WEST-OR-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

AP-SOUTH-MUM-1

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-A

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-B

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

EU-WEST-PAR-C

Sun 25

Mon 26

Tue 27

Wed 28

Thu 29

Fri 30

Sat 31

now

Public Cloud Status

Real-time updates of Public Cloud issues and outages

Public Cloud status is Minor Service Outage

GRA4

GRA1

GRA5

GRA7

GRA11

GRA5

GRA7

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-WEST-PAR

GRA2

EU-WEST-PAR-A

EU-WEST-PAR-B

GRA4

EU-WEST-PAR-C

Public Cloud Compute - Instance || GRA

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

BHS5

DE1

GRA5

GRA7

GRA9

GRA11

SBG5

SGP1

SYD1

WAW1

UK1

US-EAST-VA-1

US-WEST-OR-1

Public Cloud Containers & Orchestration || Managed Kubernetes Service