WundertreOS Status - Incident history https://wundertreos.instatus.com WundertreOS Thu, 25 Jun 2026 03:00:00 +0000 United States and Canada Twilio SMS and MMS Maintenance Type: Maintenance Affected Components: SMS May 1, 07:52:57 GMT+0 - Scheduled - Twilio is conducting a planned maintenance from 24 June 2026 at 20:00 PDT until 25 June 2026 at 00:00 PDT. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS to and from United States and Canada handsets when sending via subset of long codes, short codes and toll free numbers. Type: Maintenance

Affected Components:

<p><small>May <var data-var='date'> 1</var>, <var data-var='time'>07:52:57</var> GMT+0</small><br><strong>Scheduled</strong> - Twilio is conducting a planned maintenance from 24 June 2026 at 20:00 PDT until 25 June 2026 at 00:00 PDT. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS to and from United States and Canada handsets when sending via subset of long codes, short codes and toll free numbers..</p> ]]> Thu, 25 Jun 2026 03:00:00 +0000 https://wundertreos.instatus.com/maintenance/cmp93wxzo005xqnmjanj1hqaw https://wundertreos.instatus.com/maintenance/cmp93wxzo005xqnmjanj1hqaw United States and Canada Twilio SMS and MMS Maintenance Type: Maintenance Affected Components: SMS May 1, 07:52:33 GMT+0 - Scheduled - Twilio is conducting a planned maintenance from 17 June 2026 at 20:00 PDT until 18 June 2026 at 00:00 PDT. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS to and from United States and Canada handsets when sending via subset of long codes, short codes and toll free numbers. Type: Maintenance

Affected Components:

<p><small>May <var data-var='date'> 1</var>, <var data-var='time'>07:52:33</var> GMT+0</small><br><strong>Scheduled</strong> - Twilio is conducting a planned maintenance from 17 June 2026 at 20:00 PDT until 18 June 2026 at 00:00 PDT. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS to and from United States and Canada handsets when sending via subset of long codes, short codes and toll free numbers..</p> ]]> Thu, 18 Jun 2026 03:00:00 +0000 https://wundertreos.instatus.com/maintenance/cmp93wy00006dqnmjzpm4w35s https://wundertreos.instatus.com/maintenance/cmp93wy00006dqnmjzpm4w35s United States and Canada Twilio SMS and MMS Maintenance Type: Maintenance Affected Components: SMS May 1, 07:52:09 GMT+0 - Scheduled - Twilio is conducting a planned maintenance from 10 June 2026 at 20:00 PDT until 11 June 2026 at 00:00 PDT. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS to and from United States and Canada handsets when sending via subset of long codes, short codes and toll free numbers. Type: Maintenance

Affected Components:

<p><small>May <var data-var='date'> 1</var>, <var data-var='time'>07:52:09</var> GMT+0</small><br><strong>Scheduled</strong> - Twilio is conducting a planned maintenance from 10 June 2026 at 20:00 PDT until 11 June 2026 at 00:00 PDT. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS to and from United States and Canada handsets when sending via subset of long codes, short codes and toll free numbers..</p> ]]> Thu, 11 Jun 2026 03:00:00 +0000 https://wundertreos.instatus.com/maintenance/cmp93wxzr0065qnmjtawuxuvi https://wundertreos.instatus.com/maintenance/cmp93wxzr0065qnmjtawuxuvi United States and Canada Twilio SMS and MMS Maintenance Type: Maintenance Affected Components: SMS May 1, 07:51:36 GMT+0 - Scheduled - Twilio is conducting a planned maintenance from 03 June 2026 at 20:00 PDT until 04 June 2026 at 00:00 PDT. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS to and from United States and Canada handsets when sending via subset of long codes, short codes and toll free numbers. Type: Maintenance

Affected Components:

<p><small>May <var data-var='date'> 1</var>, <var data-var='time'>07:51:36</var> GMT+0</small><br><strong>Scheduled</strong> - Twilio is conducting a planned maintenance from 03 June 2026 at 20:00 PDT until 04 June 2026 at 00:00 PDT. During the maintenance window, there could be intermittent delays or failures delivering SMS and MMS to and from United States and Canada handsets when sending via subset of long codes, short codes and toll free numbers..</p> ]]> Thu, 4 Jun 2026 03:00:00 +0000 https://wundertreos.instatus.com/maintenance/cmp93wxzm005tqnmjqaa76dor https://wundertreos.instatus.com/maintenance/cmp93wxzm005tqnmjqaa76dor United States and Canada Twilio SMS Maintenance Type: Maintenance Affected Components: SMS Apr 14, 07:13:20 GMT+0 - Scheduled - Twilio is conducting a planned maintenance from 27 May 2026 at 20:00 PDT until 28 May 2026 at 00:00 PDT. During the maintenance window, there could be intermittent delays or failures delivering SMS to and from United States and Canada handsets via subset of long codes, short codes and toll free numbers. Type: Maintenance

Affected Components:

<p><small>Apr <var data-var='date'> 14</var>, <var data-var='time'>07:13:20</var> GMT+0</small><br><strong>Scheduled</strong> - Twilio is conducting a planned maintenance from 27 May 2026 at 20:00 PDT until 28 May 2026 at 00:00 PDT. During the maintenance window, there could be intermittent delays or failures delivering SMS to and from United States and Canada handsets via subset of long codes, short codes and toll free numbers..</p> ]]> Thu, 28 May 2026 03:00:00 +0000 https://wundertreos.instatus.com/maintenance/cmp93wxzq0061qnmjcrah2cro https://wundertreos.instatus.com/maintenance/cmp93wxzq0061qnmjcrah2cro United States and Canada Twilio SMS Maintenance Type: Maintenance Affected Components: SMS Apr 14, 07:13:01 GMT+0 - Scheduled - Twilio is conducting a planned maintenance from 20 May 2026 at 20:00 PDT until 21 May 2026 at 00:00 PDT. During the maintenance window, there could be intermittent delays or failures delivering SMS to and from United States and Canada handsets via subset of long codes, short codes and toll free numbers. Type: Maintenance

