![[object Object]](/_next/image?url=https%3A%2F%2Finstatus.com%2Fuser-content%2Fv1759057094%2Fcuzrltwwcbxfpnmbxgti.png&w=3840&q=75)
AWS EU (eu-central-1) - Operational
AWS EU (eu-central-1)
GCP EU (europe-west3) - Operational
GCP EU (europe-west3)
AWS US (us-east-1) - Operational
AWS US (us-east-1)
GCP US (us-east4) - Operational
GCP US (us-east4)
Azure NE (north-europe) - Operational
Azure NE (north-europe)
Notice history
November 2025
- ResolvedResolvedThis incident has been resolved.
- UpdateUpdateWe are currently investigating this incident.
- InvestigatingInvestigating
We are currently investigating reports of outage affecting Job Service on our https://connection.eu-central-1.keboola.com/ stack. Users may experience slow response times, connection errors, UI errors.
Our engineering team has been alerted and is actively investigating the root cause.
We apologize for the disruption and will provide an update within 30 minutes or when new information is available.
- ResolvedResolvedThis incident has been resolved.
- MonitoringMonitoring
The issues should be resolved now, we're carefully monitoring the status.
- InvestigatingInvestigating
We are currently investigating reports of outage affecting Job Service on our https://connection.eu-central-1.keboola.com/ stack. Users may experience slow response times, connection errors, UI errors.
Our engineering team has been alerted and is actively investigating the root cause.
We apologize for the disruption and will provide an update within 30 minutes or when new information is available.
October 2025
- ResolvedResolved
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.
- UpdateUpdate
We're seeing full operations on all Azure stacks. We'll be enabling automatic scaling shortly and all jobs are currently processing as usual.
- MonitoringMonitoring
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.
- UpdateUpdate
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.
- UpdateUpdate
Microsoft has updated the impact and states that network infrastructure in all Azure regions is affected.
- IdentifiedIdentified
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)
- InvestigatingInvestigating
We are aware of performance degradation affecting our Azure infrastructure. This appears to be related to an upstream issue with Azure's announced Azure Portal Access Issues (https://azure.status.microsoft/en-us/status).
Symptoms include:
Failures to prepare new nodes to accept workload, causing some jobs to be in the waiting state.
Our team is monitoring the situation.
We apologize for the disruption and will provide an update within 30 minutes or when new information is available.
- Completed2025-10-25 at 06:15Completed2025-10-25 at 06:15Maintenance has completed successfully
- In progress2025-10-25 at 05:50In progress2025-10-25 at 05:50Maintenance is now in progress
- Planned2025-10-25 at 05:50Planned2025-10-25 at 05:50
We would like to inform you about the planned maintenance of all Keboola stacks hosted on Azure.
During the database upgrades there will be a short service outage on all Azure stacks, including all single-tenant stacks and Azure North Europe multi-tenant stack (connection.north-europe.azure.keboola.com). This will take place on Saturday, October 25, 2025 between 05:50 and 06:30 UTC.
Effects of the Maintenance
During the above period, services will be scaled down and the processing of jobs may be delayed. For a very brief period (at around 06:00 UTC) the service will be unavailable for up to 10 minutes and APIs may respond with a 500 error code. After that, all services will scale up and start processing all jobs. No running jobs, data apps, or workspaces will be affected. Delayed scheduled flows and queued jobs will resume after the maintenance is completed.
Detailed Schedule
05:50–06:00 UTC: processing of new jobs stops.
06:00–06:15 UTC: service enhancement period.
06:15 UTC: processing of jobs resumes.
- ResolvedResolved
AWS reports continued improvement in recovery. All previously affected stacks are now operational. This incident has been resolved.
- UpdateUpdate
AWS reports progress with the mitigation and we are seeing signs of recovery. Jobs are successfully starting and finishing. We continue monitoring the issue.
- UpdateUpdate
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.
- MonitoringMonitoring
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.
- InvestigatingInvestigating
We still see degraded performance in AWS US stack, the jobs are currently failing start.
- UpdateUpdate
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.
- UpdateUpdate
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.
- UpdateUpdate
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.
- UpdateUpdate
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.
- UpdateUpdate
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.
- MonitoringMonitoring
We’ve paused job scheduling to prevent further impact while the AWS incident is being resolved.
- UpdateUpdate
We identified multiple stacks are experiencing degraded job execution performance. The degradation is linked to platform images hosted in the affected AWS US region.
- IdentifiedIdentified
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
- InvestigatingInvestigating
We are currently investigating issue with jobs not starting on AWS US east stack.
Our team has been notified and is actively investigating.
Next update in 20 minutes or when new information is available.
September 2025
- Completed2025-09-20 at 04:13Completed2025-09-20 at 04:13
The maintenance has been completed, and all services have been scaled back up. The platform is fully operational, and jobs are now being processed as usual. All delayed jobs will be processed shortly. Thank you for your patience.
- In progress2025-09-20 at 04:00In progress2025-09-20 at 04:00
The announced partial maintenance is ongoing, and we are expecting downtime to begin any minute now.
- Planned2025-09-20 at 03:50Planned2025-09-20 at 03:50
We would like to inform you about the planned maintenance of all Keboola stacks hosted on Azure.
During the database upgrades there will be a short service outage on all Azure stacks, including all single-tenant stacks and Azure North Europe multi-tenant stack (connection.north-europe.azure.keboola.com). This will take place on Saturday, September 20, 2025 between 05:50 and 06:30 UTC.
Effects of the Maintenance
During the above period, services will be scaled down and the processing of jobs may be delayed. For a very brief period (at around 06:00 UTC) the service will be unavailable for up to 10 minutes and APIs may respond with a 500 error code. After that, all services will scale up and start processing all jobs. No running jobs, data apps, or workspaces will be affected. Delayed scheduled flows and queued jobs will resume after the maintenance is completed.
Detailed Schedule
05:50–06:00 UTC: processing of new jobs stops.
06:00–06:15 UTC: service enhancement period.
06:15 UTC: processing of jobs resumes.
- ResolvedResolvedWe identified issues on one of our Kubernetes nodes. The node was taken out of service, and all systems are now operating normally. No jobs were lost or failed; the impact was limited to visible error messages in the user interface. We apologize for the inconvenience caused.
- InvestigatingInvestigating
We are observing a major degradation in the Azure North Europe stack (connection.north-europe.azure.keboola.com). The root cause is still unknown and investigation is ongoing. Users may encounter various errors in the UI. Mitigations have been initiated.