Keboola - Notice history

All systems operational

AWS EU (eu-central-1) - Operational

100% - uptime
February 2026 · 99.8%March · 100%April · 99.3%

Previous page

Next page

February 2026
March 2026
April 2026

GCP EU (europe-west3) - Operational

100% - uptime
February 2026 · 99.8%March · 100%April · 99.3%

Previous page

Next page

February 2026
March 2026
April 2026

AWS US (us-east-1) - Operational

100% - uptime
February 2026 · 99.8%March · 100%April · 99.3%

Previous page

Next page

February 2026
March 2026
April 2026

GCP US (us-east4) - Operational

100% - uptime
February 2026 · 99.8%March · 100%April · 99.3%

Previous page

Next page

February 2026
March 2026
April 2026

Azure NE (north-europe) - Operational

100% - uptime
February 2026 · 99.8%March · 100%April · 99.3%

Previous page

Next page

February 2026
March 2026
April 2026

Google Cloud Platform: Google BigQuery - Operational

Notice history

April 2026

SQL editor layout breaks after query
  • Resolved
    Resolved
    This incident has been resolved.
  • Identified
    Identified

    We have identified an issue with SQL editor where certain query results breaks the page layout and makes it unusable. This issue affects all Keboola stacks.

    The root case has been identified and we're looking for a fix.

Scheduled Partial Maintenance of all Azure stacks
  • Completed
    2026-04-09 at 07:25
    Completed
    2026-04-09 at 07:25
    Maintenance has completed successfully
  • In progress
    2026-04-09 at 07:00
    In progress
    2026-04-09 at 07:00
    Maintenance is now in progress
  • Planned
    2026-04-09 at 07:00
    Planned
    2026-04-09 at 07:00

    We would like to inform you about the planned maintenance of all Keboola stacks hosted on Azure.

    During the database upgrades there will be a short service outage on all Azure stacks, including all single-tenant stacks and Azure North Europe multi-tenant stack (connection.north-europe.azure.keboola.com). This will take place on Saturday, April 25, 2026 between 05:50 and 06:30 UTC.

    Effects of the Maintenance

    During the above period, services will be scaled down and the processing of jobs may be delayed. For a very brief period (at around 06:00 UTC) the service will be unavailable for up to 10 minutes and APIs may respond with a 500 error code. After that, all services will scale up and start processing all jobs. No running jobs, data apps, or workspaces will be affected. Delayed scheduled flows and queued jobs will resume after the maintenance is completed.

    Detailed Schedule

    • 05:50–06:00 UTC: processing of new jobs stops.

    • 06:00–06:15 UTC: service enhancement period.

    • 06:15 UTC: processing of jobs resumes.

March 2026

Scheduled Partial Maintenance of AWS stacks – March 28, 2026
  • Completed
    2026-03-28 at 06:40
    Completed
    2026-03-28 at 06:40
    Maintenance has completed successfully.
  • In progress
    2026-03-28 at 05:50
    In progress
    2026-03-28 at 05:50
    Maintenance is now in progress
  • Planned
    2026-03-28 at 05:50
    Planned
    2026-03-28 at 05:50

    We would like to inform you about the planned maintenance of Keboola stacks hosted on AWS.

    During the database upgrades there will be a short service outage on AWS stacks, including all single-tenant stacks and AWS EU multi-tenant stack (connection.eu-central-1.keboola.com) and AWS US multi-tenant stack (connection.keboola.com). This will take place on Saturday, March 28, 2026 between 05:50 and 06:30 UTC.

    Effects of the Maintenance

    During the above period, services will be scaled down and the processing of jobs may be delayed. For a very brief period (at around 06:00 UTC) the service will be unavailable for up to 10 minutes and APIs may respond with a 500 error code. After that, all services will scale up and start processing all jobs. No running jobs, data apps, or workspaces will be affected. Delayed scheduled flows and queued jobs will resume after the maintenance is completed.

    Detailed Schedule

    • 05:50–06:00 UTC: processing of new jobs stops.

    • 06:00–06:15 UTC: service enhancement period.

    • 06:15 UTC: processing of jobs resumes.

Degraded storage job performance
  • Resolved
    Resolved

    Storage job processing speeds have been restored. The bottleneck was identified as resource contention from an internal service. Systems are now stable, and all queued jobs have completed.

  • Identified
    Identified
    We are continuing to work on a fix for this incident.
  • Investigating
    Investigating
    We are currently investigating this incident.
Scheduled Partial Maintenance of all GCP stacks - March 21, 2026
  • Completed
    2026-03-21 at 06:30
    Completed
    2026-03-21 at 06:30
    Maintenance has completed successfully
  • In progress
    2026-03-21 at 05:50
    In progress
    2026-03-21 at 05:50
    Maintenance is now in progress
  • Planned
    2026-03-21 at 05:50
    Planned
    2026-03-21 at 05:50

    We would like to inform you about the planned maintenance of all Keboola stacks hosted on GCP.

    During the database upgrades there will be a short service outage on all GCP stacks, including all single-tenant stacks, GCP europe-west3 and us-east4 multi-tenant stacks. This will take place on March 21st, between 05:50 and 06:30 UTC.

    Effects of the Maintenance

    During the above period, services will be scaled down and the processing of jobs may be delayed. For a very brief period (at around 06:00 UTC) the service will be unavailable for up to 10 minutes and APIs may respond with a 500 error code. After that, all services will scale up and start processing all jobs. No running jobs, data apps, or workspaces will be affected. Delayed scheduled flows and queued jobs will resume after the maintenance is completed.

    Detailed Schedule

    • 05:50–06:00 UTC: processing of new jobs stops.

    • 06:00–06:30 UTC: service enhancement period.

    • 06:30 UTC: processing of jobs resumes.