Affected Components:

<p><small>Apr <var data-var='date'> 14</var>, <var data-var='time'>07:13:01</var> GMT+0</small><br><strong>Scheduled</strong> - Twilio is conducting a planned maintenance from 20 May 2026 at 20:00 PDT until 21 May 2026 at 00:00 PDT. During the maintenance window, there could be intermittent delays or failures delivering SMS to and from United States and Canada handsets via subset of long codes, short codes and toll free numbers..</p> ]]> Thu, 21 May 2026 03:00:00 +0000 https://wundertreos.instatus.com/maintenance/cmp93wxzm005rqnmjf2z4h9tr https://wundertreos.instatus.com/maintenance/cmp93wxzm005rqnmjf2z4h9tr US SMS Carrier Maintenance - Small US Carriers Type: Maintenance Affected Components: SMS May 8, 23:07:18 GMT+0 - Scheduled - A subset of small networks in the US are conducting a planned maintenance from 19 May 2026 at 02:00 PDT until 19 May 2026 at 04:00 PDT. During the maintenance window, there could be intermittent delays delivering SMS to small US carriers handsets. Type: Maintenance

Affected Components:

<p><small>May <var data-var='date'> 8</var>, <var data-var='time'>23:07:18</var> GMT+0</small><br><strong>Scheduled</strong> - A subset of small networks in the US are conducting a planned maintenance from 19 May 2026 at 02:00 PDT until 19 May 2026 at 04:00 PDT. During the maintenance window, there could be intermittent delays delivering SMS to small US carriers handsets..</p> ]]> Tue, 19 May 2026 09:00:00 +0000 https://wundertreos.instatus.com/maintenance/cmp93wy00006bqnmj93eubf2u https://wundertreos.instatus.com/maintenance/cmp93wy00006bqnmj93eubf2u United States SMS and MMS Carrier Maintenance - T-Mobile Type: Maintenance Affected Components: SMS May 15, 20:10:14 GMT+0 - Scheduled - The T-Mobile network in the United States is conducting a planned maintenance from 18 May 2026 at 20:00 PDT until 19 May 2026 at 04:00 PDT. During the maintenance window, there could be intermittent delays delivering SMS and MMS to and from T-Mobile United States handsets when sending via long codes and short codes. Type: Maintenance

Affected Components:

<p><small>May <var data-var='date'> 15</var>, <var data-var='time'>20:10:14</var> GMT+0</small><br><strong>Scheduled</strong> - The T-Mobile network in the United States is conducting a planned maintenance from 18 May 2026 at 20:00 PDT until 19 May 2026 at 04:00 PDT. During the maintenance window, there could be intermittent delays delivering SMS and MMS to and from T-Mobile United States handsets when sending via long codes and short codes..</p> ]]> Tue, 19 May 2026 03:00:00 +0000 https://wundertreos.instatus.com/maintenance/cmp93wxzp005zqnmj4a3dv9ri https://wundertreos.instatus.com/maintenance/cmp93wxzp005zqnmj4a3dv9ri United States SMS and MMS Carrier Maintenance - T-Mobile Type: Maintenance Affected Components: SMS May 14, 20:52:23 GMT+0 - Scheduled - The T-Mobile network in the United States is conducting a planned maintenance from 17 May 2026 at 20:00 PDT until 18 May 2026 at 04:00 PDT. During the maintenance window, there could be intermittent delays delivering SMS and MMS to and from T-Mobile United States handsets when sending via subset of long codes and short codes. Type: Maintenance

Affected Components:

<p><small>May <var data-var='date'> 14</var>, <var data-var='time'>20:52:23</var> GMT+0</small><br><strong>Scheduled</strong> - The T-Mobile network in the United States is conducting a planned maintenance from 17 May 2026 at 20:00 PDT until 18 May 2026 at 04:00 PDT. During the maintenance window, there could be intermittent delays delivering SMS and MMS to and from T-Mobile United States handsets when sending via subset of long codes and short codes..</p> ]]> Mon, 18 May 2026 03:00:00 +0000 https://wundertreos.instatus.com/maintenance/cmp93wxzq0063qnmjp9oecnff https://wundertreos.instatus.com/maintenance/cmp93wxzq0063qnmjp9oecnff Problem loading website Type: Incident Affected Components: WundertreOS Web App May 17, 01:18:51 GMT+0 - Investigating - We are continuing to work on a fix for this incident. May 17, 01:18:58 GMT+0 - Resolved - We managed to resolve the incident Type: Incident

Affected Components:

<p><small>May <var data-var='date'> 17</var>, <var data-var='time'>01:18:51</var> GMT+0</small><br><strong>Investigating</strong> - We are continuing to work on a fix for this incident..</p> <p><small>May <var data-var='date'> 17</var>, <var data-var='time'>01:18:58</var> GMT+0</small><br><strong>Resolved</strong> - We managed to resolve the incident.</p> ]]> Sun, 17 May 2026 01:18:51 +0000 https://wundertreos.instatus.com/incident/cmp9371i60insnpwj6fyq11g3 https://wundertreos.instatus.com/incident/cmp9371i60insnpwj6fyq11g3 Auth Service Update Type: Incident Duration: 2 days, 19 hours and 39 minutes Affected Components: Auth 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. 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. Type: Incident

