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
June 2026
- ResolvedResolved
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.
- MonitoringMonitoring
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.
- IdentifiedIdentified
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.
- InvestigatingInvestigating
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
- ResolvedResolved
This incident is now resolved. The affected project owners have been contacted directly.
- IdentifiedIdentified
We've identified the affected projects and disabled the Branched Storage on Snowflake feature there. Owners of the affected projects are being contacted.
- InvestigatingInvestigating
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.
April 2026
- ResolvedResolved
The issues affecting our Jira-powered support widget have been resolved. Atlassian has confirmed that their services are fully operational.
Tickets submitted during the outage were delivered with a delay and we have responded to all of them. If you have not received a response, please re-submit your request.
We apologize for the inconvenience. The issue was on the third-party vendor's side, not in the Keboola platform.
- UpdateUpdate
Atlassian pipeline pipeline was presumably fixed now and we're starting to gradually receive submitted tickets. We apologize for the delay in processing. We'll re-enable the support widget once we confirm it works reliably. Next update in 8 hours.
- IdentifiedIdentified
We're currently experiencing an issue with the Jira-powered support widget in the Keboola platform, which is preventing some support tickets from being submitted successfully. We're working with Atlassian to resolve this.
Workaround: Please send your support requests directly to support@keboola.com. We'll respond as usual.
We'll update this notice as soon as the widget is restored.
- Completed2026-04-25 at 06:15Completed2026-04-25 at 06:15Maintenance has completed successfully
- In progress2026-04-25 at 05:50In progress2026-04-25 at 05:50Maintenance is now in progress
- Planned2026-04-25 at 05:50Planned2026-04-25 at 05:50
We would like to inform you about the planned maintenance of all Keboola stacks hosted on Azure.
During the database upgrades there will be a short service outage on all Azure stacks, including all single-tenant stacks and Azure North Europe multi-tenant stack (connection.north-europe.azure.keboola.com). This will take place on Saturday, 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.

