<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>FrameWork Status - Incident history</title>
    <link>https://status.frameworkpm.io</link>
    <description>FrameWork</description>
    <pubDate>Tue, 29 Sep 2026 16:26:33 +0000</pubDate>
    
<item>
  <title>Intermittent latency in Eastern US</title>
  <description>
    Type: Incident
    Duration: 13 days, 13 hours and 16 minutes

    Affected Components: Supabase → API Gateway
    Oct 6, 12:15:49 GMT+0 - Resolved - A fix for this issue has been implemented and our data shows previous impacted users have recovered. Oct 5, 18:45:47 GMT+0 - Monitoring - A fix for this issue has been implemented and our data shows recovery for users on projects that have previously been affected. We expect this situation to be resolved, but will keep monitoring for a while until fully resolving this incident. Oct 2, 21:06:20 GMT+0 - Identified - While we have observed significant improvement in rates of high latency, we note that some users are still experiencing issues during peak Eastern US business hours. We continue to work with our networking partners to isolate and resolve any lingering sources of high latency. We recognize that this is a longstanding issue and appreciate the patience of affected customers. We will continue to share additional updates here as soon as they are available. Oct 1, 20:23:18 GMT+0 - Identified - Our networking partners have implemented a mitigation to the latency issue at the problematic PoP in the Eastern US, and we have since observed significant improvement in rates of high latency across the region. We are continuing to work with those partners to isolate any additional root causes of latency and improve the reliability of our networking infrastructure across the region. Sep 30, 21:26:46 GMT+0 - Identified - We are seeing signs of improvement and are continuing to work alongside our networking partners towards a resolution.
We will provide another update as more information becomes available. Sep 30, 14:54:28 GMT+0 - Identified - We&#039;re continuing to coordinate with our networking partners to deliver a permanent resolution.
We will provide updates as soon as they&#039;re available. Sep 30, 02:14:25 GMT+0 - Identified - We are working with our networking partners on a permanent fix.

While we do not have an estimated resolution time, we will share updates here as they become available. Sep 29, 21:35:08 GMT+0 - Identified - A mitigation for this issue was applied earlier today, but we do not have sufficient evidence to conclude that the mitigation resulted in improvement to this eastern US latency issue. We have tied the issue to a particular PoP, and we are continuing to work with our networking partners to bring this issue to a final resolution. We will provide another update within 4 hours, if not before. We appreciate your patience. Sep 29, 17:55:49 GMT+0 - Identified - We are continuing our work to fix this latency issue, which has been observed to impact clients connecting to Supabase Projects from the eastern United States. These clients may include servers and serverless functions located in that geographical region, regardless of the region in which the Project is hosted. Sep 29, 16:26:33 GMT+0 - Identified - We have identified an issue with increased latency for clients in the eastern US during spikes caused by bursty traffic. This is most noticeable during EDT working hours around the :00 and :30 hour marks.

We are actively working on a fix. We will provide updates as the fix is implemented. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 13 days, 13 hours and 16 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Oct <var data-var='date'> 6</var>, <var data-var='time'>12:15:49</var> GMT+0</small><br><strong>Resolved</strong> -
  A fix for this issue has been implemented and our data shows previous impacted users have recovered..</p>
<p><small>Oct <var data-var='date'> 5</var>, <var data-var='time'>18:45:47</var> GMT+0</small><br><strong>Monitoring</strong> -
  A fix for this issue has been implemented and our data shows recovery for users on projects that have previously been affected. We expect this situation to be resolved, but will keep monitoring for a while until fully resolving this incident..</p>
<p><small>Oct <var data-var='date'> 2</var>, <var data-var='time'>21:06:20</var> GMT+0</small><br><strong>Identified</strong> -
  While we have observed significant improvement in rates of high latency, we note that some users are still experiencing issues during peak Eastern US business hours. We continue to work with our networking partners to isolate and resolve any lingering sources of high latency. We recognize that this is a longstanding issue and appreciate the patience of affected customers. We will continue to share additional updates here as soon as they are available..</p>
<p><small>Oct <var data-var='date'> 1</var>, <var data-var='time'>20:23:18</var> GMT+0</small><br><strong>Identified</strong> -
  Our networking partners have implemented a mitigation to the latency issue at the problematic PoP in the Eastern US, and we have since observed significant improvement in rates of high latency across the region. We are continuing to work with those partners to isolate any additional root causes of latency and improve the reliability of our networking infrastructure across the region..</p>
<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>21:26:46</var> GMT+0</small><br><strong>Identified</strong> -
  We are seeing signs of improvement and are continuing to work alongside our networking partners towards a resolution.
We will provide another update as more information becomes available..</p>
<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>14:54:28</var> GMT+0</small><br><strong>Identified</strong> -
  We&#039;re continuing to coordinate with our networking partners to deliver a permanent resolution.
We will provide updates as soon as they&#039;re available..</p>
<p><small>Sep <var data-var='date'> 30</var>, <var data-var='time'>02:14:25</var> GMT+0</small><br><strong>Identified</strong> -
  We are working with our networking partners on a permanent fix.

While we do not have an estimated resolution time, we will share updates here as they become available..</p>
<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>21:35:08</var> GMT+0</small><br><strong>Identified</strong> -
  A mitigation for this issue was applied earlier today, but we do not have sufficient evidence to conclude that the mitigation resulted in improvement to this eastern US latency issue. We have tied the issue to a particular PoP, and we are continuing to work with our networking partners to bring this issue to a final resolution. We will provide another update within 4 hours, if not before. We appreciate your patience..</p>
<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>17:55:49</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing our work to fix this latency issue, which has been observed to impact clients connecting to Supabase Projects from the eastern United States. These clients may include servers and serverless functions located in that geographical region, regardless of the region in which the Project is hosted..</p>
<p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>16:26:33</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified an issue with increased latency for clients in the eastern US during spikes caused by bursty traffic. This is most noticeable during EDT working hours around the :00 and :30 hour marks.

We are actively working on a fix. We will provide updates as the fix is implemented..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 29 Sep 2026 16:26:33 +0000</pubDate>
  <link>https://status.frameworkpm.io/incident/cmumw76lafd0o0rrvhnnclv9k</link>
  <guid>https://status.frameworkpm.io/incident/cmumw76lafd0o0rrvhnnclv9k</guid>
</item>

<item>
  <title>Project Lifecycle Issues in eu-west-1</title>
  <description>
    Type: Incident
    Duration: 5 days, 1 hour and 52 minutes

    Affected Components: Supabase → Database
    Sep 24, 17:38:02 GMT+0 - Resolved - This incident has been resolved. Sep 24, 17:12:33 GMT+0 - Monitoring - We are continuing to monitor to ensure ongoing stability. Sep 24, 17:03:16 GMT+0 - Identified - The remaining projects have now been brought back up, and we have no projects remaining on the unhealthy underlying hardware in the upstream infrastructure. We are monitoring to ensure ongoing stability. Sep 24, 16:56:04 GMT+0 - Identified - Most projects have been brought back up, and the team is working on the remaining projects, which should be completed soon.

This issue was related to specific underlying hardware in the region, so this was isolated to only projects on that hardware. Project lifecycle operations (restarts, upgrades, etc) broadly across the region remain available. Sep 24, 16:23:54 GMT+0 - Identified - All projects affected by the upstream infrastructure issues, and mitigation efforts are underway internally. These affected projects will be brought back up on new hardware as quickly as possible. Sep 24, 15:50:26 GMT+0 - Identified - We have isolated the scope of the problem to a specific upstream incident. We are working to address the upstream incident and determine mitigations. Sep 24, 15:36:10 GMT+0 - Investigating - We are investigating project lifecycle operation issues in eu-west-1. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 days, 1 hour and 52 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>17:38:02</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>17:12:33</var> GMT+0</small><br><strong>Monitoring</strong> -
  We are continuing to monitor to ensure ongoing stability..</p>
<p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>17:03:16</var> GMT+0</small><br><strong>Identified</strong> -
  The remaining projects have now been brought back up, and we have no projects remaining on the unhealthy underlying hardware in the upstream infrastructure. We are monitoring to ensure ongoing stability..</p>
<p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>16:56:04</var> GMT+0</small><br><strong>Identified</strong> -
  Most projects have been brought back up, and the team is working on the remaining projects, which should be completed soon.

This issue was related to specific underlying hardware in the region, so this was isolated to only projects on that hardware. Project lifecycle operations (restarts, upgrades, etc) broadly across the region remain available..</p>
<p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>16:23:54</var> GMT+0</small><br><strong>Identified</strong> -
  All projects affected by the upstream infrastructure issues, and mitigation efforts are underway internally. These affected projects will be brought back up on new hardware as quickly as possible..</p>
<p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>15:50:26</var> GMT+0</small><br><strong>Identified</strong> -
  We have isolated the scope of the problem to a specific upstream incident. We are working to address the upstream incident and determine mitigations..</p>
<p><small>Sep <var data-var='date'> 24</var>, <var data-var='time'>15:36:10</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating project lifecycle operation issues in eu-west-1..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 24 Sep 2026 15:36:10 +0000</pubDate>
  <link>https://status.frameworkpm.io/incident/cmufp69sz2ekl0krvuh5b1nwj</link>
  <guid>https://status.frameworkpm.io/incident/cmufp69sz2ekl0krvuh5b1nwj</guid>
</item>

<item>
  <title>Increased error rate in project creation and project restore</title>
  <description>
    Type: Incident
    Duration: 3 days and 16 hours

    Affected Components: Supabase → Compute
    Sep 23, 10:49:14 GMT+0 - Resolved - This incident has been resolved. Sep 23, 09:54:10 GMT+0 - Monitoring - A fix has been implemented and we are monitoring the results. Sep 23, 09:39:45 GMT+0 - Identified - We&#039;ve identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this. Sep 23, 09:21:14 GMT+0 - Investigating - We are currently investigating this issue 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days and 16 hours</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 23</var>, <var data-var='time'>10:49:14</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 23</var>, <var data-var='time'>09:54:10</var> GMT+0</small><br><strong>Monitoring</strong> -
  A fix has been implemented and we are monitoring the results..</p>
<p><small>Sep <var data-var='date'> 23</var>, <var data-var='time'>09:39:45</var> GMT+0</small><br><strong>Identified</strong> -
  We&#039;ve identified the issue affecting project creation and are implementing a fix. Users may experience delays when creating new projects while we work to resolve this..</p>
<p><small>Sep <var data-var='date'> 23</var>, <var data-var='time'>09:21:14</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating this issue.</p>
]]>
  </content:encoded>
  <pubDate>Wed, 23 Sep 2026 09:21:14 +0000</pubDate>
  <link>https://status.frameworkpm.io/incident/cmudwc1j6n0rf0kmhq0vmf0s5</link>
  <guid>https://status.frameworkpm.io/incident/cmudwc1j6n0rf0kmhq0vmf0s5</guid>
</item>

<item>
  <title>Upgrade</title>
  <description>
    Type: Maintenance
    Duration: 24 minutes

    Affected Components: FrameWork API, FrameWork, FrameWork Auth
    Sep 22, 15:54:14 GMT+0 - Completed - Maintenance has completed successfully. Sep 22, 15:30:00 GMT+0 - Identified - We are planning for a scheduled maintenance during that time. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 24 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>15:54:14</var> GMT+0</small><br><strong>Completed</strong> -
  Maintenance has completed successfully..</p>
<p><small>Sep <var data-var='date'> 22</var>, <var data-var='time'>15:30:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are planning for a scheduled maintenance during that time..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 22 Sep 2026 15:30:00 +0000</pubDate>
  <link>https://status.frameworkpm.io/maintenance/cmucup9xh01lm1nnzh2b4wy3c</link>
  <guid>https://status.frameworkpm.io/maintenance/cmucup9xh01lm1nnzh2b4wy3c</guid>
</item>