Duration: 2 days, 19 hours and 39 minutes

Affected Components:

<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> <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> ]]> Fri, 15 May 2026 18:11:15 +0000 https://wundertreos.instatus.com/incident/cmp93s20f0ds3pfx4xx0ip5w4 https://wundertreos.instatus.com/incident/cmp93s20f0ds3pfx4xx0ip5w4 United States SMS Carrier Partner Maintenance Type: Maintenance Duration: 7 hours Affected Components: SMS May 15, 06:00:07 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. May 15, 05:00:08 GMT+0 - Scheduled - Maintenance will begin as scheduled in 60 minutes. May 15, 13:00:13 GMT+0 - Completed - The scheduled maintenance has been completed. May 13, 07:44:00 GMT+0 - Scheduled - Our SMS carrier partner in the United States is conducting a planned maintenance from 14 May 2026 at 23:00 PDT until 15 May 2026 at 06:00 PDT. During the maintenance window, there could be intermittent delays delivering SMS to and from United States handsets via United States long codes. Type: Maintenance

Duration: 7 hours

Affected Components:

<p><small>May <var data-var='date'> 15</var>, <var data-var='time'>06:00:07</var> GMT+0</small><br><strong>Identified</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary..</p> <p><small>May <var data-var='date'> 15</var>, <var data-var='time'>05:00:08</var> GMT+0</small><br><strong>Scheduled</strong> - Maintenance will begin as scheduled in 60 minutes..</p> <p><small>May <var data-var='date'> 15</var>, <var data-var='time'>13:00:13</var> GMT+0</small><br><strong>Completed</strong> - The scheduled maintenance has been completed..</p> <p><small>May <var data-var='date'> 13</var>, <var data-var='time'>07:44:00</var> GMT+0</small><br><strong>Scheduled</strong> - Our SMS carrier partner in the United States is conducting a planned maintenance from 14 May 2026 at 23:00 PDT until 15 May 2026 at 06:00 PDT. During the maintenance window, there could be intermittent delays delivering SMS to and from United States handsets via United States long codes..</p> ]]> Fri, 15 May 2026 06:00:00 +0000 https://wundertreos.instatus.com/maintenance/cmp93wxzo005vqnmju39bff62 https://wundertreos.instatus.com/maintenance/cmp93wxzo005vqnmju39bff62 Edge Traffic Issues Type: Incident Duration: 10 days, 19 hours and 39 minutes Affected Components: Functions May 13, 19:50:50 GMT+0 - Identified - Our investigation has identified traffic loss along a specific network path associated with a VPN exit point located in Western Europe. Some customers are experiencing connectivity issues that impact a subset of users connecting through certain VPN providers, including Mullvad. Customers impacted while using Mullvad can contact Mullvad support directly to help raise visibility into the issue from their side. May 13, 20:35:31 GMT+0 - Resolved - We've determined that the connectivity issues are isolated to users accessing Supabase through Mullvad VPN and potentially other VPN providers. The root cause appears to be network disruptions involving a specific colocation/transit provider used by Mullvad, rather than an issue with Supabase or Cloudflare infrastructure. We've reached out to Mullvad support, but as this is dependent on external providers, there are no further mitigation steps we can take internally. Users experiencing issues are advised to avoid affected VPN networks or contact their VPN provider directly for support. The incident is now resolved May 13, 16:46:49 GMT+0 - Investigating - We are continuing to investigate connectivity issues impacting access to Supabase APIs, which may result in connection timeout errors or rejected connections for some users. At this time, we have narrowed the issue down to traffic originating from at least one VPN provider (Mullvad VPN). However, we cannot yet confirm whether additional VPN providers may also be impacted. We are actively working to identify the root cause and will continue to provide updates as we learn more. May 13, 17:31:45 GMT+0 - Investigating - We are continuing to actively investigate the connectivity issues impacting access to Supabase APIs for some users. Our team remains engaged in identifying the underlying cause and validating the scope of impact. We will continue to provide updates as our investigation progresses. May 13, 16:15:51 GMT+0 - Investigating - We've observed traffic from upstream providers of a VPN provider is no longer reaching our servers. We're investigating the cause and will keep you updated. Type: Incident

Duration: 10 days, 19 hours and 39 minutes

Affected Components:

<p><small>May <var data-var='date'> 13</var>, <var data-var='time'>19:50:50</var> GMT+0</small><br><strong>Identified</strong> - Our investigation has identified traffic loss along a specific network path associated with a VPN exit point located in Western Europe. Some customers are experiencing connectivity issues that impact a subset of users connecting through certain VPN providers, including Mullvad. Customers impacted while using Mullvad can contact Mullvad support directly to help raise visibility into the issue from their side..</p> <p><small>May <var data-var='date'> 13</var>, <var data-var='time'>20:35:31</var> GMT+0</small><br><strong>Resolved</strong> - We've determined that the connectivity issues are isolated to users accessing Supabase through Mullvad VPN and potentially other VPN providers. The root cause appears to be network disruptions involving a specific colocation/transit provider used by Mullvad, rather than an issue with Supabase or Cloudflare infrastructure. We've reached out to Mullvad support, but as this is dependent on external providers, there are no further mitigation steps we can take internally. Users experiencing issues are advised to avoid affected VPN networks or contact their VPN provider directly for support. The incident is now resolved.</p> <p><small>May <var data-var='date'> 13</var>, <var data-var='time'>16:46:49</var> GMT+0</small><br><strong>Investigating</strong> - We are continuing to investigate connectivity issues impacting access to Supabase APIs, which may result in connection timeout errors or rejected connections for some users. At this time, we have narrowed the issue down to traffic originating from at least one VPN provider (Mullvad VPN). However, we cannot yet confirm whether additional VPN providers may also be impacted. We are actively working to identify the root cause and will continue to provide updates as we learn more..</p> <p><small>May <var data-var='date'> 13</var>, <var data-var='time'>17:31:45</var> GMT+0</small><br><strong>Investigating</strong> - We are continuing to actively investigate the connectivity issues impacting access to Supabase APIs for some users. Our team remains engaged in identifying the underlying cause and validating the scope of impact. We will continue to provide updates as our investigation progresses..</p> <p><small>May <var data-var='date'> 13</var>, <var data-var='time'>16:15:51</var> GMT+0</small><br><strong>Investigating</strong> - We've observed traffic from upstream providers of a VPN provider is no longer reaching our servers. We're investigating the cause and will keep you updated..</p> ]]> Wed, 13 May 2026 16:15:51 +0000 https://wundertreos.instatus.com/incident/cmp93lnex0dukqvp6335bx7bb https://wundertreos.instatus.com/incident/cmp93lnex0dukqvp6335bx7bb SMS Delivery Delays from Twilio to Panhandle Telecommunication Systems Inc. United States Type: Incident Duration: 8 days, 4 hours and 39 minutes Affected Components: SMS May 11, 14:08:49 GMT+0 - Monitoring - We have observed a recovery in SMS delivery from Twilio to Panhandle Telecommunication Systems Inc. network subscribers in the United States and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available. May 11, 16:28:46 GMT+0 - Resolved - The incident has been resolved and SMS delivery from Twilio to Panhandle Telecommunication Systems Inc. network subscribers in the United States is operating normally. May 11, 16:10:16 GMT+0 - Monitoring - We have observed a recovery in SMS delivery from Twilio to Panhandle Telecommunication Systems Inc. network subscribers in the United States and are monitoring service stability. We will provide another update in 4 hours or as soon as more information becomes available. May 11, 13:12:07 GMT+0 - Investigating - Twilio customers may be experiencing SMS delivery delays from Twilio to Panhandle Telecommunication Systems Inc. network subscribers in the United States. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available. Type: Incident

Duration: 8 days, 4 hours and 39 minutes

Affected Components:

<p><small>May <var data-var='date'> 11</var>, <var data-var='time'>14:08:49</var> GMT+0</small><br><strong>Monitoring</strong> - We have observed a recovery in SMS delivery from Twilio to Panhandle Telecommunication Systems Inc. network subscribers in the United States and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available..</p> <p><small>May <var data-var='date'> 11</var>, <var data-var='time'>16:28:46</var> GMT+0</small><br><strong>Resolved</strong> - The incident has been resolved and SMS delivery from Twilio to Panhandle Telecommunication Systems Inc. network subscribers in the United States is operating normally..</p> <p><small>May <var data-var='date'> 11</var>, <var data-var='time'>16:10:16</var> GMT+0</small><br><strong>Monitoring</strong> - We have observed a recovery in SMS delivery from Twilio to Panhandle Telecommunication Systems Inc. network subscribers in the United States and are monitoring service stability. We will provide another update in 4 hours or as soon as more information becomes available..</p> <p><small>May <var data-var='date'> 11</var>, <var data-var='time'>13:12:07</var> GMT+0</small><br><strong>Investigating</strong> - Twilio customers may be experiencing SMS delivery delays from Twilio to Panhandle Telecommunication Systems Inc. network subscribers in the United States. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available..</p> ]]> Mon, 11 May 2026 13:12:07 +0000 https://wundertreos.instatus.com/incident/cmp93wxzt0069qnmj74oas50i https://wundertreos.instatus.com/incident/cmp93wxzt0069qnmj74oas50i SMS Delivery Delays from a Subset of Twilio Long Codes and Toll-Free Numbers to AT&T United States Type: Incident Duration: 29 days, 23 hours and 30 minutes Affected Components: SMS May 11, 17:22:44 GMT+0 - Identified - Twilio customers may be experiencing SMS delivery report delays from a subset of Twilio Long Codes and Toll-Free Numbers to AT&T network subscribers in the United States. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available. May 11, 22:53:35 GMT+0 - Monitoring - We have observed a recovery in SMS delivery from a subset of Twilio Long Codes and Toll-Free Numbers to AT&T network subscribers in the United States and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available. May 11, 14:14:15 GMT+0 - Investigating - Twilio customers may be experiencing SMS delivery delays from Twilio Long Codes to AT&T network subscribers in the United States. Our team is actively investigating this issue. We will provide another update in 2 hours or as soon as more information becomes available. May 12, 01:04:53 GMT+0 - Resolved - The incident has been resolved and SMS delivery from a subset of Twilio Long Codes and Toll-Free Numbers to AT&T network subscribers in the United States is operating normally. May 11, 13:05:22 GMT+0 - Investigating - Twilio customers may be experiencing SMS delivery delays from Twilio Long Codes to AT&T network subscribers in the United States. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available. May 11, 16:16:44 GMT+0 - Investigating - Twilio customers may be experiencing SMS delivery report delays from Twilio Long Codes to AT&T network subscribers in the United States. Our team is actively investigating this issue. We will provide another update in 4 hours or as soon as more information becomes available. May 11, 19:23:42 GMT+0 - Identified - Twilio customers may be experiencing SMS delivery report delays from a subset of Twilio Long Codes and Toll-Free Numbers to AT&T network subscribers in the United States. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 4 hours or as soon as more information becomes available. May 11, 15:22:04 GMT+0 - Investigating - We are continuing to investigate this issue. May 11, 16:21:33 GMT+0 - Identified - Twilio customers may be experiencing SMS delivery report delays from a subset of Twilio Long Codes and Toll-Free Numbers to AT&T network subscribers in the United States. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available. Type: Incident

