Supabase outage history

Supabase: branch creation degradation

Supabase: network restrictions preventing read replica communication

Supabase: log ingestion issues

Supabase: shared Pooler scheduled maintenance in sa-east-1

Shared Pooler scheduled maintenance in sa-east-1

Shared Pooler scheduled maintenance in ap-southeast-1

Supabase: shared Pooler scheduled maintenance in ap-southeast-1

Customer Projects Experiencing Upgrade Issues

Supavisor connectivity in us-east-1

Supavisor connectivity in eu-central-1

403 errors for PostgREST requests

Some Projects Unreachable following Project Restart

Some projects unavailable across multiple regions

Inadvertently disabled pg_graphql for some projects

Increased errors in project creation and configuration changes in US-East-2 and AP-Northeast-1

Newly created projects may be unreachable

Edge Functions: Several users reported 503 errors with SUPABASE_EDGE_RUNTIME_ERROR error code

Increased Errors on HTTP Endpoints

Transactional Email Delivery Delays

Project creation failures in some APAC regions

Logs currently inaccessible via the Dashboard and Log Drains

Increased error rates for plan upgrades

Degraded logs ingestion

Supabase dashboard experiencing intermittent errors in Europe region

Degraded Log Ingestion

Realtime services unavailable

Branching access issues

Degraded Logging Ingestion impacting all regions

Elevated error rates affecting Edge Functions in the eu-central-1 (Frankfurt) region

Project creation failures across multiple regions

Elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region

Issues propagating Postgres configuration updates