Supabase Status

Identified: We are currently aware of an issue affecting reachability of Supabase projects for a subset of users based in India. Supabase infrastructure remains fully operational.

We have confirmed that the projects of impacted users remain accessible from regions outside India. Our investigation has confirmed that a service provider in the region is not serving the correct DNS responses for Supabase projects from their internal DNS resolvers.

We are following up through all available channels to work with the ISP to resolve this issue. We also advise affected customers to also report the issue to their ISP.

The best workaround we have currently is for affected users to use an alternative DNS providers such as: Cloudflare: https://1.1.1.1 Google https://developers.google.com/speed/public-dns Quad9: https://quad9.net/

Alternatively users can use a VPN to avoid this issue

We will post a further update once the ISP has confirmed that the issue is resolved or additional information becomes available.

Identified: We have confirmed that the projects of impacted users remain accessible from regions outside India. Our investigation is currently focused on an ISP-level block affecting users within India.

We advise affected customers to also report the issue to their ISP. Supabase infrastructure remains fully operational.

The best workaround we have currently is for affected users to use an alternative DNS providers such as: Cloudflare: https://1.1.1.1 Google https://developers.google.com/speed/public-dns Quad9: https://quad9.net/

Identified: We have confirmed that the projects of impacted users remain accessible from regions outside India. Our investigation is currently focused on a potential ISP-level block affecting users within India.

Identified: We continue to work with customers to address their connectivity issues. We are also contacting the relevant network providers to work with them to resolve the issue.

Identified: A DNS resolution issue is affecting customers in AP-South-1 and AP-Southeast-2. Certain ISP DNS servers appear to be unavailable, preventing connections to Supabase endpoints. Some users reported that switching to Cloudflare DNS (1.1.1.1) may restore connectivity. We advise affected customers to also report the issue to their ISP. Supabase infrastructure remains fully operational.

Investigating: We have reports of customers having difficulties connecting to Supabase from locations accessing AP-south-1, including a number of reports from India. We are actively investigating the issue.

Resolved: Things have remained stable, and we are confident that things are now resolved.

The impact of this event was limited to log visibility and log retention. Some logs between 20:20 UTC and 23:23 UTC on Friday, Feb 20, 2026 may not be available.

Monitoring: The configuration update has brought error rates and stability back to normal, all logging and observability data should now be accessible.

The impact of this event was limited to log visibility and log retention. Some logs between 20:20 UTC and 23:23 UTC on Friday, Feb 20, 2026 may not be available.

We will continue to monitor to ensure things continue to look good.

Identified: The team is currently pushing a configuration change we hope will finish stabilizing the analytics services. We will continue to update as we have more information.

Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. This only affects visibility of the above mentioned information.

Identified: The analytics service continues to be periodically degraded, which means some users may still periodically see issues seeing logging and observability information. We have added additional resources to the logging service to increase stability.

The team is continuing their work to stabilize all analytics functionality.

Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. This only affects visibility of the above mentioned information.

Identified: We are still seeing logging and observability services continue to stabilize, but some users may continue to see some issues. The team is continuing to working on full stabilization efforts.

Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. This only affects visibility of the above mentioned information.

Identified: We are still seeing logging and observability services continue to stabilize, but some users may continue to see some issues. The team is continuing to working on full stabilization efforts.

Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. This only affects visibility of the above mentioned information.

Identified: We've implemented a fix, and we are seeing the affected services begin to stabilize, but access to logs, observability metrics, and edge function invocation information may still be spotty.

The team is continuing to working on full stabilization efforts.

Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. This only affects visibility of the above mentioned information.

Identified: We have identified an issue resulting in missing log, observability, and edge function information.

Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. This only affects visibility of the above mentioned information.

We will have another update within 20 minutes.

Investigating: We are investigating errors across our logs and observability services and will provide an update soon.

Investigating: We are investigating errors with Edge Functions and will provide an update soon.

Resolved: Metrics collection continues to operate normally in US-West-2, and full metrics collection has been fully restored with no blips in stability.

Monitoring: The team has deployed additional capacity and has restored metrics collection operations. All metrics collection in region is fully operational and the team is actively monitoring the fixes deployed.

Identified: The team has deployed a fix and is actively monitoring recovery of partially degraded metrics collection. Some US-West-2 users may see metrics periodically available, but others may still see missing metrics.

This does not impact project availability or functionality, which remain healthy.

Identified: The team is continuing to work on a fix for metrics collection. Some US-West-2 users may see metrics periodically available, but others may still see missing metrics.

We'll continue to update here as we have more information.

This does not impact project availability or functionality, which remain healthy.

Identified: We have identified the components resulting in the delayed metrics collection, and the team is working on a fix.