Duration: 29 days, 23 hours and 30 minutes

Affected Components:

<p><small>May <var data-var='date'> 11</var>, <var data-var='time'>17:22:44</var> GMT+0</small><br><strong>Identified</strong> - Twilio customers may be experiencing SMS delivery report delays from a subset of Twilio Long Codes and Toll-Free Numbers to AT&T network subscribers in the United States. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 2 hours or as soon as more information becomes available..</p> <p><small>May <var data-var='date'> 11</var>, <var data-var='time'>22:53:35</var> GMT+0</small><br><strong>Monitoring</strong> - We have observed a recovery in SMS delivery from a subset of Twilio Long Codes and Toll-Free Numbers to AT&T network subscribers in the United States and are monitoring service stability. We will provide another update in 2 hours or as soon as more information becomes available..</p> <p><small>May <var data-var='date'> 11</var>, <var data-var='time'>14:14:15</var> GMT+0</small><br><strong>Investigating</strong> - Twilio customers may be experiencing SMS delivery delays from Twilio Long Codes to AT&T network subscribers in the United States. Our team is actively investigating this issue. We will provide another update in 2 hours or as soon as more information becomes available..</p> <p><small>May <var data-var='date'> 12</var>, <var data-var='time'>01:04:53</var> GMT+0</small><br><strong>Resolved</strong> - The incident has been resolved and SMS delivery from a subset of Twilio Long Codes and Toll-Free Numbers to AT&T network subscribers in the United States is operating normally..</p> <p><small>May <var data-var='date'> 11</var>, <var data-var='time'>13:05:22</var> GMT+0</small><br><strong>Investigating</strong> - Twilio customers may be experiencing SMS delivery delays from Twilio Long Codes to AT&T network subscribers in the United States. Our team is actively investigating this issue. We will provide another update in 1 hour or as soon as more information becomes available..</p> <p><small>May <var data-var='date'> 11</var>, <var data-var='time'>16:16:44</var> GMT+0</small><br><strong>Investigating</strong> - Twilio customers may be experiencing SMS delivery report delays from Twilio Long Codes to AT&T network subscribers in the United States. Our team is actively investigating this issue. We will provide another update in 4 hours or as soon as more information becomes available..</p> <p><small>May <var data-var='date'> 11</var>, <var data-var='time'>19:23:42</var> GMT+0</small><br><strong>Identified</strong> - Twilio customers may be experiencing SMS delivery report delays from a subset of Twilio Long Codes and Toll-Free Numbers to AT&T network subscribers in the United States. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 4 hours or as soon as more information becomes available..</p> <p><small>May <var data-var='date'> 11</var>, <var data-var='time'>15:22:04</var> GMT+0</small><br><strong>Investigating</strong> - We are continuing to investigate this issue..</p> <p><small>May <var data-var='date'> 11</var>, <var data-var='time'>16:21:33</var> GMT+0</small><br><strong>Identified</strong> - Twilio customers may be experiencing SMS delivery report delays from a subset of Twilio Long Codes and Toll-Free Numbers to AT&T network subscribers in the United States. Our team has identified the cause, and is working to resolve the issue. We will provide another update in 1 hour or as soon as more information becomes available..</p> ]]> Mon, 11 May 2026 13:05:22 +0000 https://wundertreos.instatus.com/incident/cmp93wxzt0067qnmjns5dt3xd https://wundertreos.instatus.com/incident/cmp93wxzt0067qnmjns5dt3xd Edge Functions scheduled maintenance in eu-central-1 and us-east-1 Type: Maintenance Duration: 1 hour Affected Components: Functions May 4, 05:00:08 GMT+0 - Completed - The scheduled maintenance has been completed. May 4, 03:00:07 GMT+0 - Scheduled - Maintenance will begin as scheduled in 60 minutes. May 4, 04:00:07 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. May 1, 17:18:29 GMT+0 - Scheduled - Upstream provider regular scheduled maintenance on instances in us-east-1 and eu-central-1. We do not expect downtime or impact to Edge Functions invocations or deploys during this window. We will monitor and update its progress. Type: Maintenance

Duration: 1 hour

Affected Components:

