SSL/TLS Handshake Failures in FRA1 & SFO3

Resolved

Our Engineering team has confirmed that the issue affecting access to Object Storage Buckets in the FRA1 and SFO3 regions has been fully resolved. Users should no longer experience SSL/TLS handshake failures when accessing their Buckets in these regions.

We appreciate your patience and understanding while we worked to resolve this matter. If you continue to experience any issues, please don't hesitate to open a support ticket from your account for further assistance.

Update

Our Engineering team has identified the root cause of the issue as a block imposed by a third-party provider on users utilizing residential cable services and their advanced security offerings.

During this time, a subset of users accessing their Spaces buckets in the FRA1 and SFO3 regions via residential cable services may have experienced SSL/TLS handshake failures.

This block was removed as of 17:48 UTC, and users should no longer encounter errors when accessing the contents of their buckets.

We are actively working with the third-party provider to ensure that such blocks are not imposed again in the future.

We will continue to monitor the situation and post an update once this issue is fully resolved. Thank you for your patience.

Investigating

Our Engineering team continues to investigate reports of SSL/TLS handshake failures affecting Object Storage access in the FRA1 and SFO3 regions. The team is reviewing logs and traffic flows to isolate the root cause and determine whether a misconfiguration or external dependency is contributing to the failures.

Our team is actively working to resolve the issue and we will provide further updates as soon as we have more information. Thank you for your continued patience.

Investigating

Our Engineering team is currently investigating reports of SSL/TLS handshake failures for Object Storage access in FRA1 and SFO3 regions. Affected users may see connection errors or timeouts when attempting to access buckets over HTTPS.

We are actively working to identify the root cause and implement a solution and will share further updates as more information becomes available.