AWS EU (eu-central-1) - Operational
AWS EU (eu-central-1)
GCP EU (europe-west3) - Operational
GCP EU (europe-west3)
AWS US (us-east-1) - Operational
AWS US (us-east-1)
GCP US (us-east4) - Operational
GCP US (us-east4)
Azure NE (north-europe) - Operational
Azure NE (north-europe)
Notice history
View current statusJuly 2026
- ResolvedUTCResolvedUTC
This incident has been resolved. We're sorry for the inconvenience.
- InvestigatingUTCInvestigatingUTC
We are currently investigating intermittent failures of Kai, our in-platform AI assistant, on our AWS EU (connection.eu-central-1.keboola.com) infrastructure. Requests may time out or return an error, while other attempts succeed.
Our engineering team has been alerted and is actively investigating the root cause.
We apologize for the disruption and will provide an update within 1 hour or when new information is available.We are currently investigating this incident.
- Completed2026-07-25 at 06:44UTCCompleted2026-07-25 at 06:44UTCMaintenance has completed successfully.
- Planned2026-06-25 at 08:44UTCPlanned2026-06-25 at 08:44UTC
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) and AWS US multi-tenant stack (connection.keboola.com). This will take place on Saturday, July 25, 2026 between 05:50 and 07:15 UTC.
Effects of the Maintenance
During the above period, services will be scaled down and the processing of jobs may be delayed. For a very brief period (at around 06:00 UTC) the service will be unavailable for up to 10 minutes and APIs may respond with a 500 error code. After that, all services will scale up and start processing all jobs. No running jobs, data apps, or workspaces will be affected. Delayed scheduled flows and queued jobs will resume after the maintenance is completed.
Detailed Schedule
05:50–06:00 UTC: processing of new jobs stops.
06:00–07:00 UTC: service enhancement period.
07:15 UTC: processing of jobs resumes.
- ResolvedUTCResolvedUTC
The underlying Github incident was resolved. We haven't seen any issues since approximately 11:40 UTC.
- IdentifiedUTCIdentifiedUTC
We are currently investigating failures affecting components and Data Apps that load code from external Git repositories over SSH on all stacks. This appears to be related to an upstream incident with GitHub.
Users may experience:
Errors such as
Permission denied (publickey)when jobs clone code from Git repositoriesFailures running Custom Python components and Data Apps that fetch code from Git
Our engineering team is monitoring the situation and is actively investigating.
We apologize for the disruption and will provide an update within 1 hour or when new information is available.
- Completed2026-07-18 at 06:30UTCCompleted2026-07-18 at 06:30UTCMaintenance has completed successfully
- In progress2026-07-18 at 05:50UTCIn progress2026-07-18 at 05:50UTCMaintenance is now in progress
- Planned2026-06-25 at 09:52UTCPlanned2026-06-25 at 09:52UTC
We would like to inform you about the planned maintenance of all Keboola stacks hosted on Google Cloud (GCP).
During the database upgrades there will be a short service outage on all Google Cloud stacks, including all single-tenant stacks and the GCP multi-tenant stacks (connection.europe-west3.gcp.keboola.com and connection.us-east4.gcp.keboola.com). This will take place on Saturday, July 18, 2026 between 05:50 and 06:30 UTC.
Effects of the Maintenance
During the above period, services will be scaled down and the processing of jobs may be delayed. The databases are upgraded one by one, so between approximately 06:00 and 06:30 UTC each stack will experience a brief outage of up to a few minutes (not necessarily at the same time across stacks), during which APIs may respond with a 500 error code. After each database is back up, services scale up and resume processing. No running jobs, data apps, or workspaces will be affected. Delayed scheduled flows and queued jobs will resume after the maintenance is completed.
Detailed Schedule
05:50–06:00 UTC: processing of new jobs stops.
06:00–06:25 UTC: database maintenance; short per-stack outages occur within this window.
~06:30 UTC: processing of jobs resumes.
June 2026
- ResolvedUTCResolvedUTC
Resolved – Snowflake Service Restored
Snowflake has completed mitigation efforts and has restored service for the affected AWS US West (Oregon) region. The vendor has reported that processing efficiency improvements have been implemented and service health has returned to normal.
Following a period of monitoring, we have resumed all flow scheduling and processing activities. Backlogged workloads have been successfully processed, and we are no longer observing the internal Snowflake errors that were causing storage job failures.
At this time, all systems are operating normally and this incident is considered resolved.
Root Cause
The incident was caused by a Snowflake service disruption affecting AWS US West (Oregon). According to Snowflake, elevated load in a critical internal coordination service impacted request processing for a subset of workloads, resulting in query failures and internal SQL execution errors.
We will continue to monitor platform health, but no further customer impact is expected.
- MonitoringUTCMonitoringUTC
We are seeing significant improvements in service health and are no longer observing the Snowflake internal errors that were previously causing storage job failures.
Based on these improvements, we have resumed flow scheduling and processing. Queued work is currently being processed, and the platform is working through any backlog that accumulated during the incident.
Snowflake has reported that they are continuing to investigate the underlying cause of the issue and are implementing mitigations to improve processing efficiency within their infrastructure. While service appears stable at this time, the vendor incident remains open and an official resolution has not yet been declared.
We will continue to closely monitor the environment for any recurrence of errors or performance degradation and will provide additional updates as more information becomes available.
- IdentifiedUTCIdentifiedUTC
Snowflake continues to work on resolving the underlying service incident that is causing storage job failures and internal errors.
To prevent further impact and avoid additional failed processing, we have temporarily suspended scheduling of new flows. Existing queued work will not be scheduled until the Snowflake incident is resolved.
Once Snowflake confirms service restoration and we have validated system stability, we will resume flow scheduling. Processing will automatically continue from the point at which scheduling was suspended, and queued work will be backfilled to catch up on any delayed executions.
We are actively monitoring the situation and coordinating with Snowflake. We will provide further updates as more information becomes available.
- InvestigatingUTCInvestigatingUTC
We are currently experiencing failures in storage jobs due to an ongoing incident affecting Snowflake in US West region. Our systems are receiving internal errors from Snowflake, which is causing some storage job executions to fail or remain delayed. Snowflake has acknowledged an active service incident and is actively working on mitigation - https://status.snowflake.com/incidents/zn8xxp2qzpr1
Impact
Storage jobs may fail with internal errors.
Some job executions may be delayed or remain queued.
Other platform functionality may experience degraded performance if dependent on affected Snowflake services.
We are actively monitoring the situation. We will provide updates as more information becomes available.
May 2026
- ResolvedUTCResolvedUTC
This incident is now resolved. The affected project owners have been contacted directly.
- IdentifiedUTCIdentifiedUTC
We've identified the affected projects and disabled the Branched Storage on Snowflake feature there. Owners of the affected projects are being contacted.
- InvestigatingUTCInvestigatingUTC
We're investigating multiple reports of File Input Mapping with
processed_tagsnot working correctly on projects where Branched Storage on Snowflake (https://changelog.keboola.com/branched-storage-on-snowflake/) was recently enabled.We have confirmed the issue and are currently investigating the impact and possible solutions.