Sansform - Notice history

Experiencing partially degraded performance

sansform.ai - Operational

100% - uptime
Jan 2026 · 100.0%Feb · 100.0%Mar · 100.0%

Previous page

Next page

Jan 2026
Feb 2026
Mar 2026

Notice history

Mar 2026

Elevated error rates affecting Edge Functions in the eu-central-1 (Frankfurt) region
  • Resolved
    Resolved

    Error rates have returned to normal. This incident has been resolved.

  • Monitoring
    Monitoring

    We carried out a controlled redeployment of the affected services to restore stability.
    The system is now operating normally, and we will continue to monitor.

  • Investigating
    Investigating

    We are currently investigating elevated error rates affecting Edge Functions in the eu-central-1 (Frankfurt) region

Elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region
  • Resolved
    Resolved

    The fix was implemented. All impacted projects and newly created projects in the region are now successfully connecting to storage services.

  • Identified
    Identified

    The root cause, involving task instances and batch sending events, has been identified. Our engineering team is working on a fix.

  • Update
    Update

    We are continuing to investigate elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region.
    While we are still observing a higher-than-normal level of errors, initial findings indicate that the overall impact is lower than first expected. Many affected requests are succeeding upon retry.
    Our team is actively working to determine the root cause and will provide further updates as more information becomes available.

  • Update
    Update

    We are continuing to investigate elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region.
    Newly created projects may still experience issues connecting to storage, while existing projects remain unaffected at this time.
    Our team is actively working to determine the root cause and assess the full impact.
    We will provide further updates as more information becomes available.

  • Investigating
    Investigating

    We are currently investigating elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region.
    Newly created projects may experience issues connecting to storage, while existing projects remain unaffected at this time.
    We are actively working to understand the full scope of the impact and will provide further updates as more information becomes available.

Storage errors in EU-Central-2
  • Resolved
    Resolved

    All storage operations have returned to normal.

  • Monitoring
    Monitoring

    The upstream incident has been resolved and we have not observed any additional errors. We will continue to monitor our storage infrastructure for continued stable operations.

  • Update
    Update

    We are observing storage error rates returning to normal.

  • Identified
    Identified

    We have identified the cause of the storage issue in EU-Central-2. The upstream provider is working to resolve the issue.

  • Investigating
    Investigating

    We have noticed that storage uploads and downloads have become degraded in EU-Central-2. We are investigating.

Elevated Management API error rates across all regions
  • Resolved
    Resolved

    Error rates have returned to baseline and all regions are operating as expected.

  • Monitoring
    Monitoring

    We've seen error rates return to normal levels, and all regions are now holding steady. We will continue to monitor to make sure things remain stable.

  • Update
    Update

    We are continuing to see some periodic spikes in error rates; however, total rate of errors are decreasing across most regions. We're continuing efforts to get all systems back to green.

    When error rates spike, management API functions, which would mean dashboard actions, project creation, configuration changes, and other functions remain impacted.

    Existing projects are unaffected and connectivity via the Data APIs, Postgres connections, and Supavisor are unaffected.

  • Update
    Update

    The team is continuing to deploy mitigations, and we are seeing error rates improve, but are not back to baseline yet.

    All management API functions, which would mean dashboard actions, project creation, configuration changes, and other functions remain impacted.

    Existing projects are unaffected and connectivity via the Data APIs, Postgres connections, and Supavisor are unaffected.

  • Identified
    Identified

    We have identified the source of the increased error rates, and are working on a fix now.

    All management API functions, which would mean dashboard actions, project creation, configuration changes, and other functions remain impacted.

    Existing projects are unaffected and connectivity via the Data APIs, Postgres connections, and Supavisor are unaffected.

  • Update
    Update

    We've expanded this to all management API functions, which would mean dashboard actions, project creation, configuration changes, and other functions would also be impacted. Error rates are currently improving, but the team is investigating the root cause to ensure continued stability.

    Existing projects are unaffected and connectivity via the Data APIs, Postgres connections, and Supavisor are unaffected.

  • Investigating
    Investigating

    We are currently investigating the cause, but users may see issues creating projects across all regions. Existing projects are not affected and remain up and stable.

