Edge Function Degradation
Supabase · Last saved provider status: identified
The last saved event status is not the current service status. Source lists can be incomplete, and disappearance from a source does not confirm recovery. Open the current report or the official source for newer evidence.
Saved event details
- Provider status
- identified
- Provider impact
- minor
- Provider record created
- 12 Oct 2026, 19:49:07 UTC
- Provider record updated
- 12 Oct 2026, 21:07:08 UTC
- Explicit provider start
- Not available
- Explicit provider end
- Not available
Affected components reported by the provider
Component associations were not provided or have not been recovered for this saved revision.
These associations describe this event’s reported scope. They do not establish current component availability or verified dependencies.
A record creation time is not necessarily an outage start. Unreported times remain unavailable. We do not calculate downtime from collection times.
Supabase's published platform indicator and currently listed components, incidents and scheduled maintenance. The component list may cover only part of the platform during its status-page migration. Missing lists remain unavailable; provider region names do not verify regional access or a particular project's health.
Provider updates in saved revisions
Latest first. We show up to 100 distinct updates from the latest 20 saved content revisions. Revised wording at the same provider time is retained separately.
- identified
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.
Seen in a saved revision at 12 Oct 2026, 21:07:31 UTC - identified
We're now seeing reduced error rates for Edge Functions. We've identified the root cause and are working on a fix.
Seen in a saved revision at 12 Oct 2026, 21:07:31 UTC - identified
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.
Seen in a saved revision at 12 Oct 2026, 21:07:31 UTC