Keboola - Notice history

AWS EU (eu-central-1) - Operational

100% - uptime
November 2025 · 99.96%December · 100.0%January 2026 · 99.81%
November 2025
December 2025
January 2026

GCP EU (europe-west3) - Operational

100% - uptime
November 2025 · 99.92%December · 100.0%January 2026 · 99.81%
November 2025
December 2025
January 2026

AWS US (us-east-1) - Operational

100% - uptime
November 2025 · 99.98%December · 99.53%January 2026 · 99.81%
November 2025
December 2025
January 2026

GCP US (us-east4) - Operational

100% - uptime
November 2025 · 99.98%December · 100.0%January 2026 · 99.81%
November 2025
December 2025
January 2026

Azure NE (north-europe) - Operational

100% - uptime
November 2025 · 99.98%December · 100.0%January 2026 · 99.79%
November 2025
December 2025
January 2026

Notice history

January 2026

Jobs not starting on all stacks
  • Resolved
    Resolved

    This incident has been complete resolved.
    We apologize for any inconvenience caused.

  • Update
    Update

    We have identified approximately ten stuck flows across multiple stacks and are processing them gradually. If you encounter a flow that is in a terminating state and does not complete, please contact our support team.

  • Update
    Update

    We are monitoring all stacks and can see that the backlog of accumulated jobs is gradually clearing, but you may still experience minor delays. Everything should be back to normal soon.

  • Monitoring
    Monitoring

    The Azure NE (Northern Europe) stack has now also been fixed. We will now monitor the situation for at least another hour.

  • Update
    Update

    GCP EU europe-west3 and US us-east4 has now been fixed, and all jobs will gradually start automatically.

  • Identified
    Identified

    We have identified the cause of the problem and are gradually repairing the stacks. AWS EU and US was repaired first, and tasks are now running automatically without user intervention. All stacks should be repaired within an hour at the latest. We will keep you informed.

  • Investigating
    Investigating

    We are aware of performance degradation affecting our starting jobs.

    Symptoms: Slow task execution or tasks stuck in the create state.

    Our team is monitoring the situation and working to resolve this issue.

    We apologize for the disruption and will provide an update within 1 hour or when new information is available.

December 2025

Snowflake Outage in multiple regions
  • Resolved
    Resolved

    This incident has been resolved. Snowflake resolved the incident.

  • Monitoring
    Monitoring

    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.

  • Update
    Update

    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.

  • Update
    Update

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

  • Update
    Update

    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.

  • Identified
    Identified

    We are currently experiencing failures in storage jobs importing data into tables due to an ongoing Snowflake incident affecting our stack’s region (US west). We are monitoring the snowflake incident and will wait for the fix from their side.

    For more info about the Snowflake incident see: https://status.snowflake.com/incidents/xdxj4klf7sc5

November 2025

Data Streams data are not propagated to Storage
  • Resolved
    Resolved

    Data Streams functionality has been fully restored as of 10:30 UTC.


    The Data Streams metadata layer on GCP EU experienced an outage starting 27 November at 22:05 UTC. We restored it from a snapshot taken at 22:00 UTC on 27 November.

    No existing Storage data was affected. The issue was isolated to incoming Data Streams data.


    For most customers, no data was lost. Data continued to be received during the outage and was automatically imported once the metadata layer was restored.

    Unfortunately, 3 customers were affected by data loss for the period between 27 November 22:00 UTC and 28 November 10:30 UTC. We will contact these customers directly.


    We sincerely apologize for the inconvenience this has caused. We're reviewing our systems to prevent similar issues in the future and improve the reliability of Data Streams service.

  • Update
    Update

    We are still investigating the root cause of the issue and working on restoring the Data Streams data from snapshots.

    Next update in 60 minutes.

  • Update
    Update

    Initial issues with Data Streams data propagation began yesterday, 27 November, at 22:32 UTC.

    The next update will be provided in 30 minutes.

  • Investigating
    Investigating

    We are currently investigating issues with Date Streams.

    Our team has been notified and is actively investigating.

    Next update in 30 minutes or when new information is available.

November 2025 to January 2026

Next