Identified - We have identified an issue with our cloud provider regarding insufficient compute capacity in the eu-west-3b availability zone.
We have disabled the ability to restart projects, compute or database version upgrades within eu-west-3b.

Project provisioning in eu-west-3, as well as all operations for projects located in the eu-west-3a and eu-west-3c availability zones are available.

Nov 27, 2024 - 09:58 UTC
Investigating - We are currently investigating this issue.
Nov 27, 2024 - 09:57 UTC
Analytics ? Operational
90 days ago
100.0 % uptime
Today
API Gateway ? Operational
90 days ago
100.0 % uptime
Today
Auth ? Operational
90 days ago
100.0 % uptime
Today
Connection Pooler ? Operational
90 days ago
100.0 % uptime
Today
Dashboard ? Operational
90 days ago
99.99 % uptime
Today
Database ? Operational
90 days ago
100.0 % uptime
Today
Edge Functions ? Operational
90 days ago
100.0 % uptime
Today
Management API ? Operational
90 days ago
100.0 % uptime
Today
Realtime ? Operational
90 days ago
100.0 % uptime
Today
Storage ? Operational
90 days ago
100.0 % uptime
Today
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.
Scheduled Maintenance
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.

Posted on Dec 10, 2024 - 10:24 UTC
REST API Latency (Singapore)
Fetching
REST API Latency (North Virginia)
Fetching
REST API Latency (Frankfurt)
Fetching
Past Incidents
Dec 11, 2024

No incidents reported today.

Dec 10, 2024
Resolved - This incident has been resolved.
Dec 10, 19:40 UTC
Update - Work continues on rolling out the fixes to the remaining affected projects.
Dec 10, 17:06 UTC
Identified - The issue has been identified and fix has been rolled out to most projects in the region. The fix for the remaining projects is in progress.
Dec 10, 12:54 UTC
Investigating - We are currently investigating this issue.
Dec 10, 12:52 UTC
Dec 9, 2024
Resolved - This incident has been resolved.
Dec 9, 20:48 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Dec 9, 19:28 UTC
Investigating - We are currently investigating this issue.
Dec 9, 16:28 UTC
Dec 8, 2024

No incidents reported.

Dec 7, 2024

No incidents reported.

Dec 6, 2024
Resolved - This incident has been resolved.
Dec 6, 07:06 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Dec 6, 06:49 UTC
Investigating - We are currently investigating this issue.
Dec 6, 04:52 UTC
Dec 5, 2024

No incidents reported.

Dec 4, 2024
Resolved - This incident has been resolved.
Dec 4, 18:33 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Dec 4, 17:24 UTC
Investigating - We are currently investigating this issue.
Dec 4, 16:50 UTC
Dec 3, 2024
Resolved - This incident has been resolved.
Dec 3, 17:04 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:15 UTC
Investigating - We are currently investigating this issue.
Dec 3, 14:03 UTC
Dec 2, 2024

No incidents reported.

Dec 1, 2024

No incidents reported.

Nov 30, 2024

No incidents reported.

Nov 29, 2024

No incidents reported.

Nov 28, 2024

No incidents reported.

Nov 27, 2024
Resolved - This incident has been resolved.
Nov 27, 11:41 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Nov 27, 08:40 UTC
Identified - The issue has been identified and a fix is being implemented.
Nov 27, 00:07 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Nov 26, 18:01 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, 15:16 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, 09:25 UTC
Investigating - We are currently investigating this issue.
Nov 26, 05:04 UTC