SubHero Status - Incident history https://subhero.instatus.com SubHero Tue, 19 May 2026 22:24:12 +0000 API is back up Type: Incident Affected Components: API May 20, 01:44:17 GMT+0 - Resolved - API is back up. This incident was automatically resolved by Instatus monitoring. May 20, 02:49:18 GMT+0 - Postmortem - **Summary** Between May 20, 2026 06:24 UTC and 09:44 UTC (3h 20m), SubHero's API and background workers were unavailable. Translation, transcription, and any feature that talks to our backend returned errors. The Cloudflare-hosted marketing site, in-browser subtitle editor tools, and Supabase auth were unaffected. **Root cause** Our backend (FastAPI + Celery workers) is hosted on Railway, which runs on Google Cloud Platform. During this window, GCP suspended Railway's account, taking Railway's entire infrastructure offline. Every service hosted on Railway — ours included — went down with it. This was an upstream provider issue outside our control. **Resolution** Service was restored automatically once Railway's account was reinstated and their platform recovered. No data was lost; in-flight tasks resumed when workers came back online. Apologies to everyone affected. — SubHero team May 19, 22:24:12 GMT+0 - Investigating - API is down at the moment. This incident was automatically created by Instatus monitoring. Type: Incident

Affected Components:

<p><small>May <var data-var='date'> 20</var>, <var data-var='time'>01:44:17</var> GMT+0</small><br><strong>Resolved</strong> - API is back up. This incident was automatically resolved by Instatus monitoring..</p> <p><small>May <var data-var='date'> 20</var>, <var data-var='time'>02:49:18</var> GMT+0</small><br><strong>Postmortem</strong> - **Summary** Between May 20, 2026 06:24 UTC and 09:44 UTC (3h 20m), SubHero's API and background workers were unavailable. Translation, transcription, and any feature that talks to our backend returned errors. The Cloudflare-hosted marketing site, in-browser subtitle editor tools, and Supabase auth were unaffected. **Root cause** Our backend (FastAPI + Celery workers) is hosted on Railway, which runs on Google Cloud Platform. During this window, GCP suspended Railway's account, taking Railway's entire infrastructure offline. Every service hosted on Railway — ours included — went down with it. This was an upstream provider issue outside our control. **Resolution** Service was restored automatically once Railway's account was reinstated and their platform recovered. No data was lost; in-flight tasks resumed when workers came back online. Apologies to everyone affected. — SubHero team.</p> <p><small>May <var data-var='date'> 19</var>, <var data-var='time'>22:24:12</var> GMT+0</small><br><strong>Investigating</strong> - API is down at the moment. This incident was automatically created by Instatus monitoring..</p> ]]> Tue, 19 May 2026 22:24:12 +0000 https://subhero.instatus.com/incident/cmpd79zmy00lto315uytvexu5 https://subhero.instatus.com/incident/cmpd79zmy00lto315uytvexu5 Auth Service Update Type: Incident Duration: 2 days, 19 hours and 39 minutes May 15, 18:47:47 GMT+0 - Monitoring - The update has been implemented. Service changes can be made. We will monitor the effect for the next 30 minutes to ensure stability. May 15, 19:18:54 GMT+0 - Resolved - All changes hav been applied. May 15, 18:11:15 GMT+0 - Identified - We need to implement a time-sensitive update to our Auth service. Please do not make any changes to your Auth service until we have completed this update. Type: Incident

Duration: 2 days, 19 hours and 39 minutes

