Degraded performance API requests

We have been notified that the outage that affected the Microsoft servers has been resolved. We have received the root cause analysis and we will share a post mortem of this incident with the customers who have put in a request. If you would like to receive a post mortem of this outage, please contact us via support@bettyblocks.com. You will receive the post mortem report within 30 business days.

Betty Blocks will look at the possibilities within our power on how to mitigate similar situations in the future.

Our sincerest apologies for the inconvenience this outage has caused.

All our services are operational since the implementation of the temporary solution by Microsoft. We will continue to actively monitor our traffic. We are still awaiting a root cause analysis from Microsoft.

As of this moment we have not experienced connection errors since the implementation of the temporary solution by Microsoft. We are noticing that traffic is slower than before the connection issues, this is caused by the temporary solution. At the moment we are awaiting Root cause analysis from Microsoft. We will keep actively monitoring our traffic.

At the moment we see a significant improvement with regard to connectivity issues. Microsoft is continuing investigating the root cause of the outage. We are actively monitoring our traffic and are awaiting the ongoing investigation from Microsoft.

Microsoft have isolated the impacted devices and rerouted traffic to help bring the services back to a healthy state. This is not a 100% fix, but a temporarily solution to keep as much healthy as possible while they work on the underlying issues and roll out a fix for the outage.

We are still experiencing connection issues, we see a slight improvement. We are currently monitoring our traffic and are awaiting the ongoing investigation from Microsoft.

Unfortunately the suggested options from Microsoft have not resolved the connection issues. Microsoft has acknowledged issues throughout the western Europe region. They are currently continuing conducting further investigation. We will provide an update about the situation when an update from Microsoft is given. Our sincerest apologies for the connection issues we are currently experiencing on our platform

Currently, we are implementing the suggested options from Microsoft within a test cluster to see if this will solve the issues we are encountering on the platform. If this is successful, this will also be implemented on our Production cluster.

We have been provided with options by Microsoft, that in theory should resolve the symptoms of the problem. Together with Microsoft we are still investigating what the root cause is. We hope to inform you tomorrow with steps we can do to alleviate the symptoms.

We wanted to provide an update on the ongoing issue with HTTP API requests that some of you have been experiencing for some time now. We understand that this has been frustrating for you, and we apologize for any inconvenience this may have caused.

Our engineers have been working diligently to investigate the root cause of the issue and find a solution. We're currently collaborating with our third-party hosting provider, Microsoft Azure, to address the issue.

Please know that we're taking this issue seriously, and we're doing everything we can to resolve it as soon as possible. We're committed to providing you with the best possible service, and we apologize for any frustration this may have caused.

If you have any questions or concerns, please don't hesitate to reach out to us. We value your feedback and appreciate your patience as we work to address this issue.

We are still experiencing issues with HTTP API requests to the Microsoft Azure server. We are currently investigating this issue together with the Microsoft team.

We will provide an update about the situation around 17:00 CET

We are still experiencing issues with HTTP API requests to the Microsoft Azure server. We are currently investigating this issue together with the Microsoft team.

We will provide an update about the situation around 14:00 CET

We are still experiencing issues with HTTP API requests to the Microsoft Azure server. We are currently investigating this issue together with the Microsoft team. We will keep on working on the issues during the weekend.
We will provide new updates as soon as they are available.

We are still experiencing issues with HTTP API requests. You may encounter the following errors when performing HTTP API requests:

- SSL_connect returned=1 errno=0 state=error: bad signature
- SSL_connect returned=1 errno=0 state=error: certificate verify failed
- SSL_connect returned=1 errno=0 state=error: tlsv1 alert decrypt error
- SSL_connect returned=1 errno=0 state=error: bad ecpoint

We will provide an update about the situation around 16:00 CET

We are still experiencing issues with HTTP API requests. You may encounter the following errors when performing HTTP API requests:

- SSL_connect returned=1 errno=0 state=error: bad signature
- SSL_connect returned=1 errno=0 state=error: certificate verify failed
- SSL_connect returned=1 errno=0 state=error: tlsv1 alert decrypt error
- SSL_connect returned=1 errno=0 state=error: bad ecpoint

We will provide an update about the situation around 12:00 CET

Issues Background actions and ActionJS on public zone NL4 are resolved.

We are still experiencing issues with HTTP API requests. You may encounter the following errors when performing HTTP API requests:

- SSL_connect returned=1 errno=0 state=error: bad signature
- SSL_connect returned=1 errno=0 state=error: certificate verify failed
- SSL_connect returned=1 errno=0 state=error: tlsv1 alert decrypt error
- SSL_connect returned=1 errno=0 state=error: bad ecpoint

We will provide an update about the situation around 09:00 CET

We are still experiencing issues with HTTP API requests. The impact is major outage on public zone NL4. We will provide an update about the situation around 21:00 CET.

We are still experiencing issues with HTTP API requests. The impact is major outage on public zone NL4. We will provide an update about the situation around 16:30 CET.

We are still experiencing issues with HTTP API requests. The impact is major outage on public zone NL4. We will provide an update about the situation around 15:30 CET.

We are still experiencing issues HTTP API requests. The impact has been increased to a major outage on public zone NL4. We will provide an update about the situation around 14:30 CET

You may encounter the following errors when performing HTTP API requests:

- SSL_connect returned=1 errno=0 state=error: bad signature
- SSL_connect returned=1 errno=0 state=error: certificate verify failed
- SSL_connect returned=1 errno=0 state=error: tlsv1 alert decrypt error
- SSL_connect returned=1 errno=0 state=error: bad ecpoint

This issue has been occurring since Saturday the 4th of March. Our Product team has been investigating since the first report on Monday the 6th of March. We are in contact with Microsoft Azure Kubernetes services to understand and resolve the issue. We will provide an update about the situation around 14:00 CEST.