Status

Non-isolated downloads that take more than 30 seconds are failing (all regions except Tokyo) Friday 9th February 2024 03:20:00

At 2024-02-09 11:00 UTC We have identified file downloads failures from non-isolated sites taking longer than 30 seconds to process. This affects all the regions except Tokyo (ap-northeast-1)

On-call teams are investigating the issue.

2024-02-09 11:25 UTC On-call teams have identified the issue and are working on a solution.

2024-02-10 02:40 UTC Engineering has completed rolling out a fix globally

2024-02-10 02:40 UTC

A solution has been fully rolled out and on-call teams have verified that the impact is resolved.

No further updates are expected.

Posted 5 months ago by fernando.toussaint

2024-02-10 02:40 UTC A solution has been fully rolled out and on-call teams have verified that the impact is resolved.

No further updates are expected.

Posted 5 months ago by fernando.toussaint

2024-02-09 20:05 UTC Deployment of the solution has commenced to all impacted regions. Next progress update in 1 hour.

Posted 5 months ago by fernando.toussaint

2024-02-09 16:59 UTC

On-call teams continue preparing to roll out the solution to all impacted regions

Next update in 1 hour

Posted 5 months ago by fernando.toussaint

2024-02-09 15:58 UTC

On-call teams continue preparing to roll out the solution to all impacted regions.

Next update in 1 hour.

Posted 5 months ago by admin

2024-02-09 15:22 UTC

On-call teams continue preparing to roll out the solution to all impacted regions.

Posted 5 months ago by admin

2024-02-09 14:29 UTC

On-call teams have verified a solution and are in the process of preparing to roll it out to all impacted regions.

Posted 5 months ago by admin

2024-02-09 14:07 UTC

On-call teams continue working on testing and validating the fix.

Posted 5 months ago by admin

2024-02-09 13:14 UTC

On-call teams continue working on testing and validating the fix.

Posted 5 months ago by admin

2024-02-09 12:43 UTC

On-call teams continue working on testing and validating the fix.

Posted 5 months ago by admin

2024-02-09 11:57 UTC

On-call teams have identified a possible solution and are currently testing.

Posted 5 months ago by admin