<p><small>May <var data-var='date'> 15</var>, <var data-var='time'>18:47:47</var> GMT+0</small><br><strong>Monitoring</strong> - The update has been implemented. Service changes can be made. We will monitor the effect for the next 30 minutes to ensure stability..</p> <p><small>May <var data-var='date'> 15</var>, <var data-var='time'>19:18:54</var> GMT+0</small><br><strong>Resolved</strong> - All changes hav been applied..</p> <p><small>May <var data-var='date'> 15</var>, <var data-var='time'>18:11:15</var> GMT+0</small><br><strong>Identified</strong> - We need to implement a time-sensitive update to our Auth service. Please do not make any changes to your Auth service until we have completed this update..</p> ]]> Fri, 15 May 2026 18:11:15 +0000 https://subhero.instatus.com/incident/cmpdgizwd0708p9r4qu0rlkja https://subhero.instatus.com/incident/cmpdgizwd0708p9r4qu0rlkja Some projects unavailable across multiple regions Type: Incident Duration: 16 days and 53 minutes Apr 27, 12:39:59 GMT+0 - Identified - We are seeing an increase in projects unavailable in eu-west-3 following an upstream issue with EC2 instances in the region. The team is working on restoring access to these projects Apr 27, 16:22:27 GMT+0 - Identified - The team is continuing their mitigation efforts. We've fixed and restarted most of the affected projects. We're continuously looking for any others that are affected so we can be sure to get them all fixed. Apr 27, 18:34:49 GMT+0 - Monitoring - We believe all users affected by this particular issue have been resolved. The team is going to keep an eye on these error rates to ensure we catch any that didn't originally appear, or that no new issues arise. We appreciate your patience as we worked through this issue. Apr 27, 15:00:01 GMT+0 - Identified - The team is still working to bring these back online, and have a fix under way. Many users can also resolve this on their own via a project restart. This can be performed from the <a href="https://supabase.com/dashboard/project/_/settings/general">dashboard</a> for your own projects at any time. But for those who are still seeing issues after a restart, we will be pushing a fix soon. Apr 27, 13:38:29 GMT+0 - Identified - We have identified this issue across multiple regions, not just eu-west-3 as originally suspected. We are expanding the scope of efforts to bring affected projects back online. Users can also resolve this, in most cases, on their own via a project restart. This can be performed from the <a href="https://supabase.com/dashboard/project/_/settings/general">dashboard</a> for your own projects at any time. Apr 27, 13:31:39 GMT+0 - Identified - The team is continuing to work through affected projects; however, a project restart is also effective. This can be performed from the <a href="https://supabase.com/dashboard/project/_/settings/general">dashboard</a> for your own projects at any time. Apr 27, 19:04:52 GMT+0 - Resolved - This incident has been resolved. Type: Incident

Duration: 16 days and 53 minutes

<p><small>Apr <var data-var='date'> 27</var>, <var data-var='time'>12:39:59</var> GMT+0</small><br><strong>Identified</strong> - We are seeing an increase in projects unavailable in eu-west-3 following an upstream issue with EC2 instances in the region. The team is working on restoring access to these projects.</p> <p><small>Apr <var data-var='date'> 27</var>, <var data-var='time'>16:22:27</var> GMT+0</small><br><strong>Identified</strong> - The team is continuing their mitigation efforts. We've fixed and restarted most of the affected projects. We're continuously looking for any others that are affected so we can be sure to get them all fixed..</p> <p><small>Apr <var data-var='date'> 27</var>, <var data-var='time'>18:34:49</var> GMT+0</small><br><strong>Monitoring</strong> - We believe all users affected by this particular issue have been resolved. The team is going to keep an eye on these error rates to ensure we catch any that didn't originally appear, or that no new issues arise. We appreciate your patience as we worked through this issue..</p> <p><small>Apr <var data-var='date'> 27</var>, <var data-var='time'>15:00:01</var> GMT+0</small><br><strong>Identified</strong> - The team is still working to bring these back online, and have a fix under way. Many users can also resolve this on their own via a project restart. This can be performed from the <a href="https://supabase.com/dashboard/project/_/settings/general">dashboard</a> for your own projects at any time. But for those who are still seeing issues after a restart, we will be pushing a fix soon..</p> <p><small>Apr <var data-var='date'> 27</var>, <var data-var='time'>13:38:29</var> GMT+0</small><br><strong>Identified</strong> - We have identified this issue across multiple regions, not just eu-west-3 as originally suspected. We are expanding the scope of efforts to bring affected projects back online. Users can also resolve this, in most cases, on their own via a project restart. This can be performed from the <a href="https://supabase.com/dashboard/project/_/settings/general">dashboard</a> for your own projects at any time..</p> <p><small>Apr <var data-var='date'> 27</var>, <var data-var='time'>13:31:39</var> GMT+0</small><br><strong>Identified</strong> - The team is continuing to work through affected projects; however, a project restart is also effective. This can be performed from the <a href="https://supabase.com/dashboard/project/_/settings/general">dashboard</a> for your own projects at any time..</p> <p><small>Apr <var data-var='date'> 27</var>, <var data-var='time'>19:04:52</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</p> ]]> Mon, 27 Apr 2026 12:39:59 +0000 https://subhero.instatus.com/incident/cmpdgizw90706p9r49tso7wgy https://subhero.instatus.com/incident/cmpdgizw90706p9r49tso7wgy Increased errors in project creation and configuration changes in US-East-2 and AP-Northeast-1 Type: Incident Duration: 3 days, 18 hours and 43 minutes Apr 25, 04:38:18 GMT+0 - Identified - Capacity has been freed, and the regions have been re-enabled. The team is currently working on resolving any failed project starts, resizes, restarts, or other configuration changes during this event. Apr 25, 04:26:38 GMT+0 - Identified - US-East-2 and AP-Northeast-1 have been disabled for project creation and configuration change actions, and the team is currently working to free additional capacity in these regions. Apr 25, 05:47:13 GMT+0 - Resolved - This issue has now been resolved and projects have returned to normal. Apr 25, 04:16:30 GMT+0 - Identified - We are seeing new project creation, resize requests, and project restart failures due to capacity issues in us-east-1. We are disabling project creation, project resize actions, and project restarts in these regions. We have already reached out to our provider for additional capacity, and will update here as we have additional information. Apr 25, 05:14:48 GMT+0 - Monitoring - Projects have recovered and capacity has been restored. All previously affected regions have been re-enabled, and we will continue to monitor to ensure stability. Type: Incident

