Tinybird Outage History

Tinybird is up right now

There were 13 Tinybird outages since February 11, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.tinybird.co

Minor April 28, 2026

Job Queue Degradation

Detected by Pingoru
Apr 28, 2026, 03:26 PM UTC
Resolved
Apr 28, 2026, 03:26 PM UTC
Duration
—
Timeline · 3 updates
  1. investigating Apr 28, 2026, 10:37 AM UTC

    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.

  2. monitoring Apr 28, 2026, 11:32 AM UTC

    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.

  3. resolved Apr 28, 2026, 03:26 PM UTC

    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.

Read the full incident report →

Minor April 19, 2026

Several Tinybird services might be affected

Detected by Pingoru
Apr 19, 2026, 08:07 PM UTC
Resolved
Apr 19, 2026, 08:07 PM UTC
Duration
—
Affected: Login
Timeline · 2 updates
  1. identified Apr 19, 2026, 06:56 PM UTC

    Status: Identified 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. Affected components Login (Degraded performance) Login (Degraded performance) Login (Degraded performance) Login (Degraded performance) Login (Degraded performance) Login (Degraded performance) Login (Degraded performance) Login (Degraded performance)

  2. resolved Apr 19, 2026, 08:07 PM UTC

    Status: Resolved 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. Affected components Login (Operational) Login (Operational) Login (Operational) Login (Operational) Login (Operational) Login (Operational) Login (Operational) Login (Operational)

Read the full incident report →

Minor March 11, 2026

Load balance unresponsive in GCP US East

Detected by Pingoru
Mar 11, 2026, 06:09 PM UTC
Resolved
Mar 11, 2026, 06:09 PM UTC
Duration
—
Timeline · 3 updates
  1. monitoring Mar 11, 2026, 01:26 PM UTC

    Status: Monitoring Incident resolved and all workflows are working normally.

  2. investigating Mar 11, 2026, 03:22 PM UTC

    Status: Investigating Load balancing is experiencing intermittent errors - we continue to investigate

  3. resolved Mar 11, 2026, 06:09 PM UTC

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

Read the full incident report →

Minor March 6, 2026

UI is not accessible

Detected by Pingoru
Mar 06, 2026, 02:28 PM UTC
Resolved
Mar 06, 2026, 02:28 PM UTC
Duration
—
Affected: Tinybird UI
Timeline · 6 updates
  1. investigating Mar 06, 2026, 01:28 PM UTC

    Status: Investigating The cloud.tinybird.co "cloud.tinybird.co": http://cloud.tinybird.co is currently not accessible

  2. identified Mar 06, 2026, 01:32 PM UTC

    Status: Identified A problem with an internal monitoring app is causing this, fix is underway.

  3. identified Mar 06, 2026, 01:36 PM UTC

    Status: Identified UI load is currently returning errors due to an identified problem being fixed

  4. investigating Mar 06, 2026, 01:44 PM UTC

    Status: Investigating We're investigating a problem affecting the UI Affected components Tinybird UI (Partial outage)

  5. monitoring Mar 06, 2026, 02:15 PM UTC

    Status: Monitoring Access to the UI is working again Affected components Tinybird UI (Operational)

  6. resolved Mar 06, 2026, 02:28 PM UTC

    Status: Resolved UI is fully restored and operative Affected components Tinybird UI (Operational)

Read the full incident report →

Minor March 3, 2026

GCP us-east4 region degraded

