Planned partial maintenance on Saturday, February 8, 2025 for all GCP stacks

The announced partial maintenance has just started. The platform has been scaled down and is no longer accepting new jobs. We expect a brief downtime in 30 minutes, around 8:00 UTC for GCP europe-west3 and us-east4. We will update this post with the progress of the partial maintenance.

2025-02-08 8:00 UTC: The announced partial maintenance of both GCP stacks is ongoing, and we are expecting downtime to begin any minute now. We will continue to update this post as the maintenance progresses.

2025-02-08 8:17 UTC: The maintenance of both stacks has been completed, and all services have been scaled back up. The platform is fully operational, and jobs are now being processed as usual. All delayed jobs will be processed shortly. Thank you for your patience.

Scheduled Partial Maintenance for Keboola AWS Stacks – Saturday, March 15, 2025

This maintenance is necessary to ensure that our services remain secure and reliable. Please note the affected stacks and their maintenance schedules:

Effect of the Maintenance

The maintenance is expected to last no longer than 15 minutes, during which jobs may be delayed. While you will be able to log into the Keboola platform, starting new jobs will not be possible during the maintenance. Jobs already running will not be canceled—only delayed. Running data apps or workspaces will not be affected. Scheduled jobs will automatically start after the maintenance is completed.

We apologize for the inconvenience and appreciate your understanding as we work to maintain and improve our service. If you have any questions or need further assistance, please contact our support team.

Thank you for your patience and cooperation.

Deprecation of old Jobs list API endpoint

As previously announced, we will be deprecating the old API endpoint for listing queue jobs (https://queue.[stack_id].keboola.com/jobs).

This endpoint has been replaced with a new, faster alternative: https://queue.[stack_id].keboola.com/search/jobs.

The old endpoint will be permanently shut down on March 1, 2025.

Please ensure that your API integrations are migrated to the new endpoint by this date.

If you have any questions, please contact our support team or your Keboola account manager.

Scheduled Partial Maintenance for Keboola GCP Stacks – February 2025

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

This maintenance is necessary to keep our services running smoothly and securely. Please note the following schedules and the stacks affected.

GCP EU and US Stack Maintenance – February 8, 2025

During database upgrades there will be a short service disruption on both GCP multi-tenant stacks. Here is the schedule.

Effect of the Maintenance

During the above periods, services will be scaled down and the processing of jobs may be delayed. For very brief periods (at around 8:00 UTC) the service will be unavailable for up to five 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 for europe-west3 and us-east4

  • 7:30–8:00 UTC: processing of new jobs stops.

  • 8:00–8:10 UTC: service disruption

  • 8:15 UTC: processing of jobs starts.

Effect of the Maintenance

The maintenance is expected to last no longer than 15 minutes, during which jobs may be delayed. While you will be able to log into the Keboola platform, starting new jobs will not be possible during the maintenance. Jobs already running will not be canceled—only delayed. Running data apps or workspaces will not be affected. Scheduled jobs will automatically start after the maintenance is completed.

Buffer API Deprecation & Migration to Data Streams

We would like to inform you that our Buffer API is being deprecated as part of our commitment to providing you with the best tools and services. Effective 1.3.2025, the Buffer API will no longer be available.

To ensure a seamless transition, we are introducing Data Streams, full replacement and powerful and improved service designed to enhance your data integration experience. You can learn more about Data Streams and its benefits HERE.

Why the change?

  • Enhanced Performance: Faster and more reliable data streaming
  • Improved Functionality: Supports more use cases with advanced features.
  • Streamlined Experience: Fresh UI with more intuitive and flexible integration process.

How to migrate:

We’ve created a migration tool to help you move current Buffer API endpoints to Data Streams quickly and easily. Our support team is also here to provide guidance and support throughout the process.

What you need to do:

  1. Manually migrate existing Buffer API endpoint to Data Streams - Create new Data Streams, copy the stream URL and replace the current Buffer API endpoint within your integration with it
  2. Contact our support team - we will run a script to migrate old Buffer API endpoints to new Data Streams so you can just copy paste the Data Stream URL and replace the current Buffer API endpoint within your integration with it

You can read more about Data Streams and how to set it up HERE.

Need help?

Our support team is here to help you every step of the way. If you have any questions or concerns about the migration, feel free to reach out to us.

Thank you for your understanding and for being a valued part of the Keboola community. We’re excited for you to experience the benefits of Data Streams!

Keboola Team

Jobs listing delayed on AWS EU stack

We are experiencing problem with jobs data replication on AWS EU stack (https://connection.eu-central-1.keboola.com). Jobs are being triggered and run properly but they don't appear in jobs list across whole UI.

Investigation is under way. We will post any updates available.

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


2024-12-18 14:35 UTC: We have identified and fixed the issue with the component responsible for job data replication. New jobs are now displaying correctly in the lists, and all jobs that ran during the outage period have been successfully backfilled.

Buffer API outage on AWS US stack

We are registering Buffer API outage on AWS US stack. The API is currently not receiving any requests which also affects other platform features, like AI suggestions.

Investigation is under way. We will post any updates available.

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


2024-12-18 15:15 UTC: We have discovered that the data storage behind the Buffer API was corrupted. While the service is now fully operational, it had not been receiving any incoming requests since 2024-12-17 23:00 UTC. Additionally, Buffer endpoint configurations were lost due to the data corruption. All customers with configured Buffer API integrations will be contacted by their account executives to explain the situation in more detail.

Failing Storage jobs on US east stack: "Insufficient privileges to operate on account 'KEBOOLA'"

We are investigating failing Storage jobs with the error: "Insufficient privileges to operate on account 'KEBOOLA'" on the AWS US East stack (connection.keboola.com).

Currently, it is not possible to create Snowflake workspaces.

We apologize for the inconvenience and will provide an update in 30 minutes.

UPDATE 2024-12-15 15:33 UTC

We have discovered the root cause and are working on a solution. The next update will be provided as soon as it is resolved or in 30 minutes.

UPDATE 2024-12-15 15:55 UTC

The issue has been identified and fixed. All projects are now operating normally.

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

Broken Data Apps on GCP stacks [EU, US]

We noticed that from about 12:30 CET they stopped working Data Apps on GCP stacks:

We apologize for the inconvenience; we are currently investigating the issue and will provide an update in 30 minutes.

UPDATE 2024-12-11 13:01 UTC: We have identified the root cause, which only affected configurations with authorization enabled or a secret value set. This caused failures during the decryption process. We have fixed the permissions required for decryption in the runtime job, and all systems are now operating normally. We sincerely apologize for the inconvenience.