Edge Functions experiencing high response times in ap-northeast-1 and ap-northeast-2
  • Resolved
    Resolved

    Both regions are now working as usual.

  • Monitoring
    Monitoring

    Response times in both the ap-northeast-1 (Tokyo) and ap-northeast-2 (Seoul) regions have now stabilised.
    We will continue to monitor the systems closely to ensure stability.

  • Identified
    Identified

    Response times in the ap-northeast-1 (Tokyo) region have improved following mitigation efforts.
    We are currently rolling out the fix to the ap-northeast-2 (Seoul) region.
    Further updates will be provided as the rollout continues.

  • Update
    Update

    We are continuing to investigate reports of Edge Functions experiencing high response times in Asia Pacific regions
    Our team is still working to determine the underlying cause.
    We understand the disruption this may be causing and are treating this with high priority.

  • Update
    Update

    We are continuing to investigate reports of Edge Functions experiencing high response times in Asia Pacific regions
    Our team is still working to determine the underlying cause.
    We understand the disruption this may be causing and are treating this with high priority.

  • Investigating
    Investigating

    We are currently investigating the cause for increased response times.

Feb 2026

Increased Edge Function Errors across multiple regions
  • Resolved
    Resolved

    The issue affecting Edge Functions has now been fully resolved, and users have reported Edge Functions operating as expected.
    The root cause was a denial-of-service event that led to elevated error rates and 504 responses across impacted regions.
    Mitigations have been implemented to restore stability.
    We will be publishing a full post-mortem with additional details, once our internal review is complete.
    Thank you for your patience while we worked to resolve this issue.

  • Monitoring
    Monitoring

    The fix has been implemented and early indicators suggest it has resolved the 504 errors affecting Edge Functions.
    We are continuing to monitor system performance closely to ensure stability and confirm full recovery across all affected regions.
    We will provide a final update once we are confident the issue is fully resolved.

  • Identified
    Identified

    We believe we have identified the underlying cause of the 504 errors affecting Edge Functions across multiple regions.
    The team are currently implementing corrective measures to address the issue and restore service stability.

  • Update
    Update

    We are continuing to investigate reports of Edge Functions returning 504 errors across multiple regions.
    Our team is still working to determine the underlying cause.
    We understand the disruption this may be causing and are treating this with high priority.

  • Investigating
    Investigating

    We are currently investigating reports of Edge Functions returning 504 errors across multiple regions.

    The team has been alerted and is actively investigating the root cause. We are working to identify the scope of affected regions.

    We will provide an update as soon as we have more information.

Billing Function Maintenance - February 26, 2026
  • Completed
    February 26, 2026 at 2:00 AM
    Completed
    February 26, 2026 at 2:00 AM

    The scheduled maintenance has been completed.

  • In progress
    February 26, 2026 at 1:01 AM
    In progress
    February 26, 2026 at 1:01 AM

    Scheduled maintenance is currently in progress. We will provide updates as necessary.

  • Update
    February 26, 2026 at 12:00 AM
    Update
    February 26, 2026 at 12:00 AM

    Maintenance will begin as scheduled in 60 minutes.

  • Scheduled
    February 25, 2026 at 6:07 PM
    Scheduled
    February 25, 2026 at 6:07 PM

    Our upstream billing provider is doing some important maintenance on February 26, 2026. Their maintenance window is, very conservatively, from 0100-0500 UTC. They estimate that services will be impacted for approximately the first 5 minutes of this window. We have set this maintenance window for 1 hour from our side, but do not expect the impact to be longer than 5 minutes.

    Project availability, compute add-on changes, disk scaling, and other project configuration changes ARE NOT IMPACTED. All Postgres and Data API access WILL REMAIN FUNCTIONAL. Additionally Auth, Realtime, Storage, Edge Functions, and all other features will remain functional.

    The impact for Supabase will be that the following activities will be restricted during this ~5 minute period:

    Organization creation
    Subscription plan changes (e.g. upgrades/downgrades)
    Credit top-ups and redemptions
    Billing-related API requests (e.g. the billing dashboard pages for your organization)

    We will be disabling these features starting at 01:00 UTC, and plan to re-enable them at 01:05 UTC, pending positive healthchecks from the upstream billing APIs.