<item>
  <title>Project Lifecycle Activity Degradation</title>
  <description>
    Type: Incident
    Duration: 5 days and 28 minutes

    Affected Components: Supabase → Database
    Sep 19, 22:12:33 GMT+0 - Resolved - Project lifecycle operations are behaving normally. Sep 19, 21:25:42 GMT+0 - Monitoring - Project lifecycle operations have remained stable. We will continue to monitor the platform. Sep 19, 20:34:15 GMT+0 - Investigating - We are observing recovery in project lifecycle operations. Our team is investigating the root cause and actively working to prevent recurrence. Sep 19, 20:12:05 GMT+0 - Investigating - We are experiencing degradation of project lifecycle activities. We are investigating. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 days and 28 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 19</var>, <var data-var='time'>22:12:33</var> GMT+0</small><br><strong>Resolved</strong> -
  Project lifecycle operations are behaving normally..</p>
<p><small>Sep <var data-var='date'> 19</var>, <var data-var='time'>21:25:42</var> GMT+0</small><br><strong>Monitoring</strong> -
  Project lifecycle operations have remained stable. We will continue to monitor the platform..</p>
<p><small>Sep <var data-var='date'> 19</var>, <var data-var='time'>20:34:15</var> GMT+0</small><br><strong>Investigating</strong> -
  We are observing recovery in project lifecycle operations. Our team is investigating the root cause and actively working to prevent recurrence..</p>
<p><small>Sep <var data-var='date'> 19</var>, <var data-var='time'>20:12:05</var> GMT+0</small><br><strong>Investigating</strong> -
  We are experiencing degradation of project lifecycle activities. We are investigating..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 19 Sep 2026 20:12:05 +0000</pubDate>
  <link>https://status.frameworkpm.io/incident/cmu8tsjzfd0g90rmh7mtno1a7</link>
  <guid>https://status.frameworkpm.io/incident/cmu8tsjzfd0g90rmh7mtno1a7</guid>
</item>

<item>
  <title>Auth Service Outage</title>
  <description>
    Type: Incident
    Duration: 5 days, 16 hours and 22 minutes

    Affected Components: Supabase → Auth
    Sep 16, 09:33:34 GMT+0 - Resolved - This incident has been resolved. Sep 16, 09:09:29 GMT+0 - Monitoring - We implemented a fix and are monitoring the system. Sep 16, 08:29:44 GMT+0 - Identified - We have identified a subset of projects with a failing Auth service. Our team is working to remediate the issue. Sep 16, 07:17:12 GMT+0 - Identified - We have identified an issue related to the Auth service on some projects. We are actively working on a fix. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 days, 16 hours and 22 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 16</var>, <var data-var='time'>09:33:34</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 16</var>, <var data-var='time'>09:09:29</var> GMT+0</small><br><strong>Monitoring</strong> -
  We implemented a fix and are monitoring the system..</p>
<p><small>Sep <var data-var='date'> 16</var>, <var data-var='time'>08:29:44</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified a subset of projects with a failing Auth service. Our team is working to remediate the issue..</p>
<p><small>Sep <var data-var='date'> 16</var>, <var data-var='time'>07:17:12</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified an issue related to the Auth service on some projects. We are actively working on a fix..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 16 Sep 2026 07:17:12 +0000</pubDate>
  <link>https://status.frameworkpm.io/incident/cmu3rs9ci44a30kmht5z81d02</link>
  <guid>https://status.frameworkpm.io/incident/cmu3rs9ci44a30kmht5z81d02</guid>
</item>

<item>
  <title>Unresponsive Projects</title>
  <description>
    Type: Incident
    Duration: 10 days, 4 hours and 15 minutes

    Affected Components: Supabase → Database
    Sep 11, 19:06:34 GMT+0 - Resolved - This incident has been resolved. Sep 11, 06:19:34 GMT+0 - Monitoring - We have rolled out a fix across all regions and are continuing to monitor over the next few hours. 

Due to this incident, impacted users who&#039;s project were compute constrained would have received a &#039;Your Supabase Project &lt;Name&gt; is running out of Disk IO Budget&#039; email which is no longer valid. No further action is required and your project availability should be restored to normal. Sep 11, 03:44:45 GMT+0 - Monitoring - We have rolled out a fix across all regions and are continuing to monitor over the next few hours. 
Users still affected by project outages are encouraged to restart their projects which has shown to resolve lasting errors. Sep 10, 19:41:50 GMT+0 - Identified - We have rolled out a version of the fix across all regions that will prevent recurrence of the issue. Users still affected by project outages are encouraged to restart their projects. Sep 10, 17:59:49 GMT+0 - Identified - Fix rollouts have been successful in the initial regions, we are proceeding to roll out the fix globally. Sep 10, 17:13:30 GMT+0 - Identified - A refined fix is being rolled out to specific regions, we are assessing the impact of the fix. Sep 10, 15:46:17 GMT+0 - Identified - We have identified why projects are becoming unresponsive and are implementing a mitigation. Sep 10, 15:26:19 GMT+0 - Investigating - We are aware of Nano projects becoming unresponsive after a period of time, typically hours. We are investigating. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 10 days, 4 hours and 15 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 11</var>, <var data-var='time'>19:06:34</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident has been resolved..</p>
<p><small>Sep <var data-var='date'> 11</var>, <var data-var='time'>06:19:34</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have rolled out a fix across all regions and are continuing to monitor over the next few hours. 

Due to this incident, impacted users who&#039;s project were compute constrained would have received a &#039;Your Supabase Project &lt;Name&gt; is running out of Disk IO Budget&#039; email which is no longer valid. No further action is required and your project availability should be restored to normal..</p>
<p><small>Sep <var data-var='date'> 11</var>, <var data-var='time'>03:44:45</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have rolled out a fix across all regions and are continuing to monitor over the next few hours. 
Users still affected by project outages are encouraged to restart their projects which has shown to resolve lasting errors..</p>
<p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>19:41:50</var> GMT+0</small><br><strong>Identified</strong> -
  We have rolled out a version of the fix across all regions that will prevent recurrence of the issue. Users still affected by project outages are encouraged to restart their projects..</p>
<p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>17:59:49</var> GMT+0</small><br><strong>Identified</strong> -
  Fix rollouts have been successful in the initial regions, we are proceeding to roll out the fix globally..</p>
<p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>17:13:30</var> GMT+0</small><br><strong>Identified</strong> -
  A refined fix is being rolled out to specific regions, we are assessing the impact of the fix..</p>
<p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>15:46:17</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified why projects are becoming unresponsive and are implementing a mitigation..</p>
<p><small>Sep <var data-var='date'> 10</var>, <var data-var='time'>15:26:19</var> GMT+0</small><br><strong>Investigating</strong> -
  We are aware of Nano projects becoming unresponsive after a period of time, typically hours. We are investigating..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 10 Sep 2026 15:26:19 +0000</pubDate>
  <link>https://status.frameworkpm.io/incident/cmtvonb2a969u0rqjzntk768m</link>
  <guid>https://status.frameworkpm.io/incident/cmtvonb2a969u0rqjzntk768m</guid>
</item>

<item>
  <title>Project Creation Failures</title>
  <description>
    Type: Incident
    Duration: 6 days, 14 hours and 8 minutes

    Affected Components: Supabase → Database
    Aug 31, 19:06:38 GMT+0 - Resolved - Project creation has returned to baseline consistently. Aug 31, 18:29:54 GMT+0 - Monitoring - Project creation is reporting as recovered across the platform. We will monitor for stability in the near term. Aug 31, 18:01:08 GMT+0 - Identified - We are seeing the mitigation steps having the desired effect. Project creation is recovering. Aug 31, 17:49:04 GMT+0 - Investigating - While the first set of actions are taking effect, we are implementing a second set of likely mitigations to attempt to facilitate improvement in project creation. Aug 31, 17:20:50 GMT+0 - Investigating - We continue to work this issue. The steps we have taken are addressing the hypothesized cause of the issue. We are implementing further related mitigations. Aug 31, 16:53:46 GMT+0 - Investigating - We have a working hypothesis on the cause of the issue, and are implementing steps to try to improve project creation performance. Aug 31, 16:28:30 GMT+0 - Investigating - Project creation is failing for new projects on the platform. We are investigating. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 6 days, 14 hours and 8 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>19:06:38</var> GMT+0</small><br><strong>Resolved</strong> -
  Project creation has returned to baseline consistently..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>18:29:54</var> GMT+0</small><br><strong>Monitoring</strong> -
  Project creation is reporting as recovered across the platform. We will monitor for stability in the near term..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>18:01:08</var> GMT+0</small><br><strong>Identified</strong> -
  We are seeing the mitigation steps having the desired effect. Project creation is recovering..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>17:49:04</var> GMT+0</small><br><strong>Investigating</strong> -
  While the first set of actions are taking effect, we are implementing a second set of likely mitigations to attempt to facilitate improvement in project creation..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>17:20:50</var> GMT+0</small><br><strong>Investigating</strong> -
  We continue to work this issue. The steps we have taken are addressing the hypothesized cause of the issue. We are implementing further related mitigations..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>16:53:46</var> GMT+0</small><br><strong>Investigating</strong> -
  We have a working hypothesis on the cause of the issue, and are implementing steps to try to improve project creation performance..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>16:28:30</var> GMT+0</small><br><strong>Investigating</strong> -
  Project creation is failing for new projects on the platform. We are investigating..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 31 Aug 2026 16:28:30 +0000</pubDate>
  <link>https://status.frameworkpm.io/incident/cmthge5307xma0kpwy0iwbqmx</link>
  <guid>https://status.frameworkpm.io/incident/cmthge5307xma0kpwy0iwbqmx</guid>
</item>

<item>
  <title>Issues affecting automatic disk resizing</title>
  <description>
    Type: Incident
    Duration: 5 days and 26 minutes

    Affected Components: Supabase → Compute
    Aug 24, 15:53:09 GMT+0 - Resolved - The issue affecting automatic disk resizing has been resolved.
We will continue to follow up directly with affected users who opened a support ticket. Aug 24, 14:47:53 GMT+0 - Monitoring - A fix has been applied, and the issue is now resolved. We are moving the incident to monitoring.
We will continue to follow up directly with affected users who opened a support ticket. Aug 24, 13:52:42 GMT+0 - Investigating - We are investigating an issue affecting automatic disk resizing.
Some projects may experience delays before a resize is completed, while others may see repeated or duplicate resize operations.
We are working to identify the cause and will provide an update as soon as we have more information. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 days and 26 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>15:53:09</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue affecting automatic disk resizing has been resolved.
We will continue to follow up directly with affected users who opened a support ticket..</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>14:47:53</var> GMT+0</small><br><strong>Monitoring</strong> -
  A fix has been applied, and the issue is now resolved. We are moving the incident to monitoring.
We will continue to follow up directly with affected users who opened a support ticket..</p>
<p><small>Aug <var data-var='date'> 24</var>, <var data-var='time'>13:52:42</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating an issue affecting automatic disk resizing.
Some projects may experience delays before a resize is completed, while others may see repeated or duplicate resize operations.
We are working to identify the cause and will provide an update as soon as we have more information..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 24 Aug 2026 13:52:42 +0000</pubDate>
  <link>https://status.frameworkpm.io/incident/cmt7arnngcwc20kmg5hfa1a3y</link>
  <guid>https://status.frameworkpm.io/incident/cmt7arnngcwc20kmg5hfa1a3y</guid>
</item>

<item>
  <title>401 errors due to JWT rejections</title>
  <description>
    Type: Incident
    Duration: 23 hours and 10 minutes

    Affected Components: Supabase → API Gateway
    Sep 29, 18:46:28 GMT+0 - Resolved - The latest Supabase version has been released. All users impacted by this issue can now upgrade from the dashboard to resolve this issue. 

Since this new version is released, we will resolve this issue. If you have any questions about upgrading, please refer to our documentation for more information:
https://supabase.com/docs/guides/platform/upgrading

