Duration: 25 minutes

Affected Components:

Oct 10, 06:15:00 GMT+0
Completed - Maintenance has completed successfully.

Oct 10, 05:50:01 GMT+0
Identified - Maintenance is now in progress.

Sep 29, 08:48:22 GMT+0
Identified - 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](http://connection.north-europe.azure.keboola.com)). This will take place on **Saturday, October 10, 2026 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..

Duration: 4 hours and 36 minutes

Affected Components: , , , ,

Sep 30, 15:52:45 GMT+0
Resolved - We have identified issues and deployed fix on all multi-tenant stacks..

Sep 30, 11:17:11 GMT+0
Investigating - Opening a Snowflake workspace in Snowsight via "Connect" fails with HTTP 400 for some projects using a dedicated Snowflake account, currently observed on the AWS EU (Frankfurt) stack. Jobs, transformations and the SQL Editor in Keboola are not affected and can be used in the meantime. We are investigating the issue together with Snowflake and will post an update here..

Duration: 1 hour and 19 minutes

Affected Components: , , , ,

Sep 29, 12:31:09 GMT+0
Resolved - This incident has been resolved..

Sep 29, 11:22:39 GMT+0
Monitoring - The issue is now fixed and data apps should now be starting normally. We apologize for the trouble. .

Sep 29, 11:11:51 GMT+0
Investigating - We are currently investigating this incident. The show an error similar to this: **Sandbox build failed** The app image could not be built. Next update in 30 minutes..

Duration: 5 hours and 51 minutes

Affected Components:

Sep 28, 09:51:19 GMT+0
Resolved - The issue affecting flows on the AWS EU (eu-central-1) stack has been resolved. An internal component responsible for advancing flows between phases was overloaded, which caused flows to remain in the processing state after their first phase. We have applied a fix and processed the backlog, and flows are running normally again. Flows that were delayed have continued automatically and do not need to be re-run. If you manually terminated a flow during the incident, please start it again. We are sorry for the inconvenience and are working on a permanent fix to prevent this from happening again..

Sep 28, 04:00:00 GMT+0
Investigating - We are investigating an issue affecting flows on the AWS EU (eu-central-1) stack. Flows may stay in the processing state after their first phase finishes, and the next phases start with a significant delay or not at all. Individual jobs and legacy orchestrations are not affected. Our engineering team is investigating the issue. We will provide an update within 30 minutes..

Duration: 12 minutes

Affected Components:

Sep 10, 17:22:11 GMT+0
Resolved - The issue affecting the Job Queue and Scheduler on our AWS US ([connection.keboola.com](http://connection.keboola.com)) infrastructure has been resolved. Scheduled flows and orchestrations are starting on time again and the Job Queue API is responding normally. Scheduled jobs that failed to start during the incident were not run automatically — please check your flows and re-run any missed executions manually if needed. We apologize for the disruption. Our team is continuing to monitor the platform to confirm the fix is stable..

Sep 10, 17:09:57 GMT+0
Investigating - We are currently investigating reports of degraded performance affecting the Job Queue and Scheduler on our AWS US (connection.keboola.com) infrastructure. Users may experience: * Scheduled flows and orchestrations failing to start or starting late * Intermittent errors (`502 Bad Gateway`) when creating or listing jobs via the Job Queue API or the UI Our engineering team has been alerted and is actively investigating the root cause. We apologize for the disruption and will provide an update within 1 hour or when new information is available..

Duration: 7 hours and 13 minutes

Affected Components:

Sep 8, 20:22:54 GMT+0
Resolved - This incident has been resolved..

Sep 8, 14:28:17 GMT+0
Monitoring - We implemented a fix, the backlog is currently processed, we are currently monitoring the situation..

Sep 8, 13:47:34 GMT+0
Identified - We have identified the cause, some queries are now executing, but execution is heavily slowed down. We are continuing to work on a fix for this incident. Next update in 30 minutes..

Sep 8, 13:10:05 GMT+0
Investigating - We are currently investigating issues with creating and using BigQuery workspaces on Europe West 3 [connection.europe-west3.gcp.keboola.com](https://connection.europe-west3.gcp.keboola.com/) stack. New workspaces are stuck in "initializing" state and queries timeout. Next update in 30 minutes..

Duration: 3 hours and 26 minutes

Affected Components: ,

Sep 4, 11:20:14 GMT+0
Resolved - This incident is resolved. Snowflake resolved their incident INC20000199 (<https://status.snowflake.com/incidents/fl9tkpj8d7hk>) at 10:10 UTC, after applying a fix at 09:00 UTC on 4 September 2026. Any jobs that failed during the disruption can be re-run. If you are still seeing problems, please contact our support. The root cause sits with Snowflake — see their incident report for details. We apologize for the disruption..

Sep 4, 08:55:06 GMT+0
Monitoring - Since approximately 08:30 UTC, jobs, transformations and workspaces are running normally again, and we are no longer seeing Snowflake errors. Snowflake has not yet resolved their incident INC20000199 (<https://status.snowflake.com/incidents/fl9tkpj8d7hk>), so we are keeping this post open and continuing to monitor until they confirm full recovery on their side. If you have jobs that failed during the disruption, they can be re-run now..

Sep 4, 07:54:30 GMT+0
Identified - Snowflake is currently experiencing an outage in its AWS Europe (Frankfurt) region. This is an upstream Snowflake failure — nothing changed on the Keboola side. Snowflake acknowledged the incident at 07:34 UTC on 4 September 2026, with an impact start of 07:00 UTC, and is tracking it as INC20000199: <https://status.snowflake.com/incidents/fl9tkpj8d7hk> DWH unavailability affects large part of the platform. What you may see: * Jobs failing or timing out with Snowflake errors * Transformations and data loads stalled or slow * Workspaces unavailable and unable to run any query * Failing Apps which depends on workspace access For details on the root cause, follow the original Snowflake incident. We apologize for the disruption..

Duration: 22 minutes

Affected Components:

Sep 1, 04:33:51 GMT+0
Resolved - This incident has been resolved..

Sep 1, 04:12:18 GMT+0
Investigating - We are currently investigating this incident..

Duration: 2 hours and 43 minutes

Affected Components: , , , ,

Aug 25, 17:02:24 GMT+0
Resolved - This incident has been resolved..

Aug 25, 14:58:56 GMT+0
Identified - We identified a problem and are actively working on a fix. The reauthorization might work..

Aug 25, 14:19:12 GMT+0
Investigating - We are currently investigating reports of degraded performance affecting MCP. Users may experience failed requests. Our engineering team has been alerted and is actively investigating the root cause. We apologize for the disruption and will provide an update within 1 hour or when new information is available..

Duration: 17 minutes

Affected Components: , , , ,

Aug 24, 14:44:00 GMT+0
Resolved - This incident has been resolved..

Aug 24, 14:26:58 GMT+0
Investigating - We have detected an issue with the Keboola MCP Server affecting connections from AI assistants and Keboola AI (KAI). Users may experience failed MCP server connections and errors when using KAI or logging into a project through it. Our engineering team is investigating the issue with high priority. We apologize for the disruption and will provide an update within 1 hour or when new information is available..

Duration: 1 hour

Affected Components: ,

Aug 22, 06:40:00 GMT+0
Completed - Maintenance has completed successfully.

Aug 22, 05:40:01 GMT+0
Identified - Maintenance is now in progress.

Jul 29, 11:21:46 GMT+0
Identified - We would like to inform you about the planned maintenance of the Keboola GCP EU multi-tenant stack ([connection.europe-west3.gcp.keboola.com](http://connection.europe-west3.gcp.keboola.com)) and the Keboola Azure North Europe multi-tenant stack ([connection.north-europe.azure.keboola.com](http://connection.north-europe.azure.keboola.com)). During the database upgrade there will be a short service outage on both stacks. This will take place on Saturday, August 22, 2026 between 05:40 and 07:00 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 during the service enhancement period 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:40–05:45 UTC: processing of new jobs stops. * 05:45–06:45 UTC: service enhancement period. * 07:00 UTC: processing of jobs resumes..

Duration: 1 hour

Affected Components: ,

Aug 15, 08:30:00 GMT+0
Completed - Maintenance has completed successfully.

Aug 15, 07:30:01 GMT+0
Identified - Maintenance is now in progress.

Jul 29, 11:18:53 GMT+0
Identified - We would like to inform you about the planned maintenance of the Keboola GCP US multi-tenant stack ([connection.us-east4.gcp.keboola.com](http://connection.us-east4.gcp.keboola.com)) and the Azure North Europe multi-tenant stack ([connection.north-europe.azure.keboola.com](http://connection.north-europe.azure.keboola.com)). During the database upgrades there will be a short service outage on both stacks. This will take place on **Saturday, August 15, 2026 between 07:30 and 09:00 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 during the service enhancement period 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** * 07:30–07:45 UTC: processing of new jobs stops. * 07:45–08:45 UTC: service enhancement period. * 09:00 UTC: processing of jobs resumes..

Duration: 2 hours and 46 minutes

Affected Components: , , , ,

Aug 6, 12:34:01 GMT+0
Resolved - Troubleshooting - extra column case: In some cases we experience that while the component was returning errors, some jobs completed but wrote extra, invalid columns into the destination table. After the fix, those columns are no longer returned and such jobs may fail on a column mismatch. If this affects you, drop the extra columns that were not present in the table before the incident, then re-run the configuration to backfill today's and yesterday's data. If problems persist, please contact our support. .

Aug 6, 12:14:57 GMT+0
Resolved - The fix has been released, the Google Ads data source now uses a supported Google Ads API version and configurations should run normally again. We recommend re-running your Google Ads configurations to backfill data for today and yesterday. If you still experience failures, please contact our support..

Aug 6, 10:28:36 GMT+0
Monitoring - We have identified the cause and are rolling out a fix to the Google Ads data source that upgrades it to a supported Google Ads API version. We are monitoring the rollout and job results.

Aug 6, 09:28:56 GMT+0
Investigating - We have detected an issue with the Google Ads data source affecting all projects that use it. Google has stopped accepting requests to the Google Ads API version currently used by the component, so extraction jobs fail with an `UNSUPPORTED_VERSION` error. Our engineering team is working on the upgrade with high priority. We apologize for the disruption and will provide an update within 1 hour or when new information is available..

Duration: 29 minutes

Affected Components:

Aug 6, 09:08:04 GMT+0
Resolved - This issue has been resolved. New Pay-as-you-go projects with a BigQuery backend can again be created on GCP US ([connection.us-east4.gcp.keboola.com](http://connection.us-east4.gcp.keboola.com)). Existing projects and running jobs were not affected at any point..

Aug 6, 08:39:08 GMT+0
Investigating - We are currently investigating an issue affecting new project creation on our GCP US (connection.us-east4.gcp.keboola.com) infrastructure. Users signing up through the Pay-as-you-go wizard may be unable to create new projects with a BigQuery backend. Existing projects and running jobs are not affected. Our engineering team has been alerted and is actively investigating the root cause. We apologize for the disruption and will provide an update within 1 hour or when new information is available..

Duration: 24 minutes

Affected Components:

Jul 29, 15:51:13 GMT+0
Resolved - This incident has been resolved..

Jul 29, 15:26:51 GMT+0
Investigating - We are currently investigating intermittent failures of Kai, our in-platform AI assistant, on our AWS EU (connection.eu-central-1.keboola.com) infrastructure. Requests may time out or return an error, while other attempts succeed. Our engineering team has been alerted and is actively investigating the root cause. We apologize for the disruption and will provide an update within 1 hour or when new information is available..

Duration: 51 minutes

Affected Components:

Jul 28, 14:56:10 GMT+0
Resolved - This incident has been resolved. We're sorry for the inconvenience. .

Jul 28, 12:20:00 GMT+0
Investigating - We are currently investigating intermittent failures of Kai, our in-platform AI assistant, on our AWS EU ([connection.eu-central-1.keboola.com](http://connection.eu-central-1.keboola.com)) infrastructure. Requests may time out or return an error, while other attempts succeed. Our engineering team has been alerted and is actively investigating the root cause. We apologize for the disruption and will provide an update within 1 hour or when new information is available.We are currently investigating this incident..

Duration: 29 days and 22 hours

Affected Components: ,

Jul 25, 06:44:28 GMT+0
Completed - Maintenance has completed successfully..

Jun 25, 08:44:45 GMT+0
Identified - We would like to inform you about the planned maintenance of Keboola stacks hosted on AWS. During the database upgrades there will be a short service outage on AWS stacks, including all single-tenant stacks and AWS EU multi-tenant stack ([connection.eu-central-1.keboola.com](http://connection.eu-central-1.keboola.com)) and AWS US multi-tenant stack ([connection.keboola.com](http://connection.keboola.com)). This will take place on **Saturday, July 25, 2026 between 05:50 and 07:15 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–07:00 UTC: service enhancement period. * 07:15 UTC: processing of jobs resumes..

Duration: 5 hours and 9 minutes

Affected Components: , , , ,

Jul 21, 13:38:44 GMT+0
Resolved - The [underlying Github incident](https://www.githubstatus.com/incidents/g40zcbvchny4) was resolved. We haven't seen any issues since approximately 11:40 UTC. .

Jul 21, 08:30:00 GMT+0
Identified - We are currently investigating failures affecting components and Data Apps that load code from external Git repositories over SSH on all stacks. This appears to be related to an [upstream incident with GitHub](https://www.githubstatus.com/incidents/g40zcbvchny4). Users may experience: * Errors such as `Permission denied (publickey)` when jobs clone code from Git repositories * Failures running Custom Python components and Data Apps that fetch code from Git Our engineering team is monitoring the situation and is actively investigating. We apologize for the disruption and will provide an update within 1 hour or when new information is available..

Duration: 40 minutes

Affected Components: ,

Jul 18, 06:30:00 GMT+0
Completed - Maintenance has completed successfully.

Jul 18, 05:50:01 GMT+0
Identified - Maintenance is now in progress.

Jun 25, 09:52:35 GMT+0
Identified - We would like to inform you about the planned maintenance of all Keboola stacks hosted on Google Cloud (GCP). During the database upgrades there will be a short service outage on all Google Cloud stacks, including all single-tenant stacks and the GCP multi-tenant stacks ([connection.europe-west3.gcp.keboola.com](http://connection.europe-west3.gcp.keboola.com) and [connection.us-east4.gcp.keboola.com](http://connection.us-east4.gcp.keboola.com)). This will take place on **Saturday, July 18, 2026 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. The databases are upgraded one by one, so between approximately 06:00 and 06:30 UTC each stack will experience a brief outage of up to a few minutes (not necessarily at the same time across stacks), during which APIs may respond with a 500 error code. After each database is back up, services scale up and resume processing. 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:25 UTC: database maintenance; short per-stack outages occur within this window. * \~06:30 UTC: processing of jobs resumes..

Duration: 26 minutes

Affected Components: , , , ,

Jul 8, 15:48:31 GMT+0
Resolved - We have released a fixed version of the `kds-team.ex-google-cloud-storage` component. There should be no more issues for jobs executed after \~15:40 UTC..

Jul 8, 15:22:22 GMT+0
Investigating - We have detected an issue with `kds-team.ex-google-cloud-storage` component starting at 12:00 UTC today. We're currently investigating the problem and possible impact. We apologize for the disruption and will provide an update when new information is available..

Duration: 2 minutes

Affected Components: , , , ,

Jun 29, 20:19:38 GMT+0
Resolved - This incident has been resolved..

Jun 29, 20:18:01 GMT+0
Monitoring - Today between approximately 17:15–20:00 UTC, a subset of jobs failed with a manifest validation error. The issue was introduced by a recent change to our job execution layer and affected jobs across all stacks. We identified the cause and reverted the change. Job processing has been restored to the previous working version, and new jobs are running normally. Affected jobs that failed during this window can be re-run. We are monitoring to confirm full recovery..

Duration: 18 hours and 3 minutes

Affected Components: , ,

Jun 30, 08:25:36 GMT+0
Resolved - Kai Assistant has returned to normal operation. We are no longer observing errors related to the upstream AI provider capacity constraints, and chat and suggestion requests are completing successfully..

Jun 29, 14:22:15 GMT+0
Investigating - We are currently observing elevated error rates with Kai Assistant on our EU stacks. A portion of chat messages and suggestions are failing due to temporary capacity constraints with an upstream AI provider. Affected functionality: Kai Assistant chat responses and suggestions. The issue is intermittent — many requests still succeed, but retries may be needed. Our team is actively monitoring the situation. No action is required from customers. We will provide an update as the situation improves..

Duration: 34 minutes

Affected Components: ,

Jun 26, 13:08:47 GMT+0
Resolved - This incident has been resolved. Pay as you go sign up is working again..

Jun 26, 12:35:53 GMT+0
Identified - We are continuing to work on a fix for this incident..

Jun 26, 12:34:26 GMT+0
Investigating - We are currently investigating this incident..

Duration: 1 hour and 34 minutes

Affected Components:

Jun 22, 22:24:39 GMT+0
Resolved - **Resolved – Snowflake Service Restored** Snowflake has completed mitigation efforts and has restored service for the affected AWS US West (Oregon) region. The vendor has reported that processing efficiency improvements have been implemented and service health has returned to normal. Following a period of monitoring, we have resumed all flow scheduling and processing activities. Backlogged workloads have been successfully processed, and we are no longer observing the internal Snowflake errors that were causing storage job failures. At this time, all systems are operating normally and this incident is considered resolved. **Root Cause** The incident was caused by a Snowflake service disruption affecting AWS US West (Oregon). According to Snowflake, elevated load in a critical internal coordination service impacted request processing for a subset of workloads, resulting in query failures and internal SQL execution errors. We will continue to monitor platform health, but no further customer impact is expected..

Jun 22, 22:05:59 GMT+0
Monitoring - We are seeing significant improvements in service health and are no longer observing the Snowflake internal errors that were previously causing storage job failures. Based on these improvements, we have resumed flow scheduling and processing. Queued work is currently being processed, and the platform is working through any backlog that accumulated during the incident. Snowflake has reported that they are continuing to investigate the underlying cause of the issue and are implementing mitigations to improve processing efficiency within their infrastructure. While service appears stable at this time, the vendor incident remains open and an official resolution has not yet been declared. We will continue to closely monitor the environment for any recurrence of errors or performance degradation and will provide additional updates as more information becomes available..

Jun 22, 21:27:43 GMT+0
Identified - Snowflake continues to work on resolving the underlying service incident that is causing storage job failures and internal errors. To prevent further impact and avoid additional failed processing, we have temporarily suspended scheduling of new flows. Existing queued work will not be scheduled until the Snowflake incident is resolved. Once Snowflake confirms service restoration and we have validated system stability, we will resume flow scheduling. Processing will automatically continue from the point at which scheduling was suspended, and queued work will be backfilled to catch up on any delayed executions. We are actively monitoring the situation and coordinating with Snowflake. We will provide further updates as more information becomes available..

Jun 22, 20:50:22 GMT+0
Investigating - We are currently experiencing failures in storage jobs due to an ongoing incident affecting Snowflake in US West region. Our systems are receiving internal errors from Snowflake, which is causing some storage job executions to fail or remain delayed. Snowflake has acknowledged an active service incident and is actively working on mitigation - <https://status.snowflake.com/incidents/zn8xxp2qzpr1> **Impact** * Storage jobs may fail with internal errors. * Some job executions may be delayed or remain queued. * Other platform functionality may experience degraded performance if dependent on affected Snowflake services. We are actively monitoring the situation. We will provide updates as more information becomes available..

Duration: 23 hours and 9 minutes

Affected Components:

Jun 19, 10:59:58 GMT+0
Resolved - This incident has been resolved. We're sorry for any incovenience. .

Jun 18, 13:14:15 GMT+0
Monitoring - We have attributed the failures to node scaleup events. We have increased static capacity to avoid scaling up before a fix is deployed. All jobs should now process as expected. We're monitoring the situation closely. .

Jun 18, 11:50:28 GMT+0
Investigating - We have detected increased job failure rate during a ndoe scaleup event in all Azure stacks. Users may experience application errors, retrying the job usually helps. Our engineering team is investigating the issue with high priority. We apologize for the disruption and will provide an update within 1 hour or when new information is available..

Duration: 19 minutes

Affected Components: ,

Jun 18, 09:17:38 GMT+0
Resolved - This incident has been resolved. Top up is operating normally..

Jun 18, 08:58:34 GMT+0
Investigating - We are currently investigating this incident..

Duration: 51 minutes

Affected Components:

Jun 15, 23:42:56 GMT+0
Resolved - This incident has been resolved. A temporary issue on Microsoft's side (Microsoft Container Registry) briefly delayed new compute nodes from starting in Azure NE, so some jobs waited longer than usual before running. No jobs failed or were lost - they only started later and completed normally once the registry recovered..

Jun 15, 22:51:28 GMT+0
Investigating - We're investigating jobs that remain in _waiting_ / _processing_ state longer than expected, or fail to start. Root cause analysis is in progress..

Duration: 8 hours and 58 minutes

Affected Components: ,

Jun 9, 16:28:24 GMT+0
Resolved - This incident has been resolved..

Jun 9, 15:48:16 GMT+0
Monitoring - We implemented a fix - it is being rolled out..

Jun 9, 07:30:00 GMT+0
Identified - Unable to save changes in the output mapping UI when trying to create a new bucket, and the feature to disable the legacy bucket prefix is enabled. We are continuing to work on a fix for this incident. As a temporary workaround, you can create the bucket manually and then select the existing bucket..

Duration: 56 minutes

Affected Components:

Jun 1, 08:28:14 GMT+0
Resolved - This incident has been resolved. We're sorry for this inconvenience..

Jun 1, 07:31:45 GMT+0
Investigating - The wildcard SSL certificate for Data App hubs on our Azure stacks expired on 2026-05-31, causing "not secure" errors when accessing Data Apps. We are renewing the certificates now and will update once service is restored..

Duration: 2 hours and 42 minutes

Affected Components:

May 26, 16:21:20 GMT+0
Resolved - This incident has been resolved..

May 26, 13:59:02 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result..

May 26, 13:39:50 GMT+0
Investigating - We are currently investigating reports of errors during startup of JS data apps in our GCP EU stack. Our team has been notified and is actively investigating. Next update in 1 hour or when new information is available..

Duration: 25 minutes

Affected Components:

Apr 25, 06:15:00 GMT+0
Completed - Maintenance has completed successfully.

Apr 25, 05:50:01 GMT+0
Identified - Maintenance is now in progress.

Apr 25, 05:50:00 GMT+0
Identified - 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](http://connection.north-europe.azure.keboola.com)). This will take place on **Saturday, April 25, 2026 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..

Duration: 50 minutes

Affected Components: ,

Mar 28, 06:40:27 GMT+0
Completed - Maintenance has completed successfully..

Mar 28, 05:50:01 GMT+0
Identified - Maintenance is now in progress.

Mar 28, 05:50:00 GMT+0
Identified - We would like to inform you about the planned maintenance of Keboola stacks hosted on AWS. During the database upgrades there will be a short service outage on AWS stacks, including all single-tenant stacks and AWS EU multi-tenant stack ([connection.eu-central-1.keboola.com](http://connection.eu-central-1.keboola.com)) and AWS US multi-tenant stack ([connection.keboola.com](http://connection.keboola.com)). This will take place on **Saturday, March 28, 2026 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 brief period (starting at around 06:00 UTC) the service will be unavailable for up to 1 hour 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..

Duration: 1 day and 16 hours

Affected Components: , , , ,

Mar 21, 06:30:00 GMT+0
Completed - Maintenance has completed successfully.

Mar 21, 05:50:01 GMT+0
Identified - Maintenance is now in progress.

Mar 21, 05:50:00 GMT+0
Identified - We would like to inform you about the planned maintenance of all Keboola stacks hosted on GCP. During the database upgrades there will be a short service outage on all GCP stacks, including all single-tenant stacks, GCP europe-west3 and us-east4 multi-tenant stacks. This will take place on **March 21st, 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:30 UTC: service enhancement period. * 06:30 UTC: processing of jobs resumes..

Duration: 25 minutes

Affected Components:

Feb 21, 06:15:00 GMT+0
Completed - Maintenance has completed successfully.

Feb 21, 05:50:01 GMT+0
Identified - Maintenance is now in progress.

Feb 21, 05:50:00 GMT+0
Identified - Microsoft Azure has rescheduled the underlying platform maintenance. As a result, the maintenance window for all Keboola stacks hosted on Azure will now take place on **Saturday, February 21, 2026, between 05:50 and 06:30 UTC**..

Feb 21, 05:50:00 GMT+0
Identified - 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](https://connection.north-europe.azure.keboola.com/)). This will take place on **Saturday, February 28, 2026 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..

Duration: 40 minutes

Affected Components: ,

Dec 6, 06:30:00 GMT+0
Completed - Maintenance has completed successfully.

Dec 6, 05:50:01 GMT+0
Identified - Maintenance is now in progress.

Dec 6, 05:50:00 GMT+0
Identified - We would like to inform you about the planned maintenance of all Keboola stacks hosted on GCP. During the database upgrades there will be a short service outage on all GCP stacks, including all single-tenant stacks, GCP europe-west3 and us-east4 multi-tenant stacks. This will take place on **December 6th, 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:30 UTC: service enhancement period. * 06:30 UTC: processing of jobs resumes..

Duration: 25 minutes

Affected Components:

Nov 22, 06:15:00 GMT+0
Completed - Maintenance has completed successfully.

Nov 22, 05:50:01 GMT+0
Identified - Maintenance is now in progress.

Nov 22, 05:50:00 GMT+0
Identified - We would like to inform you about unplanned maintenance on Keboola stack hosted in the GCP Europe West 3 region. Due to high database load, we will perform a database upgrade this Saturday during the routine maintenance window. A short service outage will occur. The maintenance is scheduled for **Saturday, November 22, between 05:50 and 06:15 UTC** **Effects of the Maintenance** During this period, services will be scaled down and job processing may be delayed. Around 06:00 UTC, the service will be unavailable for up to 10 minutes, and some APIs may return HTTP 500 errors. After the upgrade, all services will scale up and resume processing. No running jobs, data apps, or workspaces will be affected. Delayed scheduled flows and queued jobs will resume once maintenance is complete. **Detailed Schedule** * 05:50–06:00 UTC: Processing of new jobs stops. * 06:00–06:15 UTC: Database upgrade period. * 06:15 UTC: Processing of jobs resume..

Duration: 25 minutes

Affected Components:

Oct 25, 06:15:00 GMT+0
Completed - Maintenance has completed successfully.

Oct 25, 05:50:01 GMT+0
Identified - Maintenance is now in progress.

Oct 25, 05:50:00 GMT+0
Identified - 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](http://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..

Duration: 13 minutes

Affected Components:

Sep 20, 04:13:00 GMT+0
Completed - 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..

Sep 20, 04:00:00 GMT+0
Identified - The announced partial maintenance is ongoing, and we are expecting downtime to begin any minute now. .

Sep 20, 03:50:00 GMT+0
Identified - 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](http://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..

Duration: 56 minutes

Affected Components:

Aug 30, 04:26:00 GMT+0
Completed - 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..

Aug 30, 04:00:00 GMT+0
Identified - 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..

Aug 30, 03:30:00 GMT+0
Identified - 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..

Aug 30, 03:30:00 GMT+0
Identified - We would like to inform you about the planned maintenance of all Keboola stacks hosted on GCP. During the database upgrades there will be a short service outage on all GCP stacks, including all single-tenant stacks and GCP US and EU multi-tenant stacks ([connection.us-east4.gcp.keboola.com](http://connection.us-east4.gcp.keboola.com), [connection.europe-west3.gcp.keboola.com](http://connection.europe-west3.gcp.keboola.com)). This will take place on Saturday, August 30, 2025 between 05:30 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:30–06:00 UTC: processing of new jobs stops. * 06:00–06:15 UTC: service enhancement period. * 06:15 UTC: processing of jobs resumes..

Duration: 20 minutes

Affected Components:

Aug 16, 04:10:00 GMT+0
Completed - 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..

Aug 16, 04:00:00 GMT+0
Identified - 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..

Aug 16, 03:50:01 GMT+0
Identified - Maintenance is now in progress.

Aug 16, 03:50:00 GMT+0
Identified - 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](http://connection.north-europe.azure.keboola.com)). This will take place on **Saturday, August 16, 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..