PG15 -> PG17 Upgrade Failures

Zeitverlauf

1. 20:06 UTC Statusseite von Supabase · Reported PG15 -> PG17 Upgrade Failures
2. 20:06 UTC Statusseite von Supabase · Ursache gefunden We are actively investigating some reports of failed PG15 -> PG17 upgrades. We have identified an error in an AMI release from today and are rolling it back to unblock upgrades.
3. 20:42 UTC Statusseite von Supabase · Wird beobachtet We are seeing successful upgrades again, and error rates have returned to normal levels. We will continue to monitor to ensure continued stability.
4. 21:14 UTC Statusseite von Supabase · Behoben This issue is now resolved.