Thank you again for your patience while we worked on resolving this issue. Sep 25, 16:23:02 GMT+0 - Identified - The deployment process changes have been rolled out across all regions. We will monitor throughout the weekend. 

The new Supabase version will be released early next week. Once it is released, impacted users can upgrade from their dashboard to resolve this issue. 

Thank you again for your patience while we worked through this. We will provide an update once the new version is available and users can upgrade. Sep 23, 07:26:29 GMT+0 - Identified - We have rolled out the deployment process changes to eu-central-2 and continue to monitor. We will provide additional updates as we make this change to other regions. 

Once this change is implemented across all regions, we will release a new Supabase version that impacted users can upgrade to from their dashboard. Completing that upgrade will resolve this issue. Sep 17, 19:30:16 GMT+0 - Identified - To resolve this issue, our fleet requires a change to our deploy process. We have spent this week making these changes and will be implementing them throughout this weekend, starting on Friday, September 18. Once this change is implemented, we will release a new Supabase version that impacted users can upgrade to from their dashboard. Completing that upgrade will resolve this issue.

We recognize that this is added work for our customers. This issue has been open for over a month, as we tried to make this change on each project&#039;s behalf. In an effort to resolve this sooner, we have opted to make this deployment process change and ask users to upgrade. Sep 11, 23:41:53 GMT+0 - Identified - We continue to monitor progress and are slowly updating each region. Thank you for your patience on this issue. Sep 7, 09:49:15 GMT+0 - Identified - Testing results have been positive. 
Following some additional checks today, we plan to expand the rollout. 
We’ll continue to monitor progress and provide further updates as they become available. Sep 2, 19:38:53 GMT+0 - Identified - A stale time cache has been identified as the cause of this issue. A targeted fix has been written and is undergoing internal testing. It will be rolled out when testing is complete. Thank you for your patience while we investigated this issue. We will update the status page when the fix is rolled out. Aug 31, 19:52:53 GMT+0 - Identified - We have seen reports that the JWT rejection issue persisted with 14.17, and due to &lt;a href=&quot;https://status.supabase.com/incidents/bv4ntm4x0btf&quot;&gt;some unintended performance side effects&lt;/a&gt;, we have rolled back to Postgrest 14.5. The team continues to investigate the JWT issue and hopes to have a solution soon. Aug 28, 23:44:41 GMT+0 - Identified - We continue to monitor the fixes introduced by this latest rollout. If you are continuing to see these errors, some customers have reported that restarting their project after the rollout resolved this issue.

To restart your project, go to the General settings page in the dashboard and select Restart project. 

Please contact our support team if the issue persists after a restart. Aug 27, 17:17:54 GMT+0 - Identified - PostgREST 14.17 has now been rolled out to all regions. 
Some customers have reported that restarting their project after the rollout resolved this issue.
To restart your project, go to the General settings page in the dashboard and select Restart project. 
Please contact our support team if the issue persists after a restart. Aug 25, 18:41:58 GMT+0 - Identified - We are continuing to rollout the fixes for intermittent HTTP 401 errors. In most cases, waiting and refreshing is successful. 

This fix has been applied to the following regions: 
ap-east-1
ap-northeast-1
ap-northeast-2
ap-south-1
ap-southeast-1
ap-southeast-2
ca-central-1
eu-central-1
eu-central-2
eu-north-1
eu-west-2
eu-west-3

We will continue rolling out this fix to the remaining regions throughout this week and provide updates as more regions are successful. Aug 21, 17:21:47 GMT+0 - Identified - We are continuing to test and rollout the fixes for intermittent HTTP 401 errors. In most cases, waiting and refreshing is successful. 

We will monitor eu-central-2 over the weekend and are preparing for the fix to be pushed to all regions starting Monday. Thank you for your patience while we&#039;ve worked on multiple fixes for this issue. Aug 20, 16:37:44 GMT+0 - Identified - As part of the incident remediation flow, we have separately identified &quot;/lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34&#039; not found&quot; error between 11:15 - 16:24 UTC today affecting PostgREST. This has been fixed and we can see the error rates have subsided. Aug 18, 18:38:37 GMT+0 - Identified - Fixes for this issue are being sequentially rolled out. The impact of the issue is limited to a subset of new projects that can experience it upon some JWT renewals. We will update the status when all the fix rollouts have completed. Aug 14, 07:53:32 GMT+0 - Identified - Our teams are continuing to work on the fix and rollout is underway for selected customers. We will provide another update as we are applying the fix to all impacted users. Aug 14, 02:23:18 GMT+0 - Identified - We have identified the root cause of newly refreshed JWTs being rejected by the API, resulting in HTTP 401 errors for affected sessions. We are working on a fix and will provide updates as things progress. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 23 hours and 10 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Sep <var data-var='date'> 29</var>, <var data-var='time'>18:46:28</var> GMT+0</small><br><strong>Resolved</strong> -
  The latest Supabase version has been released. All users impacted by this issue can now upgrade from the dashboard to resolve this issue. 

Since this new version is released, we will resolve this issue. If you have any questions about upgrading, please refer to our documentation for more information:
https://supabase.com/docs/guides/platform/upgrading

Thank you again for your patience while we worked on resolving this issue..</p>
<p><small>Sep <var data-var='date'> 25</var>, <var data-var='time'>16:23:02</var> GMT+0</small><br><strong>Identified</strong> -
  The deployment process changes have been rolled out across all regions. We will monitor throughout the weekend. 

The new Supabase version will be released early next week. Once it is released, impacted users can upgrade from their dashboard to resolve this issue. 

Thank you again for your patience while we worked through this. We will provide an update once the new version is available and users can upgrade..</p>
<p><small>Sep <var data-var='date'> 23</var>, <var data-var='time'>07:26:29</var> GMT+0</small><br><strong>Identified</strong> -
  We have rolled out the deployment process changes to eu-central-2 and continue to monitor. We will provide additional updates as we make this change to other regions. 

Once this change is implemented across all regions, we will release a new Supabase version that impacted users can upgrade to from their dashboard. Completing that upgrade will resolve this issue..</p>
<p><small>Sep <var data-var='date'> 17</var>, <var data-var='time'>19:30:16</var> GMT+0</small><br><strong>Identified</strong> -
  To resolve this issue, our fleet requires a change to our deploy process. We have spent this week making these changes and will be implementing them throughout this weekend, starting on Friday, September 18. Once this change is implemented, we will release a new Supabase version that impacted users can upgrade to from their dashboard. Completing that upgrade will resolve this issue.

We recognize that this is added work for our customers. This issue has been open for over a month, as we tried to make this change on each project&#039;s behalf. In an effort to resolve this sooner, we have opted to make this deployment process change and ask users to upgrade..</p>
<p><small>Sep <var data-var='date'> 11</var>, <var data-var='time'>23:41:53</var> GMT+0</small><br><strong>Identified</strong> -
  We continue to monitor progress and are slowly updating each region. Thank you for your patience on this issue..</p>
<p><small>Sep <var data-var='date'> 7</var>, <var data-var='time'>09:49:15</var> GMT+0</small><br><strong>Identified</strong> -
  Testing results have been positive. 
Following some additional checks today, we plan to expand the rollout. 
We’ll continue to monitor progress and provide further updates as they become available..</p>
<p><small>Sep <var data-var='date'> 2</var>, <var data-var='time'>19:38:53</var> GMT+0</small><br><strong>Identified</strong> -
  A stale time cache has been identified as the cause of this issue. A targeted fix has been written and is undergoing internal testing. It will be rolled out when testing is complete. Thank you for your patience while we investigated this issue. We will update the status page when the fix is rolled out..</p>
<p><small>Aug <var data-var='date'> 31</var>, <var data-var='time'>19:52:53</var> GMT+0</small><br><strong>Identified</strong> -
  We have seen reports that the JWT rejection issue persisted with 14.17, and due to &lt;a href=&quot;https://status.supabase.com/incidents/bv4ntm4x0btf&quot;&gt;some unintended performance side effects&lt;/a&gt;, we have rolled back to Postgrest 14.5. The team continues to investigate the JWT issue and hopes to have a solution soon..</p>
<p><small>Aug <var data-var='date'> 28</var>, <var data-var='time'>23:44:41</var> GMT+0</small><br><strong>Identified</strong> -
  We continue to monitor the fixes introduced by this latest rollout. If you are continuing to see these errors, some customers have reported that restarting their project after the rollout resolved this issue.

To restart your project, go to the General settings page in the dashboard and select Restart project. 

Please contact our support team if the issue persists after a restart..</p>
<p><small>Aug <var data-var='date'> 27</var>, <var data-var='time'>17:17:54</var> GMT+0</small><br><strong>Identified</strong> -
  PostgREST 14.17 has now been rolled out to all regions. 
Some customers have reported that restarting their project after the rollout resolved this issue.
To restart your project, go to the General settings page in the dashboard and select Restart project. 
Please contact our support team if the issue persists after a restart..</p>
<p><small>Aug <var data-var='date'> 25</var>, <var data-var='time'>18:41:58</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to rollout the fixes for intermittent HTTP 401 errors. In most cases, waiting and refreshing is successful. 

This fix has been applied to the following regions: 
ap-east-1
ap-northeast-1
ap-northeast-2
ap-south-1
ap-southeast-1
ap-southeast-2
ca-central-1
eu-central-1
eu-central-2
eu-north-1
eu-west-2
eu-west-3

We will continue rolling out this fix to the remaining regions throughout this week and provide updates as more regions are successful..</p>
<p><small>Aug <var data-var='date'> 21</var>, <var data-var='time'>17:21:47</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to test and rollout the fixes for intermittent HTTP 401 errors. In most cases, waiting and refreshing is successful. 

We will monitor eu-central-2 over the weekend and are preparing for the fix to be pushed to all regions starting Monday. Thank you for your patience while we&#039;ve worked on multiple fixes for this issue..</p>
<p><small>Aug <var data-var='date'> 20</var>, <var data-var='time'>16:37:44</var> GMT+0</small><br><strong>Identified</strong> -
  As part of the incident remediation flow, we have separately identified &quot;/lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34&#039; not found&quot; error between 11:15 - 16:24 UTC today affecting PostgREST. This has been fixed and we can see the error rates have subsided..</p>
<p><small>Aug <var data-var='date'> 18</var>, <var data-var='time'>18:38:37</var> GMT+0</small><br><strong>Identified</strong> -
  Fixes for this issue are being sequentially rolled out. The impact of the issue is limited to a subset of new projects that can experience it upon some JWT renewals. We will update the status when all the fix rollouts have completed..</p>
<p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>07:53:32</var> GMT+0</small><br><strong>Identified</strong> -
  Our teams are continuing to work on the fix and rollout is underway for selected customers. We will provide another update as we are applying the fix to all impacted users..</p>
<p><small>Aug <var data-var='date'> 14</var>, <var data-var='time'>02:23:18</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the root cause of newly refreshed JWTs being rejected by the API, resulting in HTTP 401 errors for affected sessions. We are working on a fix and will provide updates as things progress..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 14 Aug 2026 02:23:18 +0000</pubDate>
  <link>https://status.frameworkpm.io/incident/cmt0roo9r1k2u0rmg6ga4c204</link>
  <guid>https://status.frameworkpm.io/incident/cmt0roo9r1k2u0rmg6ga4c204</guid>
</item>

