Synchronous actions, a mechanism behind some UI features, like testing credentials or listing available databases on a distant server, were affected by a bug and were not working properly from 12:50 UTC until 13:25 UTC when the revert of defective release was finished and the functionality is back to normal since then.
2022-08-20 14:57 UTC - we are investigating some jobs failing on internal error. Next update in 30 minutes.
2022-08-20 15:30 UTC - we see the internal error is caused by one of the internal components failing to call Azure API, however don't know the root cause. We restarted one of the instances and see no error for now. We continue monitoring the issue.
On 24th September 2022 between 10:00 CET and 10:30 CET, https://connection.eu-central-1.keboola.com will undergo planned maintenance during which one of our internal databases will be upgraded. As a result, any loads or unloads to storage will be paused during that time for up to 30 minutes. Any currently running jobs will continue to run. However, they may be delayed by up to 30 minutes as well.
2022-08-15 10:40 UTC - We are investigating component job delays in connection.keboola.com. Next update when new information will be available or in hour.
2022-08-15 11:14 UTC - We have identified the root cause of the problem and we are working on a solution. Next update when new information will be available or in hour.
2022-08-15 14:04 UTC - We've added another worker to help with the workload and the processing times has returned to normal
2022-08-15 15:32 UTC - We are investigating reoccurrence of the issue causing jobs stuck in Created state. Next update when new information will be available or in hour.
2022-08-15 15:59 UTC - The reoccurrence was resolved. We keep monitoring the situation closely, but at the moment job runtimes should be back to the normal.
2022-08-06 16:35 UTC - We are investigating higher error rates and latencies in connection.north-europe.azure.keboola.com stack. Next update in 30 minutes.
2022-08-06 17:20 UTC - Higher errors rates are resolved and latencies are back to normal. Schedules might be delayed, the backlog is processed.
2022-08-06 17:46 UTC - Backlogs is cleared. This incident has been resolved.
2022-08-05 00:40 UTC - We are investigating component job delays in connection.keboola.com. Next update when new information will be available or in hour.
UPDATE 2022-08-05 00:55 UTC - We have identified the root cause and replaced the faulty instances.
UPDATE 2022-08-05 01:00 UTC - All operations are back to normal. We're sorry for this inconvenience.
2022-08-04 12:05 UTC We are investigating internal job errors. Next update in 30 minutes.
2022-08-04 12:36 UTC We experienced two waves of internal errors, between 11:50-11:57 and 12:00-12:07 UTC. The root cause has been removed and I don't see any other errors in the reporting. We continue to monitoring the situation. Next update in 30 minutes.
2022-08-04 13:06 UTC All Keboola Connection services are running normally. The incident is resolved.
We apologize for any inconvenience.
2022-08-04 09:40 UTC We are investigating bug, which causing error pages rendered as html source code.
2022-08-04 09:55 UTC Issue is now resolved all systems are working normally.
We are sorry for the inconvenience.
We are experiencing an issue with possibility of tables with _tmp suffix might be dropped.
If you manipulate with a table <X> and there also exist a table with name <X>_tmp, the table <X>_tmp could be accidentally dropped.
These tables (<X> and <X>_tmp) have to be in the same bucket and your project has to have Snowflake backend. We found the root cause and fix will be deployed in 2 hours.
Affected tables will be restored.
2022-08-02 17:00 UTC - We have deployed the fix of this issue and fixed affected tables. The issue is now resolved. We contact affected customers directly.
We are sorry for the inconvenience.
2022-08-02 7:00 UTC We are investigating delayed orchestrations on Azure North Europe Keboola Connection stack (https://connection.north-europe.azure.keboola.com). Next update in 30 minutes.
2022-08-02 7:30 UTC After our investigation, problem starts at 6:00 UTC. Orchestrations that should have be scheduled after this time, were delayed in the order of minutes or tens of minutes. Situation returned back to normal at 7:15 UTC and all orchestrations are scheduled properly.