<p><small>May <var data-var='date'> 4</var>, <var data-var='time'>05:00:08</var> GMT+0</small><br><strong>Completed</strong> - The scheduled maintenance has been completed..</p> <p><small>May <var data-var='date'> 4</var>, <var data-var='time'>03:00:07</var> GMT+0</small><br><strong>Scheduled</strong> - Maintenance will begin as scheduled in 60 minutes..</p> <p><small>May <var data-var='date'> 4</var>, <var data-var='time'>04:00:07</var> GMT+0</small><br><strong>Identified</strong> - Scheduled maintenance is currently in progress. We will provide updates as necessary..</p> <p><small>May <var data-var='date'> 1</var>, <var data-var='time'>17:18:29</var> GMT+0</small><br><strong>Scheduled</strong> - Upstream provider regular scheduled maintenance on instances in us-east-1 and eu-central-1. We do not expect downtime or impact to Edge Functions invocations or deploys during this window. We will monitor and update its progress..</p> ]]> Mon, 4 May 2026 04:00:00 +0000 https://wundertreos.instatus.com/maintenance/cmp93lnet0dugqvp6bfwxnf7x https://wundertreos.instatus.com/maintenance/cmp93lnet0dugqvp6bfwxnf7x Some projects unavailable across multiple regions Type: Incident Duration: 16 days and 53 minutes Affected Components: , Auth, WundertreOS Database → 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, 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, 19:04:52 GMT+0 - Resolved - This incident has been resolved. 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, 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, 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, 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. Type: Incident

Duration: 16 days and 53 minutes

Affected Components: ,

<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'>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'>19:04:52</var> GMT+0</small><br><strong>Resolved</strong> - This incident has been resolved..</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'>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'>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'>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> ]]> Mon, 27 Apr 2026 12:39:59 +0000 https://wundertreos.instatus.com/incident/cmp93ncc50dowpfwtbc8v1w4h https://wundertreos.instatus.com/incident/cmp93ncc50dowpfwtbc8v1w4h Increased Errors on HTTP Endpoints Type: Incident Duration: 27 days, 20 hours and 39 minutes Affected Components: Functions, , Storage Buckets, Auth, WundertreOS Database → 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, 14:30:00 GMT+0 - Investigating - We continue to work with partners and investigate. 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, 20:35:10 GMT+0 - Identified - Some users continue to experience errors. We are raising the issue with our provider. 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 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, 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, 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, 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, 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 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, 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, 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. 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, 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: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, 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. Type: Incident

Duration: 27 days, 20 hours and 39 minutes

Affected Components: , , ,

<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'>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'> 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'>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'>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'> 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'>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'>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'>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'>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'> 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'>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'>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> <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'>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: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'>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> ]]> Fri, 17 Apr 2026 14:53:01 +0000 https://wundertreos.instatus.com/incident/cmp93lnes0dudqvp6eesv7goo https://wundertreos.instatus.com/incident/cmp93lnes0dudqvp6eesv7goo EU located subusers unable to send emails Type: Incident Duration: 6 days, 19 hours and 45 minutes Affected Components: Email Apr 15, 16:00:17 GMT+0 - Investigating - Starting around 08:30 AM PST on April 15th, 2026, our engineers began investigating an issue with EU subusers that are unable to send emails. Customer may experience the error "User is not authorized to send mail based on their regional attribute." This is currently being investigated. This impacts mail send only for subusers located in EU. We will provide another update in an hour or as soon as more information becomes available. Apr 15, 17:06:53 GMT+0 - Investigating - We are continuing investigating this issue. We will provide more updates in 2 hours, or as soon as they become available. Apr 15, 18:44:03 GMT+0 - Resolved - Our engineers have monitored the fix and confirmed the issue with EU subusers unable to send emails has now been resolved. All services are now operating normally at this time. Apr 15, 18:37:32 GMT+0 - Monitoring - Our engineers have implemented a fix and are monitoring system performance. We will provide another update in an hour or as soon as more information becomes available. Type: Incident

Duration: 6 days, 19 hours and 45 minutes

Affected Components:

<p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>16:00:17</var> GMT+0</small><br><strong>Investigating</strong> - Starting around 08:30 AM PST on April 15th, 2026, our engineers began investigating an issue with EU subusers that are unable to send emails. Customer may experience the error "User is not authorized to send mail based on their regional attribute." This is currently being investigated. This impacts mail send only for subusers located in EU. We will provide another update in an hour or as soon as more information becomes available..</p> <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>17:06:53</var> GMT+0</small><br><strong>Investigating</strong> - We are continuing investigating this issue. We will provide more updates in 2 hours, or as soon as they become available..</p> <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>18:44:03</var> GMT+0</small><br><strong>Resolved</strong> - Our engineers have monitored the fix and confirmed the issue with EU subusers unable to send emails has now been resolved. All services are now operating normally at this time..</p> <p><small>Apr <var data-var='date'> 15</var>, <var data-var='time'>18:37:32</var> GMT+0</small><br><strong>Monitoring</strong> - Our engineers have implemented a fix and are monitoring system performance. We will provide another update in an hour or as soon as more information becomes available..</p> ]]> Wed, 15 Apr 2026 16:00:17 +0000 https://wundertreos.instatus.com/incident/cmp93xsrc0iv7npwjbs5gu5f3 https://wundertreos.instatus.com/incident/cmp93xsrc0iv7npwjbs5gu5f3 Elevated error rates affecting Edge Functions in the eu-central-1 (Frankfurt) region Type: Incident Duration: 3 days, 13 hours and 59 minutes Affected Components: Functions Mar 23, 14:16:44 GMT+0 - Investigating - We are currently investigating elevated error rates affecting Edge Functions in the eu-central-1 (Frankfurt) region Mar 23, 14:32:03 GMT+0 - 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. Mar 23, 15:42:44 GMT+0 - Resolved - Error rates have returned to normal. This incident has been resolved. Type: Incident

