Project (Pro plan) — full DB outage for 37 min today (Mar 26 23:0023:37 UTC).
All services went Unhealthy (Database, PostgREST, Auth, Storage). PostgREST logs showed PGRST003: Timed out acquiring connection from connection pool.
No schema migrations or deployments were run before the incident. Was there an infra issue around this time?
The user reported a full database outage on their Pro plan project for approximately 37 minutes. All services, including Database, PostgREST, Auth, and Storage, were affected. The user noted a specific PostgREST error and asked if there was an infrastructure issue at that time.
User issue: Database stopped loading due to I/O error
User issue: Database tables not loading, causing app failures
User issue: Connection timeout prevents login and database access
There were no user reports here of that and nothing on the status page from Supabase.
Have you looked at your logs and usage charts during than period (in particular disk i/o right before)?
You might ask support if they see anything.