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 statusOctober 2026
- ResolvedUTCResolvedUTC
This incident has been resolved. Snowflake transformations are running on their configured backend size again, and job run times are back to normal.
No action is needed from you. We apologize for the slower run times this caused.
- MonitoringUTCMonitoringUTC
A fix has been deployed and Snowflake transformations are running on their configured backend size again.
Cause: Because of an issue in our job execution environment, Snowflake transformations set to a medium or large backend size were run on the default (small) warehouse. This happened whether the size was set in the configuration, in a configuration row, or on the job itself (through the API or a flow). As a result, those jobs could take noticeably longer than usual.
Resolution: The fix is now live on all stacks. On AWS EU (connection.eu-central-1.keboola.com), it has been in place since 12:58 CEST today (October 22). Jobs started after that time use the configured backend size again. We confirmed this for medium and large sizes, both on the job and in the configuration.
Affected period: Medium and large Snowflake transformations ran on the default size during these periods:
AWS EU (eu-central-1): October 20 to October 22, 12:58 CEST
AWS US (us-east-1), Azure EU (north-europe), GCP US (us-east4): October 14 until the fix was deployed
No action is needed. Your existing configurations will work as before. We are watching job run times to confirm everything is back to normal, and we will post a final update once we have.
- InvestigatingUTCInvestigatingUTC
We are currently investigating reports of degraded performance affecting Snowflake transformations on our AWS EU (connection.eu-central-1.keboola.com) infrastructure. Users may notice Snowflake transformations taking noticeably longer than usual. Jobs set to a medium or large backend size may be running on the default size instead.
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.
- ResolvedUTCResolvedUTC
This incident has been resolved. The Storage API on our GCP EU (connection.europe-west3.gcp.keboola.com) infrastructure has been fully stable since 07:32 UTC, and all jobs queued during the incident have been processed.
Summary: Between approximately 07:05 and 07:32 UTC, a database issue caused slow responses and errors (HTTP 500) in the Keboola UI and API on GCP EU. During this time, some new jobs could not be started and some running jobs failed.
If any of your jobs failed during this period, please run them again. If you notice any remaining problems, please contact our support team.
We are continuing to investigate the root cause and will take steps to prevent this from happening again. We apologize for the disruption.
- MonitoringUTCMonitoringUTC
We have identified the cause of the issue and applied a fix. The Storage API on our GCP EU (connection.europe-west3.gcp.keboola.com) infrastructure has been operating normally since 07:32 UTC. Errors have stopped and response times are back to normal levels.
Between approximately 07:05 and 07:32 UTC, users may have experienced slow responses and errors (HTTP 500) when using the Keboola UI or API. During this time, some new jobs could not be started and some running jobs may have failed. Jobs that were queued during the incident are now being processed.
If any of your jobs failed during this period, please run them again. If you continue to see problems, please contact our support team.
We are monitoring the platform closely and will provide a final update once we confirm that everything is fully stable.
- InvestigatingUTCInvestigatingUTC
We are currently investigating reports of an outage affecting the Storage API on our GCP EU (connection.europe-west3.gcp.keboola.com) infrastructure. Users may experience errors (HTTP 500) when using the Keboola UI or API, and jobs may fail or not start.
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.
September 2026
- ResolvedUTCResolvedUTC
The issue affecting the Job Queue and Scheduler on our AWS US (connection.keboola.com) infrastructure has been resolved. Scheduled flows and orchestrations are starting on time again and the Job Queue API is responding normally.
Scheduled jobs that failed to start during the incident were not run automatically — please check your flows and re-run any missed executions manually if needed.
We apologize for the disruption. Our team is continuing to monitor the platform to confirm the fix is stable. - InvestigatingUTCInvestigatingUTC
We are currently investigating reports of degraded performance affecting the Job Queue and Scheduler on our AWS US (connection.keboola.com) infrastructure. Users may experience:
- Scheduled flows and orchestrations failing to start or starting late
- Intermittent errors (
502 Bad Gateway) when creating or listing jobs via the Job Queue API or the UI
Our engineering team has been alerted and is actively investigating the root cause.
We apologize for the disruption and will provide an update within 1 hour or when new information is available.
- ResolvedUTCResolvedUTCThis incident has been resolved.
- MonitoringUTCMonitoringUTC
We implemented a fix, the backlog is currently processed, we are currently monitoring the situation.
- IdentifiedUTCIdentifiedUTC
We have identified the cause, some queries are now executing, but execution is heavily slowed down. We are continuing to work on a fix for this incident. Next update in 30 minutes.
- InvestigatingUTCInvestigatingUTC
We are currently investigating issues with creating and using BigQuery workspaces on Europe West 3 connection.europe-west3.gcp.keboola.com stack. New workspaces are stuck in "initializing" state and queries timeout. Next update in 30 minutes.
August 2026
- Completed2026-08-22 at 06:40UTCCompleted2026-08-22 at 06:40UTCMaintenance has completed successfully
- In progress2026-08-22 at 05:40UTCIn progress2026-08-22 at 05:40UTCMaintenance is now in progress
- Planned2026-07-29 at 11:21UTCPlanned2026-07-29 at 11:21UTC
We would like to inform you about the planned maintenance of the Keboola GCP EU multi-tenant stack (connection.europe-west3.gcp.keboola.com) and the Keboola Azure North Europe multi-tenant stack (connection.north-europe.azure.keboola.com).
During the database upgrade there will be a short service outage on both stacks. This will take place on Saturday, August 22, 2026 between 05:40 and 07:00 UTC.
Effects of the Maintenance
During the above period, services will be scaled down and the processing of jobs may be delayed. For a very brief period during the service enhancement period the service will be unavailable for up to 10 minutes and APIs may respond with a 500 error code. After that, all services will scale up and start processing all jobs. No running jobs, data apps, or workspaces will be affected. Delayed scheduled flows and queued jobs will resume after the maintenance is completed.
Detailed Schedule
05:40–05:45 UTC: processing of new jobs stops.
05:45–06:45 UTC: service enhancement period.
07:00 UTC: processing of jobs resumes.
- Completed2026-08-15 at 08:30UTCCompleted2026-08-15 at 08:30UTCMaintenance has completed successfully
- In progress2026-08-15 at 07:30UTCIn progress2026-08-15 at 07:30UTCMaintenance is now in progress
- Planned2026-07-29 at 11:18UTCPlanned2026-07-29 at 11:18UTC
We would like to inform you about the planned maintenance of the Keboola GCP US multi-tenant stack (connection.us-east4.gcp.keboola.com) and the Azure North Europe multi-tenant stack (connection.north-europe.azure.keboola.com).
During the database upgrades there will be a short service outage on both stacks. This will take place on Saturday, August 15, 2026 between 07:30 and 09:00 UTC.
Effects of the Maintenance
During the above period, services will be scaled down and the processing of jobs may be delayed. For a very brief period during the service enhancement period the service will be unavailable for up to 10 minutes and APIs may respond with a 500 error code. After that, all services will scale up and start processing all jobs. No running jobs, data apps, or workspaces will be affected. Delayed scheduled flows and queued jobs will resume after the maintenance is completed.
Detailed Schedule
07:30–07:45 UTC: processing of new jobs stops.
07:45–08:45 UTC: service enhancement period.
09:00 UTC: processing of jobs resumes.