Keboola - Notice history

All systems operational

AWS EU (eu-central-1) - Operational

100% - uptime
March 2026 · 100%April · 98.9%May · 100%

Previous page

Next page

March 2026
April 2026
May 2026

GCP EU (europe-west3) - Operational

100% - uptime
March 2026 · 100%April · 98.9%May · 100%

Previous page

Next page

March 2026
April 2026
May 2026

AWS US (us-east-1) - Operational

100% - uptime
March 2026 · 100%April · 99.0%May · 100%

Previous page

Next page

March 2026
April 2026
May 2026

GCP US (us-east4) - Operational

100% - uptime
March 2026 · 100%April · 99.0%May · 100%

Previous page

Next page

March 2026
April 2026
May 2026

Azure NE (north-europe) - Operational

100% - uptime
March 2026 · 100%April · 98.9%May · 100%

Previous page

Next page

March 2026
April 2026
May 2026

Google Cloud Platform: Google BigQuery - Operational

Notice history

May 2026

No notices reported this month

April 2026

Degraded performance of Kai AI features on EU stacks
  • Resolved
    Resolved

    We have seen no more throttled requests since 16:40. The incident is resolved.

  • Monitoring
    Monitoring

    We see substantial reduction of throttled requests. Only one request was throttled in the past 15 minutes.

  • Identified
    Identified

    Since 11:00 UTC we're observing degraded performance of Kai AI features on our EU stacks (connection.eu-central-1.keboola.com and connection.europe-west3.gcp.keboola.com and connection.north-europe.azure.keboola.com) . The issue is caused by rate limiting (HTTP 429 Too Many Requests) from our upstream GCP Vertex AI provider and has been intermittently affecting responses.

    Users may experience slower responses, failed requests, or errors when interacting with Kai. Other platform functionality is not affected.

    Our team is actively monitoring the situation.

    Next update in 60 minutes.

    We apologize for the inconvenience.

Support Widget in Application Temporarily Unavailable
  • Resolved
    Resolved

    The issues affecting our Jira-powered support widget have been resolved. Atlassian has confirmed that their services are fully operational.

    Tickets submitted during the outage were delivered with a delay and we have responded to all of them. If you have not received a response, please re-submit your request.

    We apologize for the inconvenience. The issue was on the third-party vendor's side, not in the Keboola platform.

  • Update
    Update

    Atlassian pipeline pipeline was presumably fixed now and we're starting to gradually receive submitted tickets. We apologize for the delay in processing. We'll re-enable the support widget once we confirm it works reliably. Next update in 8 hours.

  • Identified
    Identified

    We're currently experiencing an issue with the Jira-powered support widget in the Keboola platform, which is preventing some support tickets from being submitted successfully. We're working with Atlassian to resolve this.

    Workaround: Please send your support requests directly to support@keboola.com. We'll respond as usual.

    We'll update this notice as soon as the widget is restored.

Scheduled Partial Maintenance of all Azure stacks
  • Completed
    2026-04-25 at 06:15
    Completed
    2026-04-25 at 06:15
    Maintenance has completed successfully
  • In progress
    2026-04-25 at 05:50
    In progress
    2026-04-25 at 05:50
    Maintenance is now in progress
  • Planned
    2026-04-25 at 05:50
    Planned
    2026-04-25 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, 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.

Failing storage jobs on BigQuery backend
  • Resolved
    Resolved

    Incident resolved. Mitigation has been applied and systems have returned to normal operation. Follow-up work is in progress to implement a permanent fix and prevent recurrence.

  • Identified
    Identified

    We have identified the root cause of the failing storage jobs on the BigQuery backend. The issue is isolated to internal/system projects and does not impact customer data or workloads. We are applying mitigation steps and continue to monitor the system closely.

  • Investigating
    Investigating

    We are currently investigating this incident where storage jobs running on BigQuery backend are failing.

Degraded performance of Kai AI features on EU stacks
  • Resolved
    Resolved

    The situation has stabilized and we are no longer observing elevated 429 responses from GCP Vertex AI on the affected EU stacks. Kai AI features are operating normally again. The incident is now resolved, and we will continue to monitor the situation.

    We apologize for the inconvenience.

  • Investigating
    Investigating

    Since approximately 05:00 UTC we have been observing degraded performance of Kai AI features on our EU stacks (connection.eu-central-1.keboola.com and connection.europe-west3.gcp.keboola.com). The issue is caused by rate limiting (HTTP 429 Too Many Requests) from our upstream GCP Vertex AI provider and has been intermittently affecting responses since this morning.

    Users may experience slower responses, failed requests, or errors when interacting with Kai. Other platform functionality is not affected.

    Our team is actively monitoring the situation.

    Next update in 60 minutes.

    We apologize for the inconvenience.

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.

March 2026 to May 2026

Next