YSoft SAFEQ Cloud - Incident - SAFEQ Cloud - Potential issues with PC Client – Incident details

Our investigation and monitoring are ongoing, and we wanted to share our current working theory.

We're analysing the recent security update in the PC client, which hardens preference for TLS 1.3 and HTTP/2 over older protocols. Based on our analysis so far, this change appears to cause connectivity problems in environments where SSL packet inspection tools (such as SSL analysers or deep packet inspection proxies) are in use.

If you are affected and have such tools in your environment, a downgrade to the previous version remains available as a fallback and is recommended until a resolution is in place.

We will continue analysing and monitoring the situation and will provide further updates as our investigation progresses. Thank you for your patience and understanding.

While we have not been able to fully identify the root cause of the reported issue, we have not observed continued or widespread impact throughout the day.

Our team will continue monitoring the situation and investigating further. As a precautionary measure, we advise that a downgrade is available as a fallback option should any issues arise.

We will continue to provide updates if the situation changes. Thank you for your patience and understanding.

Our investigation is ongoing and we continue to actively monitor the situation. While we still have been unable to reproduce the issue in our environment so far, we remain committed to identifying the root cause.

The previously communicated workaround remains effective in the meantime.

We will post our next update by the end of the day. Thank you for your continued patience.

Our investigation is ongoing and we continue to actively monitor the situation. While we have been unable to reproduce the issue in our environment so far, we remain committed to identifying the root cause.

The previously communicated workaround remains effective in the meantime.

We will post our next update in approximately one hour. Thank you for your continued patience.

We are currently investigating the reported issue and our team is actively working to identify the root cause. 

At this time, we are not observing widespread or global impact, and the majority of users remain unaffected.

The previously communicated workaround continues to be effective. 

We will provide further updates as our investigation progresses. Thank you for your patience.