Duration: 3 days, 18 hours and 43 minutes

<p><small>Apr <var data-var='date'> 25</var>, <var data-var='time'>04:38:18</var> GMT+0</small><br><strong>Identified</strong> - Capacity has been freed, and the regions have been re-enabled. The team is currently working on resolving any failed project starts, resizes, restarts, or other configuration changes during this event..</p> <p><small>Apr <var data-var='date'> 25</var>, <var data-var='time'>04:26:38</var> GMT+0</small><br><strong>Identified</strong> - US-East-2 and AP-Northeast-1 have been disabled for project creation and configuration change actions, and the team is currently working to free additional capacity in these regions..</p> <p><small>Apr <var data-var='date'> 25</var>, <var data-var='time'>05:47:13</var> GMT+0</small><br><strong>Resolved</strong> - This issue has now been resolved and projects have returned to normal..</p> <p><small>Apr <var data-var='date'> 25</var>, <var data-var='time'>04:16:30</var> GMT+0</small><br><strong>Identified</strong> - We are seeing new project creation, resize requests, and project restart failures due to capacity issues in us-east-1. We are disabling project creation, project resize actions, and project restarts in these regions. We have already reached out to our provider for additional capacity, and will update here as we have additional information..</p> <p><small>Apr <var data-var='date'> 25</var>, <var data-var='time'>05:14:48</var> GMT+0</small><br><strong>Monitoring</strong> - Projects have recovered and capacity has been restored. All previously affected regions have been re-enabled, and we will continue to monitor to ensure stability..</p> ]]> Sat, 25 Apr 2026 04:16:30 +0000 https://subhero.instatus.com/incident/cmpdgih98074xp9rtgy6zfjfe https://subhero.instatus.com/incident/cmpdgih98074xp9rtgy6zfjfe Increased Errors on HTTP Endpoints Type: Incident Duration: 27 days, 20 hours and 39 minutes Apr 17, 18:34:06 GMT+0 - Identified - Our upstream provider has rolled the fix out to most regions. While we are seeing improvement, we are still seeing increased error rates in Mexico and Brazil and are continuing to work with them until this is fully resolved. Apr 17, 14:53:01 GMT+0 - Investigating - We continue to have active lines of investigation going with our upstream network provider partners, and are still working toward a resolution. This issue affects the network-level access to projects. The projects themselves and the data in them are safe and unaffected. Users are seeing two separate symptoms of these networking issues: 1. DNS Lookup failures for supabase project URLs 2. 530 responses to HTTP requests to supabase project API Endpoints Apr 17, 13:31:21 GMT+0 - Investigating - We are currently investigating reports of users experiencing login issues when using Supabase Auth. At this time, the impact appears to be limited to a subset of users, primarily in North and South America. The exact cause and scope are still being determined. Our team is actively working to identify the root of the issue and will provide updates as more information becomes available. We appreciate your patience while we investigate. Apr 17, 20:10:25 GMT+0 - Monitoring - Our upstream provider has reported their incident resolved. We will continue to monitor for any errors our customers may be experiencing for another 30 minutes. Apr 18, 00:37:57 GMT+0 - Monitoring - We've received confirmation from our networking provider that there is recovery across all regions. We are able to corroborate this with our own metrics collections. We will continue to monitor for a bit, but we believe this to be resolved at this time. We apologize for the trouble, and we appreciate your patience. Apr 17, 14:30:00 GMT+0 - Investigating - We continue to work with partners and investigate. Apr 17, 15:41:58 GMT+0 - Identified - Our upstream networking partner is continuing their investigation. We will continue to post regular updates as we have more information. Apr 18, 02:01:40 GMT+0 - Resolved - All metrics have been nominal and stable for several hours now, and our upstream provider has resolved their incident. Apr 17, 17:44:07 GMT+0 - Identified - Upstream provider mitigations are still under way, and we are seeing improvements incrementally as routing regions have the mitigations applied. We are still seeing particular impact in South America, but some users in North America may still be affected as well. We anticipate continued incremental improvements and will update as we get more information. Apr 17, 15:09:13 GMT+0 - Identified - Our upstream networking provider has discovered an issue and has declared an incident on their side. They are currently working toward resolution. We are actively working with them and will provide updates on progress as more information is available. Apr 17, 16:31:05 GMT+0 - Identified - Our upstream networking provider has identified a fix and is currently implementing a fix. We are seeing preliminary improvements to error rates for users in North America, but are still following this issue closely with our provider. Apr 17, 23:08:02 GMT+0 - Identified - We've seen a marked improvement in error rates across all regions in the last few minutes. We are still waiting on confirmation from our provider on status, but we believe things to be improved at the moment. We'll keep working on this until we have for sure reached a resolution. Apr 17, 21:31:59 GMT+0 - Identified - We recognize that some of our users, especially in parts of North and South America, are continuing to experience DNS and 5XX errors when trying to connect to their projects. We have escalated this issue with our network provider and will work with them continuously until the problems are resolved. Apr 17, 13:51:42 GMT+0 - Investigating - We are actively investigating this issue and working with relevant partner organizations. At this time, we do not believe this issue is specific to any particular network provider. A subset of users continue to be impacted in both South and North America. Apr 17, 14:16:55 GMT+0 - Investigating - We have further clarified the scope and impact of the issues currently affecting users. A subset of users across North and South America are experiencing DNS resolution failures and HTTP 530 errors. These symptoms indicate a networking-related issue impacting the availability of Supabase projects. We are actively working with both internal teams and external network providers to isolate the root cause and determine the most effective path to resolution. We will continue to provide updates as more information becomes available. Apr 17, 19:33:24 GMT+0 - Identified - The fix that our upstream provider implemented has taken effect. Service has significantly improved across all previously impacted regions. There are still residual elevated error rates in a handful of regions and we will continue to work with our provider to eliminate them. Apr 17, 20:35:10 GMT+0 - Identified - Some users continue to experience errors. We are raising the issue with our provider. Apr 17, 13:02:16 GMT+0 - Investigating - We are currently investigating reports of users experiencing login issues when using Supabase Auth. At this time, the impact appears to be limited to a subset of users, primarily in South America. The exact cause and scope are still being determined. Our team is actively working to identify the root of the issue and will provide updates as more information becomes available. We appreciate your patience while we investigate. Type: Incident

