Minor impactResolvedDatabases

Supabase incident: Log Ingestion Issues

Supabase reported this minor-impact incident on its official status page on Jul 30, 2026, 20:57 UTC. It was resolved after 53 min.

Right now Supabase is degraded. Live Supabase status →

🔔 Get alerted when Supabase has issuesFree · email alerts · no credit card
Jul 30, 2026, 20:57 UTC
started
Jul 30, 2026, 21:50 UTC
resolved
53 min
duration
Minor
impact

Affected components

  • Dashboard
  1. resolvedJul 30, 2026, 21:50 UTC

    The issue has been resolved, and customers should now see new logs appearing as expected.

  2. monitoringJul 30, 2026, 21:39 UTC

    Log ingestion has been restored, and new logs are now appearing as expected. We will continue monitoring to ensure the issue is fully resolved.

  3. identifiedJul 30, 2026, 21:33 UTC

    We have identified the cause of the issue and are working to restore normal log ingestion. Customers may continue to experience delays in new logs appearing.

  4. investigatingJul 30, 2026, 20:57 UTC

    We are experiencing a problem with log ingestion. Customers may experience a lack of new logs being visible from their projects. We are investigating.

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 47 incidents in the last 90 days, 17 of them major or critical. A typical incident lasted 2h 2m. See Supabase's uptime and incident history

Supabase incident on Jul 30, 2026: Log Ingestion Issues · APIStatus.watch