---
id: "INC-supabase-01M48WZN5HSPR8TG7AT83XRS1K"
kind: "incident"
aliases: []
title: "Supabase: Upgrade Issues"
severity: "low"
cvss: null
epss: null
exploited: false
status: "resolved"
category: "vendor"
products: [{"name": "Supabase", "fixed": [], "affected": "", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["database", "incident", "ops", "postgres", "supabase", "vendor"]
not_affected_if: []
published_at: "2026-10-06T15:23:15+00:00"
first_seen_at: "2026-10-23T19:12:22+00:00"
updated_at: "2026-10-23T20:20:06+00:00"
sources: [{"source": "statuspage", "url": "https://status.supabase.com/incidents/01M48WZN5HSPR8TG7AT83XRS1K", "first_seen_at": "2026-10-23T19:12:22+00:00"}]
---

# Supabase: Upgrade Issues

## Affected

- vendor:Supabase affected ? fixed ?

## Timeline

- 2026-10-23T19:12:22+00:00 statuspage https://status.supabase.com/incidents/01M48WZN5HSPR8TG7AT83XRS1K

## From the sources

We've rolled out a fix for this issue and re-enabled upgrades in the dashboard. We apologize for the inconvenience.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_
