Supabase

Supabase – Maintenance required on Supavisor in multiple regions.

by

Dec 19, 15:00 UTC
Completed – The scheduled maintenance has been completed.

Dec 19, 14:00 UTC
In progress – Scheduled maintenance is currently in progress. We will provide updates as necessary.

Dec 18, 13:44 UTC
Scheduled – We will be performing maintenance on Supavisor on 2024-12-19 at 14:00UTC.

The following regions will be affected:

* ap-northeast-1
* ap-south-1
* ap-southeast-2
* eu-west-1
* eu-north-1

Connections to Supavisor in the effected regions may be temporarily disconnected during this period as we perform this required maintenance.

Supabase – Maintenance required on Supavisor in multiple regions.

by

Dec 18, 14:00 UTC
Completed – The scheduled maintenance has been completed.

Dec 18, 12:00 UTC
In progress – Scheduled maintenance is currently in progress. We will provide updates as necessary.

Dec 17, 11:46 UTC
Scheduled – We will be performing maintenance on Supavisor on 2024-12-18 at 12:00UTC.

The following regions will be affected:

* ap-east-1
* ca-central-1
* eu-west-3
* sa-east-1

Connections to Supavisor in the effected regions may be temporarily disconnected during this period as we perform this required maintenance.

Supabase – Supavisor and Storage connectivity issues in ap-southeast-1 (Singapore)

by

Dec 16, 17:23 UTC
Resolved – This incident has been resolved.

Dec 16, 14:42 UTC
Monitoring – A fix has been implemented and we are monitoring the results.

Dec 16, 13:21 UTC
Update – Our engineers have identified the root cause of the issue and some connectivity has improved. We are now working on resolving the issue fully.

Dec 16, 11:20 UTC
Identified – We have identified a Supavisor connectivity issue in ap-southeast-1. This issue is affecting Supavisor and our Storage functionality. Engineers are working on resolving the issue.

Dec 16, 11:09 UTC
Investigating – We are currently investigating this issue.

Supabase – Maintenance required on Supavisor in ap-northeast-2 (Seoul) region.

by

Dec 13, 11:00 UTC
Completed – The scheduled maintenance has been completed.

Dec 13, 10:00 UTC
In progress – Scheduled maintenance is currently in progress. We will provide updates as necessary.

Dec 12, 09:42 UTC
Scheduled – We will be performing maintenance on Supavisor in ap-northeast-2 (Seoul) region on 2024-12-13 at 10:00UTC.

Connections to Supavisor in the effected region may be temporarily disconnected during this period as we perform this required maintenance.

Supabase – Maintenance required on Supavisor in eu-central-2 (Zurich) region.

by

Dec 11, 12:00 UTC
Completed – The scheduled maintenance has been completed.

Dec 11, 11:00 UTC
In progress – Scheduled maintenance is currently in progress. We will provide updates as necessary.

Dec 10, 10:24 UTC
Scheduled – We will be performing maintenance on Supavisor in eu-central-2 (Zurich) region on 2024-12-11 at 11:00UTC.

Connections to Supavisor in the effected region may be temporarily disconnected during this period as we perform this required maintenance.

Supabase – Realtime Postgres Changes degraded

by

Dec 3, 17:04 UTC
Resolved – This incident has been resolved.

Dec 3, 14:15 UTC
Monitoring – A fix has been implemented and we are monitoring the results.

Dec 3, 14:15 UTC
Identified – We have determined Postgres Changes was using an incorrect number of connections to check RLS policies.
This caused the system to reuse the same replication slot, leading to failed connections against Postgres Changes.

The issue has been identified and we’re deploying corrective measures.

Dec 3, 14:03 UTC
Investigating – We are currently investigating this issue.

Supabase – Branching unavailable

by

Nov 27, 11:41 UTC
Resolved – This incident has been resolved.

Nov 27, 08:40 UTC
Monitoring – A fix has been implemented and we are monitoring the results.

Nov 27, 00:07 UTC
Identified – The issue has been identified and a fix is being implemented.

Nov 26, 18:01 UTC
Monitoring – A fix has been implemented and we are monitoring the results.

Nov 26, 15:16 UTC
Identified – The branching service is unavailable due to an upstream issue with fly.io (https://status.flyio.net/incidents/7lfnb87h43hf) impacting internal service connectivity and workload provisioning.

Nov 26, 09:25 UTC
Monitoring – Branching service was unavailable due to an upstream issue with fly.io (https://status.flyio.net/). The upstream issue has now been resolved and branching should be available once again.

Nov 26, 05:04 UTC
Investigating – We are currently investigating this issue.