Upgrade Issues
Supabase · Last saved provider status: monitoring
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
- monitoring
- Provider impact
- minor
- Provider record created
- 06 Oct 2026, 15:23:14 UTC
- Provider record updated
- 06 Oct 2026, 17:27:21 UTC
- Explicit provider start
- 06 Oct 2026, 15:23:14 UTC
- Explicit provider end
- Not available
Affected components reported by the provider
The provider explicitly listed no affected components in 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 components, active incidents and scheduled maintenance. Provider region names do not establish independently tested regional access or the state of a particular project.
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.
- monitoring
The fix has been implemented. Upgrade operation has been restored. We will monitor for stability.
Seen in a saved revision at 06 Oct 2026, 17:29:09 UTC - identified
A fix has been developed and we are going through the review and implementation process.
Seen in a saved revision at 06 Oct 2026, 17:29:09 UTC - identified
We have identified the issue with the upgrade. To prevent issues, we have suspended the ability to upgrade projects while we resolve this issue. The problem is limited to upgrades from earlier versions of PG17 to the most recent release. We are working on a fix.
Seen in a saved revision at 06 Oct 2026, 17:29:09 UTC - investigating
We have observed failures in attempted upgrades to 17.11.0.003. We are investigating.
Seen in a saved revision at 06 Oct 2026, 17:29:09 UTC