<item>
  <title>Project Upgrade Delays</title>
  <description>
    Type: Incident
    Duration: 5 days, 5 hours and 5 minutes

    Affected Components: Supabase → Database
    Aug 5, 17:33:15 GMT+0 - Resolved - Project upgrades have remained stable, we are resolving this incident. Aug 5, 14:58:43 GMT+0 - Monitoring - We have deployed a tested fix for the upgrade issue impacting some projects. The fix has been effective and we are monitoring for continued stability. Aug 4, 23:38:20 GMT+0 - Identified - We are continuing to test the fix to project upgrades. We will update again when the fix is applied. Aug 4, 15:30:47 GMT+0 - Identified - The team has identified a likely fix and is consolidating the details in order to move to thorough testing. We will update again when the fix is applied. Aug 3, 22:46:03 GMT+0 - Identified - We are continuing to fix project upgrade issues and are investigating further remediation. We will provide our next update within the next 14 hours. Aug 3, 19:47:58 GMT+0 - Identified - We are developing a fix for the upgrade issues. Aug 3, 17:09:16 GMT+0 - Identified - We have identified the cause of the upgrade delays and are working on a fix. Aug 3, 16:19:52 GMT+0 - Investigating - We are continuing to investigate project upgrade issues. Aug 3, 15:28:10 GMT+0 - Investigating - We are investigating a potential issue that could result in a delay or failure in some users&#039; project upgrades. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 days, 5 hours and 5 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>17:33:15</var> GMT+0</small><br><strong>Resolved</strong> -
  Project upgrades have remained stable, we are resolving this incident..</p>
<p><small>Aug <var data-var='date'> 5</var>, <var data-var='time'>14:58:43</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have deployed a tested fix for the upgrade issue impacting some projects. The fix has been effective and we are monitoring for continued stability..</p>
<p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>23:38:20</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to test the fix to project upgrades. We will update again when the fix is applied..</p>
<p><small>Aug <var data-var='date'> 4</var>, <var data-var='time'>15:30:47</var> GMT+0</small><br><strong>Identified</strong> -
  The team has identified a likely fix and is consolidating the details in order to move to thorough testing. We will update again when the fix is applied..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>22:46:03</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to fix project upgrade issues and are investigating further remediation. We will provide our next update within the next 14 hours..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>19:47:58</var> GMT+0</small><br><strong>Identified</strong> -
  We are developing a fix for the upgrade issues..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>17:09:16</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the cause of the upgrade delays and are working on a fix..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>16:19:52</var> GMT+0</small><br><strong>Investigating</strong> -
  We are continuing to investigate project upgrade issues..</p>
<p><small>Aug <var data-var='date'> 3</var>, <var data-var='time'>15:28:10</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating a potential issue that could result in a delay or failure in some users&#039; project upgrades..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 3 Aug 2026 15:28:10 +0000</pubDate>
  <link>https://status.frameworkpm.io/incident/cmt0roo661k170rmgrzlqd6df</link>
  <guid>https://status.frameworkpm.io/incident/cmt0roo661k170rmgrzlqd6df</guid>
</item>

<item>
  <title>DNS creation delays</title>
  <description>
    Type: Incident
    Duration: 2 days, 10 hours and 22 minutes

    Affected Components: Supabase → Database, Supabase → API Gateway
    Jul 31, 13:26:16 GMT+0 - Resolved - The incident has been resolved. Jul 31, 12:55:52 GMT+0 - Monitoring - The upstream DNS provider has implemented a fix and is monitoring the results. We are seeing signs of recovery; we will continue to monitor the situation and will provide further updates as more information becomes available. Jul 31, 12:41:51 GMT+0 - Identified - We have identified that the issue is with an upstream DNS provider, causing DNS creation delays for newly created, unpaused, or updated databases. Our team is actively monitoring the situation and will provide further updates as more information becomes available. Jul 31, 12:27:54 GMT+0 - Investigating - We&#039;re investigating issues updating DNS records for newly created, unpaused, or updated databases. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 2 days, 10 hours and 22 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>13:26:16</var> GMT+0</small><br><strong>Resolved</strong> -
  The incident has been resolved..</p>
<p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>12:55:52</var> GMT+0</small><br><strong>Monitoring</strong> -
  The upstream DNS provider has implemented a fix and is monitoring the results. We are seeing signs of recovery; we will continue to monitor the situation and will provide further updates as more information becomes available..</p>
<p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>12:41:51</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified that the issue is with an upstream DNS provider, causing DNS creation delays for newly created, unpaused, or updated databases. Our team is actively monitoring the situation and will provide further updates as more information becomes available..</p>
<p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>12:27:54</var> GMT+0</small><br><strong>Investigating</strong> -
  We&#039;re investigating issues updating DNS records for newly created, unpaused, or updated databases..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 31 Jul 2026 12:27:53 +0000</pubDate>
  <link>https://status.frameworkpm.io/incident/cmt0rooc21k3p0rmgfhepg9me</link>
  <guid>https://status.frameworkpm.io/incident/cmt0rooc21k3p0rmgfhepg9me</guid>
</item>

<item>
  <title>Issues with Edge Function Deployment</title>
  <description>
    Type: Incident
    Duration: 18 days, 6 hours and 38 minutes

    Affected Components: Supabase → Edge Functions
    Jul 31, 13:20:23 GMT+0 - Resolved - A preventative fix (Supabase CLI v2.111.0 ) has been released to ensure that new Function deployments are not affected.
As the underlying issue has been addressed and new deployments should no longer be affected, we are resolving this incident.

All impacted users are now able to re-deploy their Functions again. In exceptional cases, Support will continue working directly with customers who require additional remediation. Jul 31, 09:36:27 GMT+0 - Identified - We are working on a permanent fix for issue affecting bulk Function deployments. 
In parallel, we are manually assisting customers who have reported the issue through support tickets. Jul 31, 03:13:26 GMT+0 - Monitoring - Our fix has completed rollout and we are monitoring for full resolution. Jul 31, 00:26:11 GMT+0 - Identified - The issue has been identified and a fix is being implemented. Jul 30, 23:40:32 GMT+0 - Investigating - We continue to investigate the root cause of this issue. Some deployment operations have recovered, but we are still investigating reports of failures affecting bulk deployments and updates to existing Edge Functions. Jul 30, 22:21:19 GMT+0 - Investigating - We are still identifying the root cause of the issue; however, if you are experiencing issues with your Edge Functions, redeployment should resolve that issue. We apologize for any inconvenience. Jul 30, 21:02:49 GMT+0 - Investigating - We are continuing to investigate this issue. Jul 30, 19:46:12 GMT+0 - Investigating - Per-function deployment appears to be working successfully. However, bulk function deployments with the `supabase functions deploy` command appear to still be experiencing issues. Additionally, we are aware of reports of issues updating existing function deployments. We are continuing to investigate these issues. Jul 30, 18:28:01 GMT+0 - Investigating - We have determined and rolled back the change that led to this issue. Users who were experiencing issues with deployments should now be able to deploy successfully. Jul 30, 18:16:21 GMT+0 - Investigating - Only a subset of users appear to be impacted by the issue with Edge Function deployments. We are investigating the root cause. Jul 30, 17:37:45 GMT+0 - Investigating - We are aware of some users experiencing issues with Edge Function deployments. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 18 days, 6 hours and 38 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>13:20:23</var> GMT+0</small><br><strong>Resolved</strong> -
  A preventative fix (Supabase CLI v2.111.0 ) has been released to ensure that new Function deployments are not affected.
As the underlying issue has been addressed and new deployments should no longer be affected, we are resolving this incident.

All impacted users are now able to re-deploy their Functions again. In exceptional cases, Support will continue working directly with customers who require additional remediation..</p>
<p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>09:36:27</var> GMT+0</small><br><strong>Identified</strong> -
  We are working on a permanent fix for issue affecting bulk Function deployments. 
In parallel, we are manually assisting customers who have reported the issue through support tickets..</p>
<p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>03:13:26</var> GMT+0</small><br><strong>Monitoring</strong> -
  Our fix has completed rollout and we are monitoring for full resolution..</p>
<p><small>Jul <var data-var='date'> 31</var>, <var data-var='time'>00:26:11</var> GMT+0</small><br><strong>Identified</strong> -
  The issue has been identified and a fix is being implemented..</p>
<p><small>Jul <var data-var='date'> 30</var>, <var data-var='time'>23:40:32</var> GMT+0</small><br><strong>Investigating</strong> -
  We continue to investigate the root cause of this issue. Some deployment operations have recovered, but we are still investigating reports of failures affecting bulk deployments and updates to existing Edge Functions..</p>
<p><small>Jul <var data-var='date'> 30</var>, <var data-var='time'>22:21:19</var> GMT+0</small><br><strong>Investigating</strong> -
  We are still identifying the root cause of the issue; however, if you are experiencing issues with your Edge Functions, redeployment should resolve that issue. We apologize for any inconvenience..</p>
<p><small>Jul <var data-var='date'> 30</var>, <var data-var='time'>21:02:49</var> GMT+0</small><br><strong>Investigating</strong> -
  We are continuing to investigate this issue..</p>
<p><small>Jul <var data-var='date'> 30</var>, <var data-var='time'>19:46:12</var> GMT+0</small><br><strong>Investigating</strong> -
  Per-function deployment appears to be working successfully. However, bulk function deployments with the `supabase functions deploy` command appear to still be experiencing issues. Additionally, we are aware of reports of issues updating existing function deployments. We are continuing to investigate these issues..</p>
<p><small>Jul <var data-var='date'> 30</var>, <var data-var='time'>18:28:01</var> GMT+0</small><br><strong>Investigating</strong> -
  We have determined and rolled back the change that led to this issue. Users who were experiencing issues with deployments should now be able to deploy successfully..</p>
<p><small>Jul <var data-var='date'> 30</var>, <var data-var='time'>18:16:21</var> GMT+0</small><br><strong>Investigating</strong> -
  Only a subset of users appear to be impacted by the issue with Edge Function deployments. We are investigating the root cause..</p>
<p><small>Jul <var data-var='date'> 30</var>, <var data-var='time'>17:37:45</var> GMT+0</small><br><strong>Investigating</strong> -
  We are aware of some users experiencing issues with Edge Function deployments..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 30 Jul 2026 17:37:44 +0000</pubDate>
  <link>https://status.frameworkpm.io/incident/cmt0roo9c1k2e0rmgbi6pn1o4</link>
  <guid>https://status.frameworkpm.io/incident/cmt0roo9c1k2e0rmgbi6pn1o4</guid>
</item>

<item>
  <title>SSO login failures in us-east-1</title>
  <description>
    Type: Incident
    Duration: 1 day, 18 hours and 41 minutes

    Affected Components: Supabase → Auth
    Jul 28, 22:07:03 GMT+0 - Resolved - The issue has been resolved. SSO login functionality in the us-east-1 region has returned to normal, and all services are operating as expected. Jul 28, 21:53:44 GMT+0 - Monitoring - We have rolled out a fix for the SSO login failures affecting the us-east-1 region. We are monitoring the results and will continue to observe the service to ensure stability before resolving the incident. Jul 28, 21:33:28 GMT+0 - Identified - We have identified the cause of the SSO login failures affecting the us-east-1 region and are working to implement a fix. We will continue to provide updates as progress is made. Jul 28, 21:24:22 GMT+0 - Investigating - We are investigating an issue causing SSO login failures in the us-east-1 region. Our team is actively investigating the cause and will provide updates as more information becomes available. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 18 hours and 41 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>22:07:03</var> GMT+0</small><br><strong>Resolved</strong> -
  The issue has been resolved. SSO login functionality in the us-east-1 region has returned to normal, and all services are operating as expected..</p>
<p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>21:53:44</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have rolled out a fix for the SSO login failures affecting the us-east-1 region. We are monitoring the results and will continue to observe the service to ensure stability before resolving the incident..</p>
<p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>21:33:28</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the cause of the SSO login failures affecting the us-east-1 region and are working to implement a fix. We will continue to provide updates as progress is made..</p>
<p><small>Jul <var data-var='date'> 28</var>, <var data-var='time'>21:24:22</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating an issue causing SSO login failures in the us-east-1 region. Our team is actively investigating the cause and will provide updates as more information becomes available..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 28 Jul 2026 21:24:22 +0000</pubDate>
  <link>https://status.frameworkpm.io/incident/cmt0rowa91l5w0rmggd9ja7uh</link>
  <guid>https://status.frameworkpm.io/incident/cmt0rowa91l5w0rmggd9ja7uh</guid>
</item>