Duration: 27 days, 20 hours and 39 minutes

<p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>18:34:06</var> GMT+0</small><br><strong>Identified</strong> - Our upstream provider has rolled the fix out to most regions. While we are seeing improvement, we are still seeing increased error rates in Mexico and Brazil and are continuing to work with them until this is fully resolved..</p> <p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>14:53:01</var> GMT+0</small><br><strong>Investigating</strong> - We continue to have active lines of investigation going with our upstream network provider partners, and are still working toward a resolution. This issue affects the network-level access to projects. The projects themselves and the data in them are safe and unaffected. Users are seeing two separate symptoms of these networking issues: 1. DNS Lookup failures for supabase project URLs 2. 530 responses to HTTP requests to supabase project API Endpoints.</p> <p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>13:31:21</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating reports of users experiencing login issues when using Supabase Auth. At this time, the impact appears to be limited to a subset of users, primarily in North and South America. The exact cause and scope are still being determined. Our team is actively working to identify the root of the issue and will provide updates as more information becomes available. We appreciate your patience while we investigate..</p> <p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>20:10:25</var> GMT+0</small><br><strong>Monitoring</strong> - Our upstream provider has reported their incident resolved. We will continue to monitor for any errors our customers may be experiencing for another 30 minutes..</p> <p><small>Apr <var data-var='date'> 18</var>, <var data-var='time'>00:37:57</var> GMT+0</small><br><strong>Monitoring</strong> - We've received confirmation from our networking provider that there is recovery across all regions. We are able to corroborate this with our own metrics collections. We will continue to monitor for a bit, but we believe this to be resolved at this time. We apologize for the trouble, and we appreciate your patience..</p> <p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>14:30:00</var> GMT+0</small><br><strong>Investigating</strong> - We continue to work with partners and investigate..</p> <p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>15:41:58</var> GMT+0</small><br><strong>Identified</strong> - Our upstream networking partner is continuing their investigation. We will continue to post regular updates as we have more information..</p> <p><small>Apr <var data-var='date'> 18</var>, <var data-var='time'>02:01:40</var> GMT+0</small><br><strong>Resolved</strong> - All metrics have been nominal and stable for several hours now, and our upstream provider has resolved their incident..</p> <p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>17:44:07</var> GMT+0</small><br><strong>Identified</strong> - Upstream provider mitigations are still under way, and we are seeing improvements incrementally as routing regions have the mitigations applied. We are still seeing particular impact in South America, but some users in North America may still be affected as well. We anticipate continued incremental improvements and will update as we get more information..</p> <p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>15:09:13</var> GMT+0</small><br><strong>Identified</strong> - Our upstream networking provider has discovered an issue and has declared an incident on their side. They are currently working toward resolution. We are actively working with them and will provide updates on progress as more information is available..</p> <p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>16:31:05</var> GMT+0</small><br><strong>Identified</strong> - Our upstream networking provider has identified a fix and is currently implementing a fix. We are seeing preliminary improvements to error rates for users in North America, but are still following this issue closely with our provider..</p> <p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>23:08:02</var> GMT+0</small><br><strong>Identified</strong> - We've seen a marked improvement in error rates across all regions in the last few minutes. We are still waiting on confirmation from our provider on status, but we believe things to be improved at the moment. We'll keep working on this until we have for sure reached a resolution..</p> <p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>21:31:59</var> GMT+0</small><br><strong>Identified</strong> - We recognize that some of our users, especially in parts of North and South America, are continuing to experience DNS and 5XX errors when trying to connect to their projects. We have escalated this issue with our network provider and will work with them continuously until the problems are resolved..</p> <p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>13:51:42</var> GMT+0</small><br><strong>Investigating</strong> - We are actively investigating this issue and working with relevant partner organizations. At this time, we do not believe this issue is specific to any particular network provider. A subset of users continue to be impacted in both South and North America..</p> <p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>14:16:55</var> GMT+0</small><br><strong>Investigating</strong> - We have further clarified the scope and impact of the issues currently affecting users. A subset of users across North and South America are experiencing DNS resolution failures and HTTP 530 errors. These symptoms indicate a networking-related issue impacting the availability of Supabase projects. We are actively working with both internal teams and external network providers to isolate the root cause and determine the most effective path to resolution. We will continue to provide updates as more information becomes available..</p> <p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>19:33:24</var> GMT+0</small><br><strong>Identified</strong> - The fix that our upstream provider implemented has taken effect. Service has significantly improved across all previously impacted regions. There are still residual elevated error rates in a handful of regions and we will continue to work with our provider to eliminate them..</p> <p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>20:35:10</var> GMT+0</small><br><strong>Identified</strong> - Some users continue to experience errors. We are raising the issue with our provider..</p> <p><small>Apr <var data-var='date'> 17</var>, <var data-var='time'>13:02:16</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating reports of users experiencing login issues when using Supabase Auth. At this time, the impact appears to be limited to a subset of users, primarily in South America. The exact cause and scope are still being determined. Our team is actively working to identify the root of the issue and will provide updates as more information becomes available. We appreciate your patience while we investigate..</p> ]]> Fri, 17 Apr 2026 14:53:01 +0000 https://subhero.instatus.com/incident/cmpdgizw90704p9r4jgp7x7ii https://subhero.instatus.com/incident/cmpdgizw90704p9r4jgp7x7ii Users Experiencing Network Connectivity Problems (India Region) Type: Incident Duration: 10 days, 15 hours and 54 minutes Feb 24, 15:42:07 GMT+0 - 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. Feb 25, 18:27:04 GMT+0 - Identified - 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. Feb 24, 15:13:10 GMT+0 - 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. Feb 24, 16:00:51 GMT+0 - 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. Feb 26, 14:56:50 GMT+0 - Identified - 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. Feb 24, 14:46:17 GMT+0 - 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. Feb 24, 16:39:08 GMT+0 - 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. Feb 27, 17:39:49 GMT+0 - Identified - 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. Feb 24, 16:08:33 GMT+0 - 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/ Feb 26, 23:36:54 GMT+0 - Identified - 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. Mar 2, 14:22:13 GMT+0 - Identified - 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. Feb 28, 16:02:03 GMT+0 - Identified - 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. Mar 3, 19:12:47 GMT+0 - 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. Mar 3, 14:42:06 GMT+0 - Identified - 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. Mar 4, 21:02:11 GMT+0 - 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. Mar 31, 22:05:18 GMT+0 - Resolved - Read more about incident and similar incidents in our new blog post about [Navigating Regional Network Blocks](https://supabase.com/blog/navigating-regional-network-blocks). Type: Incident

