Is Tinybird down?
Last checked 4m agoNo incidents right now.
Tinybird is operational right now. Last checked 4m ago; the most recent incident resolved 28d ago.
Real-time Tinybird status, recent outages, and incident history: pulled directly from Tinybird's official status page at status.tinybird.co every 5 minutes. Pingoru tracks 125 Tinybird services and has captured 7 incidents in the last 90 days (96.44% uptime). Get email, Slack, Discord, or webhook alerts the moment Tinybird reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- Events APIEvents APIEvents APIEvents APIEvents APIEvents APIEvents APIEvents APIEvents APIEvents API
Timeline · 2 updates
- investigating · Oct 01, 2026, 11:19 AM UTC
Status: Investigating We're investigating an ingestion issue while rotating some ClickHouse replicas Affected components Events API (Degraded performance)
- resolved · Oct 01, 2026, 12:04 PM UTC
Status: Resolved Ingestion has been recovered. We're ingesting the remaining data from the ingestion queue. Affected components Events API (Operational)
Latest: Status: Resolved Ingestion has been recovered. We're ingesting the remaining data from the ingestion queue. Affected components Events API (Operational)
-
- KafkaEvents APISinksGCS ConnectorCopyGCS ConnectorKafkaKafkaEvents APIAPI Endpoints
Timeline · 4 updates
- investigating · Sep 24, 2026, 10:59 AM UTC
Status: Investigating 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. Affected components Query API (Degraded performance) API Endpoints (Degraded performance) ClickHouse HTTP Interface (Degraded performance) GCS Connector (Degraded performance) S3 Connector (Degraded performance) Events API (Degraded performance) Copy (Degraded performance) Sinks (Degraded performance) Kafka (Degraded performance)
- identified · Sep 24, 2026, 11:29 AM UTC
Status: Identified 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. Affected components Query API (Degraded performance) Events API (Degraded performance) Sinks (Operational) API Endpoints (Degraded performance) ClickHouse HTTP Interface (Operational) GCS Connector (Operational) S3 Connector (Operational) Copy (Operational) Kafka (Operational)
- monitoring · Sep 24, 2026, 11:47 AM UTC
Status: Monitoring The fix is rolled out, and everything is back to normal. We keep monitoring to ensure everything works as expected. Affected components ClickHouse HTTP Interface (Operational) Query API (Operational) GCS Connector (Operational) Events API (Operational) Copy (Operational) Sinks (Operational) Kafka (Operational) API Endpoints (Operational) S3 Connector (Operational)
- resolved · Sep 24, 2026, 02:00 PM UTC
Status: Resolved Since we deployed the fix yesterday everything has been working correctly. Affected components Query API (Operational) Events API (Operational) Copy (Operational) API Endpoints (Operational) ClickHouse HTTP Interface (Operational) GCS Connector (Operational) S3 Connector (Operational) Sinks (Operational) Kafka (Operational)
Latest: Status: Resolved Since we deployed the fix yesterday everything has been working correctly. Affected components Query API (Operational) Events API (Operational) Copy (Operational) …
-
- KafkaEvents APISinksGCS ConnectorCopyGCS ConnectorKafkaKafkaCSV ImportsEvents API
Timeline · 5 updates
- investigating · Sep 18, 2026, 08:09 AM UTC
Status: Investigating We've detected degradation across all components in the region due to network issues. Affected components Query API (Degraded performance) Events API (Degraded performance) Kafka (Degraded performance) CSV Imports (Degraded performance) Login (Degraded performance) S3 Connector (Degraded performance) GCS Connector (Degraded performance) ClickHouse HTTP Interface (Degraded performance) API Endpoints (Degraded performance) Copy (Degraded performance) Sinks (Degraded performance)
- monitoring · Sep 18, 2026, 08:18 AM UTC
Status: Monitoring 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" Affected components Query API (Degraded performance) Events API (Degraded performance) CSV Imports (Degraded performance) Sinks (Degraded performance) API Endpoints (Degraded performance) Kafka (Degraded performance) Copy (Degraded performance) Login (Operational) S3 Connector (Degraded performance) GCS Connector (Degraded performance) ClickHouse HTTP Interface (Degraded performance)
- monitoring · Sep 18, 2026, 08:35 AM UTC
Status: Monitoring 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 " Affected components Kafka (Degraded performance) Login (Operational) S3 Connector (Degraded performance) GCS Connector (Degraded performance) ClickHouse HTTP Interface (Degraded performance) Copy (Degraded performance) CSV Imports (Degraded performance) Sinks (Degraded performance) Query API (Degraded performance) API Endpoints (Degraded performance) Events API (Degraded performance)
- monitoring · Sep 18, 2026, 12:25 PM UTC
Status: Monitoring Since 11:10utc we are not detecting more errors. However gcp incident still open so we keep monitoring Affected components Copy (Operational) CSV Imports (Operational) S3 Connector (Operational) GCS Connector (Operational) ClickHouse HTTP Interface (Operational) Query API (Operational) API Endpoints (Operational) Events API (Operational) Kafka (Operational) Sinks (Operational) Login (Operational)
- resolved · Sep 18, 2026, 03:41 PM UTC
Status: Resolved 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." Affected components Events API (Operational) Kafka (Operational) CSV Imports (Operational) Login (Operational) ClickHouse HTTP Interface (Operational) Query API (Operational) API Endpoints (Operational) Copy (Operational) Sinks (Operational) S3 Connector (Operational) GCS Connector (Operational)
Latest: Status: Resolved 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…
-
- KafkaEvents APISinksGCS ConnectorCopyGCS ConnectorKafkaKafkaEvents APILogin
Timeline · 3 updates
- investigating · Sep 10, 2026, 05:22 AM UTC
Status: Investigating Our team is actively investigating the cause and working to restore normal service as quickly as possible. All other regions are operating normally. Affected components Login (Degraded performance) GCS Connector (Degraded performance) Events API (Degraded performance) Copy (Degraded performance) Sinks (Degraded performance) API Endpoints (Degraded performance) ClickHouse HTTP Interface (Degraded performance) Query API (Degraded performance) S3 Connector (Degraded performance) Kafka (Degraded performance)
- investigating · Sep 10, 2026, 05:46 AM UTC
Status: Investigating 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. Affected components GCS Connector (Degraded performance) S3 Connector (Degraded performance) Copy (Degraded performance) Sinks (Degraded performance) API Endpoints (Degraded performance) ClickHouse HTTP Interface (Degraded performance) Query API (Degraded performance) Events API (Degraded performance) Kafka (Degraded performance) Login (Degraded performance)
- resolved · Sep 10, 2026, 06:32 AM UTC
Status: Resolved 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. Affected components Query API (Operational) Events API (Operational) Kafka (Operational) GCS Connector (Operational) S3 Connector (Operational) Copy (Operational) Sinks (Operational) API Endpoints (Operational) Login (Operational) ClickHouse HTTP Interface (Operational)
Latest: Status: Resolved 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…
-
- CopyCopyCopyCopyCopyCopyCopyCopyCopyCopy
Timeline · 2 updates
- identified · Aug 15, 2026, 09:15 AM UTC
Status: Identified 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. Affected components Copy (Degraded performance) Copy (Degraded performance)
- resolved · Aug 15, 2026, 12:20 PM UTC
Status: Resolved 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. Affected components Copy (Operational) Copy (Operational)
Latest: Status: Resolved 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 preve…
-
See the full Tinybird outage history
2 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Tinybird outage history →Or sign up free to get alerts when Tinybird breaks · 10 free monitors · No credit card
Incident record
Since April 2026 · incident.io · 125 components checked every 5 minutesThe longest incident in the last year, Degraded performance in the AWS us-east public cluster. on June 22, 2026, ran for 47 hours.
Most affected components, last 12 months
- Events API18
- Query API16
- API Endpoints15
- Copy15
- Kafka15
Latest incidents
- Ingestion issue in public-a
Status: Investigating We're investigating an ingestion issue while rotating some ClickHouse replicas Affected components Events API (Degraded performance)
- eu-west-1 degraded
Status: Investigating 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…
- Network issues in gcp-europe-west3
Status: Investigating We've detected degradation across all components in the region due to network issues. Affected components Query API (Degraded…
- Ingestion issue in public-a ResolvedStarted Oct 01, 2026, 11:19 AM UTC · Resolved Oct 01, 2026, 12:04 PM UTC · 45m
- eu-west-1 degraded ResolvedStarted Sep 24, 2026, 10:59 AM UTC · Resolved Sep 24, 2026, 02:00 PM UTC · 3h
- Network issues in gcp-europe-west3 ResolvedStarted Sep 18, 2026, 08:09 AM UTC · Resolved Sep 18, 2026, 03:41 PM UTC · 7h 31m
- Service Disruption – AWS eu-west-1 ResolvedStarted Sep 10, 2026, 05:22 AM UTC · Resolved Sep 10, 2026, 06:32 AM UTC · 1h 10m
- On-demand copies are failing ResolvedStarted Aug 15, 2026, 09:15 AM UTC · Resolved Aug 15, 2026, 12:20 PM UTC · 3h 5m
- Started Aug 12, 2026, 10:38 AM UTC · Resolved Aug 12, 2026, 11:34 AM UTC · 55m
- Started Aug 06, 2026, 07:59 AM UTC · Resolved Aug 06, 2026, 08:20 AM UTC · 21m