Detected by Pingoru
Mar 03, 2026, 07:10 PM UTC
Resolved
Mar 03, 2026, 07:10 PM UTC
Duration
—
Affected: KafkaSinksS3 ConnectorGCS ConnectorEvents APIQuery APIAPI EndpointsCopyCSV Imports
Timeline · 2 updates
  1. monitoring Mar 03, 2026, 05:53 PM UTC

    Status: Monitoring The region is degraded with some high latencies and rate limit possibly appled Affected components Copy (Degraded performance) Sinks (Degraded performance) S3 Connector (Degraded performance) GCS Connector (Degraded performance) Query API (Degraded performance) Events API (Degraded performance) Kafka (Degraded performance) API Endpoints (Degraded performance) CSV Imports (Degraded performance)

  2. resolved Mar 03, 2026, 07:10 PM UTC

    Status: Resolved The region is recovered. Affected components Events API (Operational) Kafka (Operational) Query API (Operational) CSV Imports (Operational) Copy (Operational) Sinks (Operational) S3 Connector (Operational) GCS Connector (Operational) API Endpoints (Operational)

Read the full incident report →

Minor March 3, 2026

Kafka service degradation

Detected by Pingoru
Mar 03, 2026, 03:08 AM UTC
Resolved
Mar 03, 2026, 03:08 AM UTC
Duration
—
Affected: Kafka
Timeline · 4 updates
  1. investigating Mar 03, 2026, 12:57 AM UTC

    Status: Investigating We're currently experiencing degradation with Kafka ingestion. We're looking for the root cause. Affected components Kafka (Degraded performance)

  2. investigating Mar 03, 2026, 01:02 AM UTC

    Status: Investigating We're currently experiencing degradation with Kafka ingestion. We're looking for the root cause. Affected components Kafka (Operational) Kafka (Degraded performance)

  3. monitoring Mar 03, 2026, 01:22 AM UTC

    Status: Monitoring Root cause is now solved. We're still monitoring the region. Kafka service is back to normal. Affected components Kafka (Operational) Kafka (Operational)

  4. resolved Mar 03, 2026, 03:08 AM UTC

    Status: Resolved All systems back to normal. No remaining lag to process Affected components Kafka (Operational) Kafka (Operational)

Read the full incident report →

Minor March 2, 2026

Service is back to normal in gcp-us-east4

Detected by Pingoru
Mar 02, 2026, 12:06 PM UTC
Resolved
Mar 02, 2026, 12:06 PM UTC
Duration
—
Affected: LoginSinksS3 ConnectorGCS ConnectorEvents APIQuery APIBI ConnectorAPI EndpointsCopyCSV Imports
Timeline · 3 updates
  1. investigating Mar 02, 2026, 11:28 AM UTC

    Status: Investigating We're currently experiencing a degradation across the entire region but Kafka. We're investigating the root cause. Affected components S3 Connector (Degraded performance) Login (Degraded performance) API Endpoints (Degraded performance) BI Connector (Degraded performance) Sinks (Degraded performance) GCS Connector (Degraded performance) Events API (Degraded performance) Query API (Degraded performance) CSV Imports (Degraded performance) Copy (Degraded performance)

  2. monitoring Mar 02, 2026, 11:36 AM UTC

    Status: Monitoring Service is back, we're still monitoring the region. Full degradation occurred from ~11:20-11:25UTC. Affected components CSV Imports (Operational) Copy (Operational) Query API (Operational) Sinks (Operational) S3 Connector (Operational) Login (Operational) GCS Connector (Operational) Events API (Operational) API Endpoints (Operational) BI Connector (Operational)

  3. resolved Mar 02, 2026, 12:06 PM UTC

    Status: Resolved Service is back to normal. Affected components API Endpoints (Operational) BI Connector (Operational) CSV Imports (Operational) S3 Connector (Operational) Events API (Operational) Query API (Operational) Copy (Operational) Sinks (Operational) Login (Operational) GCS Connector (Operational)

Read the full incident report →

Minor February 28, 2026

Degradation in GCP-us-east4

