Keboola - Notice history

Automatic scaling is turned back on and all platforms are fully operational and we'll continue monitoring all stacks. We're sorry for this inconvenience.

We're seeing full operations on all Azure stacks. We'll be enabling automatic scaling shortly and all jobs are currently processing as usual.

Azure is promising full mitigation within next four hours. We are closely monitoring the situation and once the issue is fixed we will resume all operations and turn autoscaling back on.

At this stage, we anticipate full mitigation within the next four hours as we continue to recover nodes. This means we expect recovery to happen by 23:20 UTC on 29 October 2025. We will provide another update on our progress within two hours, or sooner if warranted.

We have limited autoscaling of all Azure stacks to limit cascading the issue to new nodes and thus limiting the number of waiting jobs. We have seen partial improvement in certain regions so our hopes are up.

Microsoft has updated the impact and states that network infrastructure in all Azure regions is affected.

These issues can propagate downstream to AWS and GCP stacks, where the symptoms can include:

• Limited operations of some AI features (error explains, config description generator)

AWS reports continued improvement in recovery. All previously affected stacks are now operational. This incident has been resolved.

AWS reports progress with the mitigation and we are seeing signs of recovery. Jobs are successfully starting and finishing. We continue monitoring the issue.

The AWS outage is still ongoing and continues to affect our AWS US stack. We’re actively monitoring the situation and will share updates as soon as we have more details.

AWS reports another "significant API errors and connectivity issues across multiple services in the US-EAST-1 Region" which has impact on AWS US stack. Jobs are delayed.

We still see degraded performance in AWS US stack, the jobs are currently failing start.

The AWS incident in the US region is still not fully resolved. AWS is reporting errors leading to limited capacity to schedule new workloads, which may continue to affect the AWS US stack performance.

All stacks are operational except AWS US. The AWS US stack shows degraded performance, primarily affecting job listing visibility in the UI. Job execution is not impacted and continues to run as expected.

We’re still seeing issues on the AWS US stack following the AWS incident. Some jobs are stuck in processing and may not complete. We’re working on mitigation. Other stacks are running normally, and we’re continuing to monitor their performance.

Jobs are now running successfully on all stacks. AWS has reported significant signs of recovery. Orchestration has been unpaused on the AWS US stack, and all orchestrations scheduled between 10:30 and 11:30 (CET) will be gradually triggered until synchronization is restored.

We’re seeing jobs complete successfully on all stacks except the AWS US stack, so we’re resuming orchestrations for those unaffected stacks and continue monitoring the issue.

We’ve paused job scheduling to prevent further impact while the AWS incident is being resolved.

We identified multiple stacks are experiencing degraded job execution performance. The degradation is linked to platform images hosted in the affected AWS US region.

Based on report from AWS https://health.aws.amazon.com/health/status that this issue is affecting cloud on AWS us east 1 region only.

We will report back if we have more information