Duration: 3 days, 13 hours and 59 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>14:16:44</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating elevated error rates affecting Edge Functions in the eu-central-1 (Frankfurt) region.</p> <p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>14:32:03</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Mar <var data-var='date'> 23</var>, <var data-var='time'>15:42:44</var> GMT+0</small><br><strong>Resolved</strong> - Error rates have returned to normal. This incident has been resolved..</p> ]]> Mon, 23 Mar 2026 14:16:44 +0000 https://wundertreos.instatus.com/incident/cmp93lney0duoqvp65sl19n5k https://wundertreos.instatus.com/incident/cmp93lney0duoqvp65sl19n5k Elevated error rates affecting storage services in the ap-northeast-1 (Tokyo) region Type: Incident Duration: 4 days, 18 hours and 17 minutes Affected Components: Storage Buckets Mar 18, 16:58:23 GMT+0 - Investigating - 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. Mar 18, 17:53:31 GMT+0 - Identified - The root cause, involving task instances and batch sending events, has been identified. Our engineering team is working on a fix. Mar 18, 18:21:53 GMT+0 - Resolved - The fix was implemented. All impacted projects and newly created projects in the region are now successfully connecting to storage services. Mar 18, 17:30:07 GMT+0 - Investigating - 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. Mar 18, 16:27:35 GMT+0 - 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. Type: Incident

Duration: 4 days, 18 hours and 17 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 18</var>, <var data-var='time'>16:58:23</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Mar <var data-var='date'> 18</var>, <var data-var='time'>17:53:31</var> GMT+0</small><br><strong>Identified</strong> - The root cause, involving task instances and batch sending events, has been identified. Our engineering team is working on a fix..</p> <p><small>Mar <var data-var='date'> 18</var>, <var data-var='time'>18:21:53</var> GMT+0</small><br><strong>Resolved</strong> - The fix was implemented. All impacted projects and newly created projects in the region are now successfully connecting to storage services..</p> <p><small>Mar <var data-var='date'> 18</var>, <var data-var='time'>17:30:07</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Mar <var data-var='date'> 18</var>, <var data-var='time'>16:27:35</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> ]]> Wed, 18 Mar 2026 16:27:35 +0000 https://wundertreos.instatus.com/incident/cmp93r2pa01b9pcmh0jbsbo0o https://wundertreos.instatus.com/incident/cmp93r2pa01b9pcmh0jbsbo0o Storage errors in EU-Central-2 Type: Incident Duration: 4 days, 7 hours and 50 minutes Affected Components: Storage Buckets Mar 7, 20:22:08 GMT+0 - Identified - We have identified the cause of the storage issue in EU-Central-2. The upstream provider is working to resolve the issue. Mar 7, 21:16:37 GMT+0 - 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. Mar 7, 20:44:04 GMT+0 - Identified - We are observing storage error rates returning to normal. Mar 7, 21:56:13 GMT+0 - Resolved - All storage operations have returned to normal. Mar 7, 20:12:22 GMT+0 - Investigating - We have noticed that storage uploads and downloads have become degraded in EU-Central-2. We are investigating. Type: Incident

Duration: 4 days, 7 hours and 50 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>20:22:08</var> GMT+0</small><br><strong>Identified</strong> - We have identified the cause of the storage issue in EU-Central-2. The upstream provider is working to resolve the issue..</p> <p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>21:16:37</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>20:44:04</var> GMT+0</small><br><strong>Identified</strong> - We are observing storage error rates returning to normal..</p> <p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>21:56:13</var> GMT+0</small><br><strong>Resolved</strong> - All storage operations have returned to normal..</p> <p><small>Mar <var data-var='date'> 7</var>, <var data-var='time'>20:12:22</var> GMT+0</small><br><strong>Investigating</strong> - We have noticed that storage uploads and downloads have become degraded in EU-Central-2. We are investigating..</p> ]]> Sat, 7 Mar 2026 20:12:22 +0000 https://wundertreos.instatus.com/incident/cmp93r2ph01bbpcmh5dnbul1q https://wundertreos.instatus.com/incident/cmp93r2ph01bbpcmh5dnbul1q Edge Functions experiencing high response times in ap-northeast-1 and ap-northeast-2 Type: Incident Duration: 12 days, 21 hours and 51 minutes Affected Components: Functions Mar 6, 15:56:24 GMT+0 - 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. Mar 6, 14:47:46 GMT+0 - Investigating - 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. Mar 6, 15:46:45 GMT+0 - 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. Mar 6, 15:17:05 GMT+0 - Investigating - 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. Mar 6, 19:36:22 GMT+0 - Resolved - Both regions are now working as usual. Mar 6, 14:26:31 GMT+0 - Investigating - We are currently investigating the cause for increased response times. Type: Incident

Duration: 12 days, 21 hours and 51 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>15:56:24</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>14:47:46</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>15:46:45</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>15:17:05</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>19:36:22</var> GMT+0</small><br><strong>Resolved</strong> - Both regions are now working as usual..</p> <p><small>Mar <var data-var='date'> 6</var>, <var data-var='time'>14:26:31</var> GMT+0</small><br><strong>Investigating</strong> - We are currently investigating the cause for increased response times..</p> ]]> Fri, 6 Mar 2026 14:26:31 +0000 https://wundertreos.instatus.com/incident/cmp93lney0dumqvp6zqyfufyo https://wundertreos.instatus.com/incident/cmp93lney0dumqvp6zqyfufyo Database issues in us-east-2 Type: Incident Duration: 10 days, 20 hours and 28 minutes Affected Components: , WundertreOS Database → Mar 3, 06:31:05 GMT+0 - Resolved - Root cause has been confirmed to be addressed. Handful of projects still require manual intervention however. We will be reaching out to their respective owners. Mar 3, 03:14:07 GMT+0 - Identified - We are currently continuing with remediation actions for affected projects. If you’re affected, you can also fix it manually by restarting your project by visiting this page in the dashboard and click on Restart Project: https://supabase.com/dashboard/project/_/settings/general Mar 3, 02:10:36 GMT+0 - Investigating - We're experiencing an increased number of errors in database operations in us-east-2 region. We'll post more details as we investigate. Mar 3, 02:41:06 GMT+0 - Identified - We’ve identified that this affects only a subset of projects in us-east-2.  We are taking remediation actions for the affected projects. If you’re affected, you can also fix it manually by restarting your project by visiting this page in the dashboard and click on Restart Project: https://supabase.com/dashboard/project/_/settings/general Mar 3, 04:08:01 GMT+0 - Monitoring - We've fixed majority of the affected projects. They are very few projects that need extra steps to resolve. We are working on them at the moment. Type: Incident

