Minor impactResolvedDatabases

Supabase incident: Log Ingestion Problems

Supabase reported this minor-impact incident on its official status page on Jul 22, 2026, 16:29 UTC. It was resolved after 3h 40m.

Right now Supabase is degraded. Live Supabase status →

🔔 Get alerted when Supabase has issuesFree · email alerts · no credit card
Jul 22, 2026, 16:29 UTC
started
Jul 22, 2026, 20:10 UTC
resolved
3h 40m
duration
Minor
impact

Affected components

  • Dashboard
  1. resolvedJul 22, 2026, 20:10 UTC

    This issue is now resolved. Log ingestion has returned to normal and customers can now view project logs.

  2. monitoringJul 22, 2026, 18:40 UTC

    We are continuing to monitor log ingestion to ensure it remains stable.

  3. monitoringJul 22, 2026, 17:49 UTC

    We have implemented a fix, and log ingestion has returned to normal. We will continue to monitor this issue to ensure it stays stable.

  4. identifiedJul 22, 2026, 16:56 UTC

    We have identified the issue and are working to re-enable the ingestion of logs.

  5. investigatingJul 22, 2026, 16:29 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 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 Jul 22, 2026: Log Ingestion Problems · APIStatus.watch