Cloud Infrastructure Instability

Status update: Platform restored.

Updating status: As a possible solution to the inconsistency, a possible workaround was suggested by the cloud provider. Our team performed this workaround suggested by the cloud provider and we are currently evaluating the results.

Soon we will give you a new position

Status Update:
We still haven't heard back with more details from our cloud provider.

We will update as soon as we have more information.

Updating status: Identified a storage layer failure from our cloud provider. It is being treated as a top priority.

We will update as soon as we have more information.

Status Update:
We have received a notification from our cloud provider indicating instability.
This instability is causing our infrastructure to fail.
Our engineering team is already in contact with the provider for more details.

We identified an increase in requests in the Builder database, responsible for the flow of Builder chatbots. As a contingency measure, we scaled up the database, but the scenario persists.

We are continuing to work towards normalization.

We have identified unexpected behavior in the Desk application causing messages to fail

We identified a degradation in the builder, which is causing slow responses by the bot.