Spaces CDN Certificate and Load Balancer creates in AMS3 and SGP1

As of 03:45 UTC, Our Engineering team has confirmed the full resolution of the issue which impacted Spaces CDN certificates in AMS3 and SGP1 regions.

If you should experience any further issues, please open a ticket with our support team right away. Thank you for your patience and we apologize for the inconvenience.

Our engineering team has renewed the expired SSL certificates on the Spaces CDN in AMS3 and SGP1 regions. Users should no longer experience any errors when accessing the objects using the CDN endpoint.

We are now monitoring Spaces traffic to ensure this fix has mitigated all impacts and will post an update as soon as we confirm that is the case. Thank you for your patience!

Our Engineering team has identified the cause of the issue with the SSL certificates on the Spaces CDN in AMS3 and SGP1. These certificates expired at 00:00 UTC, causing users to see SSL warnings when accessing objects. The team is now in the process of rolling forward to new certificates, which will mitigate this issue.

Our team previously believed Load Balancer creations to be impacted due to a dependency, but has confirmed they are not impacted. All Load Balancer creations should be succeeding normally.

We will post an update once the new certificates are in place.

Our Engineering team is investigating an issue with the SSL certificate on the Spaces CDN in our AMS3 and SGP1 regions.

During this time, users with Spaces buckets not using a custom SSL certificate with the CDN will see SSL errors while viewing objects.

Due to a dependency on the Spaces CDN, users may also see slow or failed creates for Load Balancers.

We apologize for the inconvenience and will share an update once we have more information.