Keboola Status - Incident history https://keboolastatus.com Keboola Fri, 10 Apr 2026 11:30:00 +0000 SQL editor layout breaks after query Type: Incident 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. Type: Incident

Duration: 2 days, 2 hours and 3 minutes

Affected Components: , , , ,

<p><small>Apr <var data-var='date'> 10</var>, <var data-var='time'>11:30:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Apr <var data-var='date'> 12</var>, <var data-var='time'>13:33:15</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Fri, 10 Apr 2026 11:30:00 +0000 https://keboolastatus.com/incident/cmnvrsixv09cwf6xi0o2syxux https://keboolastatus.com/incident/cmnvrsixv09cwf6xi0o2syxux Scheduled Partial Maintenance of all Azure stacks Type: Maintenance Duration: 25 minutes Affected Components: Azure NE (north-europe) Apr 9, 07:00: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. Apr 9, 07:00:01 GMT+0 - Identified - Maintenance is now in progress Apr 9, 07:25:00 GMT+0 - Completed - Maintenance has completed successfully Type: Maintenance

Duration: 25 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>07:00:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>07:00:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Apr <var data-var='date'> 9</var>, <var data-var='time'>07:25:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Thu, 9 Apr 2026 07:00:00 +0000 https://keboolastatus.com/maintenance/cmnqc4suh00ijim3y61m280yz https://keboolastatus.com/maintenance/cmnqc4suh00ijim3y61m280yz Scheduled Partial Maintenance of AWS stacks – March 28, 2026 Type: Maintenance 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. Type: Maintenance

Duration: 50 minutes

Affected Components: ,

<p><small>Mar <var data-var='date'> 28</var>, <var data-var='time'>05:50:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Mar <var data-var='date'> 28</var>, <var data-var='time'>06:40:27</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully..</p> <p><small>Mar <var data-var='date'> 28</var>, <var data-var='time'>05:50:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> ]]> Sat, 28 Mar 2026 05:50:00 +0000 https://keboolastatus.com/maintenance/cmmiztx0200641005j6gbqoqy https://keboolastatus.com/maintenance/cmmiztx0200641005j6gbqoqy Degraded storage job performance Type: Incident 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. Type: Incident

Duration: 1 hour and 34 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 25</var>, <var data-var='time'>13:47:01</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Mar <var data-var='date'> 25</var>, <var data-var='time'>14:04:16</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> <p><small>Mar <var data-var='date'> 25</var>, <var data-var='time'>12:30:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> ]]> Wed, 25 Mar 2026 12:30:00 +0000 https://keboolastatus.com/incident/cmn622vh10043dvrip0dyxupu https://keboolastatus.com/incident/cmn622vh10043dvrip0dyxupu Scheduled Partial Maintenance of all GCP stacks - March 21, 2026 Type: Maintenance 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 Type: Maintenance

Duration: 1 day and 16 hours

Affected Components: , , , ,

<p><small>Mar <var data-var='date'> 21</var>, <var data-var='time'>05:50:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Mar <var data-var='date'> 21</var>, <var data-var='time'>05:50:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Mar <var data-var='date'> 21</var>, <var data-var='time'>06:30:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Sat, 21 Mar 2026 05:50:00 +0000 https://keboolastatus.com/maintenance/cmljaoezf023cogqgi64iv68i https://keboolastatus.com/maintenance/cmljaoezf023cogqgi64iv68i Keboola MCP not showing all available tools Type: Incident 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. Type: Incident

Duration: 1 day, 7 hours and 51 minutes

Affected Components: , , , ,

<p><small>Mar <var data-var='date'> 17</var>, <var data-var='time'>22:33:50</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Mar <var data-var='date'> 17</var>, <var data-var='time'>22:50:19</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Mar <var data-var='date'> 17</var>, <var data-var='time'>23:05:40</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> ]]> Tue, 17 Mar 2026 22:33:50 +0000 https://keboolastatus.com/incident/cmmv6vq7l02r1558g92ykg9qo https://keboolastatus.com/incident/cmmv6vq7l02r1558g92ykg9qo SMTP Sender component Application errors Type: Incident 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. Type: Incident

