Minor impactResolvedDatabases

Supabase incident: Log Ingestion Degradation

Supabase reported this minor-impact incident on its official status page on Sep 28, 2026, 13:47 UTC. It was resolved after 49 min.

Right now Supabase is degraded. Live Supabase status →

🔔 Get alerted when Supabase has issuesFree · email alerts · no credit card
Sep 28, 2026, 13:47 UTC
started
Sep 28, 2026, 14:36 UTC
resolved
49 min
duration
Minor
impact
  1. resolvedSep 28, 2026, 14:36 UTC

    Log ingestion is normal.

  2. monitoringSep 28, 2026, 14:00 UTC

    Log ingestion has recovered. We are monitoring for continued stability.

  3. identifiedSep 28, 2026, 13:52 UTC

    The log ingestion issue was the result of a scaling gap. The relevant resources have been scaled and ingestion is recovering.

  4. investigatingSep 28, 2026, 13:47 UTC

    Log ingestion is experiencing some delays. Ingestion will be retried by clients.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in Supabase's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Supabase have incidents?

Supabase reported 43 incidents in the last 90 days, 16 of them major or critical. A typical incident lasted 2h 2m. See Supabase's uptime and incident history

Supabase incident on Sep 28, 2026: Log Ingestion Degradation · APIStatus.watch