<item>
  <title>Delays in creation of DNS records</title>
  <description>
    Type: Incident
    Duration: 5 days, 1 hour and 49 minutes

    Affected Components: Supabase → Database, Supabase → API Gateway
    Jul 27, 22:36:44 GMT+0 - Resolved - This incident is resolved. DNS creation for new projects has been fixed since 20:35 UTC. Backfill of missing DNS records has been completed at 22:20 UTC. Please contact Support if your project seems impacted by missing DNS records. Jul 27, 22:23:08 GMT+0 - Monitoring - All failed DNS creation has been backfilled, and customers should no longer see missing DNS records in their projects. DNS record creation and latency have returned to normal levels. We will continue to monitor before resolving this incident. Jul 27, 20:53:39 GMT+0 - Identified - We have identified and mitigated the issue that was blocking DNS updates. DNS record creation is succeeding, and latency has returned to normal levels. A subset of projects that encountered provisioning failures during the incident will require DNS records to be backfilled, and we are actively remediating these affected projects. Jul 27, 20:39:48 GMT+0 - Identified - We have identified the cause of delays in DNS records creation and are actively working on a fix. We will continue to provide updates as things progress. Jul 27, 20:34:54 GMT+0 - Investigating - We are investigating failures in provisioning DNS records for projects, there may be delays in creation of DNS records for new or unpaused projects. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 5 days, 1 hour and 49 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>22:36:44</var> GMT+0</small><br><strong>Resolved</strong> -
  This incident is resolved. DNS creation for new projects has been fixed since 20:35 UTC. Backfill of missing DNS records has been completed at 22:20 UTC. Please contact Support if your project seems impacted by missing DNS records..</p>
<p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>22:23:08</var> GMT+0</small><br><strong>Monitoring</strong> -
  All failed DNS creation has been backfilled, and customers should no longer see missing DNS records in their projects. DNS record creation and latency have returned to normal levels. We will continue to monitor before resolving this incident..</p>
<p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>20:53:39</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified and mitigated the issue that was blocking DNS updates. DNS record creation is succeeding, and latency has returned to normal levels. A subset of projects that encountered provisioning failures during the incident will require DNS records to be backfilled, and we are actively remediating these affected projects..</p>
<p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>20:39:48</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the cause of delays in DNS records creation and are actively working on a fix. We will continue to provide updates as things progress..</p>
<p><small>Jul <var data-var='date'> 27</var>, <var data-var='time'>20:34:54</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating failures in provisioning DNS records for projects, there may be delays in creation of DNS records for new or unpaused projects..</p>
]]>
  </content:encoded>
  <pubDate>Mon, 27 Jul 2026 20:34:54 +0000</pubDate>
  <link>https://status.frameworkpm.io/incident/cmt0rowa21l530rmgayeasdjd</link>
  <guid>https://status.frameworkpm.io/incident/cmt0rowa21l530rmgayeasdjd</guid>
</item>

<item>
  <title>Authentication issues for some projects</title>
  <description>
    Type: Incident
    Duration: 1 day, 10 hours and 48 minutes

    Affected Components: Supabase → Auth
    Jul 25, 14:45:52 GMT+0 - Resolved - Authentication operations have returned to normal consistently. Jul 25, 14:25:27 GMT+0 - Monitoring - Authentication has returned to normal. Jul 25, 14:21:05 GMT+0 - Identified - We have implemented a fix to the authentication issue and are monitoring for recovery. Jul 25, 14:11:04 GMT+0 - Investigating - Some projects are experiencing authentication issues. We are actively investigating. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 1 day, 10 hours and 48 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 25</var>, <var data-var='time'>14:45:52</var> GMT+0</small><br><strong>Resolved</strong> -
  Authentication operations have returned to normal consistently..</p>
<p><small>Jul <var data-var='date'> 25</var>, <var data-var='time'>14:25:27</var> GMT+0</small><br><strong>Monitoring</strong> -
  Authentication has returned to normal..</p>
<p><small>Jul <var data-var='date'> 25</var>, <var data-var='time'>14:21:05</var> GMT+0</small><br><strong>Identified</strong> -
  We have implemented a fix to the authentication issue and are monitoring for recovery..</p>
<p><small>Jul <var data-var='date'> 25</var>, <var data-var='time'>14:11:04</var> GMT+0</small><br><strong>Investigating</strong> -
  Some projects are experiencing authentication issues. We are actively investigating..</p>
]]>
  </content:encoded>
  <pubDate>Sat, 25 Jul 2026 14:11:04 +0000</pubDate>
  <link>https://status.frameworkpm.io/incident/cmt0rowa71l5n0rmg7pv4csb1</link>
  <guid>https://status.frameworkpm.io/incident/cmt0rowa71l5n0rmg7pv4csb1</guid>
</item>

<item>
  <title>Project Actions Failing Across Multiple Regions</title>
  <description>
    Type: Incident
    Duration: 19 days, 15 hours and 46 minutes

    Affected Components: Supabase → Database
    Jul 18, 01:41:45 GMT+0 - Resolved - Project actions have been sustained at normal performance. This incident is resolved. Jul 17, 20:21:37 GMT+0 - Monitoring - The mitigation has returned project activity to normal performance. Project actions that failed during the outage are being requeued to run. We will continue to monitor to ensure project functionality. Jul 17, 19:45:29 GMT+0 - Identified - We have identified a problem with a specific job in us-east-1, we have mitigated the job and are observing the results. Jul 17, 19:20:33 GMT+0 - Investigating - We are testing mitigation options to attempt to restore project action performance. Jul 17, 18:47:55 GMT+0 - Investigating - We have determined that there are four main project actions impacted in the identified regions: Pause/unpause failures, Restore/PITR failures, PITR configuration failures and Backup problems. We are pursuing root cause and mitigation options in parallel. Jul 17, 18:16:46 GMT+0 - Investigating - Project actions in us-east-1, us-east-2, sa-east-1, ca-central-1 are experiencing significant increases in error rates. We are exploring the best options for restoring performance. Jul 17, 17:49:58 GMT+0 - Investigating - Certain project actions are failing. We are actively investigating to determine the regions impacted and source of the issue. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 19 days, 15 hours and 46 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 18</var>, <var data-var='time'>01:41:45</var> GMT+0</small><br><strong>Resolved</strong> -
  Project actions have been sustained at normal performance. This incident is resolved..</p>
<p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>20:21:37</var> GMT+0</small><br><strong>Monitoring</strong> -
  The mitigation has returned project activity to normal performance. Project actions that failed during the outage are being requeued to run. We will continue to monitor to ensure project functionality..</p>
<p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>19:45:29</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified a problem with a specific job in us-east-1, we have mitigated the job and are observing the results..</p>
<p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>19:20:33</var> GMT+0</small><br><strong>Investigating</strong> -
  We are testing mitigation options to attempt to restore project action performance..</p>
<p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>18:47:55</var> GMT+0</small><br><strong>Investigating</strong> -
  We have determined that there are four main project actions impacted in the identified regions: Pause/unpause failures, Restore/PITR failures, PITR configuration failures and Backup problems. We are pursuing root cause and mitigation options in parallel..</p>
<p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>18:16:46</var> GMT+0</small><br><strong>Investigating</strong> -
  Project actions in us-east-1, us-east-2, sa-east-1, ca-central-1 are experiencing significant increases in error rates. We are exploring the best options for restoring performance..</p>
<p><small>Jul <var data-var='date'> 17</var>, <var data-var='time'>17:49:58</var> GMT+0</small><br><strong>Investigating</strong> -
  Certain project actions are failing. We are actively investigating to determine the regions impacted and source of the issue..</p>
]]>
  </content:encoded>
  <pubDate>Fri, 17 Jul 2026 17:49:58 +0000</pubDate>
  <link>https://status.frameworkpm.io/incident/cmt0rowa71l5p0rmg4va7w0ri</link>
  <guid>https://status.frameworkpm.io/incident/cmt0rowa71l5p0rmg4va7w0ri</guid>
</item>

<item>
  <title>Elevated JWT authorization errors</title>
  <description>
    Type: Incident
    Duration: 3 days, 7 hours and 56 minutes

    Affected Components: Supabase → Edge Functions
    Jul 8, 19:57:48 GMT+0 - Resolved - Edge function operations are normal. Jul 8, 19:28:06 GMT+0 - Monitoring - A rollback mitigation implemented by our team has addressed the problem. Edge functions have returned to normal. We will continue to monitor performance. Jul 8, 19:16:17 GMT+0 - Identified - We have identified likely reasons for the problem and are investigating options for resolution. We advise all customers to ensure they are using valid JWT keys with their projects. Jul 8, 18:37:52 GMT+0 - Investigating - We are aware of reports of elevated legacy JWT authorization errors on edge functions in some regions 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days, 7 hours and 56 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>19:57:48</var> GMT+0</small><br><strong>Resolved</strong> -
  Edge function operations are normal..</p>
<p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>19:28:06</var> GMT+0</small><br><strong>Monitoring</strong> -
  A rollback mitigation implemented by our team has addressed the problem. Edge functions have returned to normal. We will continue to monitor performance..</p>
<p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>19:16:17</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified likely reasons for the problem and are investigating options for resolution. We advise all customers to ensure they are using valid JWT keys with their projects..</p>
<p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>18:37:52</var> GMT+0</small><br><strong>Investigating</strong> -
  We are aware of reports of elevated legacy JWT authorization errors on edge functions in some regions.</p>
]]>
  </content:encoded>
  <pubDate>Wed, 8 Jul 2026 18:37:52 +0000</pubDate>
  <link>https://status.frameworkpm.io/incident/cmt0rp4me1lym0rmgz895toxl</link>
  <guid>https://status.frameworkpm.io/incident/cmt0rp4me1lym0rmgz895toxl</guid>
</item>

<item>
  <title>Functions management API is returning 500s for multiple function operations</title>
  <description>
    Type: Incident
    Duration: 3 days, 19 hours and 40 minutes

    Affected Components: Supabase → Edge Functions
    Jul 1, 16:12:21 GMT+0 - Resolved - Edge Function API requests have returned to normal. This issue is now resolved. Jul 1, 15:30:50 GMT+0 - Monitoring - We have implemented a fix, and error rates have returned to expected levels.
We are continuing to monitor the platform closely to ensure the issue is fully resolved. Jul 1, 14:59:10 GMT+0 - Identified - The team has identified the root cause of the issue and is currently rolling out a fix across the platform.
We will continue to monitor the rollout and provide another update once it has been completed. Jul 1, 14:40:41 GMT+0 - Investigating - We are currently investigating an issue affecting the Edge Function API requests.
Our team is working on a fix, and we will provide another update as soon as more information becomes available. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days, 19 hours and 40 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>16:12:21</var> GMT+0</small><br><strong>Resolved</strong> -
  Edge Function API requests have returned to normal. This issue is now resolved..</p>
<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>15:30:50</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have implemented a fix, and error rates have returned to expected levels.
We are continuing to monitor the platform closely to ensure the issue is fully resolved..</p>
<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>14:59:10</var> GMT+0</small><br><strong>Identified</strong> -
  The team has identified the root cause of the issue and is currently rolling out a fix across the platform.
We will continue to monitor the rollout and provide another update once it has been completed..</p>
<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>14:40:41</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating an issue affecting the Edge Function API requests.
Our team is working on a fix, and we will provide another update as soon as more information becomes available..</p>
]]>
  </content:encoded>
  <pubDate>Wed, 1 Jul 2026 14:40:41 +0000</pubDate>
  <link>https://status.frameworkpm.io/incident/cmt0rp4zy1m2d0rmgrmny2ffc</link>
  <guid>https://status.frameworkpm.io/incident/cmt0rp4zy1m2d0rmgrmny2ffc</guid>
</item>

<item>
  <title>Project status change failures in multiple regions</title>
  <description>
    Type: Incident
    Duration: 22 days, 3 hours and 31 minutes

    Affected Components: Supabase → Compute
    Jul 13, 16:00:12 GMT+0 - Resolved - Capacity availability and project creation, resize, and restart operations have returned to normal and have remained stable for an extended period of time. We are resolving this incident.

