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 的已保存修订中观察到