Upgrade Issues
Supabase · 最近儲存的提供方狀態：monitoring
官方來源文字以原始語言顯示。
最近儲存的事件狀態不是當前服務狀態。來源列表可能不完整，事件從來源消失不確認恢復。請開啟當前報告或官方來源檢視較新證據。
已儲存事件詳情
- 提供方狀態
- monitoring
- 提供方影響程度
- minor
- 提供方記錄建立時間
- 06 Oct 2026, 15:23:14 UTC
- 提供方記錄更新時間
- 06 Oct 2026, 17:27:21 UTC
- 提供方明確報告的開始時間
- 06 Oct 2026, 15:23:14 UTC
- 提供方明確報告的結束時間
- 不可用
提供方報告的受影響元件
提供方在此已儲存修訂中明確列出沒有受影響元件。
這些關聯描述此事件的報告範圍。不能確認當前元件可用性或已核實依賴關係。
記錄建立時間未必是故障開始時間。未報告的時間保持不可用。我們不根據收集時間計算故障時長。
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.
已儲存修訂中的提供方更新
最新優先。最多顯示最近 20 份已儲存內容修訂中的 100 條不同更新。同一提供方時間的文字修訂單獨保留。
- monitoring
The fix has been implemented. Upgrade operation has been restored. We will monitor for stability.
在 06 Oct 2026, 17:29:09 UTC 的已儲存修訂中觀察到 - identified
A fix has been developed and we are going through the review and implementation process.
在 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.
在 06 Oct 2026, 17:29:09 UTC 的已儲存修訂中觀察到 - investigating
We have observed failures in attempted upgrades to 17.11.0.003. We are investigating.
在 06 Oct 2026, 17:29:09 UTC 的已儲存修訂中觀察到