WhatBrokeToday
GTA 6FAQ
Supabase

Supabase: Projects in sa-east-1 experiencing delayed event ingestion

minor

Is it fixed? Yes.

Resolved after 8 h 46 min. First reported Nov 17, 03:59 UTC, resolved Nov 17, 12:46 UTC. The vendor posted it on its status page first.

What happened

Projects in the sa-east-1 region are experiencing delayed event ingestion and appearing unhealthy in the Dashboard due to timing out EC2 scheduled events. Supabase is currently investigating the issue.

What caused it?

EC2 scheduled events are timing out for projects in sa-east-1.

Workaround available

re-start their project

Reported inStatusevidence [1]
Official fix

Timeline

  1. Investigating(done)
  2. Workaround available(done)
  3. Resolved(current)
  1. First report on status page

    Projects in sa-east-1 experiencing delayed event ingestion

    Source
  2. Official statement

    Status: Investigating EC2 scheduled events are timing out for projects in sa-east-1, leading to a subset of projects being reported as unhealthy in the Dashboard.

    Source
  3. Status changed

    Status changed: new → workaround_available (workaround reported in source signals).

  4. Official statement

    ⚠️ Supabase is reporting an incident: Projects in sa-east-1 experiencing delayed event ingestion Investigating: As a workaround, impacted users can re-start their project while we are working on providing a fix. t.lpl.dev/pIy5c9Q

    Source
  5. Official statement

    ✅ Resolved: Supabase - Projects in sa-east-1 experiencing delayed event ingestion

    Source
  6. Status changed

    Status changed: workaround_available → resolved (official status page reports resolution).

Show all 8 updates
  1. First report on status page

    Projects in sa-east-1 experiencing delayed event ingestion

    Source
  2. Official statement

    Status: Investigating EC2 scheduled events are timing out for projects in sa-east-1, leading to a subset of projects being reported as unhealthy in the Dashboard.

    Source
  3. Workaround discovered

    Workaround reported: re-start their project

    Source
  4. Status changed

    Status changed: new → workaround_available (workaround reported in source signals).

  5. Confirmed on Bluesky post

    ⚠️ Supabase is reporting an incident: Projects in sa-east-1 experiencing delayed event ingestion

    Source
  6. Official statement

    ⚠️ Supabase is reporting an incident: Projects in sa-east-1 experiencing delayed event ingestion Investigating: As a workaround, impacted users can re-start their project while we are working on providing a fix. t.lpl.dev/pIy5c9Q

    Source
  7. Official statement

    ✅ Resolved: Supabase - Projects in sa-east-1 experiencing delayed event ingestion

    Source
  8. Status changed

    Status changed: workaround_available → resolved (official status page reports resolution).

Evidence

3 reports · 1 Status, 2 BlueskyShow
  1. [1]
    Status First report
    Projects in sa-east-1 experiencing delayed event ingestion(opens official status page in a new tab)

    Status: Investigating EC2 scheduled events are timing out for projects in sa-east-1, leading to a subset of projects being reported as unhealthy in the Dashboard. As a workaround, impacted users can re-start their project while we are working on providing a fix.

    by supabase status

  2. [2]
    Bluesky
    ⚠️ Supabase is reporting an incident: Projects in sa-east-1 experiencing delayed event ingestion(opens the official status page in a new tab)

    ⚠️ Supabase is reporting an incident: Projects in sa-east-1 experiencing delayed event ingestion Investigating: As a workaround, impacted users can re-start their project while we are working on providing a fix. t.lpl.dev/pIy5c9Q

    by telescope.littleplanetlabs.comOpens the official status page 0upvotes 1comments96% match

  3. [3]
    Bluesky
    ✅ Resolved: Supabase - Projects in sa-east-1 experiencing delayed event ingestion(opens the official status page in a new tab)

    ✅ Resolved: Supabase - Projects in sa-east-1 experiencing delayed event ingestion

    by telescope.littleplanetlabs.comOpens the official status page 1upvotes 0comments93% match

FAQ

What happened in the Supabase outage?

Projects in the sa-east-1 region are experiencing delayed event ingestion and appearing unhealthy in the Dashboard due to timing out EC2 scheduled events. Supabase is currently investigating the issue.

What is affected by the Supabase outage?

Supabase.

When did the Supabase outage start and end?

It started Nov 17, 03:59 UTC and was resolved Nov 17, 12:46 UTC, after 8 h 46 min.

How do I get alerts for Supabase?

Subscribe to the Supabase RSS feed for every new Supabase incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Supabase is down. Supabase feed

Where does this information come from?

WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 3 reports from 2 independent sources, including the vendor’s own status page.