Duration: 4 hours and 34 minutes

Affected Components: Azure NE (north-europe), AWS EU (eu-central-1), GCP EU (europe-west3)

Apr 28, 11:00:00 GMT+0
Identified - Since 11:00 UTC we're observing degraded performance of Kai AI features on our EU stacks (`connection.eu-central-1.keboola.com` and `connection.europe-west3.gcp.keboola.com` and `connection.north-europe.azure.keboola.com`) . The issue is caused by rate limiting (HTTP 429 Too Many Requests) from our upstream GCP Vertex AI provider and has been intermittently affecting responses. Users may experience slower responses, failed requests, or errors when interacting with Kai. Other platform functionality is not affected. Our team is actively monitoring the situation. Next update in 60 minutes. We apologize for the inconvenience..

Apr 28, 14:14:50 GMT+0
Monitoring - We see substantial reduction of throttled requests. Only one request was throttled in the past 15 minutes. .

Apr 28, 15:33:42 GMT+0
Resolved - We have seen no more throttled requests since 16:40\. The incident is resolved. .

Duration: 1 day and 46 minutes

Affected Components: Azure NE (north-europe), AWS EU (eu-central-1), AWS US (us-east-1), GCP EU (europe-west3), GCP US (us-east4)

Apr 28, 10:56:26 GMT+0
Identified - We're currently experiencing an issue with the Jira-powered support widget in the Keboola platform, which is preventing some support tickets from being submitted successfully. We're working with Atlassian to resolve this. **Workaround:** Please send your support requests directly to [support@keboola.com](mailto:support@keboola.com). We'll respond as usual. We'll update this notice as soon as the widget is restored..

Apr 28, 22:19:37 GMT+0
Identified - Atlassian pipeline pipeline was presumably fixed now and we're starting to gradually receive submitted tickets. We apologize for the delay in processing. We'll re-enable the support widget once we confirm it works reliably. Next update in 8 hours..

Apr 29, 11:42:04 GMT+0
Resolved - The issues affecting our Jira-powered support widget have been resolved. Atlassian has confirmed that their services are fully operational. Tickets submitted during the outage were delivered with a delay and we have responded to all of them. If you have not received a response, please re-submit your request. We apologize for the inconvenience. The issue was on the third-party vendor's side, not in the Keboola platform..

Duration: 25 minutes

Affected Components: Azure NE (north-europe)

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

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

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: 41 minutes

Affected Components: GCP EU (europe-west3)

Apr 23, 10:10:41 GMT+0
Investigating - We are currently investigating this incident where storage jobs running on BigQuery backend are failing..

Apr 23, 10:24:54 GMT+0
Identified - We have identified the root cause of the failing storage jobs on the BigQuery backend. The issue is isolated to internal/system projects and does not impact customer data or workloads. We are applying mitigation steps and continue to monitor the system closely..

Apr 23, 10:51:24 GMT+0
Resolved - Incident resolved. Mitigation has been applied and systems have returned to normal operation. Follow-up work is in progress to implement a permanent fix and prevent recurrence..

Duration: 7 hours and 41 minutes

Affected Components: AWS EU (eu-central-1), GCP EU (europe-west3)

Apr 21, 10:40:52 GMT+0
Resolved - The situation has stabilized and we are no longer observing elevated 429 responses from GCP Vertex AI on the affected EU stacks. Kai AI features are operating normally again. The incident is now resolved, and we will continue to monitor the situation. We apologize for the inconvenience..

Apr 21, 03:00:00 GMT+0
Investigating - Since approximately 05:00 UTC we have been observing degraded performance of Kai AI features on our EU stacks (`connection.eu-central-1.keboola.com` and `connection.europe-west3.gcp.keboola.com`). The issue is caused by rate limiting (HTTP 429 Too Many Requests) from our upstream GCP Vertex AI provider and has been intermittently affecting responses since this morning. Users may experience slower responses, failed requests, or errors when interacting with Kai. Other platform functionality is not affected. Our team is actively monitoring the situation. Next update in 60 minutes. We apologize for the inconvenience..

Duration: 2 hours and 12 minutes

Affected Components: Azure NE (north-europe), AWS EU (eu-central-1), AWS US (us-east-1), GCP EU (europe-west3), GCP US (us-east4)

Apr 20, 08:14:00 GMT+0
Investigating - We have detected an issue with Conditional Flow. Since 08:14 UTC users may experience `Failed to create task job for task` errors. Our engineering team is investigating the issue with high priority..