This does not impact project availability or functionality, which remain healthy.

Investigating: We have discovered an issue with metrics collection for projects in US-West-2. Some users may not be able to see metrics for these projects in the dashboard, and functions such as automatic disk resizes may be delayed as well.

This does not impact project availability or functionality, which remain healthy.

The team is currently investigating.

Identified: We are currently aware of an issue affecting reachability of Supabase projects for a subset of users based in India. Supabase infrastructure remains fully operational.

We have confirmed that the projects of impacted users remain accessible from regions outside India. Our investigation has confirmed that a service provider in the region is not serving the correct DNS responses for Supabase projects from their internal DNS resolvers.

We are following up through all available channels to work with the ISP to resolve this issue. We also advise affected customers to also report the issue to their ISP.

The best workaround we have currently is for affected users to use an alternative DNS providers such as: Cloudflare: https://1.1.1.1 Google https://developers.google.com/speed/public-dns Quad9: https://quad9.net/

Alternatively users can use a VPN to avoid this issue

We will post a further update once the ISP has confirmed that the issue is resolved or additional information becomes available.

Identified: We have confirmed that the projects of impacted users remain accessible from regions outside India. Our investigation is currently focused on an ISP-level block affecting users within India.

We advise affected customers to also report the issue to their ISP. Supabase infrastructure remains fully operational.

The best workaround we have currently is for affected users to use an alternative DNS providers such as: Cloudflare: https://1.1.1.1 Google https://developers.google.com/speed/public-dns Quad9: https://quad9.net/

Identified: We have confirmed that the projects of impacted users remain accessible from regions outside India. Our investigation is currently focused on a potential ISP-level block affecting users within India.

Identified: We continue to work with customers to address their connectivity issues. We are also contacting the relevant network providers to work with them to resolve the issue.

Identified: A DNS resolution issue is affecting customers in AP-South-1 and AP-Southeast-2. Certain ISP DNS servers appear to be unavailable, preventing connections to Supabase endpoints. Some users reported that switching to Cloudflare DNS (1.1.1.1) may restore connectivity. We advise affected customers to also report the issue to their ISP. Supabase infrastructure remains fully operational.

Investigating: We have reports of customers having difficulties connecting to Supabase from locations accessing AP-south-1, including a number of reports from India. We are actively investigating the issue.

Resolved: Things have remained stable, and we are confident that things are now resolved.

The impact of this event was limited to log visibility and log retention. Some logs between 20:20 UTC and 23:23 UTC on Friday, Feb 20, 2026 may not be available.

Monitoring: The configuration update has brought error rates and stability back to normal, all logging and observability data should now be accessible.

The impact of this event was limited to log visibility and log retention. Some logs between 20:20 UTC and 23:23 UTC on Friday, Feb 20, 2026 may not be available.

We will continue to monitor to ensure things continue to look good.

Identified: The team is currently pushing a configuration change we hope will finish stabilizing the analytics services. We will continue to update as we have more information.

Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. This only affects visibility of the above mentioned information.

Identified: The analytics service continues to be periodically degraded, which means some users may still periodically see issues seeing logging and observability information. We have added additional resources to the logging service to increase stability.

The team is continuing their work to stabilize all analytics functionality.

Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. This only affects visibility of the above mentioned information.

Identified: We are still seeing logging and observability services continue to stabilize, but some users may continue to see some issues. The team is continuing to working on full stabilization efforts.

Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. This only affects visibility of the above mentioned information.

Identified: We are still seeing logging and observability services continue to stabilize, but some users may continue to see some issues. The team is continuing to working on full stabilization efforts.

Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. This only affects visibility of the above mentioned information.

Identified: We've implemented a fix, and we are seeing the affected services begin to stabilize, but access to logs, observability metrics, and edge function invocation information may still be spotty.

The team is continuing to working on full stabilization efforts.

Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. This only affects visibility of the above mentioned information.

Identified: We have identified an issue resulting in missing log, observability, and edge function information.

Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. This only affects visibility of the above mentioned information.

We will have another update within 20 minutes.

Investigating: We are investigating errors across our logs and observability services and will provide an update soon.

Investigating: We are investigating errors with Edge Functions and will provide an update soon.

Resolved: Metrics collection continues to operate normally in US-West-2, and full metrics collection has been fully restored with no blips in stability.

Monitoring: The team has deployed additional capacity and has restored metrics collection operations. All metrics collection in region is fully operational and the team is actively monitoring the fixes deployed.

Identified: The team has deployed a fix and is actively monitoring recovery of partially degraded metrics collection. Some US-West-2 users may see metrics periodically available, but others may still see missing metrics.