Users Experiencing Network Connectivity Problems (India Region)
  • Update
    Update

    Read more about incident and similar incidents in our new blog post about Navigating Regional Network Blocks.

  • Resolved
    Resolved

    We are pleased to inform our community that access to Supabase’s website supabase.co has now been fully restored for all users across India. We sincerely thank the Ministry of Electronics and Information Technology (MeitY) for their prompt action and constructive engagement in resolving this matter.

    Access to our services has been fully restored, and we deeply appreciate the continued patience and support of builders, developers, and businesses across India.

  • Monitoring
    Monitoring

    We are pleased to inform our community that access to Supabase’s website supabase.co has now been fully restored for all users across India. We sincerely thank the Ministry of Electronics and Information Technology (MeitY) for their prompt action and constructive engagement in resolving this matter. Access to our services has been fully restored, and we deeply appreciate the continued patience and support of builders,  developers, and businesses across India.

    If you were previously affected, you should now be able to access your Supabase projects without any interruptions. Please clear your DNS cache or restart your network connection if you still encounter issues. Additionally, please allow up to 24 hours for the provider-side changes to propagate. If you continue to see access problems after 24 hours, let us know!

    Thank you for your patience while we worked through this incident.

  • Update
    Update

    We have continuing contact with the relevant authorities to address the connectivity issues impacting some users in India. Decision makers are involved on all sides. While we don’t have a confirmed timeline to share just yet, this is top priority for our team and leadership.
    We will post an update once the issue is resolved or additional information becomes available.

  • Update
    Update

    We continue to work closely with the relevant authorities to address the connectivity issues impacting some users in India.
    Our discussions are progressing, and we’re seeing constructive engagement as we work towards a resolution.
    While we don’t have a confirmed timeline to share just yet, this is top priority for our team.
    We will post an update once the issue is resolved or additional information becomes available.

  • Update
    Update

    We acknowledge the ongoing impact this issue is having on our users in India. We have made important progress in our contact with the relevant authorities and continue to actively work towards a resolution.

    We continue to advise affected customers to use an alternative DNS provider or a VPN as a workaround in the interim. For some customers, custom domains may also be a viable solution. If you have any questions regarding these options, please contact Supabase support.

    We will post an update once the issue is resolved or additional information becomes available.

  • Update
    Update

    We understand many users in India continue to be blocked from accessing Supabase. We acknowledge the difficulties this is causing for our users there. Supabase continues to follow up through all available channels to resolve this issue.

    We continue to advise affected customers to use an alternative DNS provider or a VPN as a workaround in the interim. For some customers, custom domains may also be a viable solution. If you have any questions regarding these options, please contact Supabase support.

    We will post an update once the issue is resolved or additional information becomes available.

  • Update
    Update

    Affected customers who are using the Custom Domain feature may be able to restore connectivity by switching their Custom Domain's DNS to an alternative DNS and enabling proxying.

    We advise affected customers to continue to report the issue to their ISP.

  • Update
    Update

    We have received some reports that other ISPs in India may be impacted by access limitations. We continue to follow up through all available channels to resolve this issue. We have engaged multiple teams at Supabase communicating with multiple entities in India in an effort to do all we can to resolve the access issues our users in India are experiencing.

    We advise affected customers to continue to report the issue to their ISP and to use an alternative DNS provider or a VPN as a workaround in the interim.

    We will post an update once the issue is resolved or additional information becomes available.

  • Update
    Update

    We continue to follow up through all available channels to work with the ISP to resolve this issue.

    We advise affected customers to also report the issue to their ISP and to use an alternative DNS provider as a workaround.

    We will post an updated once the ISP has confirmed that the issue is resolved or additional information becomes available.

  • Update
    Update

    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.

  • Update
    Update

    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/

  • Update
    Update

    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.

  • Update
    Update

    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
    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
    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.

Jan 2026

No notices reported this month

Jan 2026 to Mar 2026

Next