Out of an abundance of caution, and out of respect for the impact this incident had for our users, we held the incident open for a considerable amount of time after the observed impact was mitigated. We wanted to be certain any residual potential impact was fully cleared before formally resolving the statuspage. Jul 10, 18:41:44 GMT+0 - Monitoring - We continue to monitor capacity across all regions.

The additional mitigations and machine types available to all Postgres versions are contributing to capacity stability. We continue to work to improve our resiliency.

We will continue monitoring closely to ensure ongoing work is effective and we don&#039;t have any re-occurrence of these or similar issues before we resolve this entirely. Jul 8, 16:41:39 GMT+0 - Monitoring - We continue to monitor capacity recovery across all regions. 

We have added additional mitigations and machine types available to all Postgres versions, and we are also seeing error rates for these users stabilize. While there is still ongoing work behind the scenes to continue to improve our resiliency, users should no longer be affected by capacity issues stemming from this incident. We are showing stable capacity across all regions on all machine sizes and types.

We will be monitoring this thru the rest of the week to ensure ongoing work is effective and we don&#039;t have any re-occurrence of these or similar issues before we resolve this entirely. Jul 6, 16:36:49 GMT+0 - Monitoring - Capacity has continued to recover across all regions, and the large majority of restart, resize, and project-creation operations are now completing normally. We are continuing to monitor the system.

We have added additional mitigations and machine types available to all Postgres versions, and we are also seeing error rates for these users stabilize. While there is still ongoing work behind the scenes to continue to improve our resiliency, users should no longer be affected by capacity issues stemming from this incident. We are showing stable capacity across all regions on all machine sizes and types.

We will be monitoring this for the next day or two at least just to ensure the ongoing work is effective and we don&#039;t have any re-occurrence of these or similar issues before we resolve this entirely.

If you continue to receive errors relating to capacity, please notify our support team via https://supabase.help and reference this status page. Jul 6, 11:32:36 GMT+0 - Identified - Capacity has continued to recover across all regions, and the large majority of restart, resize, and project-creation operations are now completing normally. We are continuing to monitor the system.

The remaining impact is limited to projects running a Postgres version older than 17.6.1.121. These older versions can only run on a narrower set of instance types, which are the ones still under capacity pressure, so a restart or resize may fail or need a retry. Projects on 17.6.1.121 or newer can run on a wider set of instance types and are much less likely to be affected.

If a restart or resize is failing, upgrading to Postgres 17.6.1.121 or newer resolves it in most cases. You can check your current version and start an upgrade from your project&#039;s infrastructure settings here: https://supabase.com/dashboard/project/_/settings/infrastructure
If you&#039;re still unable to resize or restart after upgrading, our support team can help.

We will update this page as the situation materially changes. Jul 4, 22:40:14 GMT+0 - Identified - We are continuing to monitor available capacity in all regions.

If your project is on a version older than Postgres 17.6.1.121, upgrading to 17.6.1.121 and above will grant access to additional machine types, which improves the likelihood of a successful restart or resize. You can check your current version and start an upgrade from your project&#039;s infrastructure settings here: https://supabase.com/dashboard/project/_/settings/infrastructure

If your project is affected and you&#039;re unable to resize or restart, our support team can help.

We&#039;ll update this page as the situation materially changes. Jul 4, 04:34:48 GMT+0 - Identified - Update - Availability for smaller compute sizes has improved across most regions, and error rates are trending down. We are continuing to monitor available capacity in all regions.

If your project is on a version older than Postgres 17.6.1.121, upgrading to 17.6.1.121 and above will grant access to additional machine types, which improves the likelihood of a successful restart or resize. You can check your current version and start an upgrade from your project&#039;s infrastructure settings here: https://supabase.com/dashboard/project/_/settings/infrastructure

If your project is affected and you&#039;re unable to resize or restart, our support team can help.

We&#039;ll update this page as the situation materially changes. Jul 3, 19:57:30 GMT+0 - Identified - We&#039;re continuing to work through elevated capacity errors affecting some restart and resize operations. Availability for smaller compute sizes has improved across most regions, and error rates are trending down.

Capacity for some smaller compute sizes remains constrained in a number of regions, most notably Medium. We are actively adding capacity across all regions to relieve this.

If your project is on Postgres 17.6.1.121 or earlier, upgrading to 17.6.1.121 or higher gives it access to additional machine types, which improves the likelihood of a successful restart or resize in affected regions. You can check your current version and start an upgrade from your project&#039;s infrastructure settings: https://supabase.com/dashboard/project/_/settings/infrastructure

If your project is affected and you&#039;re unable to resize or restart, our support team can help.

We&#039;ll update this page as the situation materially changes. Jul 3, 16:03:14 GMT+0 - Identified - Capacity is currently available across all regions, and we are continuing to progress the remaining mitigation work, including bringing additional capacity online. This remains our highest priority.

We have recovered most projects that were unavailable due to infrastructure compatibility constraints. Our team is continuing to restore the remaining affected projects and will provide further updates as this work progresses.
The remaining impact is primarily limited to Medium instances running PostgreSQL versions earlier than 17.6.1.121. 
New project deployments should succeed, but restarts or resizes for projects matching this profile may fail.

Existing projects are not affected unless they have been restarted or resized during this incident. Jul 3, 09:43:42 GMT+0 - Identified - We currently have capacity available across all regions and are continuing to make progress on our remaining mitigation work, primarily by bringing additional capacity online. This is currently our top priority. 

We are also recovering a subset of projects which are still down due to infrastructure compatibility constraints. Our team is continuing to restore these remaining affected projects and will provide further updates as this work progresses.

This issue does not affect existing projects or their availability unless the instance has undergone restarts or resizes while the incident has been in progress. Jul 2, 15:08:17 GMT+0 - Identified - We continue to see capacity improvements across all regions and have implemented mitigation measures to sustain capacity. Project creation, resizing, restarts, and branch operations are continuing to recover, and we ask users to retry their database actions. Please reach out to our support if you continue to see failures.

We are working to recover subset of projects which are still down due to infrastructure compatibility constraints. Our team is actively working on solutions to restore these remaining affected projects and will provide further updates as this work progresses.

This issue does not affect existing projects or their availability unless the instance has undergone restarts or resizes while the incident has been in progress. Jul 2, 10:40:45 GMT+0 - Identified - We continue to see capacity improvements across all regions and have implemented mitigation measures to sustain capacity. Project creation, resizing, restarts, branch revisioning, and restores are continuing to recover, and we ask users to retry their database actions. Please reach out to our support if you continue to see failures.

Our team is actively working to restore the remaining affected projects. We will provide further updates as this work progresses.

This issue does not affect existing projects or their availability unless the instance has undergone restarts with stores or database upgrades while the incident has been in progress Jul 2, 05:53:07 GMT+0 - Identified - We are seeing capacity improvements across all regions, but are continuing to work on a full mitigation for all users. Project creation, project resizing, project restarts, branch provisioning, and restores are slowly recovering and we are asking users to re-try their database actions. Please reach out to our Support if you continue to fail.

Running projects are unaffected and stay available. The issue has only surfaced during a restart, restore, or database upgrade.

We are still addressing an issue with Read Replicas and continuing to increase capacity to restore normal service in full with highest priority. Jul 2, 01:30:02 GMT+0 - Identified - We continue to experience widespread capacity constraints across most regions, affecting project creation, project resizing, project restarts, branch provisioning, and restores. As a result, some users may experience repeated failures when attempting these operations.

Our team is actively implementing mitigation measures to increase capacity and restore normal service. 
We will provide further updates as the situation evolves.

If you&#039;re attempting to create a new project, we recommend waiting until the incident has progressed and the status page indicates that additional capacity has been made available before retrying.

This issue does not affect existing projects or their availability unless the instance undergoes restarts, restores, or database upgrades. Jul 1, 16:58:37 GMT+0 - Identified - We continue to experience widespread capacity constraints across most regions, affecting project creation, project resizing, project restarts, branch provisioning, and restores. As a result, some users may experience repeated failures when attempting these operations.

Our team is actively implementing mitigation measures to increase capacity and restore normal service. 
We will provide further updates as the situation evolves.

If you&#039;re attempting to create a new project, we recommend waiting until the incident has progressed and the status page indicates that additional capacity has been made available before retrying.
This issue does not affect existing running projects or their availability. Jul 1, 10:12:44 GMT+0 - Identified - We continue to experience intermittent capacity related issues across all regions, impacting operations such as project creation, project resizing, branch provisioning, and project restarts.
These operations may fail intermittently or require one or more retries to complete successfully.
Our team is actively investigating ways to improve the situation and is implementing a number of mitigation measures to reduce the impact on affected operations.
We will provide another update as soon as more information becomes available. Jul 1, 03:23:43 GMT+0 - Identified - We are continuing to remediate the capacity constraints affecting multiple regions (ap-northeast-1, ap-northeast-2, ap-south-1, ap-southeast-1, ap-southeast-2, eu-central-2, eu-north-1, sa-east-1, us-east-1, us-east-2). 

Project operations that require capacity in these regions may continue to fail or require a re-try. We will provide another update as soon as more information is available. Jun 30, 22:22:56 GMT+0 - Identified - We are continuing to investigate the remaining capacity constraints affecting ap-northeast-2, ap-south-1, and eu-north-1. Project operations that require capacity in these regions may continue to fail. We will provide another update as soon as more information is available. Jun 30, 18:58:41 GMT+0 - Identified - We are continuing to investigate the remaining capacity constraints affecting ap-northeast-2, ap-south-1, and eu-north-1. Project operations that require capacity in these regions may continue to fail. We will provide another update as soon as more information is available. Jun 30, 11:20:04 GMT+0 - Identified - Additional capacity has been made available in the majority of regions, and we&#039;re seeing reduced failure rates in terms of project creation, project resizing, branch provisioning, and project restarts.
We are still experiencing limited instance capacity in ap-northeast-2, ap-south-1, and eu-north-1. 
As a result, project operations that require capacity in these regions, including project creation, resizing, branch provisioning, restarts, may continue to fail.
We are actively working to restore full capacity and will provide another update as soon as more information is available. Jun 30, 06:49:02 GMT+0 - Identified - We are still working to resolve the issue affecting project creation, project resizing, branch provisioning, and project restarts across multiple regions. We will continue to provide updates as our work progresses. Jun 30, 05:11:59 GMT+0 - Identified - We are still working to resolve the issue affecting project creation, project resizing, branch provisioning, and project restarts across multiple regions. We will continue to provide updates as our work progresses. Jun 30, 04:32:20 GMT+0 - Identified - We are continuing to work on a fix for the issue and will provide updates as more information is available. Jun 30, 03:38:57 GMT+0 - Identified - We have identified the issue and are working on a fix. Impact is currently affecting project creation, project resizing, branch provisioning, and project restarts across multiple regions. We will provide another update as soon as we have more information. Jun 30, 03:08:41 GMT+0 - Investigating - We have identified the issue and confirmed that impact extends beyond project creation. Project creation, project resizing, branch provisioning, and project restarts are currently affected across multiple regions. We will share another update as soon as we have more information. Jun 30, 02:43:49 GMT+0 - Investigating - Project creation is impacted across multiple regions, we are investigating the root cause. Jun 30, 02:38:13 GMT+0 - Investigating - We are currently investigating an issue affecting project creation in multiple regions. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 22 days, 3 hours and 31 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jul <var data-var='date'> 13</var>, <var data-var='time'>16:00:12</var> GMT+0</small><br><strong>Resolved</strong> -
  Capacity availability and project creation, resize, and restart operations have returned to normal and have remained stable for an extended period of time. We are resolving this incident.