This does not impact project availability or functionality, which remain healthy.

Identified: The team is continuing to work on a fix for metrics collection. Some US-West-2 users may see metrics periodically available, but others may still see missing metrics.

We'll continue to update here as we have more information.

This does not impact project availability or functionality, which remain healthy.

Identified: We have identified the components resulting in the delayed metrics collection, and the team is working on a fix.

This does not impact project availability or functionality, which remain healthy.

Investigating: We have discovered an issue with metrics collection for projects in US-West-2. Some users may not be able to see metrics for these projects in the dashboard, and functions such as automatic disk resizes may be delayed as well.

This does not impact project availability or functionality, which remain healthy.

The team is currently investigating.

Identified: We are currently aware of an issue affecting reachability of Supabase projects for a subset of users based in India. Supabase infrastructure remains fully operational.

We have confirmed that the projects of impacted users remain accessible from regions outside India. Our investigation has confirmed that a service provider in the region is not serving the correct DNS responses for Supabase projects from their internal DNS resolvers.

We are following up through all available channels to work with the ISP to resolve this issue. We also advise affected customers to also report the issue to their ISP.

The best workaround we have currently is for affected users to use an alternative DNS providers such as: Cloudflare: https://1.1.1.1 Google https://developers.google.com/speed/public-dns Quad9: https://quad9.net/

Alternatively users can use a VPN to avoid this issue

We will post a further update once the ISP has confirmed that the issue is resolved or additional information becomes available.

Identified: We have confirmed that the projects of impacted users remain accessible from regions outside India. Our investigation is currently focused on an ISP-level block affecting users within India.

We advise affected customers to also report the issue to their ISP. Supabase infrastructure remains fully operational.

The best workaround we have currently is for affected users to use an alternative DNS providers such as: Cloudflare: https://1.1.1.1 Google https://developers.google.com/speed/public-dns Quad9: https://quad9.net/

Identified: We have confirmed that the projects of impacted users remain accessible from regions outside India. Our investigation is currently focused on a potential ISP-level block affecting users within India.

Identified: We continue to work with customers to address their connectivity issues. We are also contacting the relevant network providers to work with them to resolve the issue.

Identified: A DNS resolution issue is affecting customers in AP-South-1 and AP-Southeast-2. Certain ISP DNS servers appear to be unavailable, preventing connections to Supabase endpoints. Some users reported that switching to Cloudflare DNS (1.1.1.1) may restore connectivity. We advise affected customers to also report the issue to their ISP. Supabase infrastructure remains fully operational.

Investigating: We have reports of customers having difficulties connecting to Supabase from locations accessing AP-south-1, including a number of reports from India. We are actively investigating the issue.

Resolved: Things have remained stable, and we are confident that things are now resolved.

The impact of this event was limited to log visibility and log retention. Some logs between 20:20 UTC and 23:23 UTC on Friday, Feb 20, 2026 may not be available.

Monitoring: The configuration update has brought error rates and stability back to normal, all logging and observability data should now be accessible.

The impact of this event was limited to log visibility and log retention. Some logs between 20:20 UTC and 23:23 UTC on Friday, Feb 20, 2026 may not be available.

We will continue to monitor to ensure things continue to look good.

Identified: The team is currently pushing a configuration change we hope will finish stabilizing the analytics services. We will continue to update as we have more information.

Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. This only affects visibility of the above mentioned information.

Identified: The analytics service continues to be periodically degraded, which means some users may still periodically see issues seeing logging and observability information. We have added additional resources to the logging service to increase stability.

The team is continuing their work to stabilize all analytics functionality.

Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. This only affects visibility of the above mentioned information.

Identified: We are still seeing logging and observability services continue to stabilize, but some users may continue to see some issues. The team is continuing to working on full stabilization efforts.

Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. This only affects visibility of the above mentioned information.

Identified: We are still seeing logging and observability services continue to stabilize, but some users may continue to see some issues. The team is continuing to working on full stabilization efforts.

Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. This only affects visibility of the above mentioned information.

Identified: We've implemented a fix, and we are seeing the affected services begin to stabilize, but access to logs, observability metrics, and edge function invocation information may still be spotty.

The team is continuing to working on full stabilization efforts.

Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. This only affects visibility of the above mentioned information.

Identified: We have identified an issue resulting in missing log, observability, and edge function information.

Projects and services are up and running, edge function invocations are unaffected, and project creation/adjustments are unaffected. This only affects visibility of the above mentioned information.

We will have another update within 20 minutes.

Investigating: We are investigating errors across our logs and observability services and will provide an update soon.

Investigating: We are investigating errors with Edge Functions and will provide an update soon.