Apr 20, 09:42:07 GMT+0
Monitoring - We have rolled back to a previous working version and we are currently monitoring the result..

Apr 20, 10:25:48 GMT+0
Resolved - The issue affecting Conditional Flows has been fully resolved. All functionality has been restored, all jobs are now running as expected. Thank you for your patience while we worked to resolve this issue and sorry for any inconvenience this may have caused..

Duration: 2 days, 2 hours and 3 minutes

Affected Components: Azure NE (north-europe), AWS EU (eu-central-1), AWS US (us-east-1), GCP EU (europe-west3), GCP US (us-east4)

Apr 10, 11:30:00 GMT+0
Identified - We have identified an issue with SQL editor where certain query results breaks the page layout and makes it unusable. This issue affects all Keboola stacks. The root case has been identified and we're looking for a fix..

Apr 12, 13:33:15 GMT+0
Resolved - This incident has been resolved..

Duration: 50 minutes

Affected Components: AWS EU (eu-central-1), AWS US (us-east-1)

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

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

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 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: 1 hour and 34 minutes

Affected Components: GCP EU (europe-west3)

Mar 25, 13:47:01 GMT+0
Identified - We are continuing to work on a fix for this incident..

Mar 25, 14:04:16 GMT+0
Resolved - Storage job processing speeds have been restored. The bottleneck was identified as resource contention from an internal service. Systems are now stable, and all queued jobs have completed..

Mar 25, 12:30:00 GMT+0
Investigating - We are currently investigating this incident..

Duration: 1 day and 16 hours

Affected Components: Azure NE (north-europe), AWS EU (eu-central-1), AWS US (us-east-1), GCP EU (europe-west3), GCP US (us-east4)

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..

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

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

Duration: 1 day, 7 hours and 51 minutes

Affected Components: Azure NE (north-europe), AWS EU (eu-central-1), AWS US (us-east-1), GCP EU (europe-west3), GCP US (us-east4)

Mar 17, 22:33:50 GMT+0
Investigating - We have detected an issue with our MCP server that under some circumstances shows only `run_sync_action` tool or does not show any tools at all. Our engineering team is investigating the issue with high priority. We apologize for the disruption and will provide an update when new information is available..

Mar 17, 22:50:19 GMT+0
Investigating - Kai assistant (and other forms of platform chats) are not affected by this issue. Only external use of the MCP server (e. g. in Claude) are affected..

Mar 17, 23:05:40 GMT+0
Resolved - It seems that reauthorizing the MCP server resolves the issue. If you are experiencing missing or limited tools, please disconnect and reconnect the MCP server in your client. We are continuing to investigate the root cause to prevent recurrence..

Duration: 7 hours and 53 minutes

Affected Components: Azure NE (north-europe), AWS EU (eu-central-1), AWS US (us-east-1), GCP EU (europe-west3), GCP US (us-east4)

Mar 5, 01:00:00 GMT+0
Investigating - We have detected an issue with SMTP Sender component affecting all configurations. Users may experience application errors..

Mar 5, 08:53:00 GMT+0
Resolved - The issue affecting SMTP Sender component has been fully resolved. All functionality has been restored. Thank you for your patience while we worked to resolve this issue and sorry for any inconvenience this may have caused..

Duration: 17 minutes

Affected Components: Azure NE (north-europe), AWS EU (eu-central-1), AWS US (us-east-1), GCP EU (europe-west3), GCP US (us-east4)

Mar 3, 12:20:00 GMT+0
Investigating - We have detected an issue with job failures currently affecting MySQL writer. Jobs are ending with internal errors. Our engineering team is investigating the issue with high priority. We apologize for the disruption and will provide an update within 30 minutes or when new information is available..

Mar 3, 12:27:36 GMT+0
Monitoring - We have identified the issue and rolled back to the previous version. The platform should be stable. We continue to monitor..

Mar 3, 12:37:08 GMT+0
Resolved - The issue has been fully resolved. All functionality has been restored. Thank you for your patience while we worked to resolve this issue and sorry for any inconvenience this may have caused..

Duration: 1 hour and 20 minutes

Affected Components: Azure NE (north-europe)

Feb 21, 06:59:46 GMT+0
Identified - We have identified the root cause as database inconsistency. Only a low number of flow jobs are stuck in processing state despite all their child jobs are finished (mostly failed). Our team is now working on implementing a solution. We apologize for the disruption and will provide an update within 1 hour or when new information is available..