Keboola MCP not showing all available tools
  • Resolved
    Resolved

    It seems that reauthorizing the MCP server resolves the issue. If you are experiencing missing or limited tools, please disconnect and reconnect the MCP server in your client. We are continuing to investigate the root cause to prevent recurrence.

  • Update
    Update

    Kai assistant (and other forms of platform chats) are not affected by this issue. Only external use of the MCP server (e. g. in Claude) are affected.

  • Investigating
    Investigating

    We have detected an issue with our MCP server that under some circumstances shows only run_sync_action tool or does not show any tools at all. Our engineering team is investigating the issue with high priority.

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

SMTP Sender component Application errors
  • Resolved
    Resolved

    The issue affecting SMTP Sender component has been fully resolved. All functionality has been restored.

    Thank you for your patience while we worked to resolve this issue and sorry for any inconvenience this may have caused.

  • Investigating
    Investigating

    We have detected an issue with SMTP Sender component affecting all configurations. Users may experience application errors.

February 2026

Inconsistencies affecting Flow jobs in all Azure stacks
  • Update
    Update

    We have identified multiple Storage jobs stuck in a processing state, blocking downstream jobs from proceeding. All of them have been terminated, and job processing should now be unblocked.

    We apologize for any inconvenience this may have caused.

  • Resolved
    Resolved

    The issue affecting stuck flow jobs has been resolved, and normal operation has been restored.

    We apologize for any inconvenience this may have caused.

  • Identified
    Identified

    We have identified the root cause as database inconsistency. Only a low number of flow jobs are stuck in processing state despite all their child jobs are finished (mostly failed). Our team is now working on implementing a solution.

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

  • Investigating
    Investigating

    We are currently investigating reports of inconsistent flow jobs. Some users may be experiencing stuck flows.

    Our team has been notified and is actively investigating.

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

Scheduled Partial Maintenance of all Azure stacks – February 21, 2026
  • Completed
    2026-02-21 at 06:15
    Completed
    2026-02-21 at 06:15
    Maintenance has completed successfully
  • In progress
    2026-02-21 at 05:50
    In progress
    2026-02-21 at 05:50
    Maintenance is now in progress
  • Update
    2026-02-21 at 05:50
    Update
    2026-02-21 at 05:50

    Microsoft Azure has rescheduled the underlying platform maintenance. As a result, the maintenance window for all Keboola stacks hosted on Azure will now take place on Saturday, February 21, 2026, between 05:50 and 06:30 UTC.

  • Planned
    2026-02-21 at 05:50
    Planned
    2026-02-21 at 05:50

    We would like to inform you about the planned maintenance of all Keboola stacks hosted on Azure.

    During the database upgrades there will be a short service outage on all Azure stacks, including all single-tenant stacks and Azure North Europe multi-tenant stack (connection.north-europe.azure.keboola.com). This will take place on Saturday, February 28, 2026 between 05:50 and 06:30 UTC.

    Effects of the Maintenance

    During the above period, services will be scaled down and the processing of jobs may be delayed. For a very brief period (at around 06:00 UTC) the service will be unavailable for up to 10 minutes and APIs may respond with a 500 error code. After that, all services will scale up and start processing all jobs. No running jobs, data apps, or workspaces will be affected. Delayed scheduled flows and queued jobs will resume after the maintenance is completed.

    Detailed Schedule

    • 05:50–06:00 UTC: processing of new jobs stops.

    • 06:00–06:15 UTC: service enhancement period.

    • 06:15 UTC: processing of jobs resumes.

Jobs not starting on all stacks
  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    We implemented a fix, jobs should be now starting normally. We apologize for the inconvenience.

  • Investigating
    Investigating

    We are currently investigating this incident. Jobs are stuck in "Created" state. Next update in 30 minutes or sooner.

  • Identified
    Identified

    New jobs are now starting as they should. We are continuing to work on a fix for jobs started between ~12:10 and ~12:50 UTC that are still stuck in "Created" state. Next update in 30 minutes or sooner.

Issues with KAI assistant approvals
  • Update
    Update

    This incident has been resolved.

    Few chats started approximately between 6:30 UTC and 8:30 UTC may still show the errors below, if you encounter these, please start a new chat.

  • Resolved
    Resolved
    This incident has been resolved.
  • Monitoring
    Monitoring

    We have identified the root cause and deployed a fix. Please start a new fresh conversation in case you see any of the error messages:

    messages.4: user messages must have non-empty content
messages.11.content.1.text: cache_control cannot be set for empty text blocks
  • Update
    Update
    We are currently investigating this incident.
  • Investigating
    Investigating

    We are currently investigating issues with failing action approvals with KAI assistant in GCP US stack.

Project Access Issues
  • Resolved
    Resolved

    The issue has been fixed. We reverted the changes that caused the problem and full access has been restored across all regions.

    All users can now access their projects normally, including those with Guest and Read-only roles who were previously affected.

    Thank you for your patience.

  • Identified
    Identified

    We have identified that this issue affects users with Guest and Read-only roles. Users with other roles should be able to use the platform normally.

    The issue is related to a release deployed at 13:50 UTC. We are currently working on a rollback.

    Next update within 30 minutes.

  • Investigating
    Investigating

    We are currently investigating reports of some users being unable to access their projects after login. Affected users may encounter HTTP 403 or 404 errors.

    Our team is actively investigating the root cause. We will provide an update within 30 minutes.

    We apologize for any inconvenience.

February 2026 to April 2026

Next