Keboola Status

2025-03-13 23:46 CET – We are investigating a service degradation on the https://connection.europe-west3.gcp.keboola.com/ stack.

2025-03-14 00:01 CET – Services on the https://connection.europe-west3.gcp.keboola.com/ stack have resumed normal operations. Component events (level INFO) display only 50% of the logs.

2025-03-14 22:09 CET – To avoid database bottleneck during peak hours this night we have implemented events sampling. Component events (level info) will display only 50% of the logs. All storage events and component events with higher level will not be affected by this change. 

2025-03-12 06:00 UTC - we are investigation possible service degradation on https://connection.europe-west3.gcp.keboola.com/ stack

2025-03-12 07:15 UTC - we are still working on the issue, stack is operational, but jobs are being delayed

2025-03-12 08:15 UTC - All services are fully operational now however you may experience job delays due to limited worker capacity. We have identified a database bottleneck and are working towards getting to full capacity.

2025-03-12 23:40 UTC - To avoid database bottleneck during peak hours this night we have implemented events sampling. Component events (level info) will display only 50% of the logs. All storage events and component events with higher level will not be affected by this change. 

2025-03-13 09:15 UTC - Sampling of the component events has been removed and all events created from now on are displaying.

2025-03-11 23:15 UTC - we are investigation possible service degradation on https://connection.europe-west3.gcp.keboola.com/ stack

2025-03-12 00:15 UTC - stack is now fully operational, ale jobs are being processed.

2025-03-11 10:50 UTC - we are investigating failed jobs for component keboola.ex-telemetry-data

2025-03-11 11:30 UTC - We found invalid record in telemetry data which caused telemetry extractor to fail. Record was fixed and all telemetry extractors are working as expected. 

We are sorry for caused inconvenience.

2025-03-11 10:00 UTC - we are investigation possible service degradation on https://connection.eu-central-1.keboola.com stack

2025-03-11 11:10 UTC - all services are operating normally now. Only marginal number of component job was affected with delayed processing.

2025-03-05 16:10 UTC We are currently experiencing degraded performance with workspace creation, which may impact all jobs that rely on workspace creation as part of their lifecycle.

Our team is actively investigating the issue, and we will provide updates as we have more information.

We appreciate your patience and apologize for any inconvenience this may cause.

2025-03-05 17:15 UTC We've identified the core issue and deployed a fix. All Storage jobs associated with WorkspaceCreate should now be functioning properly.

2025-03-04 10:00 UTC - We are investigating import failures for the Stream service on connection.eu-central-1.keboola.com due to receiver errors. We will provide an update as soon as we have more information.

2025-03-04 10:10 UTC – We have identified the root cause and resolved the issue. The backlog of imports is now being processed, and we are continuing to monitor the situation.

2025-03-04 12:11 UTC – Some projects still have unprocessed Stream imports. We are continuing the investigation.

2025-03-04 13:21 UTC – The backlog has been cleared, and Stream services are stable and fully operational. However, a few customers' data was not imported during the incident window starting on February 28th. We will contact these customers directly.

Starting at 12:00 UTC, all jobs that were either processing or started at that time began failing due to an error introduced in the latest release. At 12:40 UTC, we reverted to the previous stable version, and we expect job processing to return to normal.

We are actively monitoring the situation and will provide updates as needed.

Please be aware that this endpoint will be permanently shut down on March 1, 2025.

Ensure that your API integrations are migrated to the new endpoint by this date.

2025-02-13 11:01 UTC - We are currently investigating a potential column mismatch issue with the Salesforce extractor, which started occuring around February 12, 2025. The investigation is ongoing, and we will provide more information as soon as we have further details.

2025-02-13 11:48 UTC - We have reverted the affected extractor version to the previous one. Extracted objects with frozen columns that were not aligned with the current Salesforce API version may have had mismatched columns if they were processed using the affected extractor version, which was released on February 11, 2025, at 8:07 UTC. A full load using the reverted extractor is advised.