Is Supabase down?

Last checked 1m ago
Current status
Supabase is up

No incidents right now.

Official status page: https://status.supabase.com · Polled every 5 minutes · 26 components tracked

Supabase is operational right now. Last checked 1m ago; the most recent incident resolved 23h ago.

Real-time Supabase status, recent outages, and incident history — pulled directly from Supabase's official status page at https://status.supabase.com every 5 minutes. Pingoru tracks 26 Supabase services and has captured 48 incidents in the last 90 days (97.43% uptime). Get email, Slack, Discord, or webhook alerts the moment Supabase reports a new incident — free for 5 monitors, no credit card.

Users who monitor Supabase also follow these Database services: Snowflake Stitch Data ClickHouse Iron.io Aiven SolarWinds Observability Neo4j Aura Upstash Pinecone PlanetScale View all 6,000+ providers
Supabase uptime 97.43% uptime · past 90 days
Mon Wed Fri
MarAprMayJun
Less More

Active incidents 2

  1. Ongoing ● 5d 19h
    Started Jun 08, 2026, 03:39 AM UTC
    Timeline · 6 updates
    • identified · Jun 08, 2026, 03:39 AM UTC

      We are investigating reports of DNS resolution failures affecting a subset of customers connecting to Supabase project endpoints. This appears to be related to a third-party issue with .co TLD resolution impacting multiple DNS providers. Customers may be able to bypass this issue by using a VPN while we work towards resolution. We will update the statuspage when we have more information to share.

    • monitoring · Jun 08, 2026, 06:37 AM UTC

      The third-party has confirmed a fix has been implemented and we are validating the results with our impacted users.

    • monitoring · Jun 08, 2026, 12:38 PM UTC

      Our testing has observed that the issue is related to selected ISP resolvers to .co domains. The clients impacted are mainly located in us-east-1, us-east-2 region. We continue to review this issue for resolution with our third party network partner.

    • monitoring · Jun 08, 2026, 05:32 PM UTC

      We have opened a follow-up issue with our provider to address the continued problems a subset of our customers in the Americas are experiencing with top-level ".co" domain resolution. We will continue to pursue this issue until it is resolved and customers who have reported the issue are able to correctly resolve the domain name.

    • monitoring · Jun 10, 2026, 11:24 PM UTC

      Our upstream TLD provider believes they have identified the underlying issue, and we are continuing to coordinate with them to review their findings and potential remediation options. In parallel, we are investigating other factors that may be contributing to the ongoing resolution problems affecting a subset of customers. VPNs continue to provide a workaround for impacted end users while our investigation remains ongoing.

    • monitoring · Jun 12, 2026, 11:09 AM UTC

      Our upstream TLD provider is continuing to make changes to its network routing policies to address this issue. These changes are intended to improve regional traffic routing and reduce DNS resolution failures. We have already begun to see improvements as these changes take effect, but the issue has not yet been fully resolved. We are continuing to monitor the situation closely and work with the provider toward a complete resolution. We will provide another update as soon as more information becomes available.

    Latest: Our upstream TLD provider is continuing to make changes to its network routing policies to address this issue. These changes are intended to improve regional traffic routing and re…

  2. Ongoing ● 30d 7h
    Started May 14, 2026, 03:34 PM UTC
    Timeline · 8 updates
    • investigating · May 14, 2026, 03:34 PM UTC

      We are investigating reports of some access issues to Supabase IP addresses from a network provider in Brazil.

    • investigating · May 14, 2026, 03:54 PM UTC

      We have isolated the issue to a specific Internet provider in Brazil and are working to contact that provider to resolve the issue. We will update the statuspage when we have more information to share.

    • investigating · May 14, 2026, 04:37 PM UTC

      We have made contact with the ISP in Brazil and are working through their support process for this issue. Customers may be able to bypass the problem by using a VPN or alternative network while we work towards resolution.

    • identified · May 14, 2026, 10:23 PM UTC

      We are continuing to contact the ISP in Brazil to work through this issue. Customers may be able to bypass this issue by using a VPN or alternative network while we work towards resolution. Thank you for your patience. We will provide an update when we have more information to share.

    • identified · May 19, 2026, 10:30 PM UTC

      We are continuing to contact the ISP in Brazil to work through this issue: however they have remained unresponsive to outreach. We are exploring other options to get in touch with them. Customers may be able to bypass this issue by using a VPN or alternative network while we work towards resolution. Thank you for your patience. We will provide an update when we have more information to share.

    • identified · Jun 03, 2026, 09:32 PM UTC

      We continue to work with the service provider to resolve the residual access issues. We have scheduled direct consultations with the provider to attempt to resolve the issue.

    • identified · Jun 09, 2026, 01:26 PM UTC

      We are engaged with senior networking team members at the impacted provider. They are actively investigating the domain name resolution issues we have reported. If you are continuing to experience .co name resolution issues in Brazil, please update your ticket or open a new ticket to let us know so we can add that information to the investigation.

    • monitoring · Jun 12, 2026, 02:42 PM UTC

      We continue to work with the relevant provider and have seen improvements. We are monitoring the progress that has been made to ensure it continues.

    Latest: We continue to work with the relevant provider and have seen improvements. We are monitoring the progress that has been made to ensure it continues.

Recent outages & incidents

