Is Tinybird down?

Last checked 9m ago
Current status
Tinybird is up

No incidents right now.

Official status page: https://status.tinybird.co · Polled every 5 minutes · 125 components tracked

Tinybird is operational right now. Last checked 9m ago; the most recent incident resolved 4d ago.

Real-time Tinybird status, recent outages, and incident history — pulled directly from Tinybird's official status page at https://status.tinybird.co every 5 minutes. Pingoru tracks 125 Tinybird services and has captured 11 incidents in the last 90 days (99.26% uptime). Get email, Slack, Discord, or webhook alerts the moment Tinybird reports a new incident — free for 5 monitors, no credit card.

Users who monitor Tinybird also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 6,000+ providers
Tinybird uptime 99.26% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Recent outages & incidents

Past 90 days
  1. Resolved
    Started Sep 10, 2026, 06:32 AM UTC · Resolved Sep 10, 2026, 06:32 AM UTC
    LoginCopySinksQuery APIKafkaGCS ConnectorAPI EndpointsS3 ConnectorEvents APIClickHouse HTTP Interface
    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…

  2. Resolved
    Started Aug 15, 2026, 12:20 PM UTC · Resolved Aug 15, 2026, 12:20 PM UTC
    Copy
    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…

  3. Resolved
    Started Aug 12, 2026, 11:34 AM UTC · Resolved Aug 12, 2026, 11:34 AM UTC
    Timeline · 3 updates
    • investigating · Aug 12, 2026, 10:38 AM UTC

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

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

    • resolved · Aug 12, 2026, 11:34 AM UTC

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

    Latest: Status: Resolved 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 curren…

  4. Resolved
    Started Aug 06, 2026, 08:20 AM UTC · Resolved Aug 06, 2026, 08:20 AM UTC
    LoginCopySinkQuery APIKafkaGCS ConnectorCopyAPI EndpointsS3 ConnectorEvents API
    Timeline · 3 updates
    • investigating · Aug 06, 2026, 07:59 AM UTC

      Status: 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. Affected components Copy (Degraded performance) Events API (Degraded performance) Query API (Degraded performance) S3 Connector (Degraded performance) Login (Degraded performance) Kafka (Degraded performance) API Endpoints (Degraded performance) Sink (Degraded performance) GCS Connector (Degraded performance) ClickHouse HTTP Interface (Degraded performance)

    • monitoring · Aug 06, 2026, 08:11 AM UTC

      Status: 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. Affected components Login (Degraded performance) Copy (Degraded performance) API Endpoints (Degraded performance) Query API (Degraded performance) S3 Connector (Degraded performance) GCS Connector (Degraded performance) Events API (Degraded performance) Kafka (Degraded performance) Sink (Degraded performance) ClickHouse HTTP Interface (Degraded performance)

    • resolved · Aug 06, 2026, 08:20 AM UTC

      Status: Resolved The incident is now resolved. Affected components Query API (Operational) GCS Connector (Operational) Login (Operational) S3 Connector (Operational) ClickHouse HTTP Interface (Operational) Copy (Operational) Events API (Operational) Kafka (Operational) API Endpoints (Operational) Sink (Operational)

    Latest: Status: Resolved The incident is now resolved. Affected components Query API (Operational) GCS Connector (Operational) Login (Operational) S3 Connector (Operational) ClickHouse HTT…

  5. Resolved
    Started Jul 30, 2026, 11:13 AM UTC · Resolved Jul 30, 2026, 11:13 AM UTC
    CopyCopy
    Timeline · 3 updates
    • investigating · Jul 30, 2026, 10:40 AM UTC

      Status: Investigating We're investigating an issue when creating or deleting new replicas. This affects cluster replicas and jobs on-demand (populates and copies). Affected components Copy (Partial outage) Copy (Partial outage) Copy (Partial outage) Copy (Partial outage) Copy (Partial outage) Copy (Partial outage) Copy (Partial outage) Copy (Partial outage) Copy (Partial outage) Copy (Partial outage)

    • monitoring · Jul 30, 2026, 10:56 AM UTC

      Status: 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. Affected components Copy (Partial outage) Copy (Partial outage) Copy (Partial outage) Copy (Partial outage) Copy (Partial outage) Copy (Partial outage) Copy (Partial outage) Copy (Partial outage) Copy (Partial outage) Copy (Partial outage)

    • resolved · Jul 30, 2026, 11:13 AM UTC

      Status: Resolved The incident is now resolved. Affected components Copy (Operational) Copy (Operational) Copy (Operational) Copy (Operational) Copy (Operational) Copy (Operational) Copy (Operational) Copy (Operational) Copy (Operational) Copy (Operational)

    Latest: Status: Resolved The incident is now resolved. Affected components Copy (Operational) Copy (Operational) Copy (Operational) Copy (Operational) Copy (Operational) Copy (Operational)…

See the full Tinybird outage history

6 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

Outage history

Past 90 days · 11 incidents View full outage history →