Feb 21, 06:15:00 GMT+0
Investigating - We are currently investigating reports of inconsistent flow jobs. Some users may be experiencing stuck flows. Our team has been notified and is actively investigating. Next update in 30 minutes or when new information is available..

Feb 21, 07:35:21 GMT+0
Resolved - The issue affecting stuck flow jobs has been resolved, and normal operation has been restored. We apologize for any inconvenience this may have caused..

Feb 23, 11:57:54 GMT+0
Resolved - We have identified multiple Storage jobs stuck in a processing state, blocking downstream jobs from proceeding. All of them have been terminated, and job processing should now be unblocked. We apologize for any inconvenience this may have caused. .

Duration: 25 minutes

Affected Components: Azure NE (north-europe)

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

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

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: 45 minutes

Affected Components: Azure NE (north-europe), AWS EU (eu-central-1), AWS US (us-east-1), GCP EU (europe-west3), GCP US (us-east4)

Feb 18, 00:40:00 GMT+0
Investigating - We are currently investigating this incident. Jobs are stuck in "Created" state. Next update in 30 minutes or sooner..

Feb 18, 01:25:00 GMT+0
Resolved - This incident has been resolved..

Feb 18, 00:40:00 GMT+0
Identified - New jobs are now starting as they should. We are continuing to work on a fix for jobs started between \~12:10 and \~12:50 UTC that are still stuck in "Created" state. Next update in 30 minutes or sooner..

Feb 18, 01:15:00 GMT+0
Monitoring - We implemented a fix, jobs should be now starting normally. We apologize for the inconvenience..

Duration: 2 hours and 44 minutes

Affected Components: AWS EU (eu-central-1), GCP US (us-east4)

Feb 16, 08:00:56 GMT+0
Investigating - We are currently investigating issues with failing action approvals with KAI assistant in GCP US stack..

Feb 16, 08:48:56 GMT+0
Investigating - We are currently investigating this incident..

Feb 16, 10:08:55 GMT+0
Monitoring - We have identified the root cause and deployed a fix. Please start a new fresh conversation in case you see any of the error messages: ``` messages.4: user messages must have non-empty content messages.11.content.1.text: cache_control cannot be set for empty text blocks ```.

Feb 16, 10:44:33 GMT+0
Resolved - This incident has been resolved..

Feb 16, 10:56:42 GMT+0
Resolved - This incident has been resolved. Few chats started approximately between 6:30 UTC and 8:30 UTC may still show the errors below, if you encounter these, please start a new chat. .

Duration: 2 hours and 47 minutes

Affected Components: Azure NE (north-europe), AWS EU (eu-central-1), AWS US (us-east-1), GCP EU (europe-west3), GCP US (us-east4)

Feb 12, 13:50:00 GMT+0
Investigating - We are currently investigating reports of some users being unable to access their projects after login. Affected users may encounter HTTP 403 or 404 errors. Our team is actively investigating the root cause. We will provide an update within 30 minutes. We apologize for any inconvenience..

Feb 12, 16:02:45 GMT+0
Identified - We have identified that this issue affects users with Guest and Read-only roles. Users with other roles should be able to use the platform normally. The issue is related to a release deployed at 13:50 UTC. We are currently working on a rollback. Next update within 30 minutes..

Feb 12, 16:36:30 GMT+0
Resolved - The issue has been fixed. We reverted the changes that caused the problem and full access has been restored across all regions. All users can now access their projects normally, including those with Guest and Read-only roles who were previously affected. Thank you for your patience..

Duration: 5 hours

Affected Components: Azure NE (north-europe), AWS EU (eu-central-1), AWS US (us-east-1), GCP EU (europe-west3), GCP US (us-east4)

Feb 12, 15:45:00 GMT+0
Resolved - The fix is now deployed (writer version 4.5.0). Full load configurations will self-heal automatically on the next run. Where manual intervention is needed, we will reach out to affected customers directly. We apologize for the inconvenience. If you have any questions, please contact our support team..

Feb 10, 15:10:00 GMT+0
Identified - We identified a bug in the Snowflake writer UI that **affected numeric data type length** settings for configurations created or tables added between **December 16, 2025 and February 12, 2026.** Custom numeric type lengths were silently reset to Snowflake defaults. For example, a DECIMAL(18,2) would become DECIMAL(38,0), effectively losing decimal precision. **What is NOT affected** Data Gateway, all Snowflake extractors and transformations, and data stored in Keboola Storage are not impacted by this issue..

Duration: 1 hour and 29 minutes

Feb 6, 10:27:00 GMT+0
Investigating - We're investigating reports of failing SSO/SAML logins in all single-tenant stacks. Google/Microsoft login in multi-tenant stacks is not affected..

