Keboola - Notice history

The problem with the jobs has been resolved. All systems are now operating normally.

We apologize for any inconvenience this may have caused and thank you for your patience.

The infrastructure issues affecting our Azure infrastructure have been resolved, all our Azure stacks are fully operational now.

We apologize for the inconvenience and thank you for your patience.

We're seeing improvements in performance on all stacks, everything seems to be running fine and we're closely monitoring the situation.

From Azure Status:

Current status: We have determined that these issues were caused by a recent configuration change that affected public access to certain Microsoft‑managed storage accounts, used to host extension packages. We are actively working to mitigate impact, by updating our configuration to restore relevant access permissions. After applying this update in one region, we validated that it mitigates the issues customers were experiencing - we are making good progress applying this same mitigation across all impacted regions, in parallel where possible. We still expect that this will be completed across all impacted regions by approximately 00:00 UTC, approximately one hour from now. Our next update will be provided by then, or sooner if we have progress to share.

Azure have acknowledged the underlying issue and are working on a fix. See https://azure.status.microsoft/en-gb/status for more details.

Active - Virtual Machine service management issues - Multiple regions

Impact statement: We are aware of an ongoing issue causing customers to receive error notifications when performing service management operations - such as create, delete, update, scaling, start, stop - for Virtual Machines (VMs).

We're monitoring the issue closely and provide an update within 1 hour or when new information is available.

The infrastructure issues affecting our AI Assistant infrastructure have been resolved. Microsoft has confirmed that their services are fully operational.

We apologize for the inconvenience.

The issue is an underlying issue in an upstream service. We will monitor the situation on Azure Health page, and will keep this status updated.

This incident has been resolved. Snowflake resolved the incident.

We are seeing signs of improvement and are no longer observing any errors in our systems. While Snowflake continues to mitigate the issue, our services are currently operating normally. We will continue to closely monitor the situation and provide updates if anything changes.

Snowflake is executing mitigation efforts. As mitigation progresses, customers may see gradual improvements while resolution steps are completed. Snowflake’s current estimate for full service restoration is 15:00 UTC.

Snowflake has indicated that service is expected to be restored by 14:00 UTC. We will continue to monitor and provide updates.

We continue to monitor the Snowflake incident and are seeing a reduction in table import job errors, though the issue is not yet fully resolved.