Detected by Pingoru
Feb 28, 2026, 06:12 AM UTC
Resolved
Feb 28, 2026, 06:12 AM UTC
Duration
—
Affected: LoginKafkaSinksS3 ConnectorGCS ConnectorEvents APIQuery APIBI ConnectorAPI EndpointsCopyCSV Imports
Timeline · 3 updates
  1. investigating Feb 28, 2026, 05:18 AM UTC

    Status: Investigating We're seeing an increase in errors in GCP-us-east4. We're investigating. Affected components Events API (Degraded performance) Kafka (Degraded performance) API Endpoints (Degraded performance) BI Connector (Degraded performance) CSV Imports (Degraded performance) Copy (Degraded performance) S3 Connector (Degraded performance) Login (Degraded performance) Query API (Degraded performance) Sinks (Degraded performance) GCS Connector (Degraded performance)

  2. monitoring Feb 28, 2026, 05:55 AM UTC

    Status: Monitoring We've identified the cause of the errors and applied a fix. We're monitoring the situation. Affected components Copy (Degraded performance) S3 Connector (Degraded performance) Login (Degraded performance) GCS Connector (Degraded performance) Events API (Degraded performance) Kafka (Degraded performance) API Endpoints (Degraded performance) Query API (Degraded performance) BI Connector (Degraded performance) Sinks (Degraded performance) CSV Imports (Degraded performance)

  3. resolved Feb 28, 2026, 06:12 AM UTC

    Status: Resolved The incident was caused by a sudden spike of requests. This is now resolved. Affected components GCS Connector (Operational) Events API (Operational) CSV Imports (Operational) Copy (Operational) Sinks (Operational) Kafka (Operational) API Endpoints (Operational) Query API (Operational) BI Connector (Operational) S3 Connector (Operational) Login (Operational)

Read the full incident report →

Minor February 24, 2026

Degraded performance in gcp-us-east

Detected by Pingoru
Feb 24, 2026, 12:20 PM UTC
Resolved
Feb 24, 2026, 12:20 PM UTC
Duration
—
Affected: Events APIAPI Endpoints
Timeline · 3 updates
  1. investigating Feb 24, 2026, 11:10 AM UTC

    Status: Investigating We're returning an increased rate of errors in API endpoints and Events API Affected components Events API (Degraded performance) API Endpoints (Degraded performance)

  2. monitoring Feb 24, 2026, 11:19 AM UTC

    Status: Monitoring Temporary increase in errors in Events API and API endpoints Affected components API Endpoints (Operational) Events API (Operational)

  3. resolved Feb 24, 2026, 12:20 PM UTC

    Status: Resolved There was a degradation in the ingestion on gcp-us-east due to some integrity checks, we identified the issue and fixed it. So now we are finishing processing retries and the situation is stable. Affected components Events API (Operational) API Endpoints (Operational)

Read the full incident report →

Minor February 22, 2026

Tinybird Dashboard degraded due to Auth0 incident

Detected by Pingoru
Feb 22, 2026, 07:00 PM UTC
Resolved
Feb 22, 2026, 07:00 PM UTC
Duration
—
Affected: Tinybird UI
Timeline · 2 updates
  1. monitoring Feb 22, 2026, 05:01 PM UTC

    Status: Monitoring Tinybird Dashboard is partially down and experiencing slowness due to an open incident in Auth0: https://status.auth0.com/incidents/kknl0nbdzbvx, our identity provider. Affected components Tinybird UI (Partial outage)

  2. resolved Feb 22, 2026, 07:00 PM UTC

    Status: Resolved Tinybird Dashboard is recovered, the incident in Auth0: https://status.auth0.com/incidents/kknl0nbdzbvx, our identity provider, is now resolved. Affected components Tinybird UI (Operational)

Read the full incident report →

Minor February 17, 2026

Degraded performance in aws-us-east-1