Duration: 10 days, 20 hours and 28 minutes

Affected Components:

<p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>06:31:05</var> GMT+0</small><br><strong>Resolved</strong> - Root cause has been confirmed to be addressed. Handful of projects still require manual intervention however. We will be reaching out to their respective owners..</p> <p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>03:14:07</var> GMT+0</small><br><strong>Identified</strong> - We are currently continuing with remediation actions for affected projects. If you’re affected, you can also fix it manually by restarting your project by visiting this page in the dashboard and click on Restart Project: https://supabase.com/dashboard/project/_/settings/general.</p> <p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>02:10:36</var> GMT+0</small><br><strong>Investigating</strong> - We're experiencing an increased number of errors in database operations in us-east-2 region. We'll post more details as we investigate..</p> <p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>02:41:06</var> GMT+0</small><br><strong>Identified</strong> - We’ve identified that this affects only a subset of projects in us-east-2.  We are taking remediation actions for the affected projects. If you’re affected, you can also fix it manually by restarting your project by visiting this page in the dashboard and click on Restart Project: https://supabase.com/dashboard/project/_/settings/general.</p> <p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>04:08:01</var> GMT+0</small><br><strong>Monitoring</strong> - We've fixed majority of the affected projects. They are very few projects that need extra steps to resolve. We are working on them at the moment..</p> ]]> Tue, 3 Mar 2026 02:10:36 +0000 https://wundertreos.instatus.com/incident/cmp93ncbx0doupfwt9acdb923 https://wundertreos.instatus.com/incident/cmp93ncbx0doupfwt9acdb923 Mail delivery delays Type: Incident Affected Components: Email Mar 3, 01:05:32 GMT+0 - Resolved - Between 4:00pm to 4:30pm PT, some mail delivery were delayed. There was no data loss or API unavailability. Our Engineers identified and resolved the issue. Type: Incident

Affected Components:

<p><small>Mar <var data-var='date'> 3</var>, <var data-var='time'>01:05:32</var> GMT+0</small><br><strong>Resolved</strong> - Between 4:00pm to 4:30pm PT, some mail delivery were delayed. There was no data loss or API unavailability. Our Engineers identified and resolved the issue..</p> ]]> Tue, 3 Mar 2026 01:05:32 +0000 https://wundertreos.instatus.com/incident/cmp93xsrb0iv5npwjhf171w2n https://wundertreos.instatus.com/incident/cmp93xsrb0iv5npwjhf171w2n Increased Edge Function Errors across multiple regions Type: Incident Duration: 3 days, 14 hours and 39 minutes Affected Components: Functions Feb 28, 14:04:56 GMT+0 - 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. Feb 28, 13:48:32 GMT+0 - Investigating - 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. Feb 28, 14:09:51 GMT+0 - 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. Feb 28, 13:03:11 GMT+0 - 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. Feb 28, 14:29:50 GMT+0 - 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. Type: Incident

Duration: 3 days, 14 hours and 39 minutes

Affected Components:

<p><small>Feb <var data-var='date'> 28</var>, <var data-var='time'>14:04:56</var> GMT+0</small><br><strong>Identified</strong> - 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..</p> <p><small>Feb <var data-var='date'> 28</var>, <var data-var='time'>13:48:32</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Feb <var data-var='date'> 28</var>, <var data-var='time'>14:09:51</var> GMT+0</small><br><strong>Monitoring</strong> - 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..</p> <p><small>Feb <var data-var='date'> 28</var>, <var data-var='time'>13:03:11</var> GMT+0</small><br><strong>Investigating</strong> - 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..</p> <p><small>Feb <var data-var='date'> 28</var>, <var data-var='time'>14:29:50</var> GMT+0</small><br><strong>Resolved</strong> - 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..</p> ]]> Sat, 28 Feb 2026 13:03:11 +0000 https://wundertreos.instatus.com/incident/cmp93lnew0duiqvp6qpk45qh2 https://wundertreos.instatus.com/incident/cmp93lnew0duiqvp6qpk45qh2 Users Experiencing Network Connectivity Problems (India Region) Type: Incident Duration: 10 days, 15 hours and 54 minutes Affected Components: Functions, Auth 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). 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, 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. 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. 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. 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: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 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/ 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 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. 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 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. 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 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 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. 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. Type: Incident

Duration: 10 days, 15 hours and 54 minutes

Affected Components: ,

<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> <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'>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>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>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>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: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'> 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>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'> 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>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'> 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>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'> 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'> 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>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> ]]> Tue, 24 Feb 2026 14:46:17 +0000 https://wundertreos.instatus.com/incident/cmp93lnes0dueqvp6qhr8i03l https://wundertreos.instatus.com/incident/cmp93lnes0dueqvp6qhr8i03l