Feb 6, 11:52:59 GMT+0
Identified - We have identified the root cause and rolling back the latest update. .

Feb 6, 11:56:08 GMT+0
Resolved - The issue affecting SSO/SAML login has been resolved, and normal operation has been restored. We apologize for any inconvenience this may have caused..

Duration: 8 minutes

Feb 2, 19:59:00 GMT+0
Resolved - This incident has been resolved..

Feb 2, 19:48:14 GMT+0
Investigating - We are currently investigating reports of outage affecting job on our [https://connection.north-europe.azure.keboola.com ](http://connection.north-europe.azure.keboola.com/)infrastructure. Users may have problems with their jobs not starting. 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..

Feb 2, 19:56:01 GMT+0
Identified - The problem with the jobs has been resolved. All systems are now operating normally. We apologize for any inconvenience this may have caused and thank you for your patience..

Duration: 4 hours and 32 minutes

Affected Components: Azure NE (north-europe)

Feb 2, 19:00:00 GMT+0
Investigating - We are aware of performance degradation affecting our Azure infrastructure in all regions. This appears to be related to an upstream issue with global Azure's cluster autoscaling services. We're able to process jobs with the currently provisioned capacity but we're unable to scale out new nodes for additional jobs. Symptoms: * Extended delays in jobs processing (jobs staying longer in waiting state) or jobs processing delayed indefinitely * Inability to start Data Apps or Workspaces Our team is monitoring the situation and waiting for Azure response to our incident reports. We apologize for the disruption and will provide an update within 1 hour or when new information is available..

Feb 2, 21:41:05 GMT+0
Identified - Azure have acknowledged the underlying issue and are working on a fix. See <https://azure.status.microsoft/en-gb/status> for more details. > **Active - Virtual Machine service management issues - Multiple regions** > > Impact statement: We are aware of an ongoing issue causing customers to receive error notifications when performing service management operations - such as create, delete, update, scaling, start, stop - for Virtual Machines (VMs). We're monitoring the issue closely and provide an update within 1 hour or when new information is available..

Feb 2, 23:05:52 GMT+0
Identified - From Azure Status: > Current status: We have determined that these issues were caused by a recent configuration change that affected public access to certain Microsoft‑managed storage accounts, used to host extension packages. We are actively working to mitigate impact, by updating our configuration to restore relevant access permissions. After applying this update in one region, we validated that it mitigates the issues customers were experiencing - we are making good progress applying this same mitigation across all impacted regions, in parallel where possible. We still expect that this will be completed across all impacted regions by approximately 00:00 UTC, approximately one hour from now. Our next update will be provided by then, or sooner if we have progress to share..

Feb 2, 23:22:43 GMT+0
Monitoring - We're seeing improvements in performance on all stacks, everything seems to be running fine and we're closely monitoring the situation..

Feb 2, 23:31:53 GMT+0
Resolved - The infrastructure issues affecting our Azure infrastructure have been resolved, all our Azure stacks are fully operational now. We apologize for the inconvenience and thank you for your patience. .

Duration: 2 hours and 2 minutes

Affected Components: GCP EU (europe-west3)

Jan 29, 20:15:13 GMT+0
Monitoring - We implemented a fix and are currently monitoring the result. We identified a couple of jobs processing (or terminating) longer also on other stacks. Altogether less than 20 jobs were affected. We apologize for the inconvenience..

Jan 29, 20:20:22 GMT+0
Resolved - This incident has been resolved..

Jan 29, 18:18:39 GMT+0
Investigating - We are aware of performance degradation affecting our GCP Europe-west3 infrastructure. Symptoms: * Jobs being stuck in termination phase Our team is working on resolving this issue. We apologize for the disruption and will provide an update within 1 hour or when new information is available..

Jan 29, 19:09:00 GMT+0
Identified - The root cause has been identified. New jobs will now terminate correctly, but some jobs remain stuck in terminating state. We are continuing to work on a fix..

Duration: 3 hours and 13 minutes

Affected Components: Azure NE (north-europe), AWS EU (eu-central-1), AWS US (us-east-1), GCP EU (europe-west3), GCP US (us-east4)

Jan 27, 12:58:35 GMT+0
Investigating - We are currently investigating reports of degraded performance affecting Keboola's AI assistant on all of our environments. Users may experience error, and configuration description not working. 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..

Jan 27, 13:51:16 GMT+0
Monitoring - The issue is an underlying issue in an upstream service. We will monitor the situation on [Azure Health](https://azure.status.microsoft/en-gb/status) page, and will keep this status updated..

Jan 27, 16:12:00 GMT+0
Resolved - The infrastructure issues affecting our AI Assistant infrastructure have been resolved. Microsoft has confirmed that their services are fully operational. We apologize for the inconvenience..

Duration: 37 minutes

Affected Components: Azure NE (north-europe)

Jan 21, 15:52:00 GMT+0
Resolved - This incident has been resolved. We have reverted an internal service causing the slowdown to the previous version and jobs processing is now back to normal. .

Jan 21, 15:15:00 GMT+0
Identified - We are investigating jobs processes delays in Azure North Europe stack. .

Duration: 20 minutes

Affected Components: Azure NE (north-europe), AWS EU (eu-central-1), AWS US (us-east-1), GCP EU (europe-west3), GCP US (us-east4)

Jan 19, 10:43:05 GMT+0
Investigating - We are currently investigating reports of degraded performace affecting Data Gateway on all ourstacks. Users may experience failures when creating new configurations of the Data Gateway app. 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..

Jan 19, 11:03:15 GMT+0
Resolved - We have rolled back to a previous working version and Data Gateway Apps are fully working. .

Duration: 24 minutes

Affected Components: AWS EU (eu-central-1), AWS US (us-east-1)

Jan 13, 10:59:55 GMT+0
Investigating - We are currently investigating reports of accessing sandboxes using Snowsight. Some users may have problems connecting to their sandboxes. This problem affects projects which are not using SSO login to Snowsight yet. Our team has been notified and is actively investigating. Next update in 30 minutes or when new information is available..

Jan 13, 11:23:28 GMT+0
Resolved - The problem should be resolved; we have deployed the latest functional version. We apologize for any inconvenience..

Duration: 4 hours and 38 minutes

Affected Components: Azure NE (north-europe), AWS EU (eu-central-1), AWS US (us-east-1), GCP EU (europe-west3), GCP US (us-east4)

Jan 8, 15:29:17 GMT+0
Identified - We have identified the cause of the problem and are gradually repairing the stacks. AWS EU and US was repaired first, and tasks are now running automatically without user intervention. All stacks should be repaired within an hour at the latest. We will keep you informed..

Jan 8, 15:35:00 GMT+0
Identified - GCP EU europe-west3 and US us-east4 has now been fixed, and all jobs will gradually start automatically. .

Jan 8, 15:45:11 GMT+0
Monitoring - The Azure NE (Northern Europe) stack has now also been fixed. We will now monitor the situation for at least another hour..

Jan 8, 15:53:35 GMT+0
Monitoring - We are monitoring all stacks and can see that the backlog of accumulated jobs is gradually clearing, but you may still experience minor delays. Everything should be back to normal soon..

Jan 8, 17:45:07 GMT+0
Monitoring - We have identified approximately ten stuck flows across multiple stacks and are processing them gradually. If you encounter a flow that is in a terminating state and does not complete, please contact our support team..

Jan 8, 19:02:45 GMT+0
Resolved - This incident has been complete resolved. We apologize for any inconvenience caused..

Jan 8, 14:24:40 GMT+0
Investigating - We are aware of performance degradation affecting our starting jobs. Symptoms: Slow task execution or tasks stuck in the create state. Our team is monitoring the situation and working to resolve this issue. We apologize for the disruption and will provide an update within 1 hour or when new information is available..

Duration: 44 minutes

Affected Components: Azure NE (north-europe), AWS EU (eu-central-1), AWS US (us-east-1), GCP EU (europe-west3), GCP US (us-east4)

Jan 7, 10:35:45 GMT+0
Identified - We are currently investigating this incident where Data apps are failing to start. We have identified a root cause and rolling out a fix that is expected to be deployed within 30 minutes. .

Jan 7, 11:19:31 GMT+0
Resolved - We have deployed a fix and data apps are now starting successfully. This incident has been resolved..

Duration: 40 minutes

Affected Components: GCP EU (europe-west3), GCP US (us-east4)

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..

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

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

Duration: 25 minutes

Affected Components: GCP EU (europe-west3)

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..

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

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

Duration: 25 minutes

Affected Components: Azure NE (north-europe)

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

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

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: Azure NE (north-europe)

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..

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..

Duration: 56 minutes

Affected Components: GCP US (us-east4)

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, 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 - 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..

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..

Duration: 20 minutes

Affected Components: Azure NE (north-europe)

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

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: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..