Is Tinybird down?

Status: Investigating We are investigation an increase of errors in multiple regions Affected components Kafka (Partial outage) BI Connector (Partial outage) Query API (Partial outage) BI Connector (Partial outage) Copy (Partial outage) Query API (Partial outage) Events API (Partial outage) Copy (Partial outage) Sinks (Partial outage) Kafka (Partial outage) Kafka (Partial outage) API Endpoints (Partial outage) API Endpoint (Partial outage) GCS Connector (Partial outage) GCS Connector (Partial outage) API Endpoints (Partial outage) Copy (Partial outage) Copy (Partial outage) BI Connector (Partial outage) S3 Connector (Partial outage) Copy (Partial outage) Login (Partial outage) Kafka (Partial outage) API Endpoints (Partial outage) Copy (Partial outage) CSV Imports (Partial outage) Sinks (Partial outage) Kafka (Partial outage) Kafka (Partial outage) Events API (Partial outage) CSV Imports (Partial outage) Sinks (Partial outage) S3 Connector (Partial outage) GCS Connector (Partial outage) Query API (Partial outage) Query API (Partial outage) API Endpoints (Partial outage) Login (Partial outage) Login (Partial outage) Login (Partial outage) API Endpoints (Partial outage) Sinks (Partial outage) DynamoDB Connector (Partial outage) Query API (Partial outage) GCS Connector (Partial outage) Query API (Partial outage) DynamoDB Connector (Partial outage) Events API (Partial outage) Sink (Partial outage) Sinks (Partial outage) GCS Connector (Partial outage) Events API (Partial outage) BI Connector (Partial outage) CSV Imports (Partial outage) Login (Partial outage) Login (Partial outage) S3 Connector (Partial outage) Events API (Partial outage) Events API (Partial outage) CSV Imports (Partial outage) S3 Connector (Partial outage) S3 Connector (Partial outage) S3 Connector (Partial outage) GCS Connector (Partial outage)

Status: Monitoring 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 Affected components Login (Operational) Copy (Operational) Query API (Operational) CSV Imports (Operational) Login (Operational) Login (Operational) BI Connector (Operational) Kafka (Operational) API Endpoints (Operational) BI Connector (Operational) Query API (Operational) API Endpoints (Operational) Events API (Operational) GCS Connector (Operational) GCS Connector (Operational) Copy (Operational) API Endpoints (Operational) Events API (Operational) GCS Connector (Operational) Kafka (Operational) Login (Operational) Copy (Operational) Copy (Operational) Login (Operational) Sink (Operational) Query API (Operational) CSV Imports (Operational) Sinks (Operational) Kafka (Operational) Kafka (Operational) Query API (Operational) API Endpoints (Operational) Events API (Operational) DynamoDB Connector (Operational) Copy (Operational) API Endpoints (Operational) S3 Connector (Operational) Events API (Operational) S3 Connector (Operational) S3 Connector (Operational) BI Connector (Operational) Login (Operational) DynamoDB Connector (Operational) API Endpoint (Operational) Sinks (Operational) GCS Connector (Operational) GCS Connector (Operational) Query API (Operational) BI Connector (Operational) Kafka (Operational) CSV Imports (Operational) Sinks (Operational) Query API (Operational) S3 Connector (Operational) GCS Connector (Operational) Copy (Operational) Events API (Operational) Events API (Operational) CSV Imports (Operational) S3 Connector (Operational) S3 Connector (Operational) Kafka (Operational) Sinks (Operational) Sinks (Operational)

Status: Resolved 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. Affected components API Endpoints (Operational) BI Connector (Operational) API Endpoints (Operational) S3 Connector (Operational) Copy (Operational) Kafka (Operational) GCS Connector (Operational) GCS Connector (Operational) Events API (Operational) Query API (Operational) GCS Connector (Operational) Events API (Operational) Query API (Operational) CSV Imports (Operational) Copy (Operational) Sinks (Operational) Login (Operational) Login (Operational) DynamoDB Connector (Operational) S3 Connector (Operational) GCS Connector (Operational) CSV Imports (Operational) Login (Operational) API Endpoint (Operational) S3 Connector (Operational) Kafka (Operational) Copy (Operational) CSV Imports (Operational) GCS Connector (Operational) Query API (Operational) Events API (Operational) Query API (Operational) Copy (Operational) Login (Operational) Sink (Operational) Kafka (Operational) BI Connector (Operational) CSV Imports (Operational) Sinks (Operational) Query API (Operational) S3 Connector (Operational) Sinks (Operational) API Endpoints (Operational) Kafka (Operational) BI Connector (Operational) API Endpoints (Operational) BI Connector (Operational) Kafka (Operational) Kafka (Operational) Sinks (Operational) API Endpoints (Operational) Query API (Operational) S3 Connector (Operational) Login (Operational) DynamoDB Connector (Operational) Events API (Operational) Login (Operational) Events API (Operational) S3 Connector (Operational) Copy (Operational) Copy (Operational) Sinks (Operational) Events API (Operational) GCS Connector (Operational)

Status: Investigating We're investigating an increase in latencies in the region Affected components API Endpoints (Degraded performance) Query API (Degraded performance)

Status: Monitoring We've identified the root cause and applied the fix, and latencies are back to normal now Affected components API Endpoints (Operational) Query API (Operational)

Status: Resolved The platform is back to normal and everything is stable Affected components API Endpoints (Operational) Query API (Operational)

Status: Investigating 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. Affected components API Endpoints (Degraded performance) Events API (Degraded performance) Query API (Degraded performance)

Status: Resolved We've identified the root cause that was slowing down a small percentage of requests and have applied the solution. Affected components API Endpoints (Operational) Events API (Operational) Query API (Operational)

Status: Investigating A component of the ingestion infra is degraded and ingestion is delayed in the region Affected components S3 Connector (Partial outage) Events API (Partial outage) Kafka (Partial outage)

Status: Investigating We keep working on stabilizing the situation. Ingestion is still delayed. Affected components Events API (Partial outage) Kafka (Partial outage) S3 Connector (Partial outage)

Status: Monitoring Live ingestion is now much more stable, and shortly we'll start catching up with delayed inserts. Affected components Events API (Degraded performance) Kafka (Degraded performance) S3 Connector (Degraded performance)

Status: Monitoring There are still some delayed inserts being processed. We'll resolve the incident when all ingestion is caught up. Affected components Events API (Degraded performance) Kafka (Degraded performance) S3 Connector (Degraded performance)

Status: Resolved We've caught up with ingestion. Affected components Events API (Operational) Kafka (Operational) S3 Connector (Operational)

Status: Investigating 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.

Status: Monitoring 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.

Status: Resolved 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.