Past 90 days
  1. Resolved 8h 39m
    Started Jun 12, 2026, 04:00 PM UTC · Resolved Jun 13, 2026, 12:40 AM UTC
    Storage
    Timeline · 8 updates
    • identified · Jun 12, 2026, 04:00 PM UTC

      Users in US-West-2 are seeing increased latency on storage requests. The team has identified the issue and is working on a solution.

    • identified · Jun 12, 2026, 04:30 PM UTC

      We are implementing load mitigation strategies to improve the performance of storage requests in US-West-2.

    • identified · Jun 12, 2026, 05:29 PM UTC

      The team is still working on a solution, and mitigation work is underway.

    • identified · Jun 12, 2026, 06:28 PM UTC

      We have implemented further mitigations and are tracking their progress. We continue to actively work this issue.

    • identified · Jun 12, 2026, 07:30 PM UTC

      We are seeing improvement in the performance of us-west-2 after implementation of our mitigation strategies. Storage operation is returning to normal. We will continue to monitor performance in this region.

    • monitoring · Jun 12, 2026, 08:26 PM UTC

      Backlog is being effectively processed and operations have returned to normal. We continue to monitor the performance in us-west-2.

    • monitoring · Jun 12, 2026, 11:57 PM UTC

      Job queues continue to drain. We will actively monitor until they are complete.

    • resolved · Jun 13, 2026, 12:40 AM UTC

      All residual jobs have drained. Storage performance and job activity is normal.

    Latest: All residual jobs have drained. Storage performance and job activity is normal.

  2. Resolved
    Started Jun 10, 2026, 12:00 AM UTC · Resolved Jun 10, 2026, 12:00 AM UTC
    Timeline · 1 update
    • resolved · Jun 10, 2026, 01:43 AM UTC

      From 00:52 to 01:02 UTC on 10th June an internal deployment in one of the ap-northeast-1 clusters caused a higher connection failure rate. Users would have experienced failing connections, increased query latency and would not have been able to retrieve pooler metrics. The deployment has now been reverted and full service availability restored.

    Latest: From 00:52 to 01:02 UTC on 10th June an internal deployment in one of the ap-northeast-1 clusters caused a higher connection failure rate. Users would have experienced failing conn…

  3. Resolved 1h 5m
    Started Jun 02, 2026, 01:36 PM UTC · Resolved Jun 02, 2026, 02:41 PM UTC
    Management API
    Timeline · 4 updates
    • investigating · Jun 02, 2026, 01:36 PM UTC

      We are currently investigating an issue affecting pause, restore, and backup operations for projects in us-east-2 (Ohio) We will provide further updates as more information becomes available.

    • identified · Jun 02, 2026, 02:05 PM UTC

      We have identified the cause is related to a recent deployment. We have initiated a redeploy to address the issue.

    • monitoring · Jun 02, 2026, 02:12 PM UTC

      The redeployment has returned pause, restore and backup operations in the affected region to normal. We will continue to monitor for any residual impact.

    • resolved · Jun 02, 2026, 02:41 PM UTC

      All operations have continued as normal since moving this incident to Monitoring. We are resolving this incident.

    Latest: All operations have continued as normal since moving this incident to Monitoring. We are resolving this incident.

  4. Resolved 2h 39m
    Started May 21, 2026, 04:46 PM UTC · Resolved May 21, 2026, 07:26 PM UTC
    Timeline · 4 updates
    • investigating · May 21, 2026, 04:46 PM UTC

      We are seeing degradation in branch creation linked to database migration locks. We are investigating and will share further updates as progress is made.

    • investigating · May 21, 2026, 05:45 PM UTC

      We continue investigating different possible underlying causes and will provide updates as progress is made.

    • monitoring · May 21, 2026, 06:54 PM UTC

      Branch creation has returned to normal. We are investigating a set of factors that likely contributed to the degradation, including cluster load, lock contention, and service start-up sequencing to identify areas for improvement going forward. We will monitor our platform for another 30 minutes to ensure the problem has fully resolved before resolving the incident.

    • resolved · May 21, 2026, 07:26 PM UTC

      Branch creation continues to be stable.

    Latest: Branch creation continues to be stable.

  5. Resolved 2h 20m
    Started May 21, 2026, 08:30 AM UTC · Resolved May 21, 2026, 10:51 AM UTC
    Dashboard
    Timeline · 6 updates
    • investigating · May 21, 2026, 08:30 AM UTC

      Users that are already logged in are not affected.

    • investigating · May 21, 2026, 08:33 AM UTC

      We are currently investigating an issue causing login failures for some users attempting to authenticate to the Supabase dashboard via SSO or email/password login flows. Affected users may see an error similar to: “captcha protection: request disallowed (sitekey-secret-mismatch)” Currently logged-in users are not affected, and GitHub authentication continues to operate normally. We will continue to provide updates as more information becomes available.

    • identified · May 21, 2026, 08:49 AM UTC

      We have identified the issue as being related to a recent key rotation and are currently working on a fix.

    • identified · May 21, 2026, 09:26 AM UTC

      A fix has been implemented and is currently being rolled out. We will continue to provide updates as the deployment progresses.

    • monitoring · May 21, 2026, 09:43 AM UTC

      We have applied a fix and are seeing login services return to normal. We will continue to monitor authentication success rates over the next 60 minutes to ensure stability.

    • resolved · May 21, 2026, 10:51 AM UTC

      The issue affecting SSO logins has now been resolved. Thank you for your patience while we worked through this issue.

    Latest: The issue affecting SSO logins has now been resolved. Thank you for your patience while we worked through this issue.

See the full Supabase outage history

34 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Supabase outage history →

Or sign up free to get alerts when Supabase breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 39 incidents View full outage history →