Out of an abundance of caution, and out of respect for the impact this incident had for our users, we held the incident open for a considerable amount of time after the observed impact was mitigated. We wanted to be certain any residual potential impact was fully cleared before formally resolving the statuspage..</p>
<p><small>Jul <var data-var='date'> 10</var>, <var data-var='time'>18:41:44</var> GMT+0</small><br><strong>Monitoring</strong> -
  We continue to monitor capacity across all regions.

The additional mitigations and machine types available to all Postgres versions are contributing to capacity stability. We continue to work to improve our resiliency.

We will continue monitoring closely to ensure ongoing work is effective and we don&#039;t have any re-occurrence of these or similar issues before we resolve this entirely..</p>
<p><small>Jul <var data-var='date'> 8</var>, <var data-var='time'>16:41:39</var> GMT+0</small><br><strong>Monitoring</strong> -
  We continue to monitor capacity recovery across all regions. 

We have added additional mitigations and machine types available to all Postgres versions, and we are also seeing error rates for these users stabilize. While there is still ongoing work behind the scenes to continue to improve our resiliency, users should no longer be affected by capacity issues stemming from this incident. We are showing stable capacity across all regions on all machine sizes and types.

We will be monitoring this thru the rest of the week to ensure ongoing work is effective and we don&#039;t have any re-occurrence of these or similar issues before we resolve this entirely..</p>
<p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>16:36:49</var> GMT+0</small><br><strong>Monitoring</strong> -
  Capacity has continued to recover across all regions, and the large majority of restart, resize, and project-creation operations are now completing normally. We are continuing to monitor the system.

We have added additional mitigations and machine types available to all Postgres versions, and we are also seeing error rates for these users stabilize. While there is still ongoing work behind the scenes to continue to improve our resiliency, users should no longer be affected by capacity issues stemming from this incident. We are showing stable capacity across all regions on all machine sizes and types.

We will be monitoring this for the next day or two at least just to ensure the ongoing work is effective and we don&#039;t have any re-occurrence of these or similar issues before we resolve this entirely.

If you continue to receive errors relating to capacity, please notify our support team via https://supabase.help and reference this status page..</p>
<p><small>Jul <var data-var='date'> 6</var>, <var data-var='time'>11:32:36</var> GMT+0</small><br><strong>Identified</strong> -
  Capacity has continued to recover across all regions, and the large majority of restart, resize, and project-creation operations are now completing normally. We are continuing to monitor the system.

The remaining impact is limited to projects running a Postgres version older than 17.6.1.121. These older versions can only run on a narrower set of instance types, which are the ones still under capacity pressure, so a restart or resize may fail or need a retry. Projects on 17.6.1.121 or newer can run on a wider set of instance types and are much less likely to be affected.

If a restart or resize is failing, upgrading to Postgres 17.6.1.121 or newer resolves it in most cases. You can check your current version and start an upgrade from your project&#039;s infrastructure settings here: https://supabase.com/dashboard/project/_/settings/infrastructure
If you&#039;re still unable to resize or restart after upgrading, our support team can help.

We will update this page as the situation materially changes..</p>
<p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>22:40:14</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to monitor available capacity in all regions.

If your project is on a version older than Postgres 17.6.1.121, upgrading to 17.6.1.121 and above will grant access to additional machine types, which improves the likelihood of a successful restart or resize. You can check your current version and start an upgrade from your project&#039;s infrastructure settings here: https://supabase.com/dashboard/project/_/settings/infrastructure

If your project is affected and you&#039;re unable to resize or restart, our support team can help.

We&#039;ll update this page as the situation materially changes..</p>
<p><small>Jul <var data-var='date'> 4</var>, <var data-var='time'>04:34:48</var> GMT+0</small><br><strong>Identified</strong> -
  Update - Availability for smaller compute sizes has improved across most regions, and error rates are trending down. We are continuing to monitor available capacity in all regions.

If your project is on a version older than Postgres 17.6.1.121, upgrading to 17.6.1.121 and above will grant access to additional machine types, which improves the likelihood of a successful restart or resize. You can check your current version and start an upgrade from your project&#039;s infrastructure settings here: https://supabase.com/dashboard/project/_/settings/infrastructure

If your project is affected and you&#039;re unable to resize or restart, our support team can help.

We&#039;ll update this page as the situation materially changes..</p>
<p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>19:57:30</var> GMT+0</small><br><strong>Identified</strong> -
  We&#039;re continuing to work through elevated capacity errors affecting some restart and resize operations. Availability for smaller compute sizes has improved across most regions, and error rates are trending down.

Capacity for some smaller compute sizes remains constrained in a number of regions, most notably Medium. We are actively adding capacity across all regions to relieve this.

If your project is on Postgres 17.6.1.121 or earlier, upgrading to 17.6.1.121 or higher gives it access to additional machine types, which improves the likelihood of a successful restart or resize in affected regions. You can check your current version and start an upgrade from your project&#039;s infrastructure settings: https://supabase.com/dashboard/project/_/settings/infrastructure

If your project is affected and you&#039;re unable to resize or restart, our support team can help.

We&#039;ll update this page as the situation materially changes..</p>
<p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>16:03:14</var> GMT+0</small><br><strong>Identified</strong> -
  Capacity is currently available across all regions, and we are continuing to progress the remaining mitigation work, including bringing additional capacity online. This remains our highest priority.

We have recovered most projects that were unavailable due to infrastructure compatibility constraints. Our team is continuing to restore the remaining affected projects and will provide further updates as this work progresses.
The remaining impact is primarily limited to Medium instances running PostgreSQL versions earlier than 17.6.1.121. 
New project deployments should succeed, but restarts or resizes for projects matching this profile may fail.

Existing projects are not affected unless they have been restarted or resized during this incident..</p>
<p><small>Jul <var data-var='date'> 3</var>, <var data-var='time'>09:43:42</var> GMT+0</small><br><strong>Identified</strong> -
  We currently have capacity available across all regions and are continuing to make progress on our remaining mitigation work, primarily by bringing additional capacity online. This is currently our top priority. 

We are also recovering a subset of projects which are still down due to infrastructure compatibility constraints. Our team is continuing to restore these remaining affected projects and will provide further updates as this work progresses.

This issue does not affect existing projects or their availability unless the instance has undergone restarts or resizes while the incident has been in progress..</p>
<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>15:08:17</var> GMT+0</small><br><strong>Identified</strong> -
  We continue to see capacity improvements across all regions and have implemented mitigation measures to sustain capacity. Project creation, resizing, restarts, and branch operations are continuing to recover, and we ask users to retry their database actions. Please reach out to our support if you continue to see failures.

We are working to recover subset of projects which are still down due to infrastructure compatibility constraints. Our team is actively working on solutions to restore these remaining affected projects and will provide further updates as this work progresses.

This issue does not affect existing projects or their availability unless the instance has undergone restarts or resizes while the incident has been in progress..</p>
<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>10:40:45</var> GMT+0</small><br><strong>Identified</strong> -
  We continue to see capacity improvements across all regions and have implemented mitigation measures to sustain capacity. Project creation, resizing, restarts, branch revisioning, and restores are continuing to recover, and we ask users to retry their database actions. Please reach out to our support if you continue to see failures.

Our team is actively working to restore the remaining affected projects. We will provide further updates as this work progresses.

This issue does not affect existing projects or their availability unless the instance has undergone restarts with stores or database upgrades while the incident has been in progress.</p>
<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>05:53:07</var> GMT+0</small><br><strong>Identified</strong> -
  We are seeing capacity improvements across all regions, but are continuing to work on a full mitigation for all users. Project creation, project resizing, project restarts, branch provisioning, and restores are slowly recovering and we are asking users to re-try their database actions. Please reach out to our Support if you continue to fail.

Running projects are unaffected and stay available. The issue has only surfaced during a restart, restore, or database upgrade.

We are still addressing an issue with Read Replicas and continuing to increase capacity to restore normal service in full with highest priority..</p>
<p><small>Jul <var data-var='date'> 2</var>, <var data-var='time'>01:30:02</var> GMT+0</small><br><strong>Identified</strong> -
  We continue to experience widespread capacity constraints across most regions, affecting project creation, project resizing, project restarts, branch provisioning, and restores. As a result, some users may experience repeated failures when attempting these operations.

Our team is actively implementing mitigation measures to increase capacity and restore normal service. 
We will provide further updates as the situation evolves.

If you&#039;re attempting to create a new project, we recommend waiting until the incident has progressed and the status page indicates that additional capacity has been made available before retrying.

This issue does not affect existing projects or their availability unless the instance undergoes restarts, restores, or database upgrades..</p>
<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>16:58:37</var> GMT+0</small><br><strong>Identified</strong> -
  We continue to experience widespread capacity constraints across most regions, affecting project creation, project resizing, project restarts, branch provisioning, and restores. As a result, some users may experience repeated failures when attempting these operations.

Our team is actively implementing mitigation measures to increase capacity and restore normal service. 
We will provide further updates as the situation evolves.

If you&#039;re attempting to create a new project, we recommend waiting until the incident has progressed and the status page indicates that additional capacity has been made available before retrying.
This issue does not affect existing running projects or their availability..</p>
<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>10:12:44</var> GMT+0</small><br><strong>Identified</strong> -
  We continue to experience intermittent capacity related issues across all regions, impacting operations such as project creation, project resizing, branch provisioning, and project restarts.
These operations may fail intermittently or require one or more retries to complete successfully.
Our team is actively investigating ways to improve the situation and is implementing a number of mitigation measures to reduce the impact on affected operations.
We will provide another update as soon as more information becomes available..</p>
<p><small>Jul <var data-var='date'> 1</var>, <var data-var='time'>03:23:43</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to remediate the capacity constraints affecting multiple regions (ap-northeast-1, ap-northeast-2, ap-south-1, ap-southeast-1, ap-southeast-2, eu-central-2, eu-north-1, sa-east-1, us-east-1, us-east-2). 

Project operations that require capacity in these regions may continue to fail or require a re-try. We will provide another update as soon as more information is available..</p>
<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>22:22:56</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to investigate the remaining capacity constraints affecting ap-northeast-2, ap-south-1, and eu-north-1. Project operations that require capacity in these regions may continue to fail. We will provide another update as soon as more information is available..</p>
<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>18:58:41</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to investigate the remaining capacity constraints affecting ap-northeast-2, ap-south-1, and eu-north-1. Project operations that require capacity in these regions may continue to fail. We will provide another update as soon as more information is available..</p>
<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>11:20:04</var> GMT+0</small><br><strong>Identified</strong> -
  Additional capacity has been made available in the majority of regions, and we&#039;re seeing reduced failure rates in terms of project creation, project resizing, branch provisioning, and project restarts.
We are still experiencing limited instance capacity in ap-northeast-2, ap-south-1, and eu-north-1. 
As a result, project operations that require capacity in these regions, including project creation, resizing, branch provisioning, restarts, may continue to fail.
We are actively working to restore full capacity and will provide another update as soon as more information is available..</p>
<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>06:49:02</var> GMT+0</small><br><strong>Identified</strong> -
  We are still working to resolve the issue affecting project creation, project resizing, branch provisioning, and project restarts across multiple regions. We will continue to provide updates as our work progresses..</p>
<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>05:11:59</var> GMT+0</small><br><strong>Identified</strong> -
  We are still working to resolve the issue affecting project creation, project resizing, branch provisioning, and project restarts across multiple regions. We will continue to provide updates as our work progresses..</p>
<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>04:32:20</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work on a fix for the issue and will provide updates as more information is available..</p>
<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>03:38:57</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the issue and are working on a fix. Impact is currently affecting project creation, project resizing, branch provisioning, and project restarts across multiple regions. We will provide another update as soon as we have more information..</p>
<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>03:08:41</var> GMT+0</small><br><strong>Investigating</strong> -
  We have identified the issue and confirmed that impact extends beyond project creation. Project creation, project resizing, branch provisioning, and project restarts are currently affected across multiple regions. We will share another update as soon as we have more information..</p>
<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>02:43:49</var> GMT+0</small><br><strong>Investigating</strong> -
  Project creation is impacted across multiple regions, we are investigating the root cause..</p>
