Minor impactResolvedDatabases

Supabase incident: Edge Function Degradation

Supabase reported this minor-impact incident on its official status page on Oct 12, 2026, 19:49 UTC. It was resolved after 22h 36m.

Right now Supabase is operational. Live Supabase status →

🔔 Get alerted when Supabase has issuesFree · email alerts · no credit card
Oct 12, 2026, 19:49 UTC
started
Oct 13, 2026, 18:24 UTC
resolved
22h 36m
duration
Minor
impact
  1. resolvedOct 13, 2026, 18:24 UTC

    Edge function deployments have remained stable. We are closing the incident.

  2. monitoringOct 13, 2026, 02:24 UTC

    Edge Functions deployments have returned to normal levels. We will continue monitoring for full recovery.

  3. identifiedOct 12, 2026, 21:07 UTC

    Edge Functions deployments have returned to normal levels. We're now reviewing worker jobs that failed during the incident, including any backups that may have been affected. We'll re-queue these jobs once we've identified them, and we'll share more details on the status page. If you're noticing particular job failures that are unusual, please reach out to support.

  4. identifiedOct 12, 2026, 20:23 UTC

    We're now seeing reduced error rates for Edge Functions. We've identified the root cause and are working on a fix.

  5. identifiedOct 12, 2026, 19:49 UTC

    We are experiencing significant degraded performance across edge functions, mainly affecting deploy and retrieving function body. We have identified the root cause and are working on the fix now.

What APIStatus.watch saw

  • Oct 12, 2026, 19:42 UTCoperational → degraded
  • Oct 13, 2026, 02:24 UTCdegraded → operational
  • Oct 13, 2026, 13:54 UTCoperational → degraded

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does Supabase have incidents?

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