In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jan 26, 2026 - 10:30 UTC
Jan 26, 2026 - 10:30 UTC
Scheduled - We are making some improvements to the way that we take and manage backups of projects across the fleet. We introduced this new method some time ago, and it's already in use for larger projects, projects with PITR enabled, and projects with Read Replicas. We also made the new method the default for all new projects last week.
We are now pushing this change out to all remaining projects across the fleet in stages through the week of January 26, 2026. We will start with Free plan projects, and move through paid subscribers after.
What's not changing?
You'll still get daily backups as you do today — this is an infrastructure improvement on our end that benefits you automatically.
What this means for you:
Faster restores — If you ever need to restore your database, it'll be back online significantly faster, especially for larger databases.
Less impact on your database — Backups will run with lower overhead, so you won't notice any performance impact during the backup window.
Is there any downtime?
Transitioning to the new backup method does involve a Postgres restart. The downtime is extremely minimal, just a few seconds in most circumstances. Any direct or pooler connections will disconnect on restart. As a best practice for using any hosted database, we recommend including reconnect logic in our application to re-establish connections if they're severed for any reason.
You can read more about the old vs new backup method here: https://supabase.com/docs/guides/platform/backups
If you have any additional questions or concerns please don't hesitate to reach out at https://supabase.help
Jan 26, 2026 10:30 - Feb 2, 2026 10:30 UTC
We are now pushing this change out to all remaining projects across the fleet in stages through the week of January 26, 2026. We will start with Free plan projects, and move through paid subscribers after.
What's not changing?
You'll still get daily backups as you do today — this is an infrastructure improvement on our end that benefits you automatically.
What this means for you:
Faster restores — If you ever need to restore your database, it'll be back online significantly faster, especially for larger databases.
Less impact on your database — Backups will run with lower overhead, so you won't notice any performance impact during the backup window.
Is there any downtime?
Transitioning to the new backup method does involve a Postgres restart. The downtime is extremely minimal, just a few seconds in most circumstances. Any direct or pooler connections will disconnect on restart. As a best practice for using any hosted database, we recommend including reconnect logic in our application to re-establish connections if they're severed for any reason.
You can read more about the old vs new backup method here: https://supabase.com/docs/guides/platform/backups
If you have any additional questions or concerns please don't hesitate to reach out at https://supabase.help
Jan 26, 2026 10:30 - Feb 2, 2026 10:30 UTC
Compute capacity
Operational
ap-northeast-1
Operational
ap-northeast-2
Operational
ap-south-1
Operational
ap-southeast-1
Operational
ap-southeast-2
Operational
ca-central-1
Operational
eu-central-1
Operational
eu-central-2
Operational
eu-north-1
Operational
eu-west-1
Operational
eu-west-2
Operational
eu-west-3
Operational
sa-east-1
Operational
us-east-1
Operational
us-east-2
Operational
us-west-1
Operational
Analytics
Operational
API Gateway
Operational
Auth
Under Maintenance
Connection Pooler
Operational
Dashboard
Operational
Database
Under Maintenance
Edge Functions
Under Maintenance
Management API
Operational
Realtime
Under Maintenance
Storage
Under Maintenance
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.