Detected by Pingoru
Feb 17, 2026, 07:52 PM UTC
Resolved
Feb 17, 2026, 07:52 PM UTC
Duration
—
Affected: LoginKafkaSinksDynamoDB ConnectorS3 ConnectorGCS ConnectorEvents APIQuery APIBI ConnectorAPI EndpointsCopyCSV ImportsTinybird UI
Timeline · 4 updates
  1. investigating Feb 17, 2026, 02:01 PM UTC

    Status: Investigating We're investigating error reports of users accessing our UI for workspaces in aws-us-east-1. The region selector seems to be affected too. Affected components Tinybird UI (Partial outage)

  2. identified Feb 17, 2026, 03:01 PM UTC

    Status: Identified We're taking longer to fulfill requests to aws-us-east-1 across the board. We've identified the cause and are working on a fix. Affected components S3 Connector (Degraded performance) GCS Connector (Degraded performance) API Endpoints (Degraded performance) BI Connector (Degraded performance) Kafka (Degraded performance) Copy (Degraded performance) Sinks (Degraded performance) Login (Degraded performance) Tinybird UI (Partial outage) DynamoDB Connector (Degraded performance) Events API (Degraded performance) Query API (Degraded performance) CSV Imports (Degraded performance)

  3. monitoring Feb 17, 2026, 03:25 PM UTC

    Status: Monitoring We've applied a fix that's resolved the situation. We're still monitoring. Affected components Events API (Operational) CSV Imports (Operational) Copy (Operational) Sinks (Operational) API Endpoints (Operational) Kafka (Operational) Query API (Operational) S3 Connector (Operational) Login (Operational) Tinybird UI (Operational) DynamoDB Connector (Operational) GCS Connector (Operational) BI Connector (Operational)

  4. resolved Feb 17, 2026, 07:52 PM UTC

    Status: Resolved The issue was fully resolved at 15:10 UTC Affected components Copy (Operational) Sinks (Operational) S3 Connector (Operational) Login (Operational) Kafka (Operational) Events API (Operational) Tinybird UI (Operational) DynamoDB Connector (Operational) GCS Connector (Operational) API Endpoints (Operational) BI Connector (Operational) Query API (Operational) CSV Imports (Operational)

Read the full incident report →

Minor February 11, 2026

Service datasources stop ingesting data and queries using them are failing

Detected by Pingoru
Feb 11, 2026, 12:46 PM UTC
Resolved
Feb 11, 2026, 12:46 PM UTC
Duration
—
Affected: API EndpointAPI Endpoints
Timeline · 4 updates
  1. investigating Feb 11, 2026, 10:50 AM UTC

    Status: Investigating Since 10.50 UTC, the service datasources from all the regions started to not report data and also queries to those service datasources are failing. Affected components API Endpoints (Partial outage) API Endpoints (Partial outage) API Endpoints (Partial outage) API Endpoint (Partial outage) API Endpoints (Partial outage) API Endpoints (Partial outage) API Endpoints (Partial outage) API Endpoints (Partial outage)

  2. identified Feb 11, 2026, 11:54 AM UTC

    Status: Identified We've identified the problem and we are deploying fix Affected components API Endpoints (Partial outage) API Endpoint (Partial outage) API Endpoints (Partial outage) API Endpoints (Partial outage) API Endpoints (Partial outage) API Endpoints (Partial outage) API Endpoints (Partial outage) API Endpoints (Partial outage)

  3. monitoring Feb 11, 2026, 12:04 PM UTC

    Status: Monitoring We've deployed the fix. We are monitoring that everything is back to normal Affected components API Endpoint (Operational) API Endpoints (Operational) API Endpoints (Operational) API Endpoints (Operational) API Endpoints (Operational) API Endpoints (Operational) API Endpoints (Operational) API Endpoints (Operational)

  4. resolved Feb 11, 2026, 12:46 PM UTC

    Status: Resolved Since 10.50 UTC, some service data sources in 4 of our regions have not been reporting data, causing queries to those sources to fail. A fix was deployed, and all queries are working as expected now. Affected components API Endpoints (Operational) API Endpoints (Operational) API Endpoints (Operational) API Endpoints (Operational) API Endpoints (Operational) API Endpoint (Operational) API Endpoints (Operational) API Endpoints (Operational)

Read the full incident report →

Looking to track Tinybird downtime and outages?

Pingoru polls Tinybird's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when Tinybird reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track Tinybird alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring Tinybird for free

5 free monitors · No credit card required