Tinybird Outage History
Tinybird is up right nowPingoru has recorded 49 incidents for Tinybird: 49 in the last 12 months and 7 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 2 | 6 of 720 (1%) |
| May 2026 | 4 | 10 of 744 (1%) |
| June 2026 | 3 | 49 of 720 (7%) |
| July 2026 | 4 | 4 of 744 (0%) |
| August 2026 | 3 | 4 of 744 (1%) |
| September 2026 | 3 | 12 of 720 (2%) |
| October 2026 | 1 | 1 of 744 (0%) |
| November 2026 | 0 | 0 of 25 (0%) |
Incidents, newest first
Minor October 1, 2026 Ingestion issue in public-a 45m GCP europe-west3 (Events API), AWS us-east-1 (Events API), AWS eu-central-1 (Events API), AWS us-west-2 (Events API) and 6 more
Started Oct 01, 2026, 11:19 AM UTC· resolved Oct 01, 2026, 12:04 PM UTC
- investigating Oct 01, 2026, 11:19 AM UTC
We're investigating an ingestion issue while rotating some ClickHouse replicas
- resolved Oct 01, 2026, 12:04 PM UTC
Ingestion has been recovered. We're ingesting the remaining data from the ingestion queue.
- resolved Oct 01, 2026, 12:04 PM UTC
Ingestion has been recovered. We're ingesting the remaining data from the ingestion queue.
Minor September 24, 2026 eu-west-1 degraded 3h GCP europe-west2 (Kafka), GCP europe-west3 (Events API), AWS eu-central-1 (Sinks), GCP europe-west3 (GCS Connector) and 84 more
Started Sep 24, 2026, 10:59 AM UTC· resolved Sep 24, 2026, 02:00 PM UTC
- investigating Sep 24, 2026, 10:59 AM UTC
We detected some degradation in the eu-west-1 region due to a metadata database failure. The team is looking into it, and we'll update you with more information soon.
- identified Sep 24, 2026, 11:29 AM UTC
The root cause was identified. A major traffic spike hit an endpoint with synchronous metadata database queries, affecting some applications' performance and causing a cascading database failure, which has already recovered. A fix is being deployed and should restore the region's performance.
- monitoring Sep 24, 2026, 11:47 AM UTC
The fix is rolled out, and everything is back to normal. We keep monitoring to ensure everything works as expected.
- resolved Sep 24, 2026, 02:00 PM UTC
Since we deployed the fix yesterday everything has been working correctly.
- resolved Sep 24, 2026, 02:00 PM UTC
Since we deployed the fix yesterday everything has been working correctly.
Minor September 18, 2026 Network issues in gcp-europe-west3 7h 31m GCP europe-west2 (Kafka), GCP europe-west3 (Events API), AWS eu-central-1 (Sinks), GCP europe-west3 (GCS Connector) and 99 more
Started Sep 18, 2026, 08:09 AM UTC· resolved Sep 18, 2026, 03:41 PM UTC
- investigating Sep 18, 2026, 08:09 AM UTC
We've detected degradation across all components in the region due to network issues.
- monitoring Sep 18, 2026, 08:18 AM UTC
We've detected degradation across all components in the region due to network issues related to an ongoing incident on GCP: "Virtual Private Cloud (VPC) experiencing intermittent packet loss and elevated latency in europe-west3-c zone"
- monitoring Sep 18, 2026, 08:35 AM UTC
We've detected degradation across all components in the region due to network issues related to an ongoing incident on GCP: "Virtual Private Cloud (VPC) experiencing intermittent packet loss and elevated latency in europe-west3-c zone. Event ID: LJCMWTL "
- monitoring Sep 18, 2026, 12:25 PM UTC
Since 11:10utc we are not detecting more errors. However gcp incident still open so we keep monitoring
- resolved Sep 18, 2026, 03:41 PM UTC
GCP marked as resolved the incident impacting europe-west3: "The issue with Virtual Private Cloud (VPC) has been resolved for all affected users as of Friday, 2026-09-18 05:35 UTC+2."
- resolved Sep 18, 2026, 03:41 PM UTC
GCP marked as resolved the incident impacting europe-west3: "The issue with Virtual Private Cloud (VPC) has been resolved for all affected users as of Friday, 2026-09-18 05:35 UTC+2."
Minor September 10, 2026 Service Disruption – AWS eu-west-1 1h 10m GCP europe-west2 (Kafka), GCP europe-west3 (Events API), AWS eu-central-1 (Sinks), GCP europe-west3 (GCS Connector) and 94 more
Started Sep 10, 2026, 05:22 AM UTC· resolved Sep 10, 2026, 06:32 AM UTC
- investigating Sep 10, 2026, 05:22 AM UTC
Our team is actively investigating the cause and working to restore normal service as quickly as possible. All other regions are operating normally.
- investigating Sep 10, 2026, 05:46 AM UTC
The service disruption affecting our AWS eu-west-1 region has been resolved and the region is operating as normal. We are continuing to investigate the root cause and will share any relevant updates. All other regions were unaffected.
- resolved Sep 10, 2026, 06:32 AM UTC
We have identified the root cause of this morning's disruption: a fault in an internal monitoring component caused resource exhaustion on some infrastructure hosts, impacting service availability in the region. The issue has been resolved and the region is operating as normal.
- resolved Sep 10, 2026, 06:32 AM UTC
We have identified the root cause of this morning's disruption: a fault in an internal monitoring component caused resource exhaustion on some infrastructure hosts, impacting service availability in the region. The issue has been resolved and the region is operating as normal.
Minor August 15, 2026 On-demand copies are failing 3h 5m GCP europe-west2 (Copy), AWS eu-central-1 (Copy), AWS us-east-1 (Copy), AWS us-west-2 (Copy) and 6 more
Started Aug 15, 2026, 09:15 AM UTC· resolved Aug 15, 2026, 12:20 PM UTC
- identified Aug 15, 2026, 09:15 AM UTC
Some customers were unable to provision new on-demand replicas. Existing replicas and normal (non on-demand) replica provisioning were not affected. Queries and ingestion on already-running replicas continued to operate normally throughout the window.
- resolved Aug 15, 2026, 12:20 PM UTC
A fix was rolled out to the replica provisioning path. Subsequent on-demand replica creations completed successfully. We are conducting a follow-up review to prevent recurrence. We apologize for the disruption and any inconvenience caused.
- resolved Aug 15, 2026, 12:20 PM UTC
A fix was rolled out to the replica provisioning path. Subsequent on-demand replica creations completed successfully. We are conducting a follow-up review to prevent recurrence. We apologize for the disruption and any inconvenience caused.
Minor August 12, 2026 Reads and writes degraded on US East (AWS) public cluster 55m
Started Aug 12, 2026, 10:38 AM UTC· resolved Aug 12, 2026, 11:34 AM UTC
- investigating Aug 12, 2026, 10:38 AM UTC
We're investigating an issue causing delays in data ingestion for some workspaces in the the US East (AWS) region
- investigating Aug 12, 2026, 10:56 AM UTC
We're investigating a service disruption in our US East (AWS) public cluster that began at 10:25 UTC and is affecting both reads and writes: API queries may fail or return errors, and incoming data is being queued. Our team is actively investigating and working to restore stability.
- resolved Aug 12, 2026, 11:34 AM UTC
We have successfully identified the root cause of the US East (AWS) public cluster disruption and fully restored both read and write operations; our team is currently processing the backlog of queued inserts accumulated during the incident.
- resolved Aug 12, 2026, 11:34 AM UTC
We have successfully identified the root cause of the US East (AWS) public cluster disruption and fully restored both read and write operations; our team is currently processing the backlog of queued inserts accumulated during the incident.
Minor August 6, 2026 Degradation on GCP europe-west2 public cluster 21m GCP europe-west2 (Kafka), GCP europe-west3 (Events API), GCP europe-west3 (GCS Connector), GCP europe-west2 (Copy) and 86 more
Started Aug 06, 2026, 07:59 AM UTC· resolved Aug 06, 2026, 08:20 AM UTC
- investigating Aug 06, 2026, 07:59 AM UTC
We're investigating an issue causing degradation on GCP europe-west2 public-a cluster. We'll keep you updated as soon as we find the issue.
- monitoring Aug 06, 2026, 08:11 AM UTC
The issue was caused due to a peak of heavy queries causing OOM in one of the replicas. This is now fixed and everything should be working properly now. We'll keep monitoring.
- resolved Aug 06, 2026, 08:20 AM UTC
The incident is now resolved.
- resolved Aug 06, 2026, 08:20 AM UTC
The incident is now resolved.
Minor July 30, 2026 Errors when creating and deleting replicas 33m GCP europe-west2 (Copy), AWS eu-central-1 (Copy), AWS us-east-1 (Copy), AWS us-west-2 (Copy) and 6 more
Started Jul 30, 2026, 10:40 AM UTC· resolved Jul 30, 2026, 11:13 AM UTC
- investigating Jul 30, 2026, 10:40 AM UTC
We're investigating an issue when creating or deleting new replicas. This affects cluster replicas and jobs on-demand (populates and copies).
- monitoring Jul 30, 2026, 10:56 AM UTC
We have identified the issue and it should be fixed now. We're already seeing some new replicas being provisioned. We'll keep monitoring.
- resolved Jul 30, 2026, 11:13 AM UTC
The incident is now resolved.
Minor July 28, 2026 A significant fraction of Clickhouse replicas marked as unhealthy 1h 20m GCP europe-west2 (Kafka), GCP europe-west3 (Events API), BI Connector, AWS eu-central-1 (Sinks) and 108 more
Started Jul 28, 2026, 06:44 AM UTC· resolved Jul 28, 2026, 08:04 AM UTC
- investigating Jul 28, 2026, 06:44 AM UTC
Load balancers seem to be down, everything is affected
- monitoring Jul 28, 2026, 07:20 AM UTC
We've marked as healthy the database replicas that were incorrectly marked as unhealthy. We're confirming the cause and have a few suspects. We keep monitoring the situation.
- monitoring Jul 28, 2026, 07:38 AM UTC
We have narrowed the root cause to an automatic Ubuntu package upgrade triggering the restart of our database services on many servers, and those being marked unhealthy as a result. Service should be generally restored already.
- resolved Jul 28, 2026, 08:04 AM UTC
We've confirmed that service has been restored fully.
Minor July 17, 2026 Kafka connector is working well, ingestion is catching up 36m GCP europe-west2 (Kafka), AWS eu-west-1 (Kafka), AWS us-east-1 (Kafka), GCP us-east4 (Kafka) and 6 more
Started Jul 17, 2026, 08:26 AM UTC· resolved Jul 17, 2026, 09:03 AM UTC
- investigating Jul 17, 2026, 08:26 AM UTC
Kafka connector is not consuming messages
- investigating Jul 17, 2026, 08:29 AM UTC
A Kafka connector update is affecting message consumption
- identified Jul 17, 2026, 08:31 AM UTC
We've identified the issue and are deploying a fix
- monitoring Jul 17, 2026, 08:40 AM UTC
The problem is fixed now ingestion is recovered
- monitoring Jul 17, 2026, 08:50 AM UTC
GCP europe-west3 still having problems, we're redeploying the region
- resolved Jul 17, 2026, 09:03 AM UTC
Ingestion is up to date now
Minor July 1, 2026 High error rate on GCP europe-west-3 59m GCP europe-west2 (Copy), AWS us-east-1 (CSV Imports), GCP europe-west3 (Login), AWS us-east-1 (BI Connector) and 18 more
Started Jul 01, 2026, 04:21 AM UTC· resolved Jul 01, 2026, 05:20 AM UTC
- investigating Jul 01, 2026, 04:21 AM UTC
We're investigating a sudden increase in error rate in the region.
- monitoring Jul 01, 2026, 05:08 AM UTC
We've identified the issue and applied a fix. We're monitoring the situation.
- resolved Jul 01, 2026, 05:20 AM UTC
The situation is now resolved. There shouldn't be more errors.
Minor June 22, 2026 Degraded performance in the AWS us-east public cluster. 1d 22h GCP europe-west2 (Copy), AWS us-east-1 (Copy), GCP northamerica-northeast2 (Query API), GCP us-east4 (Copy) and 2 more
Started Jun 22, 2026, 04:51 PM UTC· resolved Jun 24, 2026, 03:43 PM UTC
- investigating Jun 22, 2026, 04:51 PM UTC
There’s a performance degradation in the public cluster on AWS us-east.
- investigating Jun 22, 2026, 05:49 PM UTC
We keep working on identifying the root cause. There's impact in both reads and writes, and in all clusters in the region as the incident is affecting a shared component. We are storing the data that gets to the Events API to retry the inserts later.
- identified Jun 22, 2026, 06:52 PM UTC
We're still working on stabilising the region. We're struggling with Zookeeper, in charge of coordination between ClickHouse replicas, which is why write are a lot more affected than reads. We've just tweaked a couple parameters that hope will aid the situation.
- identified Jun 22, 2026, 09:30 PM UTC
We've already identified the root cause and we're working through the fix. Real-time ingestion is now fully available, we're working on ingesting past data that hasn't been processed yet.
- monitoring Jun 22, 2026, 09:56 PM UTC
We've identify the root cause and we are recovering the retries from the HFI ingestion at the moment. The platform should be stable now
- monitoring Jun 22, 2026, 10:05 PM UTC
We keep ingesting the delayed real time data
- monitoring Jun 23, 2026, 10:26 AM UTC
We're continuing to work through a backlog of delayed ingestion on our AWS US East 1 shared cluster following yesterday's degradation. Our coordination layer was resized last night and the bulk of the impact has cleared. Recovery is taking longer than expected, so affected workspaces may continue to see ingestion lag while we work through the remaining queue.
- monitoring Jun 23, 2026, 02:03 PM UTC
The bulk of the earlier retries has now been recovered, and no new ingestion errors are being introduced on the customer side. Recovery is progressing more slowly than we'd like because we are currently being rate-limited by our upstream storage provider, which is limiting how quickly we can drain the remaining retries. No data has been lost, all affected inserts are being safely retried. We'll provide the next update as soon as we see meaningful progress on either front.
- monitoring Jun 24, 2026, 07:54 AM UTC
We are still getting rate-limited by our upstream storage provider but we are draining retries faster than before because of some optimizations we have made on the system. We are working on accelerating them as much as possible but we still have some retries in the queue. No data has been lost, all affected inserts are being safely retried.
- resolved Jun 24, 2026, 03:43 PM UTC
All data has been recovered and the system health is back to normal
Minor June 16, 2026 We are investigate a degradation in AWS US EAST public cluster 48m GCP northamerica-northeast2 (Query API), GCP us-east4 (API Endpoints), GCP us-east4 (Query API), AWS eu-central-1 (API Endpoints)
Started Jun 16, 2026, 01:38 PM UTC· resolved Jun 16, 2026, 02:27 PM UTC
- investigating Jun 16, 2026, 01:38 PM UTC
We are seeing a degradation of the performance in the public AWS US EAST cluster
- monitoring Jun 16, 2026, 01:51 PM UTC
We deploying a fix to improve the stability of the platform
- resolved Jun 16, 2026, 02:27 PM UTC
We've deployed a fix to improve the stability of the platform. Sorry for the inconvenience
Minor June 16, 2026 GCP EU Public-a cluster is saturated 53m GCP europe-west2 (Copy), AWS us-east-1 (CSV Imports), AWS us-east-1 (BI Connector), AWS eu-central-1 (Kafka) and 16 more
Started Jun 16, 2026, 10:37 AM UTC· resolved Jun 16, 2026, 11:31 AM UTC
- identified Jun 16, 2026, 10:37 AM UTC
Public cluster in gcp-europe-west3 is slightly degraded. We're working on restoring int.
- monitoring Jun 16, 2026, 11:22 AM UTC
Cluster is recovering
- resolved Jun 16, 2026, 11:31 AM UTC
Cluster operating normally now
Minor May 27, 2026 Degradation of the service in multiple regions 29m BI Connector, GCP europe-west2 (Copy), AWS us-east-1 (CSV Imports), GCP europe-west3 (Login) and 23 more
Started May 27, 2026, 12:25 PM UTC· resolved May 27, 2026, 12:55 PM UTC
- investigating May 27, 2026, 12:25 PM UTC
We are investigation an increase of errors in multiple regions
- monitoring May 27, 2026, 12:42 PM UTC
We've identified a merge request that cause an expected moved of pods in Kubernetes causing a spike of 503. We are not seeing any more errors. We will keep monitoring everything
- resolved May 27, 2026, 12:55 PM UTC
The platform is stable again. We are going to review which has been the impact of the incident and contain the customers affected by it.
Minor May 22, 2026 Increased latencies in aws-us-west-2 44m GCP northamerica-northeast2 (Query API), GCP us-east4 (API Endpoints), GCP us-east4 (Query API), AWS eu-central-1 (API Endpoints) and 2 more
Started May 22, 2026, 03:16 PM UTC· resolved May 22, 2026, 04:01 PM UTC
- investigating May 22, 2026, 03:16 PM UTC
We're investigating an increase in latencies in the region
- monitoring May 22, 2026, 03:42 PM UTC
We've identified the root cause and applied the fix, and latencies are back to normal now
- resolved May 22, 2026, 04:01 PM UTC
The platform is back to normal and everything is stable
Minor May 8, 2026 Connectivity issues affecting traffic in AWS us-east 5h 46m GCP northamerica-northeast2 (Query API), GCP us-east4 (API Endpoints), GCP us-east4 (Query API), AWS eu-central-1 (API Endpoints) and 6 more
Started May 08, 2026, 10:30 AM UTC· resolved May 08, 2026, 04:16 PM UTC
- investigating May 08, 2026, 10:30 AM UTC
We're currently investigating a connectivity issue affecting a subset of traffic in region AWS us-east. Some requests may experience increased latency or occasional delays. Our initial analysis indicates this is caused by network-level packet loss on the path between our load balancer infrastructure and the public internet. At this stage, we do not believe this is related to application code, recent changes, or backend service saturation. We're continuing to investigate at the infrastructure and network layer, including host-level networking, NIC behavior, and potential AWS network/AZ conditions. We're also working on mitigation options to reduce the impact while we identify the root cause. We'll share updates as soon as we have more information.
- resolved May 08, 2026, 04:16 PM UTC
We've identified the root cause that was slowing down a small percentage of requests and have applied the solution.
Minor May 5, 2026 Degraded ingestion in gcp-us-east4 2h 54m AWS eu-central-1 (Kafka), AWS eu-central-1 (S3 Connector), GCP northamerica-northeast2 (Kafka), GCP us-east4 (S3 Connector) and 5 more
Started May 05, 2026, 03:19 PM UTC· resolved May 05, 2026, 06:13 PM UTC
- investigating May 05, 2026, 03:19 PM UTC
A component of the ingestion infra is degraded and ingestion is delayed in the region
- investigating May 05, 2026, 03:33 PM UTC
We keep working on stabilizing the situation. Ingestion is still delayed.
- monitoring May 05, 2026, 03:44 PM UTC
Live ingestion is now much more stable, and shortly we'll start catching up with delayed inserts.
- monitoring May 05, 2026, 05:46 PM UTC
There are still some delayed inserts being processed. We'll resolve the incident when all ingestion is caught up.
- resolved May 05, 2026, 06:13 PM UTC
We've caught up with ingestion.
Minor April 28, 2026 Job Queue Degradation 4h 48m
Started Apr 28, 2026, 10:37 AM UTC· resolved Apr 28, 2026, 03:26 PM UTC
- investigating Apr 28, 2026, 10:37 AM UTC
We are currently investigating an issue affecting our job queue. Some jobs may be delayed or not processing as expected. Our team is actively looking into the root cause. We apologize for the inconvenience.
- monitoring Apr 28, 2026, 11:32 AM UTC
A fix has been applied to resolve the job queue processing issue. We are now monitoring the system to ensure stability and that all pending jobs are being processed correctly. No action is needed on your end. We will confirm full resolution shortly.
- resolved Apr 28, 2026, 03:26 PM UTC
The job queue processing issue has been fully resolved. All pending jobs are being processed and the system is operating normally. We apologize for the disruption caused and thank you for your patience.
Minor April 19, 2026 Several Tinybird services might be affected 1h 10m GCP europe-west3 (Login), AWS eu-central-1 (Login), GCP northamerica-northeast2 (Login), AWS ap-southeast-2 (Login)
Started Apr 19, 2026, 06:56 PM UTC· resolved Apr 19, 2026, 08:07 PM UTC
- identified Apr 19, 2026, 06:56 PM UTC
Due to the security incident on a third-party provider, we have initiated a credential rotation across our environment variables. Services depending on these credentials may be temporarily disrupted. ETA for resolution: under investigation. Updates to follow.
- resolved Apr 19, 2026, 08:07 PM UTC
The credential rotation has been completed successfully. All services are operating normally and the impact caused by the incident has been resolved. We appreciate your patience during this time. If you continue to experience any issues, please don't hesitate to reach out.
Minor March 11, 2026 Load balance unresponsive in GCP US East 4h 42m
Started Mar 11, 2026, 01:26 PM UTC· resolved Mar 11, 2026, 06:09 PM UTC
- monitoring Mar 11, 2026, 01:26 PM UTC
Incident resolved and all workflows are working normally.
- investigating Mar 11, 2026, 03:22 PM UTC
Load balancing is experiencing intermittent errors - we continue to investigate
- resolved Mar 11, 2026, 06:09 PM UTC
We were impacted by a spike of requests to the v0/events endpoint which bypass our protections in our load balancers causing a saturation of them which impacted on the rest of the requests. We have added extra resources to be able to handle any news spikes and we started to work on better protections to avoid any new incident
Notice March 11, 2026 Load balance unresponsive in GCP US East 4h 42m
Started Mar 11, 2026, 01:26 PM UTC· resolved Mar 11, 2026, 06:09 PM UTC
No vendor updates were posted for this incident.
Major March 9, 2026 Public cluster in GCP us east down –
Started Mar 09, 2026, 09:58 AM UTC· resolved Mar 09, 2026, 09:58 AM UTC
No vendor updates were posted for this incident.
Minor March 9, 2026 Public cluster in GCP us east down 6m GCP europe-west2 (Copy), AWS us-east-1 (CSV Imports), AWS us-east-1 (BI Connector), AWS eu-central-1 (Kafka) and 25 more
Started Mar 09, 2026, 09:52 AM UTC· resolved Mar 09, 2026, 09:58 AM UTC
- investigating Mar 09, 2026, 09:52 AM UTC
Ingestion and queries from GCP us east public cluster are failing.
- resolved Mar 09, 2026, 09:58 AM UTC
Everything should be working now
Minor March 6, 2026 UI is not accessible 1h Tinybird UI
Started Mar 06, 2026, 01:28 PM UTC· resolved Mar 06, 2026, 02:28 PM UTC
- investigating Mar 06, 2026, 01:28 PM UTC
The cloud.tinybird.co "cloud.tinybird.co": http://cloud.tinybird.co is currently not accessible
- identified Mar 06, 2026, 01:32 PM UTC
A problem with an internal monitoring app is causing this, fix is underway.
- identified Mar 06, 2026, 01:36 PM UTC
UI load is currently returning errors due to an identified problem being fixed
- investigating Mar 06, 2026, 01:44 PM UTC
We're investigating a problem affecting the UI
- monitoring Mar 06, 2026, 02:15 PM UTC
Access to the UI is working again
- resolved Mar 06, 2026, 02:28 PM UTC
UI is fully restored and operative