Supabase Status

Resolved: This incident has been resolved.

Monitoring: Our upstream partner has marked their issues resolved. We are seeing latency return to normal, but will continue to monitor.

Identified: Our upstream partner has made some adjustments which appear to have reduced observed lantency in the us-east-1 region. We are continuing the work with them as well as monitor impact on our side.

Identified: We are still investigating any possible issues on our side, but our upstream networking partner has confirmed issues in the US-East region currently, which we suspect is the cause of added latency for our Data API layer. We've been informed they have isolated the issue and are working on a fix.

Investigating: We are receiving reports of increased latency across a number of Supabase APIs. The team is currently looking into this now.

Resolved: This incident has been resolved.

Monitoring: We determined that there was a spike in activity relating to saved content (queries and folders in the SQL Editor). Things are looking normal at the moment. We are re-enabling saved query and folder access and will monitor for any increased error rates in the management API.

Investigating: We've spotted high error rates for some of the API requests. We made a temporary fix that prevents access to saved queries and folders. We are actively working on getting things back to normal and turning this functionality back on.

Resolved: This incident has been resolved.

Monitoring: Our upstream partner has marked their issues resolved. We are seeing latency return to normal, but will continue to monitor.

Identified: Our upstream partner has made some adjustments which appear to have reduced observed lantency in the us-east-1 region. We are continuing the work with them as well as monitor impact on our side.

Identified: We are still investigating any possible issues on our side, but our upstream networking partner has confirmed issues in the US-East region currently, which we suspect is the cause of added latency for our Data API layer. We've been informed they have isolated the issue and are working on a fix.

Investigating: We are receiving reports of increased latency across a number of Supabase APIs. The team is currently looking into this now.

Resolved: This incident has been resolved.

Monitoring: Our upstream partner has marked their issues resolved. We are seeing latency return to normal, but will continue to monitor.

Identified: Our upstream partner has made some adjustments which appear to have reduced observed lantency in the us-east-1 region. We are continuing the work with them as well as monitor impact on our side.

Identified: We are still investigating any possible issues on our side, but our upstream networking partner has confirmed issues in the US-East region currently, which we suspect is the cause of added latency for our Data API layer. We've been informed they have isolated the issue and are working on a fix.

Investigating: We are receiving reports of increased latency across a number of Supabase APIs. The team is currently looking into this now.

Resolved: This incident has been resolved.

Monitoring: Our upstream partner has marked their issues resolved. We are seeing latency return to normal, but will continue to monitor.

Identified: Our upstream partner has made some adjustments which appear to have reduced observed lantency in the us-east-1 region. We are continuing the work with them as well as monitor impact on our side.

Identified: We are still investigating any possible issues on our side, but our upstream networking partner has confirmed issues in the US-East region currently, which we suspect is the cause of added latency for our Data API layer. We've been informed they have isolated the issue and are working on a fix.

Investigating: We are receiving reports of increased latency across a number of Supabase APIs. The team is currently looking into this now.

Resolved: This incident has been resolved.

Monitoring: Our upstream partner has marked their issues resolved. We are seeing latency return to normal, but will continue to monitor.

Identified: Our upstream partner has made some adjustments which appear to have reduced observed lantency in the us-east-1 region. We are continuing the work with them as well as monitor impact on our side.

Identified: We are still investigating any possible issues on our side, but our upstream networking partner has confirmed issues in the US-East region currently, which we suspect is the cause of added latency for our Data API layer. We've been informed they have isolated the issue and are working on a fix.

Investigating: We are receiving reports of increased latency across a number of Supabase APIs. The team is currently looking into this now.

Resolved: This incident has been resolved.

Monitoring: We determined that there was a spike in activity relating to saved content (queries and folders in the SQL Editor). Things are looking normal at the moment. We are re-enabling saved query and folder access and will monitor for any increased error rates in the management API.

Investigating: We've spotted high error rates for some of the API requests. We made a temporary fix that prevents access to saved queries and folders. We are actively working on getting things back to normal and turning this functionality back on.

Resolved: This incident has been resolved.

Monitoring: Our upstream partner has marked their issues resolved. We are seeing latency return to normal, but will continue to monitor.

Identified: Our upstream partner has made some adjustments which appear to have reduced observed lantency in the us-east-1 region. We are continuing the work with them as well as monitor impact on our side.

Identified: We are still investigating any possible issues on our side, but our upstream networking partner has confirmed issues in the US-East region currently, which we suspect is the cause of added latency for our Data API layer. We've been informed they have isolated the issue and are working on a fix.

Investigating: We are receiving reports of increased latency across a number of Supabase APIs. The team is currently looking into this now.

Resolved: This incident has been resolved.

Monitoring: Our upstream partner has marked their issues resolved. We are seeing latency return to normal, but will continue to monitor.

Identified: Our upstream partner has made some adjustments which appear to have reduced observed lantency in the us-east-1 region. We are continuing the work with them as well as monitor impact on our side.

Identified: We are still investigating any possible issues on our side, but our upstream networking partner has confirmed issues in the US-East region currently, which we suspect is the cause of added latency for our Data API layer. We've been informed they have isolated the issue and are working on a fix.

Investigating: We are receiving reports of increased latency across a number of Supabase APIs. The team is currently looking into this now.