Duration: 7 hours and 53 minutes

Affected Components: , , , ,

<p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>01:00:00</var> GMT+0</small><br><strong>Investigating</strong> - We have detected an issue with SMTP Sender component affecting all configurations. Users may experience application errors..</p> <p><small>Mar <var data-var='date'> 5</var>, <var data-var='time'>08:53:00</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> ]]> Thu, 5 Mar 2026 01:00:00 +0000 https://keboolastatus.com/incident/cmmd9g4b60zoj50p1zmhgddtr https://keboolastatus.com/incident/cmmd9g4b60zoj50p1zmhgddtr Component Job Failures Type: Incident 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. Type: Incident

Duration: 17 minutes

Affected Components: , , , ,

<p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>12:20:00</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>12:27:36</var> GMT+0</small><br><strong>Monitoring</strong> - We have identified the issue and rolled back to the previous version. The platform should be stable. We continue to monitor..</p> <p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>12:37:08</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> ]]> Tue, 3 Mar 2026 12:20:00 +0000 https://keboolastatus.com/incident/cmmaksew40bcgdfl6ee2qaaq3 https://keboolastatus.com/incident/cmmaksew40bcgdfl6ee2qaaq3 Inconsistencies affecting Flow jobs in all Azure stacks Type: Incident 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. Type: Incident

Duration: 1 hour and 20 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 21</var>, <var data-var='time'>06:59:46</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Feb <var data-var='date'> 21</var>, <var data-var='time'>06:15:00</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Feb <var data-var='date'> 21</var>, <var data-var='time'>07:35:21</var> GMT+0</small><br><strong>Resolved</strong> - The issue affecting stuck flow jobs has been resolved, and normal operation has been restored. We apologize for any inconvenience this may have caused..</p> <p><small>Feb <var data-var='date'> 23</var>, <var data-var='time'>11:57:54</var> GMT+0</small><br><strong>Resolved</strong> - 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. .</p> ]]> Sat, 21 Feb 2026 06:15:00 +0000 https://keboolastatus.com/incident/cmlvy8i2k04fl12qqdm22h1pv https://keboolastatus.com/incident/cmlvy8i2k04fl12qqdm22h1pv Scheduled Partial Maintenance of all Azure stacks – February 21, 2026 Type: Maintenance 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. Type: Maintenance

Duration: 25 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 21</var>, <var data-var='time'>05:50:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Feb <var data-var='date'> 21</var>, <var data-var='time'>06:15:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Feb <var data-var='date'> 21</var>, <var data-var='time'>05:50:00</var> GMT+0</small><br><strong>Identified</strong> - 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**..</p> <p><small>Feb <var data-var='date'> 21</var>, <var data-var='time'>05:50:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> ]]> Sat, 21 Feb 2026 05:50:00 +0000 https://keboolastatus.com/maintenance/cmkv2kqlv068n9n713qhsq9z2 https://keboolastatus.com/maintenance/cmkv2kqlv068n9n713qhsq9z2 Jobs not starting on all stacks Type: Incident 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. Type: Incident

Duration: 45 minutes

Affected Components: , , , ,

<p><small>Feb <var data-var='date'> 18</var>, <var data-var='time'>00:40:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident. Jobs are stuck in "Created" state. Next update in 30 minutes or sooner..</p> <p><small>Feb <var data-var='date'> 18</var>, <var data-var='time'>01:25:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Feb <var data-var='date'> 18</var>, <var data-var='time'>00:40:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Feb <var data-var='date'> 18</var>, <var data-var='time'>01:15:00</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix, jobs should be now starting normally. We apologize for the inconvenience..</p> ]]> Wed, 18 Feb 2026 00:40:00 +0000 https://keboolastatus.com/incident/cmlusrv290pmfqmpznjxkmexj https://keboolastatus.com/incident/cmlusrv290pmfqmpznjxkmexj Issues with KAI assistant approvals Type: Incident 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. Type: Incident

