Due to the inoperability of the Atlassian Service Desk In the morning of January 18, 2024 our support services are temporarily unavailable.
We will provide an update as soon as services have returned to normal.
Many apologies for this inconvenience.
<January 18, 2024 12:30 CET>. Support systems have resumed normal operations
2024-01-15 07:20 UTC - We experienced another incident on connection.eu-central-1.keboola.com between Jan 14 23:30 UTC and Jan 15 07:54 UTC. Some jobs ended in error due to an underlying node failure. We're still investigating the root cause and taking measures to prevent future incidents.
2024-01-11 13:04 - We are currently investigating a problem related to email delivery from the Keboola platform. We will provide an update as soon as we have more information.
UPDATE 13:19 - We have fixed the underlying issue (invalid SPF record). If you still have issues receiving messages from any Keboola platform please let us know.
2024-04-01 06:35 UTC - We experienced incident on https://connection.keboola.com. Some jobs ended in error due to an underlying node failure. We're still investigating the root cause and taking measures to prevent future incidents.
Update 2024-04-01 06:54 UTC The incident is now resolved, and the platform is stable again.
We apologize for the inconvenience.
A limited service disruption on AWS EU stack will start at 15:00 UTC today, as announced earlier. Storage jobs, Queue v1, and Orchestration (in projects with Queue v1) processing will stop and new jobs will be delayed until the upgrade is completed. All running jobs will be cancelled, but will resume after the upgrade.
All APIs and other unaffected services, such as Workspaces and Queue v2 jobs, will remain operational, though their operations may be delayed due to the Storage job delays. We will provide an update when the service disruption starts and ends.
We apologize for any inconvenience caused and thank you for your understanding.
Update 15:00 UTC: The limited service disruption has begun.
Update 15:35 UTC: The service disruption has been resolved and the stack is now fully operational.
Thank you for your patience.
A limited service disruption on AWS EU stack will start at 13:00 UTC today Friday, December 29, as announced earlier. Storage jobs, Queue v1, and Orchestration (in projects with Queue v1) processing will stop and new jobs will be delayed until the upgrade is completed. All running jobs will be cancelled, but will resume after the upgrade.
All APIs and other unaffected services, such as Workspaces and Queue v2 jobs, will remain operational, though their operations may be delayed due to the Storage job delays. We will provide an update when the service disruption starts and ends.
We apologize for any inconvenience caused and thank you for your understanding.
Update 13:00 UTC: The limited service disruption has begun.
Update 13:35 UTC: The service disruption has been resolved and the stack is now fully operational.
Thank you for your patience.
Due to necessary database upgrades to our AWS US and EU stacks, a limited service disruption will take place on December 29:
- 13:00–14:00 UTC (14:00–15:00 CET) for the AWS EU stack
- 15:00–16:00 UTC (07:00–08:00 PDT) for the AWS US stack
We anticipate the duration of the disruption will be approximately 15 minutes, but it should not exceed 60 minutes. Hopefully, this will be resolved before you return from your lunch or coffee break.
During this period, Storage jobs, Queue v1 and Orchestration (in projects with Queue v1) processing will stop, and new jobs will be delayed until the upgrade is completed. All running jobs will be paused, but will resume after the upgrade. The platform will be unavailable for approximately 5 minutes. The platform will then generate a 500 HTTP response for the majority of API requests. Throughout the remainder of the maintenance window, the platform will be fully accessible but will not process any new or existing Storage jobs or Queue v1 jobs.
All APIs and other unaffected services, such as Workspaces and Queue v2 jobs, will remain operational, though their operations may be delayed due to the Storage job delays.
We apologize for any inconvenience caused and thank you for your understanding.
Between 9:18 and 10:42 UTC some flows were processing longer than usual with jobs "stuck" in processing or waiting state. This was caused be a recent update which was already reverted. The issue affected all stacks but only a small portion of jobs. We sincerely apologize for the inconvenience.
Since 14:00 UTC, we have been experiencing slower job processing in the Azure North Europe stack (https://connection.north-europe.azure.keboola.com). We are currently investigating the issue.
Update 16:20 UTC we have rolled back a previous version of one of our services that was causing the delays and all operations are back normal. We're sorry for this inconvenience.
We are investigating event triggers not working and also not visible in UI in AWS US stack (https://connection.keboola.com). No flows based on event triggers are being executed at the moment. Time based schedules are working as expected as well as event triggers in other stacks.
Update 13:35 UTC: We identified the root cause and will now proceed to restore event triggers configurations.
(Resolved) Update 14:05 UTC: We restored event triggers configurations, all event triggers are now working as expected and we don't observe any failures regarding even triggered flows. However if you still experience issues please contact us on support to resolve it further.