<p><small>Jun <var data-var='date'> 30</var>, <var data-var='time'>02:38:13</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating an issue affecting project creation in multiple regions..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 30 Jun 2026 03:08:41 +0000</pubDate>
  <link>https://status.frameworkpm.io/incident/cmt0rp4mv1lyu0rmg3lpudvqm</link>
  <guid>https://status.frameworkpm.io/incident/cmt0rp4mv1lyu0rmg3lpudvqm</guid>
</item>

<item>
  <title>Upgrade Failures</title>
  <description>
    Type: Incident
    Duration: 11 days, 7 hours and 8 minutes

    Affected Components: Supabase → Database
    Jun 25, 18:51:40 GMT+0 - Resolved - Through our monitoring, we have determined that project upgrade behavior has returned to normal across the fleet. This incident is resolved. Jun 25, 18:08:06 GMT+0 - Monitoring - We have implemented all necessary mitigations and the project upgrade rates have returned to normal across the fleet. We will continue to monitor these flows for any irregularities or recurring degradation. If you are still experiencing delayed or blocked upgrades on your Project, please contact Support. Jun 25, 17:46:27 GMT+0 - Identified - We are starting to notice improvements as a result of our mitigation efforts, and expect that project upgrades should start to become less delayed. We’ll continue monitoring and will update as we observe improvements across the fleet. Jun 25, 17:03:54 GMT+0 - Identified - We are continuing our operational and investigative work to  improve upgrade flow performance and mitigate further problems. Jun 25, 16:27:00 GMT+0 - Identified - We are implementing operational mitigations to try to improve upgrade performance. Jun 25, 16:03:11 GMT+0 - Identified - We are continuing to work through a variety of options for improving upgrade performance. This includes working with our upstream provider and adjusting operational parameters. Jun 25, 15:32:53 GMT+0 - Identified - We are aware that upgrades continue to be delayed. We are exploring other factors that are contributing to the slow upgrades. Jun 25, 15:01:28 GMT+0 - Identified - The upgrade delays have been caused by resource capacity limits. We are taking actions to increase the appropriate resources. Jun 25, 14:41:28 GMT+0 - Investigating - Upgrades are taking longer than usual, but generally will complete if allowed to proceed. We are investigating the cause of the delays. Jun 25, 14:20:31 GMT+0 - Investigating - We are investigating potential upgrade issues in multiple regions. We are working to confirm impact and determine next steps. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 11 days, 7 hours and 8 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>18:51:40</var> GMT+0</small><br><strong>Resolved</strong> -
  Through our monitoring, we have determined that project upgrade behavior has returned to normal across the fleet. This incident is resolved..</p>
<p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>18:08:06</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have implemented all necessary mitigations and the project upgrade rates have returned to normal across the fleet. We will continue to monitor these flows for any irregularities or recurring degradation. If you are still experiencing delayed or blocked upgrades on your Project, please contact Support..</p>
<p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>17:46:27</var> GMT+0</small><br><strong>Identified</strong> -
  We are starting to notice improvements as a result of our mitigation efforts, and expect that project upgrades should start to become less delayed. We’ll continue monitoring and will update as we observe improvements across the fleet..</p>
<p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>17:03:54</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing our operational and investigative work to  improve upgrade flow performance and mitigate further problems..</p>
<p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>16:27:00</var> GMT+0</small><br><strong>Identified</strong> -
  We are implementing operational mitigations to try to improve upgrade performance..</p>
<p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>16:03:11</var> GMT+0</small><br><strong>Identified</strong> -
  We are continuing to work through a variety of options for improving upgrade performance. This includes working with our upstream provider and adjusting operational parameters..</p>
<p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>15:32:53</var> GMT+0</small><br><strong>Identified</strong> -
  We are aware that upgrades continue to be delayed. We are exploring other factors that are contributing to the slow upgrades..</p>
<p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>15:01:28</var> GMT+0</small><br><strong>Identified</strong> -
  The upgrade delays have been caused by resource capacity limits. We are taking actions to increase the appropriate resources..</p>
<p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>14:41:28</var> GMT+0</small><br><strong>Investigating</strong> -
  Upgrades are taking longer than usual, but generally will complete if allowed to proceed. We are investigating the cause of the delays..</p>
<p><small>Jun <var data-var='date'> 25</var>, <var data-var='time'>14:20:31</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating potential upgrade issues in multiple regions. We are working to confirm impact and determine next steps..</p>
]]>
  </content:encoded>
  <pubDate>Thu, 25 Jun 2026 14:20:31 +0000</pubDate>
  <link>https://status.frameworkpm.io/incident/cmt0rp4zx1m2c0rmgvpn438ew</link>
  <guid>https://status.frameworkpm.io/incident/cmt0rp4zx1m2c0rmgvpn438ew</guid>
</item>

<item>
  <title>Project create and unpause errors in eu-west-1</title>
  <description>
    Type: Incident
    Duration: 3 days, 3 hours and 41 minutes

    Affected Components: Supabase → Database
    Jun 23, 16:32:38 GMT+0 - Resolved - Project create and unpause operations have returned to normal and remained stable for the past 30 minutes. Jun 23, 16:01:57 GMT+0 - Monitoring - Key updates and other mitigations have been fully deployed and project creation and unpause functionality is returning to normal. We will continue to monitor this region for stability for the next 30 minutes. Jun 23, 15:46:38 GMT+0 - Identified - During this incident, postgres upgrade functionality has also been affected. The key updates are being deployed and other mitigations continue to take effect. Jun 23, 15:43:13 GMT+0 - Identified - Multiple mitigations have been deployed and project create performance is improving. Jun 23, 15:26:40 GMT+0 - Identified - We have identified the issue is related to keys and are preparing a mitigation. Jun 23, 15:16:57 GMT+0 - Investigating - We are investigating errors in creating and unpausing projects in the eu-west-1 region. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 3 days, 3 hours and 41 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>16:32:38</var> GMT+0</small><br><strong>Resolved</strong> -
  Project create and unpause operations have returned to normal and remained stable for the past 30 minutes..</p>
<p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>16:01:57</var> GMT+0</small><br><strong>Monitoring</strong> -
  Key updates and other mitigations have been fully deployed and project creation and unpause functionality is returning to normal. We will continue to monitor this region for stability for the next 30 minutes..</p>
<p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>15:46:38</var> GMT+0</small><br><strong>Identified</strong> -
  During this incident, postgres upgrade functionality has also been affected. The key updates are being deployed and other mitigations continue to take effect..</p>
<p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>15:43:13</var> GMT+0</small><br><strong>Identified</strong> -
  Multiple mitigations have been deployed and project create performance is improving..</p>
<p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>15:26:40</var> GMT+0</small><br><strong>Identified</strong> -
  We have identified the issue is related to keys and are preparing a mitigation..</p>
<p><small>Jun <var data-var='date'> 23</var>, <var data-var='time'>15:16:57</var> GMT+0</small><br><strong>Investigating</strong> -
  We are investigating errors in creating and unpausing projects in the eu-west-1 region..</p>
]]>
  </content:encoded>
  <pubDate>Tue, 23 Jun 2026 15:16:57 +0000</pubDate>
  <link>https://status.frameworkpm.io/incident/cmt0rp5031m2o0rmgm374taro</link>
  <guid>https://status.frameworkpm.io/incident/cmt0rp5031m2o0rmgm374taro</guid>
</item>

<item>
  <title>Degraded Management API performance affecting payments and Supabase Studio</title>
  <description>
    Type: Incident
    Duration: 4 days, 2 hours and 59 minutes

    Affected Components: Supabase → Compute, Supabase → API Gateway
    Jun 17, 14:10:07 GMT+0 - Resolved - All regions continue to report healthy Management API performance and platform stability. Jun 17, 13:15:23 GMT+0 - Monitoring - We have resolved the degraded performance affecting our Management API in the impacted regions. All systems are now fully operational. 

All payment features have been re-enabled. Customers should no longer experience failed payments or failed project creations.

We are continuing to monitor the system closely and will provide a final update once we have confirmed full stability. Jun 17, 12:51:44 GMT+0 - Investigating - We are currently experiencing degraded performance with our Management API in the following regions: ca-central-1, sa-east-1, us-east-1, and us-east-2.

Customers may experience failed payments, failed project creations, and degraded performance in Supabase Studio.

As a precautionary measure, we have temporarily disabled the following features while we investigate: 
- Top up Credits
- Update Billing Information
- Redeem Credits

To reduce impact, we have redirected traffic to healthy regions. Our team continues to actively investigate and work toward a full resolution. Jun 17, 12:31:07 GMT+0 - Investigating - We are currently investigating the issue 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Incident</p>
    <p><strong>Duration:</strong> 4 days, 2 hours and 59 minutes</p>
    <p><strong>Affected Components:</strong> </p>
    <p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>14:10:07</var> GMT+0</small><br><strong>Resolved</strong> -
  All regions continue to report healthy Management API performance and platform stability..</p>
<p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>13:15:23</var> GMT+0</small><br><strong>Monitoring</strong> -
  We have resolved the degraded performance affecting our Management API in the impacted regions. All systems are now fully operational. 

All payment features have been re-enabled. Customers should no longer experience failed payments or failed project creations.

We are continuing to monitor the system closely and will provide a final update once we have confirmed full stability..</p>
<p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>12:51:44</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently experiencing degraded performance with our Management API in the following regions: ca-central-1, sa-east-1, us-east-1, and us-east-2.

Customers may experience failed payments, failed project creations, and degraded performance in Supabase Studio.

As a precautionary measure, we have temporarily disabled the following features while we investigate: 
- Top up Credits
- Update Billing Information
- Redeem Credits

To reduce impact, we have redirected traffic to healthy regions. Our team continues to actively investigate and work toward a full resolution..</p>
<p><small>Jun <var data-var='date'> 17</var>, <var data-var='time'>12:31:07</var> GMT+0</small><br><strong>Investigating</strong> -
  We are currently investigating the issue.</p>
]]>
  </content:encoded>
  <pubDate>Wed, 17 Jun 2026 12:31:07 +0000</pubDate>
  <link>https://status.frameworkpm.io/incident/cmt0rpcz01mtv0rmgd9pr3gti</link>
  <guid>https://status.frameworkpm.io/incident/cmt0rpcz01mtv0rmgd9pr3gti</guid>
</item>

<item>
  <title>Edge Functions scheduled maintenance in eu-central-1 and us-east-1</title>
  <description>
    Type: Maintenance
    Duration: 1 hour

    Affected Components: Supabase → Edge Functions
    May 4, 05:00:08 GMT+0 - Completed - The scheduled maintenance has been completed. May 4, 04:00:07 GMT+0 - Identified - Scheduled maintenance is currently in progress. We will provide updates as necessary. May 4, 03:00:07 GMT+0 - Planned - Maintenance will begin as scheduled in 60 minutes. May 1, 17:18:29 GMT+0 - Planned - 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. 
  </description>
  <content:encoded>
    <![CDATA[<p><strong>Type:</strong> Maintenance</p>
    <p><strong>Duration:</strong> 1 hour</p>
    <p><strong>Affected Components:</strong> </p>
    <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'>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'> 4</var>, <var data-var='time'>03:00:07</var> GMT+0</small><br><strong>Planned</strong> -
  Maintenance will begin as scheduled in 60 minutes..</p>
<p><small>May <var data-var='date'> 1</var>, <var data-var='time'>17:18:29</var> GMT+0</small><br><strong>Planned</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>
]]>
  </content:encoded>
  <pubDate>Mon, 4 May 2026 04:00:00 +0000</pubDate>
  <link>https://status.frameworkpm.io/maintenance/cmt0rpmir1nc70rmgcq5d9eu2</link>
  <guid>https://status.frameworkpm.io/maintenance/cmt0rpmir1nc70rmgcq5d9eu2</guid>
</item>

  </channel>
  </rss>