Duration: 2 hours and 44 minutes

Affected Components: ,

<p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>08:00:56</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating issues with failing action approvals with KAI assistant in GCP US stack..</p> <p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>08:48:56</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>10:08:55</var> GMT+0</small><br><strong>Monitoring</strong> - 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 ```.</p> <p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>10:44:33</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Feb <var data-var='date'> 16</var>, <var data-var='time'>10:56:42</var> GMT+0</small><br><strong>Resolved</strong> - 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. .</p> ]]> Mon, 16 Feb 2026 08:00:56 +0000 https://keboolastatus.com/incident/cmloyrxy80rwbkiq0pdloqe5e https://keboolastatus.com/incident/cmloyrxy80rwbkiq0pdloqe5e Project Access Issues Type: Incident 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. Type: Incident

Duration: 2 hours and 47 minutes

Affected Components: , , , ,

<p><small>Feb <var data-var='date'> 12</var>, <var data-var='time'>13:50:00</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Feb <var data-var='date'> 12</var>, <var data-var='time'>16:02:45</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Feb <var data-var='date'> 12</var>, <var data-var='time'>16:36:30</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> ]]> Thu, 12 Feb 2026 13:50:00 +0000 https://keboolastatus.com/incident/cmljmnkvy006yqfu0b4jcsjhx https://keboolastatus.com/incident/cmljmnkvy006yqfu0b4jcsjhx Snowflake Writer — Data Type Length Bug Fix (All Stacks) Type: Incident 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. Type: Incident

Duration: 5 hours

Affected Components: , , , ,

<p><small>Feb <var data-var='date'> 12</var>, <var data-var='time'>15:45:00</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> <p><small>Feb <var data-var='date'> 10</var>, <var data-var='time'>15:10:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> ]]> Tue, 10 Feb 2026 15:10:00 +0000 https://keboolastatus.com/incident/cmlkz77qc00vc8kgkk23lng4n https://keboolastatus.com/incident/cmlkz77qc00vc8kgkk23lng4n SSO Login not working for single-tenant stacks Type: Incident 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. Type: Incident

Duration: 1 hour and 29 minutes

<p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>10:27:00</var> GMT+0</small><br><strong>Investigating</strong> - We're investigating reports of failing SSO/SAML logins in all single-tenant stacks. Google/Microsoft login in multi-tenant stacks is not affected..</p> <p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>11:52:59</var> GMT+0</small><br><strong>Identified</strong> - We have identified the root cause and rolling back the latest update. .</p> <p><small>Feb <var data-var='date'> 6</var>, <var data-var='time'>11:56:08</var> GMT+0</small><br><strong>Resolved</strong> - The issue affecting SSO/SAML login has been resolved, and normal operation has been restored. We apologize for any inconvenience this may have caused..</p> ]]> Fri, 6 Feb 2026 10:27:00 +0000 https://keboolastatus.com/incident/cmlatp3mb004ue4wqde9co4in https://keboolastatus.com/incident/cmlatp3mb004ue4wqde9co4in No new jobs are being created at AZN Type: Incident 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. Type: Incident

Duration: 8 minutes

<p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>19:59:00</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>19:48:14</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>19:56:01</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> ]]> Mon, 2 Feb 2026 19:48:14 +0000 https://keboolastatus.com/incident/cml5l152b04vhl8fqzmj5orzd https://keboolastatus.com/incident/cml5l152b04vhl8fqzmj5orzd Azure Scaling Issue in All Regions Type: Incident 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. Type: Incident

Duration: 4 hours and 32 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>19:00:00</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>21:41:05</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>23:05:52</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>23:22:43</var> GMT+0</small><br><strong>Monitoring</strong> - We're seeing improvements in performance on all stacks, everything seems to be running fine and we're closely monitoring the situation..</p> <p><small>Feb <var data-var='date'> 2</var>, <var data-var='time'>23:31:53</var> GMT+0</small><br><strong>Resolved</strong> - 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. .</p> ]]> Mon, 2 Feb 2026 19:00:00 +0000 https://keboolastatus.com/incident/cml5orsnw0be2yejscmj67wp9 https://keboolastatus.com/incident/cml5orsnw0be2yejscmj67wp9 [GCP Europe-west3] Jobs stuck in terminating phase Type: Incident 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. Type: Incident

Duration: 2 hours and 2 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>20:15:13</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>20:20:22</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> <p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>18:18:39</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Jan <var data-var='date'> 29</var>, <var data-var='time'>19:09:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> ]]> Thu, 29 Jan 2026 18:18:39 +0000 https://keboolastatus.com/incident/cmkzs2j44094bvibrs3w8a9v6 https://keboolastatus.com/incident/cmkzs2j44094bvibrs3w8a9v6 AI Assistant Issues Type: Incident 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. Type: Incident

Duration: 3 hours and 13 minutes

Affected Components: , , , ,

<p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>12:58:35</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>13:51:16</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Jan <var data-var='date'> 27</var>, <var data-var='time'>16:12:00</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> ]]> Tue, 27 Jan 2026 12:58:35 +0000 https://keboolastatus.com/incident/cmkwlr73s009h13vdc1vars8f https://keboolastatus.com/incident/cmkwlr73s009h13vdc1vars8f Jobs processing slowed down Type: Incident 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. Type: Incident

Duration: 37 minutes

Affected Components:

<p><small>Jan <var data-var='date'> 21</var>, <var data-var='time'>15:52:00</var> GMT+0</small><br><strong>Resolved</strong> - 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. .</p> <p><small>Jan <var data-var='date'> 21</var>, <var data-var='time'>15:15:00</var> GMT+0</small><br><strong>Identified</strong> - We are investigating jobs processes delays in Azure North Europe stack. .</p> ]]> Wed, 21 Jan 2026 15:15:00 +0000 https://keboolastatus.com/incident/cmko7jd3s00mknonfulycpbvi https://keboolastatus.com/incident/cmko7jd3s00mknonfulycpbvi Data Gateway App Issues Type: Incident 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. Type: Incident

Duration: 20 minutes

Affected Components: , , , ,

<p><small>Jan <var data-var='date'> 19</var>, <var data-var='time'>10:43:05</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Jan <var data-var='date'> 19</var>, <var data-var='time'>11:03:15</var> GMT+0</small><br><strong>Resolved</strong> - We have rolled back to a previous working version and Data Gateway Apps are fully working. .</p> ]]> Mon, 19 Jan 2026 10:43:05 +0000 https://keboolastatus.com/incident/cmkl1e4ze015012fti0c9xt51 https://keboolastatus.com/incident/cmkl1e4ze015012fti0c9xt51 Problem accessing workspaces using Snowsight Type: Incident 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. Type: Incident

Duration: 24 minutes

Affected Components: ,

<p><small>Jan <var data-var='date'> 13</var>, <var data-var='time'>10:59:55</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Jan <var data-var='date'> 13</var>, <var data-var='time'>11:23:28</var> GMT+0</small><br><strong>Resolved</strong> - The problem should be resolved; we have deployed the latest functional version. We apologize for any inconvenience..</p> ]]> Tue, 13 Jan 2026 10:59:55 +0000 https://keboolastatus.com/incident/cmkchcoo507dp5oe6dlthk4kx https://keboolastatus.com/incident/cmkchcoo507dp5oe6dlthk4kx Jobs not starting on all stacks Type: Incident 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. Type: Incident

Duration: 4 hours and 38 minutes

Affected Components: , , , ,

<p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>15:29:17</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>15:35:00</var> GMT+0</small><br><strong>Identified</strong> - GCP EU europe-west3 and US us-east4 has now been fixed, and all jobs will gradually start automatically. .</p> <p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>15:45:11</var> GMT+0</small><br><strong>Monitoring</strong> - The Azure NE (Northern Europe) stack has now also been fixed. We will now monitor the situation for at least another hour..</p> <p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>15:53:35</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>17:45:07</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>19:02:45</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been complete resolved. We apologize for any inconvenience caused..</p> <p><small>Jan <var data-var='date'> 8</var>, <var data-var='time'>14:24:40</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> ]]> Thu, 8 Jan 2026 14:24:40 +0000 https://keboolastatus.com/incident/cmk5jgqnd08c4hv4k7nx60kxp https://keboolastatus.com/incident/cmk5jgqnd08c4hv4k7nx60kxp Data apps failing to start Type: Incident 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. Type: Incident

Duration: 44 minutes

Affected Components: , , , ,

<p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>10:35:45</var> GMT+0</small><br><strong>Identified</strong> - 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. .</p> <p><small>Jan <var data-var='date'> 7</var>, <var data-var='time'>11:19:31</var> GMT+0</small><br><strong>Resolved</strong> - We have deployed a fix and data apps are now starting successfully. This incident has been resolved..</p> ]]> Wed, 7 Jan 2026 10:35:45 +0000 https://keboolastatus.com/incident/cmk3vuh7b004j213hcidmymgg https://keboolastatus.com/incident/cmk3vuh7b004j213hcidmymgg Microsoft Advertising Component Taking Longer Than Usual, Timing Out Type: Incident Duration: 1 hour and 7 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) Dec 28, 17:20:59 GMT+0 - Investigating - We have detected an issue with **kds-team.ex-bing-ads** component affecting configurations using it. Users may experience much longer job run times, or even timeouts. 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. Dec 28, 18:28:00 GMT+0 - Resolved - The issue with the **kds-team.ex-bing-ads** component has been resolved. All affected configurations are now completing successfully within expected timeframes. Our investigation found no issues with the component itself. We believe the delays were caused by a temporary issue with an upstream service provider. Thank you for your patience, and we apologize for any inconvenience this may have caused. Type: Incident

Duration: 1 hour and 7 minutes

Affected Components: , , , ,

<p><small>Dec <var data-var='date'> 28</var>, <var data-var='time'>17:20:59</var> GMT+0</small><br><strong>Investigating</strong> - We have detected an issue with **kds-team.ex-bing-ads** component affecting configurations using it. Users may experience much longer job run times, or even timeouts. 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..</p> <p><small>Dec <var data-var='date'> 28</var>, <var data-var='time'>18:28:00</var> GMT+0</small><br><strong>Resolved</strong> - The issue with the **kds-team.ex-bing-ads** component has been resolved. All affected configurations are now completing successfully within expected timeframes. Our investigation found no issues with the component itself. We believe the delays were caused by a temporary issue with an upstream service provider. Thank you for your patience, and we apologize for any inconvenience this may have caused..</p> ]]> Sun, 28 Dec 2025 17:20:59 +0000 https://keboolastatus.com/incident/cmjpzx3k3090k4qg3ffcy3jhz https://keboolastatus.com/incident/cmjpzx3k3090k4qg3ffcy3jhz Jobs are slowing down Type: Incident Duration: 3 hours and 56 minutes Affected Components: GCP US (us-east4) Dec 18, 15:30:00 GMT+0 - Investigating - We are currently investigating this incident. Dec 18, 17:14:46 GMT+0 - Investigating - We are currently investigating this incident. Dec 18, 18:06:56 GMT+0 - Identified - We identified root cause and working on mitigating issue. Dec 18, 18:54:38 GMT+0 - Monitoring - Jobs are processing normally again and we are monitoring situation. Dec 18, 19:25:50 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 3 hours and 56 minutes

Affected Components:

<p><small>Dec <var data-var='date'> 18</var>, <var data-var='time'>15:30:00</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Dec <var data-var='date'> 18</var>, <var data-var='time'>17:14:46</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating this incident..</p> <p><small>Dec <var data-var='date'> 18</var>, <var data-var='time'>18:06:56</var> GMT+0</small><br><strong>Identified</strong> - We identified root cause and working on mitigating issue..</p> <p><small>Dec <var data-var='date'> 18</var>, <var data-var='time'>18:54:38</var> GMT+0</small><br><strong>Monitoring</strong> - Jobs are processing normally again and we are monitoring situation..</p> <p><small>Dec <var data-var='date'> 18</var>, <var data-var='time'>19:25:50</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 18 Dec 2025 15:30:00 +0000 https://keboolastatus.com/incident/cmjbqeudt0202q1ks8mtwf15o https://keboolastatus.com/incident/cmjbqeudt0202q1ks8mtwf15o High API Error Rate Affecting - Queue Public API Type: Incident Duration: 39 minutes Affected Components: GCP US (us-east4) Dec 16, 15:52:01 GMT+0 - Investigating - We are currently investigating reports of High API Error Rate Affecting - Queue Public API. Our team has been notified and is actively investigating. Next update in 1 hour when new information is available. Dec 16, 16:28:32 GMT+0 - Identified - We are continuing to work on a fix for this incident. Dec 16, 16:31:07 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 39 minutes

Affected Components:

<p><small>Dec <var data-var='date'> 16</var>, <var data-var='time'>15:52:01</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating reports of High API Error Rate Affecting - Queue Public API. Our team has been notified and is actively investigating. Next update in 1 hour when new information is available..</p> <p><small>Dec <var data-var='date'> 16</var>, <var data-var='time'>16:28:32</var> GMT+0</small><br><strong>Identified</strong> - We are continuing to work on a fix for this incident..</p> <p><small>Dec <var data-var='date'> 16</var>, <var data-var='time'>16:31:07</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Tue, 16 Dec 2025 15:52:01 +0000 https://keboolastatus.com/incident/cmj8rghg100kfq1p0461rkljw https://keboolastatus.com/incident/cmj8rghg100kfq1p0461rkljw Snowflake Outage in multiple regions Type: Incident Duration: 13 hours and 2 minutes Affected Components: AWS US (us-east-1) Dec 16, 03:40:00 GMT+0 - Identified - We are currently experiencing failures in storage jobs importing data into tables due to an ongoing Snowflake incident affecting our stack’s region (US west). We are monitoring the snowflake incident and will wait for the fix from their side. For more info about the Snowflake incident see: <https://status.snowflake.com/incidents/xdxj4klf7sc5> Dec 16, 09:28:11 GMT+0 - Identified - We continue to monitor the Snowflake incident and are seeing a reduction in table import job errors, though the issue is not yet fully resolved. Dec 16, 10:37:29 GMT+0 - Identified - Snowflake has indicated that service is expected to be restored by 14:00 UTC. We will continue to monitor and provide updates. Dec 16, 12:34:30 GMT+0 - Identified - Snowflake is executing mitigation efforts. As mitigation progresses, customers may see gradual improvements while resolution steps are completed. Snowflake’s current estimate for full service restoration is 15:00 UTC. Dec 16, 15:20:45 GMT+0 - Monitoring - We are seeing signs of improvement and are no longer observing any errors in our systems. While Snowflake continues to mitigate the issue, our services are currently operating normally. We will continue to closely monitor the situation and provide updates if anything changes. Dec 16, 16:42:09 GMT+0 - Resolved - This incident has been resolved. Snowflake resolved the incident. Type: Incident

Duration: 13 hours and 2 minutes

Affected Components:

<p><small>Dec <var data-var='date'> 16</var>, <var data-var='time'>03:40:00</var> GMT+0</small><br><strong>Identified</strong> - We are currently experiencing failures in storage jobs importing data into tables due to an ongoing Snowflake incident affecting our stack’s region (US west). We are monitoring the snowflake incident and will wait for the fix from their side. For more info about the Snowflake incident see: <https://status.snowflake.com/incidents/xdxj4klf7sc5>.</p> <p><small>Dec <var data-var='date'> 16</var>, <var data-var='time'>09:28:11</var> GMT+0</small><br><strong>Identified</strong> - We continue to monitor the Snowflake incident and are seeing a reduction in table import job errors, though the issue is not yet fully resolved..</p> <p><small>Dec <var data-var='date'> 16</var>, <var data-var='time'>10:37:29</var> GMT+0</small><br><strong>Identified</strong> - Snowflake has indicated that service is expected to be restored by 14:00 UTC. We will continue to monitor and provide updates..</p> <p><small>Dec <var data-var='date'> 16</var>, <var data-var='time'>12:34:30</var> GMT+0</small><br><strong>Identified</strong> - Snowflake is executing mitigation efforts. As mitigation progresses, customers may see gradual improvements while resolution steps are completed. Snowflake’s current estimate for full service restoration is 15:00 UTC..</p> <p><small>Dec <var data-var='date'> 16</var>, <var data-var='time'>15:20:45</var> GMT+0</small><br><strong>Monitoring</strong> - We are seeing signs of improvement and are no longer observing any errors in our systems. While Snowflake continues to mitigate the issue, our services are currently operating normally. We will continue to closely monitor the situation and provide updates if anything changes..</p> <p><small>Dec <var data-var='date'> 16</var>, <var data-var='time'>16:42:09</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved. Snowflake resolved the incident..</p> ]]> Tue, 16 Dec 2025 03:40:00 +0000 https://keboolastatus.com/incident/cmj8b9og30dddntvby8dqftxd https://keboolastatus.com/incident/cmj8b9og30dddntvby8dqftxd Storage Events missing in the UI Type: Incident Duration: 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) Dec 11, 14:51:40 GMT+0 - Investigating - We are currently investigating an issue with displaying storage events in the UI. Preliminary investigation shows that this would be just a UI issue of displaying the events. Next update in 1h or earlier. Dec 11, 15:03:09 GMT+0 - Monitoring - We implemented a fix. If you still encounter the issue with listing storage events, please reload the UI. Dec 11, 15:04:02 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 12 minutes

Affected Components: , , , ,

<p><small>Dec <var data-var='date'> 11</var>, <var data-var='time'>14:51:40</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating an issue with displaying storage events in the UI. Preliminary investigation shows that this would be just a UI issue of displaying the events. Next update in 1h or earlier..</p> <p><small>Dec <var data-var='date'> 11</var>, <var data-var='time'>15:03:09</var> GMT+0</small><br><strong>Monitoring</strong> - We implemented a fix. If you still encounter the issue with listing storage events, please reload the UI..</p> <p><small>Dec <var data-var='date'> 11</var>, <var data-var='time'>15:04:02</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Thu, 11 Dec 2025 14:51:40 +0000 https://keboolastatus.com/incident/cmj1k3m1700n947dxucov01tz https://keboolastatus.com/incident/cmj1k3m1700n947dxucov01tz Scheduled Partial Maintenance of all GCP stacks - December 6, 2025 Type: Maintenance 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 Type: Maintenance

Duration: 40 minutes

Affected Components: ,

<p><small>Dec <var data-var='date'> 6</var>, <var data-var='time'>05:50:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Dec <var data-var='date'> 6</var>, <var data-var='time'>05:50:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Dec <var data-var='date'> 6</var>, <var data-var='time'>06:30:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Sat, 6 Dec 2025 05:50:00 +0000 https://keboolastatus.com/maintenance/cmhj6xvr400luk35kn8f7u7zg https://keboolastatus.com/maintenance/cmhj6xvr400luk35kn8f7u7zg Unplanned Partial Maintenance of GCP Europe West 3 stack Type: Maintenance 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 Type: Maintenance

Duration: 25 minutes

Affected Components:

<p><small>Nov <var data-var='date'> 22</var>, <var data-var='time'>05:50:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Nov <var data-var='date'> 22</var>, <var data-var='time'>05:50:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Nov <var data-var='date'> 22</var>, <var data-var='time'>06:15:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> ]]> Sat, 22 Nov 2025 05:50:00 +0000 https://keboolastatus.com/maintenance/cmi8np0c70a20nyit7sh2gi39 https://keboolastatus.com/maintenance/cmi8np0c70a20nyit7sh2gi39 Scheduled Partial Maintenance of all Azure stacks – October 25, 2025 Type: Maintenance 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. Type: Maintenance

Duration: 25 minutes

Affected Components:

<p><small>Oct <var data-var='date'> 25</var>, <var data-var='time'>05:50:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Oct <var data-var='date'> 25</var>, <var data-var='time'>06:15:00</var> GMT+0</small><br><strong>Completed</strong> - Maintenance has completed successfully.</p> <p><small>Oct <var data-var='date'> 25</var>, <var data-var='time'>05:50:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> ]]> Sat, 25 Oct 2025 05:50:00 +0000 https://keboolastatus.com/maintenance/cmgj4q1vy041n6w9oo8e4hr8o https://keboolastatus.com/maintenance/cmgj4q1vy041n6w9oo8e4hr8o Scheduled Partial Maintenance of all Azure stacks Type: Maintenance 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. Type: Maintenance

Duration: 13 minutes

Affected Components:

<p><small>Sep <var data-var='date'> 20</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br><strong>Identified</strong> - The announced partial maintenance is ongoing, and we are expecting downtime to begin any minute now. .</p> <p><small>Sep <var data-var='date'> 20</var>, <var data-var='time'>03:50:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Sep <var data-var='date'> 20</var>, <var data-var='time'>04:13:00</var> GMT+0</small><br><strong>Completed</strong> - 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..</p> ]]> Sat, 20 Sep 2025 03:50:00 +0000 https://keboolastatus.com/maintenance/cmfz830fx006p7rdiltdjuws4 https://keboolastatus.com/maintenance/cmfz830fx006p7rdiltdjuws4 Scheduled Partial Maintenance of all GCP stacks Type: Maintenance 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. Type: Maintenance

Duration: 56 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 30</var>, <var data-var='time'>03:30:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Aug <var data-var='date'> 30</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Aug <var data-var='date'> 30</var>, <var data-var='time'>03:30:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Aug <var data-var='date'> 30</var>, <var data-var='time'>04:26:00</var> GMT+0</small><br><strong>Completed</strong> - 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..</p> ]]> Sat, 30 Aug 2025 03:30:00 +0000 https://keboolastatus.com/maintenance/cmfzaha7a005ldb6ut92xkwcw https://keboolastatus.com/maintenance/cmfzaha7a005ldb6ut92xkwcw Scheduled Partial Maintenance of all Azure stacks Type: Maintenance 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. Type: Maintenance

Duration: 20 minutes

Affected Components:

<p><small>Aug <var data-var='date'> 16</var>, <var data-var='time'>03:50:01</var> GMT+0</small><br><strong>Identified</strong> - Maintenance is now in progress.</p> <p><small>Aug <var data-var='date'> 16</var>, <var data-var='time'>04:10:00</var> GMT+0</small><br><strong>Completed</strong> - 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..</p> <p><small>Aug <var data-var='date'> 16</var>, <var data-var='time'>04:00:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Aug <var data-var='date'> 16</var>, <var data-var='time'>03:50:00</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> ]]> Sat, 16 Aug 2025 03:50:00 +0000 https://keboolastatus.com/maintenance/cmg0nany200sqcu8omxyoupdl https://keboolastatus.com/maintenance/cmg0nany200sqcu8omxyoupdl