Duration: 10 days, 15 hours and 54 minutes

<p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>15:42:07</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Feb <var data-var='date'> 25</var>, <var data-var='time'>18:27:04</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>15:13:10</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>16:00:51</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>14:56:50</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>14:46:17</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>16:39:08</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Feb <var data-var='date'> 27</var>, <var data-var='time'>17:39:49</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Feb <var data-var='date'> 24</var>, <var data-var='time'>16:08:33</var> GMT+0</small><br><strong>Identified</strong> - 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/.</p> <p><small>Feb <var data-var='date'> 26</var>, <var data-var='time'>23:36:54</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Mar <var data-var='date'> 2</var>, <var data-var='time'>14:22:13</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Feb <var data-var='date'> 28</var>, <var data-var='time'>16:02:03</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>19:12:47</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>14:42:06</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Mar <var data-var='date'> 4</var>, <var data-var='time'>21:02:11</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> <p><small>Mar <var data-var='date'> 31</var>, <var data-var='time'>22:05:18</var> GMT+0</small><br><strong>Resolved</strong> - Read more about incident and similar incidents in our new blog post about [Navigating Regional Network Blocks](https://supabase.com/blog/navigating-regional-network-blocks)..</p> ]]> Tue, 24 Feb 2026 14:46:17 +0000 https://subhero.instatus.com/incident/cmpdgizwj070ap9r4ud2dn78x https://subhero.instatus.com/incident/cmpdgizwj070ap9r4ud2dn78x