After more than 11 years of sharing updates on this blog, it’s time for an upgrade.
All future status updates will now live on our new dedicated status page: keboolastatus.com.
Please bookmark the new page to stay informed and enjoy the improved features. No action needed if you’re subscribed by email — all subscriptions have been moved, and email updates will continue without interruption.
Thank you for following along here — see you at our new home!
We are currently investigating issues when creating new Python and R Workspace with Large backend on AWS stacks.
Next update in 30 minutes.
We're sorry for this inconvenience.
UPDATE 11:29:03 UTC The issue has been resolved. All workspace operations returned to normal.
The announced partial maintenance has just started. The platform has been scaled down and is no longer accepting new jobs. We expect a brief downtime in 10 minutes, around 06:00 UTC. We will update this post with the progress of the partial maintenance.
Update 06:00 UTC: The announced partial maintenance is ongoing, and we are expecting downtime to begin any minute now. We will continue to update this post as the maintenance progresses.
Update 06:13 UTC: 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.
We are currently investigating issues when creating new Pay As You Go projects on https://connection.us-east4.gcp.keboola.com/.
UPDATE 08:13 UTC: The issue was resolved, Pay As You Go sign ups are now fully operational.
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.
Update 19:08 UTC
We 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.
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
We're investigating an outage in Project Consumption dashboard on connection.us-east4.gcp.keboola.com stack.
UPDATE 07:10 UTC: Project Consumption and Organization Usage dashboards are back online.
We're sorry for this inconvenience.
The announced partial maintenance has just started. The platform has been scaled down and is no longer accepting new jobs. We expect a brief downtime in 20 minutes, around 06:00 UTC. We will update this post with the progress of the partial maintenance.
Update 06:00 UTC: The announced partial maintenance is ongoing, and we are expecting downtime to begin any minute now. We will continue to update this post as the maintenance progresses.
Update 06:26 UTC: 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.
Due to an underlying infrastructure issue, some jobs failed prematurely in North Europe (Azure). The root cause is still under investigation. Please contact support if your job was affected. We apologize for the disruption and thank you for your understanding.
The jobs should be running again as usual
In the beta version of conditional flows, when a flow is executed in the development branch, the child jobs are mistakenly executed in the main (production) branch.
We are already investigating this issue and preparing a fix. If your production data was affected, we sincerely apologize for the inconvenience.
2025-08-27T13:54:39 UTC – We have deployed a fix that ensures conditional flows created on a branch are executed within that same branch, including storage, component configuration, transformations, or data apps version from the branch where the conditional flow was created. As a result, jobs from the development branch are no longer running in main (production) with main configurations.