Looking for an update now? Check the current status, or follow Tinybird for future changes.
93.1%of 58 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
90%
30
3
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 23Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
No source-attested incident records are available for the current collector history. Older legacy archive records remain available below.
Legacy Incident Archive
15 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
August 2026
Reads and writes degraded on US East (AWS) public cluster
Source not attested
Last archived state: resolved
View archived record details
investigating
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.
investigating
We're investigating an issue causing delays in data ingestion for some workspaces in the the **US East (AWS)** region
Degradation on GCP europe-west2 public cluster
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
investigating
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.
July 2026
Errors when creating and deleting replicas
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have identified the issue and it should be fixed now. We're already seeing some new replicas being provisioned. We'll keep monitoring.
investigating
We're investigating an issue when creating or deleting new replicas. This affects cluster replicas and jobs on-demand (populates and copies).
A significant fraction of Clickhouse replicas marked as unhealthy
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
monitoring
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.
investigating
Some database replicas have been marked as unhealthy incorrectly. This is affecting how traffic is distributed among healthy replicas, and in some clusters it's resulting in degraded performance and some errors.
Kafka connector is working well, ingestion is catching up
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
GCP europe-west3 still having problems, we're redeploying the region
monitoring
The problem is fixed now ingestion is recovered
identified
We've identified the issue and are deploying a fix
investigating
A Kafka connector update is affecting message consumption
investigating
Kafka connector is not consuming messages
High error rate on GCP europe-west-3
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
We've identified the issue and applied a fix. We're monitoring the situation.
investigating
We're investigating a sudden increase in error rate in the region.
June 2026
Degraded performance in the AWS us-east public cluster.
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
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.
monitoring
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
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
We keep ingesting the delayed real time data
monitoring
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
identified
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.
identified
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.
investigating
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.
investigating
There’s a performance degradation in the public cluster on AWS us-east.
We are investigate a degradation in AWS US EAST public cluster
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We deploying a fix to improve the stability of the platform
investigating
We are seeing a degradation of the performance in the public AWS US EAST cluster
GCP EU Public-a cluster is saturated
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
Cluster is recovering
identified
Public cluster in gcp-europe-west3 is slightly degraded. We're working on restoring int.
