{"provider":"supabase","label":"Supabase","source":"https://status.supabase.com","license":"CC BY 4.0","citeAs":"Repose, \"Supabase incident history\", https://repose.sh/upstream/supabase","generatedAt":"2026-09-25T19:44:04.419Z","count":50,"incidents":[{"id":"czcxy9zjx7kt","title":"Project Lifecycle Issues in eu-west-1","impact":"major","status":"resolved","startedAt":"2026-09-24T15:36:10.752Z","resolvedAt":"2026-09-24T17:38:02.869Z","updatedAt":"2026-09-24T17:38:02.889Z","components":["Database","Management API","eu-west-1"],"url":"https://stspg.io/dl2ny990gmmq","updates":[{"at":"2026-09-24T15:36:10.854Z","body":"We are investigating project lifecycle operation issues in eu-west-1.","status":"investigating"},{"at":"2026-09-24T15:50:26.471Z","body":"We have isolated the scope of the problem to a specific upstream incident. We are working to address the upstream incident and determine mitigations.","status":"identified"},{"at":"2026-09-24T16:23:54.874Z","body":"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.","status":"identified"},{"at":"2026-09-24T16:56:04.431Z","body":"Most projects have been brought back up, and the team is working on the remaining projects, which should be completed soon.\n\nThis 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.","status":"identified"},{"at":"2026-09-24T17:03:16.233Z","body":"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.","status":"identified"},{"at":"2026-09-24T17:12:33.852Z","body":"We are continuing to monitor to ensure ongoing stability.","status":"monitoring"},{"at":"2026-09-24T17:38:02.869Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"ftwdxhst1yns","title":"Permission errors in the Supabase Dashboard","impact":"critical","status":"resolved","startedAt":"2026-09-24T10:37:32.362Z","resolvedAt":"2026-09-24T11:49:44.190Z","updatedAt":"2026-09-24T11:49:44.207Z","components":["Dashboard"],"url":"https://stspg.io/8798ng9lpk1v","updates":[{"at":"2026-09-24T10:37:32.455Z","body":"We are investigating reports of users encountering permission-related errors, such as “You need additional permissions,” when performing administrative actions in the Supabase Dashboard.\nThis may prevent some users from managing their projects through the Dashboard. \nWe are working to identify the cause and will provide further updates as they become available.","status":"investigating"},{"at":"2026-09-24T10:50:12.409Z","body":"We have identified the issue causing some users to encounter permission-related errors, such as “You need additional permissions,” when performing administrative actions in the Supabase Dashboard.\nWe are working on a fix and will provide another update once it has been implemented.","status":"identified"},{"at":"2026-09-24T11:08:39.965Z","body":"We have applied a fix, and administrative operations in the Supabase Dashboard are now completing as expected.\nWe are monitoring the results to ensure the issue is fully resolved.","status":"monitoring"},{"at":"2026-09-24T11:49:44.190Z","body":"This incident has been resolved. \nAdministrative operations in the Supabase Dashboard are completing as expected, and we have observed no further permission related errors following the fix.","status":"resolved"}]},{"id":"z02rx5zhtwlv","title":"Supabase CLI CI workflow failures","impact":"minor","status":"resolved","startedAt":"2026-09-23T21:58:58.934Z","resolvedAt":"2026-09-23T23:41:21.490Z","updatedAt":"2026-09-23T23:41:21.505Z","components":[],"url":"https://stspg.io/f8pzxc1stbmh","updates":[{"at":"2026-09-23T21:58:58.989Z","body":"We're seeing rate limiting issues causing Supabase CLI CI workflow failures","status":"investigating"},{"at":"2026-09-23T22:36:23.954Z","body":"We've identified the cause and are working on a fix.","status":"identified"},{"at":"2026-09-23T22:56:21.963Z","body":"We are no longer seeing rate limiting issues affecting Supabase CLI CI workflows. We're continuing to monitor the service for stability while we roll out a fallback patch to improve resilience and help prevent the issue from recurring.","status":"monitoring"},{"at":"2026-09-23T23:41:21.490Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"4rbrdl79zz9p","title":"Storage search failing for restored projects","impact":"minor","status":"resolved","startedAt":"2026-09-23T09:31:49.040Z","resolvedAt":"2026-09-24T10:01:25.139Z","updatedAt":"2026-09-24T10:01:25.158Z","components":["Storage"],"url":"https://stspg.io/twg3y61l6b6b","updates":[{"at":"2026-09-23T09:31:49.145Z","body":"We have identified an issue with Storage for projects are restoring from backups. Users may experience increased 500 errors.\n\nWe are working to identify the root cause and will notify for any progress as soon as we have an update","status":"investigating"},{"at":"2026-09-23T10:20:36.697Z","body":"A fix has been implemented for the affected tenants and we are monitoring the results. We will continue to monitor the situation and will provide further updates as more information becomes available.","status":"monitoring"},{"at":"2026-09-24T10:01:25.139Z","body":"Storage is now operating normally. We apologise for the disruption. \n\nHardening measures are being put in place to prevent recurrence and will be communicated upon completion.","status":"resolved"}]},{"id":"v53hyqsty0b8","title":"Increased error rate in project creation and project restore","impact":"major","status":"resolved","startedAt":"2026-09-23T09:21:14.145Z","resolvedAt":"2026-09-23T10:49:14.336Z","updatedAt":"2026-09-23T10:49:14.355Z","components":["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-1","eu-west-2","eu-west-3","sa-east-1","us-east-1","us-east-2","us-west-1","us-west-2"],"url":"https://stspg.io/694ll1by982q","updates":[{"at":"2026-09-23T09:21:14.590Z","body":"We are currently investigating this issue","status":"investigating"},{"at":"2026-09-23T09:39:45.765Z","body":"We'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.","status":"identified"},{"at":"2026-09-23T09:54:10.078Z","body":"A fix has been implemented and we are monitoring the results.","status":"monitoring"},{"at":"2026-09-23T10:49:14.336Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"4y2r6jwycqk5","title":"Supavisor connection disruptions in EU West 1 (Ireland)","impact":"minor","status":"resolved","startedAt":"2026-09-22T10:49:34.085Z","resolvedAt":"2026-09-22T12:20:13.694Z","updatedAt":"2026-09-22T12:20:13.711Z","components":["Connection Pooler"],"url":"https://stspg.io/lst22nh36x3d","updates":[{"at":"2026-09-22T10:49:34.168Z","body":"Some projects in the EU West 1 (Ireland) region may experience disruptions to Supavisor connections. \nOur team is aware of the issue and actively working on a resolution. \nWe’ll share further updates as they become available.","status":"investigating"},{"at":"2026-09-22T11:05:14.328Z","body":"The affected Supavisor node has been restarted, and error rates have returned to normal levels. \nWe’ll continue to monitor the service to ensure stability.","status":"monitoring"},{"at":"2026-09-22T12:20:13.694Z","body":"This incident has been resolved. \nFollowing the restart of the affected Supavisor node, error rates returned to normal and no further disruptions have been observed during the monitoring period. \nAll services are operating normally.","status":"resolved"}]},{"id":"5b8plszn1ndp","title":"Project creations are degraded in multiple regions","impact":"minor","status":"resolved","startedAt":"2026-09-22T08:33:41.219Z","resolvedAt":"2026-09-22T09:05:10.473Z","updatedAt":"2026-09-22T09:05:10.488Z","components":[],"url":"https://stspg.io/fnfvygj4t5mf","updates":[{"at":"2026-09-22T08:33:41.261Z","body":"We have identified increased latency in Project creations in these regions from 0730 UTC to 0805 UTC:\n\nap-northeast-1\nap-northeast-2\neu-central-1\neu-central-2\neu-north-1\neu-west-1\neu-west-3\nus-west-1 \n\nThe latency has since recovered and our teams are monitoring for full recovery.\n\nExisting project availability has not been impacted.","status":"monitoring"},{"at":"2026-09-22T09:05:10.473Z","body":"The latency has recovered and the incident is now resolved.","status":"resolved"}]},{"id":"ms1mxwhtp30y","title":"Project Lifecycle Activity Degradation","impact":"major","status":"resolved","startedAt":"2026-09-19T20:12:05.159Z","resolvedAt":"2026-09-19T22:12:33.333Z","updatedAt":"2026-09-19T22:12:33.352Z","components":["Database","Management API"],"url":"https://stspg.io/962nvljg4zjf","updates":[{"at":"2026-09-19T20:12:05.246Z","body":"We are experiencing degradation of project lifecycle activities. We are investigating.","status":"investigating"},{"at":"2026-09-19T20:34:15.568Z","body":"We are observing recovery in project lifecycle operations. Our team is investigating the root cause and actively working to prevent recurrence.","status":"investigating"},{"at":"2026-09-19T21:25:42.048Z","body":"Project lifecycle operations have remained stable. We will continue to monitor the platform.","status":"monitoring"},{"at":"2026-09-19T22:12:33.333Z","body":"Project lifecycle operations are behaving normally.","status":"resolved"}]},{"id":"zkmggc01sdvj","title":"Query slowness for projects running Postgres version 14 in us-east-1 and ap-northeast-2","impact":"minor","status":"resolved","startedAt":"2026-09-16T17:53:59.228Z","resolvedAt":"2026-09-16T20:36:02.256Z","updatedAt":"2026-09-16T20:36:02.275Z","components":[],"url":"https://stspg.io/nrzrl5kydt57","updates":[{"at":"2026-09-16T17:53:59.276Z","body":"Projects running Postgres version 14 in us-east-1 and ap-northeast-2 may experience query slowness. We've identified the cause and are working on a fix.","status":"identified"},{"at":"2026-09-16T18:32:49.074Z","body":"We are continuing to work on a fix and will provide updates as things progress.","status":"identified"},{"at":"2026-09-16T19:17:37.334Z","body":"The fix has been implemented for ap-northeast-2 and we're working on implementing the fix for us-east-1. We will continue to provide updates as progress is made.","status":"identified"},{"at":"2026-09-16T19:48:08.927Z","body":"The fix has been rolled out to us-east-1. We will continue to monitor  both regions for stability.","status":"monitoring"},{"at":"2026-09-16T20:36:02.256Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"fp29jh55kf58","title":"Edge Function Latency","impact":"minor","status":"resolved","startedAt":"2026-09-16T09:24:30.934Z","resolvedAt":"2026-09-16T12:27:02.626Z","updatedAt":"2026-09-16T12:27:02.641Z","components":[],"url":"https://stspg.io/8hqltbj2f8dc","updates":[{"at":"2026-09-16T09:24:30.984Z","body":"We are investigating reports of increased Edge Function latency and elevated rates of HTTP 503 responses, beginning at approximately 06:00 UTC.\n\nOur team is working to identify the cause and will provide further updates as they become available.","status":"investigating"},{"at":"2026-09-16T09:38:20.823Z","body":"Error rates have returned to normal, and the service is operating as expected. \nThe team continues to investigate the underlying cause of the latency and spike in 503 errors.","status":"monitoring"},{"at":"2026-09-16T12:27:02.626Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"frmk3zk2cwql","title":"Auth Service Outage","impact":"minor","status":"resolved","startedAt":"2026-09-16T07:17:12.371Z","resolvedAt":"2026-09-16T09:33:34.525Z","updatedAt":"2026-09-16T09:33:34.541Z","components":["Auth"],"url":"https://stspg.io/m02m3yc0vjqq","updates":[{"at":"2026-09-16T07:17:12.493Z","body":"We have identified an issue related to the Auth service on some projects. We are actively working on a fix.","status":"identified"},{"at":"2026-09-16T08:29:44.444Z","body":"We have identified a subset of projects with a failing Auth service. Our team is working to remediate the issue.","status":"identified"},{"at":"2026-09-16T09:09:29.463Z","body":"We implemented a fix and are monitoring the system.","status":"monitoring"},{"at":"2026-09-16T09:33:34.525Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"5bfyvbj5l6rl","title":"Latency issues resulting in 504 errors","impact":"none","status":"resolved","startedAt":"2026-09-14T17:45:01.946Z","resolvedAt":"2026-09-11T17:00:00.000Z","updatedAt":"2026-09-14T17:45:02.013Z","components":[],"url":"https://stspg.io/bqm7fthjp94q","updates":[{"at":"2026-09-11T17:00:00.000Z","body":"We observed latency issues over the weekend resulting in 504 errors primarily impacting customers on the Free tier. The incident has been resolved.","status":"resolved"}]},{"id":"4mkcsnlf6p5x","title":"Unresponsive Projects","impact":"major","status":"resolved","startedAt":"2026-09-10T15:26:19.837Z","resolvedAt":"2026-09-11T19:06:34.963Z","updatedAt":"2026-09-11T19:06:34.982Z","components":["Database"],"url":"https://stspg.io/jqy7hh45k7l1","updates":[{"at":"2026-09-10T15:26:19.911Z","body":"We are aware of Nano projects becoming unresponsive after a period of time, typically hours. We are investigating.","status":"investigating"},{"at":"2026-09-10T15:46:17.545Z","body":"We have identified why projects are becoming unresponsive and are implementing a mitigation.","status":"identified"},{"at":"2026-09-10T17:13:30.984Z","body":"A refined fix is being rolled out to specific regions, we are assessing the impact of the fix.","status":"identified"},{"at":"2026-09-10T17:59:49.344Z","body":"Fix rollouts have been successful in the initial regions, we are proceeding to roll out the fix globally.","status":"identified"},{"at":"2026-09-10T19:41:50.434Z","body":"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.","status":"identified"},{"at":"2026-09-11T03:44:45.366Z","body":"We have rolled out a fix across all regions and are continuing to monitor over the next few hours. \nUsers still affected by project outages are encouraged to restart their projects which has shown to resolve lasting errors.","status":"monitoring"},{"at":"2026-09-11T06:19:34.104Z","body":"We have rolled out a fix across all regions and are continuing to monitor over the next few hours. \n\nDue to this incident, impacted users who's project were compute constrained would have received a 'Your Supabase Project <Name> is running out of Disk IO Budget' email which is no longer valid. No further action is required and your project availability should be restored to normal.","status":"monitoring"},{"at":"2026-09-11T19:06:34.963Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"q69r9vqtxxgk","title":"Brief connection disruptions in us-east-1 (N. Virginia)","impact":"minor","status":"resolved","startedAt":"2026-09-09T08:47:38.393Z","resolvedAt":"2026-09-09T08:47:38.438Z","updatedAt":"2026-09-09T08:47:47.316Z","components":[],"url":"https://stspg.io/yl1dl21j7xd8","updates":[{"at":"2026-09-09T08:47:38.438Z","body":"Between 05:50–06:05 UTC some customer using Supavisor in us-east-1 may have experienced brief dropped connections or connection disruptions. This issue was caused by an unexpected restart of Supavisor instances in the affected cluster.\nWe apologize for any disruption caused.","status":"resolved"}]},{"id":"m2r2sgmsnw2g","title":"Project Lifecycle Actions Showing increased error rates across all regions","impact":"critical","status":"resolved","startedAt":"2026-09-04T00:15:47.258Z","resolvedAt":"2026-09-04T08:18:40.012Z","updatedAt":"2026-09-04T08:18:40.031Z","components":["Management API"],"url":"https://stspg.io/34wlkdly7fxp","updates":[{"at":"2026-09-04T00:15:47.324Z","body":"We are seeing increased error rates in actions across all project lifecycle actions - Creations, Deletions, Restores, Configuration and Compute size upgrades. We are currently looking into the cause.\n\nOut of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved. We will provide additional updates as we have more information","status":"investigating"},{"at":"2026-09-04T00:30:51.231Z","body":"We have identified the source of the errors with project lifecycle actions, and the team is currently working to resolve it.\n\nThis is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc.\n\nRunning projects remain running, and the data APIs and direct postgres client connections are NOT affected.\n\nOut of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved. We will provide additional updates as we have more information.","status":"identified"},{"at":"2026-09-04T00:58:04.000Z","body":"The team has applied a fix, but error rates remain high. We are continuing to work and will take other necessary steps to resolve this as soon as possible.\n\nRunning projects remain running, and the data APIs and direct postgres client connections are NOT affected.\n\nOut of an abundance of caution, we would suggest against taking any of these actions until this incident is resolved: Creates, Configuration changes, Restarts, or Compute size changes. We will provide additional updates as we have more information.","status":"identified"},{"at":"2026-09-04T01:37:15.374Z","body":"The team is continuing to work on restoring project lifecycle operations. Out of caution, we have disabled lifecycle operations. \n\nThis is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc.\n\nRunning projects remain running, and the data APIs and direct postgres client connections are NOT affected.\n\nWe will provide additional updates as we have more information.","status":"identified"},{"at":"2026-09-04T02:02:23.109Z","body":"We are seeing incremental improvements internally. There is a large backlog of actions that we are working through, but things are progressing. Once we make it through most of the backlog, we will re-enable lifecycle actions.\n\nThis is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc.\n\nRunning projects remain running, and the data APIs and direct postgres client connections are NOT affected.","status":"identified"},{"at":"2026-09-04T03:01:39.446Z","body":"Error rates have returned to normal, and the backlogs are draining well. We are beginning to slowly re-enable lifecycle operations for users.\n\nWe will be monitoring impact, and we hope to have this re-enabled everywhere soon. We will leave this in this state until lifecycle operations have been completely restored.\n\nRunning projects remain running, and the data APIs and direct postgres client connections are NOT affected.","status":"identified"},{"at":"2026-09-04T03:41:38.249Z","body":"We've increased project lifecycle operations to 50% of users and things are holding steady. We're continuing to ramp this up until operations are restored for all users.\n\nThis is impacting all project-related lifecycle operations: Creates, Configuration changes, Restarts, Compute size Updates, etc.\n\nRunning projects remain running, and the data APIs and direct postgres client connections are NOT affected.","status":"identified"},{"at":"2026-09-04T04:28:19.171Z","body":"Lifecycle operations have been re-enabled for 100% of users and error rates have returned to normal.\n\nWe are going to monitor to ensure that things stay stable. The team is working through any remaining projects which did not automatically resolve.\n\nSome users may also notice that backups will happen a bit later than usual, but these jobs are running and completing normally.","status":"monitoring"},{"at":"2026-09-04T08:18:40.012Z","body":"Lifecycle operations have been re-enabled for 100% of users and error rates have returned to normal.","status":"resolved"}]},{"id":"vfb32z24wt64","title":"User unable to log in to Supabase Dashboard","impact":"critical","status":"resolved","startedAt":"2026-09-01T08:45:07.636Z","resolvedAt":"2026-09-01T10:34:27.603Z","updatedAt":"2026-09-01T10:34:27.617Z","components":["Dashboard"],"url":"https://stspg.io/s2mz940kv44d","updates":[{"at":"2026-09-01T08:45:07.768Z","body":"We are currently investigating an issue where users are unable to login to the Supabase dashboard","status":"investigating"},{"at":"2026-09-01T08:51:30.752Z","body":"We’re investigating an issue preventing users from logging in to the Supabase Dashboard. \nUsers who were logged into the dashboard were logged out. \nDashboard actions are currently not available. \n\nProjects remain online and available. Non-Dashboard traffic is not impacted. \nWe’ll share another update as soon as we have more information.","status":"investigating"},{"at":"2026-09-01T09:20:31.373Z","body":"A recent change affected users ability to log in to the Supabase Dashboard.\nWe’ve reverted the change, and testing indicates that the issue is resolved.\nPlease try logging in again. If you’re still unable to log in, perform a full browser refresh and retry.\nProjects and non-Dashboard traffic remained unaffected.","status":"monitoring"},{"at":"2026-09-01T10:34:27.603Z","body":"This incident has been resolved. \nUsers should now be able to log in to the Supabase Dashboard normally.\nProjects and non-Dashboard traffic were unaffected throughout the incident.","status":"resolved"}]},{"id":"wj0jmv0qcmw7","title":"Project Creation Failures","impact":"major","status":"resolved","startedAt":"2026-08-31T16:28:30.464Z","resolvedAt":"2026-08-31T19:06:38.572Z","updatedAt":"2026-08-31T19:06:38.587Z","components":["Database"],"url":"https://stspg.io/56wmdpzzs6cj","updates":[{"at":"2026-08-31T16:28:30.549Z","body":"Project creation is failing for new projects on the platform. We are investigating.","status":"investigating"},{"at":"2026-08-31T16:53:46.606Z","body":"We have a working hypothesis on the cause of the issue, and are implementing steps to try to improve project creation performance.","status":"investigating"},{"at":"2026-08-31T17:20:50.173Z","body":"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.","status":"investigating"},{"at":"2026-08-31T17:49:04.751Z","body":"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.","status":"investigating"},{"at":"2026-08-31T18:01:08.694Z","body":"We are seeing the mitigation steps having the desired effect. Project creation is recovering.","status":"identified"},{"at":"2026-08-31T18:29:54.360Z","body":"Project creation is reporting as recovered across the platform. We will monitor for stability in the near term.","status":"monitoring"},{"at":"2026-08-31T19:06:38.572Z","body":"Project creation has returned to baseline consistently.","status":"resolved"}]},{"id":"m3rr3q187n3b","title":"Projects failing to load Supautils in multiple regions","impact":"major","status":"resolved","startedAt":"2026-08-28T16:18:05.061Z","resolvedAt":"2026-08-28T16:18:05.118Z","updatedAt":"2026-08-28T16:18:11.791Z","components":[],"url":"https://stspg.io/96r5hdw8zttb","updates":[{"at":"2026-08-28T16:18:05.118Z","body":"PostgreSQL 15 projects were failing to load /usr/lib/postgresql/15/lib/supautils.so because GLIBC_2.33 is unavailable on affected hosts.\nThis disrupted database access in multiple regions. \nRollback is now complete and we are seeing access restored to projects in the affected regions.","status":"resolved"}]},{"id":"bv4ntm4x0btf","title":"Increased response times for requests","impact":"major","status":"resolved","startedAt":"2026-08-27T17:20:43.856Z","resolvedAt":"2026-08-31T15:57:33.771Z","updatedAt":"2026-08-31T15:57:33.785Z","components":[],"url":"https://stspg.io/tql268ymyfqj","updates":[{"at":"2026-08-27T17:20:43.901Z","body":"We’re currently investigating latency issue that may cause increased response times for a small percentage of requests. In some cases, this may also result in 525 errors.\n\nOur team is actively working to resolve the issue. We’ll share another update as soon as we have more information.","status":"investigating"},{"at":"2026-08-27T17:57:44.525Z","body":"We’re continuing to investigate the issue causing increased response times for requests and 525 errors. Our team remains actively engaged in the investigation, we’ll provide another update as soon as we have more details.","status":"investigating"},{"at":"2026-08-27T18:55:52.098Z","body":"We are continuing to investigate this issue and we’ll share more information as soon as it becomes available.","status":"investigating"},{"at":"2026-08-27T20:37:02.482Z","body":"We are continuing to investigate this issue and we’ll share more information as soon as it becomes available.","status":"investigating"},{"at":"2026-08-28T01:38:06.278Z","body":"The team has identified the change which resulted in additional latency and error rates for some data API Requests. They are preparing to roll this change back. This rollout will take some time, and we will update again as there is news on the progress of the fix.","status":"identified"},{"at":"2026-08-28T13:10:07.552Z","body":"We are continuing to work through the remediation plan for the latency issues.\nWe will provide a further update as soon as more information is available.","status":"identified"},{"at":"2026-08-28T17:21:25.707Z","body":"PostgREST 14.5 has been deployed since 12:00pm UTC to all AP regions: ap-east-1, ap-northeast-1, ap-northeast-2, ap-south-1, ap-southeast-1, and ap-southeast-2\nas well as sa-east-1 and ca-central-1, eu-central-1, eu-central-2, eu-north-1, eu-west-2, and eu-west-3, us-west-1\nWe'll continue to provide updates as we roll out the change for the remaining impacted regions.","status":"identified"},{"at":"2026-08-28T18:15:42.429Z","body":"The roll out has also been completed for us-east-1.","status":"identified"},{"at":"2026-08-28T21:06:26.835Z","body":"The rollout has been completed in all regions. We will continue to monitor.","status":"monitoring"},{"at":"2026-08-29T01:25:00.855Z","body":"Response times have recovered in all regions. We will continue to monitor throughout the weekend.","status":"monitoring"},{"at":"2026-08-31T15:57:33.771Z","body":"Response times have recovered in all regions. This issue is now resolved.","status":"resolved"}]},{"id":"6ky4qpn3srzg","title":"pgBouncer issues on some older projects","impact":"minor","status":"resolved","startedAt":"2026-08-26T19:49:36.418Z","resolvedAt":"2026-08-27T18:24:26.842Z","updatedAt":"2026-08-27T18:24:26.860Z","components":["Connection Pooler","Storage"],"url":"https://stspg.io/19qmmrvn7hj1","updates":[{"at":"2026-08-26T19:49:36.526Z","body":"Some users on older Projects are experiencing a pgBouncer configuration issue causing connection issues for the Dedicated Pooler and Storage services. This issue should only affect users with Project versions 15.1 and older. We have determined the cause of this issue and we are rolling out a fix.","status":"investigating"},{"at":"2026-08-26T21:36:24.990Z","body":"Some users on Project versions 15.1 and older are experiencing a pgBouncer configuration issue causing connection issues for the Dedicated Pooler and Storage services. We are continuing our investigation of this issue.","status":"investigating"},{"at":"2026-08-27T01:21:38.893Z","body":"This issue is fixed in eu-central-2 and ap-south-1. We are continuing to rollout the fix to all regions.","status":"identified"},{"at":"2026-08-27T10:12:12.134Z","body":"We are continuing to rollout the fix to further regions.","status":"identified"},{"at":"2026-08-27T13:04:29.985Z","body":"An enhanced automated solution is currently being tested in staging. \nIt is expected to be more effective and efficient than the approach used previously.\nOnce testing has completed successfully, we will use this approach to roll out the fix in production.\nWe will provide further updates as this work progresses.","status":"identified"},{"at":"2026-08-27T16:34:16.128Z","body":"A fix has been rolled out across all regions, and results are positive. \nWe will continue monitoring to ensure the service remains stable.\nMoving this incident to monitoring.","status":"monitoring"},{"at":"2026-08-27T18:24:26.842Z","body":"The fix has remained stable across all regions, and the issue has been resolved.","status":"resolved"}]},{"id":"yx5g3m1wb58q","title":"Increased rates of Pooler connection timeouts in us-east-1","impact":"none","status":"resolved","startedAt":"2026-08-24T15:26:51.020Z","resolvedAt":"2026-08-24T16:38:59.201Z","updatedAt":"2026-08-28T07:27:14.949Z","components":["Connection Pooler"],"url":"https://stspg.io/jxdy7363pv65","updates":[{"at":"2026-08-24T15:26:51.058Z","body":"We are aware of reports of increased rates of connection timeouts for users connecting to Projects in us-east-1 via Supavisor.","status":"investigating"},{"at":"2026-08-24T15:38:00.000Z","body":"We have identified a degraded Supavisor node and we have rolled out a fix. We are monitoring to ensure continued stability. Confirmed Impact: On Aug 24, 2026 between 14:30 and 15:20 UTC we observed increased rates of connection timeouts connecting to Supavisor in us-east-1 due to a degraded node.","status":"monitoring"},{"at":"2026-08-24T16:38:59.201Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"j9sl6g1wyng3","title":"Issues affecting automatic disk resizing","impact":"major","status":"resolved","startedAt":"2026-08-24T13:52:42.481Z","resolvedAt":"2026-08-24T15:53:09.029Z","updatedAt":"2026-08-24T15:53:09.045Z","components":["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-1","eu-west-2","eu-west-3","sa-east-1","us-east-1","us-east-2","us-west-1","us-west-2"],"url":"https://stspg.io/fdx6ybdwplv5","updates":[{"at":"2026-08-24T13:52:42.826Z","body":"We are investigating an issue affecting automatic disk resizing.\nSome projects may experience delays before a resize is completed, while others may see repeated or duplicate resize operations.\nWe are working to identify the cause and will provide an update as soon as we have more information.","status":"investigating"},{"at":"2026-08-24T14:47:53.803Z","body":"A fix has been applied, and the issue is now resolved. We are moving the incident to monitoring.\nWe will continue to follow up directly with affected users who opened a support ticket.","status":"monitoring"},{"at":"2026-08-24T15:53:09.029Z","body":"The issue affecting automatic disk resizing has been resolved.\nWe will continue to follow up directly with affected users who opened a support ticket.","status":"resolved"}]},{"id":"2g6ttgsm5q9q","title":"Error spikes in one of the ap-northeast-2 Supavisor clusters","impact":"minor","status":"resolved","startedAt":"2026-08-24T06:02:06.508Z","resolvedAt":"2026-08-24T09:51:35.039Z","updatedAt":"2026-08-24T09:51:35.052Z","components":[],"url":"https://stspg.io/tyr4q7z15pvq","updates":[{"at":"2026-08-24T06:02:06.551Z","body":"We are investigating error spikes in the ap-northeast-2 Supavisor clusters. \n\nUsers reported failures in connecting to postgres via Supavisor with the error: ClientHandler: (ECHECKOUTTIMEOUT) unable to check out connection from the pool after 15000ms in Transaction mode.","status":"investigating"},{"at":"2026-08-24T07:07:44.204Z","body":"We are continuing to investigate the errors in ap-northeast-2 Supavisor clusters.","status":"investigating"},{"at":"2026-08-24T09:13:45.434Z","body":"We have applied a fix and are monitoring for full resolution. Errors have ceased in the last minutes and all connections are back to healthy.","status":"monitoring"},{"at":"2026-08-24T09:51:35.039Z","body":"The issue has been resolved.","status":"resolved"}]},{"id":"4t0rlr9x4ksr","title":"Error spikes in one of the eu-east-1 Supavisor clusters","impact":"none","status":"resolved","startedAt":"2026-08-24T05:39:46.311Z","resolvedAt":"2026-08-24T05:39:46.359Z","updatedAt":"2026-08-24T05:39:46.369Z","components":[],"url":"https://stspg.io/z84f50vdwf30","updates":[{"at":"2026-08-24T05:39:46.359Z","body":"Between 04:54 and 04:58 UTC we observed error spikes in one of the eu-east-1 Supavisor clusters. Users would have experienced errors in connecting to postgres via Supavisor. The issue has since recovered. \n\nErrors reported: ClientHandler: (ECHECKOUTTIMEOUT) unable to check out connection from the pool after 15000ms in Transaction mode.","status":"resolved"}]},{"id":"lpyc4sbm44cz","title":"Delays in project provisioning","impact":"none","status":"resolved","startedAt":"2026-08-21T10:26:19.309Z","resolvedAt":"2026-08-21T12:15:15.093Z","updatedAt":"2026-08-21T12:15:15.109Z","components":[],"url":"https://stspg.io/nstzvzjfq4bm","updates":[{"at":"2026-08-21T10:26:19.362Z","body":"We're investigating delays affecting project pause/restore, branch creation, and project provisioning across multiple regions. Some users may see failures or slowness when performing these operations. We'll share updates as we learn more.","status":"investigating"},{"at":"2026-08-21T11:09:35.816Z","body":"We've identified the issue causing delays and failures in project pause/restore, branch creation, and project provisioning across multiple regions. \n\nBranch creation is currently failing for affected users, and project provisioning may be delayed. We're continuing to work on a fix and will share the next update as we have more information.","status":"identified"},{"at":"2026-08-21T11:35:28.077Z","body":"We've applied a fix for the issue affecting project pause/restore, branch creation, and project provisioning across multiple regions. \n\nErrors related to branch creation have dropped, and we're continuing to monitor to confirm full recovery. We'll share another update once we've confirmed the issue is resolved.","status":"monitoring"},{"at":"2026-08-21T12:15:15.093Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"swgfk4tv1rvs","title":"Network access issues affecting a limited number of users in Myanmar","impact":"none","status":"resolved","startedAt":"2026-08-19T15:52:31.142Z","resolvedAt":"2026-09-15T12:48:14.288Z","updatedAt":"2026-09-15T12:48:14.310Z","components":[],"url":"https://stspg.io/d0dv2tg5rmbn","updates":[{"at":"2026-08-19T15:52:31.190Z","body":"We are investigating reports that a limited number of users in Myanmar are unable to access Supabase. \nWe will provide additional updates as information becomes available.","status":"investigating"},{"at":"2026-08-19T17:08:53.689Z","body":"The connectivity issues appear to be limited to a subset of ISPs in Myanmar. Impacted users could try alternative ISPs to restore connectivity while we work to address this issue.","status":"investigating"},{"at":"2026-08-20T12:18:10.044Z","body":"We have reached out to the ISPs that have been involved in the connectivity challenges for users in Myanmar. We are continuing to work to address the issue.","status":"identified"},{"at":"2026-08-25T23:31:42.790Z","body":"We continue to reach out and make contact with the ISPs that have been involved in the connectivity challenges for some users in Myanmar. We are continuing to work to address the issue.","status":"identified"},{"at":"2026-09-02T19:05:13.025Z","body":"Supabase has taken the steps it can to address the blockage. We recommend customers contact their ISP for assistance: https://supabase.com/blog/navigating-regional-network-blocks","status":"monitoring"},{"at":"2026-09-09T18:29:25.426Z","body":"We continue to try to resolve this issue. We have made official requests for resolution to the appropriate parties in Myanmar.","status":"monitoring"},{"at":"2026-09-15T12:48:14.288Z","body":"We have made a repeat reminder for resolution to the appropriate parties in Myanmar. As no further response has been received, this incident will be resolved. \n\nWe recommend customers still experiencing issues to contact their ISP for assistance or review our workarounds proposed here: https://supabase.com/blog/navigating-regional-network-blocks","status":"resolved"}]},{"id":"1kzddpb0fhwr","title":"Sign-in failures for `signInWithIdToken` (OIDC) logins on free-tier projects","impact":"minor","status":"resolved","startedAt":"2026-08-19T12:47:10.801Z","resolvedAt":"2026-08-19T15:56:16.825Z","updatedAt":"2026-08-19T15:56:16.841Z","components":[],"url":"https://stspg.io/364rg94t32hm","updates":[{"at":"2026-08-19T12:47:10.881Z","body":"We've identified an issue causing sign-in failures for `signInWithIdToken` (OIDC) logins on free-tier projects. Users authenticating with non-Google/Apple/Firebase OIDC providers may see failed login attempts.\n\nWe've identified the root cause and fix has been rolled out.\n\nImpacted timeframe was 18th August 4pm UTC - 19th Aug 10:30am UTC","status":"monitoring"},{"at":"2026-08-19T12:48:53.135Z","body":"We've identified that starting 4pm UTC on August 18th we began seeing sign-in failures with signInWithIdToken (OIDC) logins on free-tier projects.  Users authenticating with OIDC providers other than Google/Apple/Firebase may have seen failed login attempts.\n\nWe've identified the root cause and fix has been rolled out.","status":"monitoring"},{"at":"2026-08-19T13:01:13.935Z","body":"We've identified that starting 4pm UTC on August 18th we began seeing sign-in failures with signInWithIdToken (OIDC) logins on free-tier projects.  Users authenticating with OIDC providers other than Google/Apple/Firebase may have seen failed login attempts.\n\nWe've identified the root cause and fix has been rolled out. We are monitoring for continued stability.","status":"monitoring"},{"at":"2026-08-19T15:56:16.825Z","body":"We have confirmed that the fix has been effective and are marking this incident as resolved.","status":"resolved"}]},{"id":"rd2q17kjw5p2","title":"Project creation failing in selected regions","impact":"minor","status":"resolved","startedAt":"2026-08-17T01:47:24.264Z","resolvedAt":"2026-08-17T01:56:20.980Z","updatedAt":"2026-08-17T01:56:20.999Z","components":[],"url":"https://stspg.io/skjjn30687zq","updates":[{"at":"2026-08-17T01:47:24.301Z","body":"We are investigating an issue with project creation failing. We will be confirming more information shortly.","status":"investigating"},{"at":"2026-08-17T01:56:20.980Z","body":"We have identified this as a non-user impacting alert and as such this is being resolved.","status":"resolved"}]},{"id":"ctvf19frbkw4","title":"Project access, updating and creation impacted in us-east-2","impact":"critical","status":"resolved","startedAt":"2026-08-14T09:31:06.913Z","resolvedAt":"2026-08-14T10:44:53.034Z","updatedAt":"2026-08-14T10:44:53.052Z","components":["us-east-2"],"url":"https://stspg.io/jq68bf48cfjj","updates":[{"at":"2026-08-14T09:31:07.022Z","body":"We are investigating an issue of project creation and updating in us-east-2. A fix is under review and prepared for being rolled out.","status":"identified"},{"at":"2026-08-14T09:49:52.898Z","body":"A fix is being rolled out and we are seeing improved performance across impacted projects. We are continuing to roll out the full fix and will be confirming recovery asap.","status":"identified"},{"at":"2026-08-14T09:59:10.453Z","body":"A fix has been applied to all impacted projects in us-east-2. We are monitoring for full resolution.","status":"monitoring"},{"at":"2026-08-14T10:44:53.034Z","body":"This incident has been resolved.","status":"resolved"}]},{"id":"6q5902p2xd9f","title":"401 errors due to JWT rejections","impact":"minor","status":"identified","startedAt":"2026-08-14T02:23:18.361Z","resolvedAt":null,"updatedAt":"2026-09-25T16:23:02.233Z","components":["API Gateway"],"url":"https://stspg.io/18v97b9scdh2","updates":[{"at":"2026-08-14T02:23:18.446Z","body":"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.","status":"identified"},{"at":"2026-08-14T07:53:32.996Z","body":"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.","status":"identified"},{"at":"2026-08-18T18:38:37.907Z","body":"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.","status":"identified"},{"at":"2026-08-20T16:37:44.059Z","body":"As part of the incident remediation flow, we have separately identified \"/lib/aarch64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found\" error between 11:15 - 16:24 UTC today affecting PostgREST. This has been fixed and we can see the error rates have subsided.","status":"identified"},{"at":"2026-08-21T17:21:47.790Z","body":"We are continuing to test and rollout the fixes for intermittent HTTP 401 errors. In most cases, waiting and refreshing is successful. \n\nWe 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've worked on multiple fixes for this issue.","status":"identified"},{"at":"2026-08-25T18:41:58.565Z","body":"We are continuing to rollout the fixes for intermittent HTTP 401 errors. In most cases, waiting and refreshing is successful. \n\nThis fix has been applied to the following regions: \nap-east-1\nap-northeast-1\nap-northeast-2\nap-south-1\nap-southeast-1\nap-southeast-2\nca-central-1\neu-central-1\neu-central-2\neu-north-1\neu-west-2\neu-west-3\n\nWe will continue rolling out this fix to the remaining regions throughout this week and provide updates as more regions are successful.","status":"identified"},{"at":"2026-08-27T17:17:54.328Z","body":"PostgREST 14.17 has now been rolled out to all regions. \nSome customers have reported that restarting their project after the rollout resolved this issue.\nTo restart your project, go to the General settings page in the dashboard and select Restart project. \nPlease contact our support team if the issue persists after a restart.","status":"identified"},{"at":"2026-08-28T23:44:41.276Z","body":"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.\n\nTo restart your project, go to the General settings page in the dashboard and select Restart project. \n\nPlease contact our support team if the issue persists after a restart.","status":"identified"},{"at":"2026-08-31T19:52:53.202Z","body":"We have seen reports that the JWT rejection issue persisted with 14.17, and due to <a href=\"https://status.supabase.com/incidents/bv4ntm4x0btf\">some unintended performance side effects</a>, we have rolled back to Postgrest 14.5. The team continues to investigate the JWT issue and hopes to have a solution soon.","status":"identified"},{"at":"2026-09-02T19:38:53.487Z","body":"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.","status":"identified"},{"at":"2026-09-07T09:49:15.983Z","body":"Testing results have been positive. \nFollowing some additional checks today, we plan to expand the rollout. \nWe’ll continue to monitor progress and provide further updates as they become available.","status":"identified"},{"at":"2026-09-11T23:41:53.552Z","body":"We continue to monitor progress and are slowly updating each region. Thank you for your patience on this issue.","status":"identified"},{"at":"2026-09-17T19:30:16.538Z","body":"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.\n\nWe 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's behalf. In an effort to resolve this sooner, we have opted to make this deployment process change and ask users to upgrade.","status":"identified"},{"at":"2026-09-23T07:26:29.163Z","body":"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. \n\nOnce 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.","status":"identified"},{"at":"2026-09-25T16:23:02.230Z","body":"The deployment process changes have been rolled out across all regions. We will monitor throughout the weekend. \n\nThe new Supabase version will be released early next week. Once it is released, impacted users can upgrade to from their dashboard to resolve this issue. \n\nThank 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.","status":"identified"}]},{"id":"srkdws515yyf","title":"MCP connection error to branch environments","impact":"none","status":"resolved","startedAt":"2026-08-11T14:37:44.247Z","resolvedAt":"2026-08-11T18:30:28.393Z","updatedAt":"2026-08-11T18:30:28.407Z","components":[],"url":"https://stspg.io/zj87dz8zwjx0","updates":[{"at":"2026-08-11T14:37:44.297Z","body":"We're currently investigating an issue that is impacting MCP connections to branch environments.","status":"investigating"},{"at":"2026-08-11T15:09:47.768Z","body":"We've identified the root cause that was leading to permission errors on MCP connections to branch environments. We're currently working on addressing this.","status":"identified"},{"at":"2026-08-11T15:52:00.494Z","body":"We're still working on implementing a fix for the identified root cause.","status":"identified"},{"at":"2026-08-11T16:33:35.000Z","body":"UPDATE: We are currently pushing a fix to address the root cause. We'll provide another update once the fix has been fully deployed.","status":"monitoring"},{"at":"2026-08-11T17:48:35.368Z","body":"We have pushed a fix to address the root cause and are monitoring the situation. If you continue to see an error, you can re-authenticate with the Supabase MCP server and also confirm that you have access to the preview branch.","status":"monitoring"},{"at":"2026-08-11T18:30:28.393Z","body":"Customers should now be able to connect to branch environments via MCP normally.","status":"resolved"}]},{"id":"2vt3m1qjsf29","title":"Project Upgrade Delays","impact":"minor","status":"resolved","startedAt":"2026-08-03T15:28:10.633Z","resolvedAt":"2026-08-05T17:33:15.967Z","updatedAt":"2026-08-05T17:33:15.986Z","components":["Database"],"url":"https://stspg.io/db35bb4v7l92","updates":[{"at":"2026-08-03T15:28:10.712Z","body":"We are investigating a potential issue that could result in a delay or failure in some users' project upgrades.","status":"investigating"},{"at":"2026-08-03T16:19:52.579Z","body":"We are continuing to investigate project upgrade issues.","status":"investigating"},{"at":"2026-08-03T17:09:16.479Z","body":"We have identified the cause of the upgrade delays and are working on a fix.","status":"identified"},{"at":"2026-08-03T19:47:58.294Z","body":"We are developing a fix for the upgrade issues.","status":"identified"},{"at":"2026-08-03T22:46:03.907Z","body":"We are continuing to fix project upgrade issues and are investigating further remediation. We will provide our next update within the next 14 hours.","status":"identified"},{"at":"2026-08-04T15:30:47.219Z","body":"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.","status":"identified"},{"at":"2026-08-04T23:38:20.423Z","body":"We are continuing to test the fix to project upgrades. We will update again when the fix is applied.","status":"identified"},{"at":"2026-08-05T14:58:43.566Z","body":"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.","status":"monitoring"},{"at":"2026-08-05T17:33:15.967Z","body":"Project upgrades have remained stable, we are resolving this incident.","status":"resolved"}]},{"id":"4ymz5r933c1c","title":"Management API Performance Degradation","impact":"minor","status":"resolved","startedAt":"2026-07-31T18:36:40.696Z","resolvedAt":"2026-08-04T20:00:04.081Z","updatedAt":"2026-08-04T20:00:04.102Z","components":["Management API"],"url":"https://stspg.io/w08jdzj4dsj0","updates":[{"at":"2026-07-31T18:36:40.759Z","body":"We have been alerted that our Management API is experiencing performance degradation due to intermittent network issues. Users who experience the problem are encouraged to log out and log back in to the dashboard as that has cleared the issue in many cases. Additionally, users can retry failed actions as needed. We are actively investigating a persistent fix.","status":"identified"},{"at":"2026-07-31T20:49:18.538Z","body":"We've isolated the cause of the network issues with the Management API and we are working on a fix.","status":"identified"},{"at":"2026-07-31T21:41:20.557Z","body":"Cause isolation is continuing. We are doing work to ensure the accuracy of the understood cause in order to have confidence in the mitigation method under consideration.","status":"identified"},{"at":"2026-07-31T22:55:05.056Z","body":"We are continuing mitigation efforts for the intermittent issues with the Management API.","status":"identified"},{"at":"2026-08-01T01:19:27.679Z","body":"We have identified the root cause and deployed a fix. We will continue to monitor the behavior through the weekend to ensure no further occurrences appear.","status":"monitoring"},{"at":"2026-08-03T22:36:38.511Z","body":"We are continuing to monitor the the Management API to ensure no further intermittent occurrences appear. We will provide another update within 24 hours.","status":"monitoring"},{"at":"2026-08-04T20:00:04.081Z","body":"After monitoring, we have confirmed that issues affecting Management API performance have been resolved.","status":"resolved"}]},{"id":"h69vvktls1pz","title":"DNS creation delays","impact":"minor","status":"resolved","startedAt":"2026-07-31T12:27:53.960Z","resolvedAt":"2026-07-31T13:26:16.600Z","updatedAt":"2026-07-31T13:26:16.614Z","components":["API Gateway","Database"],"url":"https://stspg.io/fpxbpxhb9s5x","updates":[{"at":"2026-07-31T12:27:54.074Z","body":"We're investigating issues updating DNS records for newly created, unpaused, or updated databases.","status":"investigating"},{"at":"2026-07-31T12:41:51.395Z","body":"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.","status":"identified"},{"at":"2026-07-31T12:55:52.730Z","body":"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.","status":"monitoring"},{"at":"2026-07-31T13:26:16.600Z","body":"The incident has been resolved.","status":"resolved"}]},{"id":"mbb6cqhv790h","title":"Log Ingestion Issues","impact":"minor","status":"resolved","startedAt":"2026-07-30T20:57:58.555Z","resolvedAt":"2026-07-30T21:50:35.656Z","updatedAt":"2026-07-30T21:50:35.679Z","components":["Dashboard"],"url":"https://stspg.io/trn06qd15c4l","updates":[{"at":"2026-07-30T20:57:58.624Z","body":"We are experiencing a problem with log ingestion. Customers may experience a lack of new logs being visible from their projects. We are investigating.","status":"investigating"},{"at":"2026-07-30T21:33:59.155Z","body":"We have identified the cause of the issue and are working to restore normal log ingestion. Customers may continue to experience delays in new logs appearing.","status":"identified"},{"at":"2026-07-30T21:39:24.517Z","body":"Log ingestion has been restored, and new logs are now appearing as expected. We will continue monitoring to ensure the issue is fully resolved.","status":"monitoring"},{"at":"2026-07-30T21:50:35.656Z","body":"The issue has been resolved, and customers should now see new logs appearing as expected.","status":"resolved"}]},{"id":"w5pc099bpkdc","title":"Management API Performance Degradation","impact":"minor","status":"resolved","startedAt":"2026-07-30T20:51:05.830Z","resolvedAt":"2026-07-31T02:42:40.899Z","updatedAt":"2026-07-31T02:42:40.915Z","components":["Management API"],"url":"https://stspg.io/dd1h0nn6q996","updates":[{"at":"2026-07-30T20:51:05.906Z","body":"We have been alerted that our management API is experiencing performance degradation due to intermittent network issues. Users who experience the problem are encouraged to log out and log back in to the dashboard as that has cleared the issue in many cases. We are actively investigating a persistent fix.","status":"investigating"},{"at":"2026-07-30T21:19:03.488Z","body":"We are continuing to investigate the issue.","status":"investigating"},{"at":"2026-07-30T21:58:51.186Z","body":"We have identified some anomalies that appear correlated to this issue and we are continuing to investigate.","status":"investigating"},{"at":"2026-07-30T22:54:54.177Z","body":"We are continuing to investigate the issue. We will provide further updates as progress is made.","status":"investigating"},{"at":"2026-07-31T00:30:40.940Z","body":"The intermittent networking issues have subsided. Management-api is operating normally now. We will continue to monitor for abnormal behavior.","status":"monitoring"},{"at":"2026-07-31T02:42:40.899Z","body":"The intermittent networking issues have subsided. Management-api is operating normally now.","status":"resolved"}]},{"id":"y0tjlh6hhxlv","title":"Issues with Edge Function Deployment","impact":"major","status":"resolved","startedAt":"2026-07-30T17:37:44.988Z","resolvedAt":"2026-07-31T13:20:23.000Z","updatedAt":"2026-08-03T04:54:03.885Z","components":["Edge Functions"],"url":"https://stspg.io/fptknzxz37wz","updates":[{"at":"2026-07-30T17:37:45.078Z","body":"We are aware of some users experiencing issues with Edge Function deployments.","status":"investigating"},{"at":"2026-07-30T18:16:21.998Z","body":"Only a subset of users appear to be impacted by the issue with Edge Function deployments. We are investigating the root cause.","status":"investigating"},{"at":"2026-07-30T18:28:01.669Z","body":"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.","status":"investigating"},{"at":"2026-07-30T19:46:12.009Z","body":"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.","status":"investigating"},{"at":"2026-07-30T21:02:49.616Z","body":"We are continuing to investigate this issue.","status":"investigating"},{"at":"2026-07-30T22:21:19.643Z","body":"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.","status":"investigating"},{"at":"2026-07-30T23:40:32.567Z","body":"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.","status":"investigating"},{"at":"2026-07-31T00:26:11.127Z","body":"The issue has been identified and a fix is being implemented.","status":"identified"},{"at":"2026-07-31T03:13:26.577Z","body":"Our fix has completed rollout and we are monitoring for full resolution.","status":"monitoring"},{"at":"2026-07-31T09:36:27.646Z","body":"We are working on a permanent fix for issue affecting bulk Function deployments. \nIn parallel, we are manually assisting customers who have reported the issue through support tickets.","status":"identified"},{"at":"2026-07-31T13:20:23.000Z","body":"A preventative fix (Supabase CLI v2.111.0 ) has been released to ensure that new Function deployments are not affected.\nAs the underlying issue has been addressed and new deployments should no longer be affected, we are resolving this incident.\n\nAll 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.","status":"resolved"}]},{"id":"964tqxf5jb2t","title":"SSO login failures in us-east-1","impact":"minor","status":"resolved","startedAt":"2026-07-28T21:24:22.371Z","resolvedAt":"2026-07-28T22:07:03.428Z","updatedAt":"2026-07-28T22:07:03.448Z","components":["Auth"],"url":"https://stspg.io/kfbmmql891tk","updates":[{"at":"2026-07-28T21:24:22.427Z","body":"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.","status":"investigating"},{"at":"2026-07-28T21:33:28.960Z","body":"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.","status":"identified"},{"at":"2026-07-28T21:53:44.251Z","body":"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.","status":"monitoring"},{"at":"2026-07-28T22:07:03.428Z","body":"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.","status":"resolved"}]},{"id":"pg5mnvsyxl31","title":"Documents Search Unavailable","impact":"minor","status":"resolved","startedAt":"2026-07-28T14:06:41.528Z","resolvedAt":"2026-07-28T14:13:11.612Z","updatedAt":"2026-07-28T14:13:11.628Z","components":["Dashboard"],"url":"https://stspg.io/bdq3054xz9hy","updates":[{"at":"2026-07-28T14:06:41.598Z","body":"We noticed the search function for our documentation was not available as it should be. We're making the necessary updates to fix that problem.","status":"identified"},{"at":"2026-07-28T14:13:11.612Z","body":"Documentation search functionality has been restored.","status":"resolved"}]},{"id":"ms53dzxm1gtl","title":"Delays in creation of DNS records","impact":"minor","status":"resolved","startedAt":"2026-07-27T20:34:54.395Z","resolvedAt":"2026-07-27T22:36:44.234Z","updatedAt":"2026-07-27T22:36:44.254Z","components":["API Gateway","Database"],"url":"https://stspg.io/ppxcrhg4bdfv","updates":[{"at":"2026-07-27T20:34:54.460Z","body":"We are investigating failures in provisioning DNS records for projects, there may be delays in creation of DNS records for new or unpaused projects.","status":"investigating"},{"at":"2026-07-27T20:39:48.263Z","body":"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.","status":"identified"},{"at":"2026-07-27T20:53:39.596Z","body":"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.","status":"identified"},{"at":"2026-07-27T22:23:08.226Z","body":"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.","status":"monitoring"},{"at":"2026-07-27T22:36:44.234Z","body":"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.","status":"resolved"}]},{"id":"79r5t79bj15y","title":"Project Resize Problems in US-West-2","impact":"major","status":"resolved","startedAt":"2026-07-27T17:42:27.750Z","resolvedAt":"2026-07-27T20:47:01.347Z","updatedAt":"2026-07-27T20:47:01.366Z","components":["us-west-2"],"url":"https://stspg.io/m4xm198ksyf6","updates":[{"at":"2026-07-27T17:42:27.787Z","body":"We have noticed an issue with project resizing in us-west-2 and are investigating.","status":"investigating"},{"at":"2026-07-27T17:53:39.756Z","body":"We are continuing to investigate this issue.","status":"investigating"},{"at":"2026-07-27T18:11:03.556Z","body":"We have identified the cause of the resize issues and are evaluating options for mitigating the problem.","status":"identified"},{"at":"2026-07-27T19:01:18.544Z","body":"We have a mitigation in place for resizing issues for projects in us-west-2. We will be monitoring going forward. If your project is in us-west-2, and you experience issues resizing going forward, please open a support ticket so we can directly assist you.","status":"monitoring"},{"at":"2026-07-27T20:47:01.347Z","body":"Project resizing has maintained expected performance in us-west-2.","status":"resolved"}]},{"id":"cqjl192cn8sz","title":"Authentication issues for some projects","impact":"minor","status":"resolved","startedAt":"2026-07-25T14:11:04.184Z","resolvedAt":"2026-07-25T14:45:52.846Z","updatedAt":"2026-07-25T14:45:52.863Z","components":["Auth"],"url":"https://stspg.io/00ft6yc54nd0","updates":[{"at":"2026-07-25T14:11:04.257Z","body":"Some projects are experiencing authentication issues. We are actively investigating.","status":"investigating"},{"at":"2026-07-25T14:21:05.501Z","body":"We have implemented a fix to the authentication issue and are monitoring for recovery.","status":"identified"},{"at":"2026-07-25T14:25:27.534Z","body":"Authentication has returned to normal.","status":"monitoring"},{"at":"2026-07-25T14:45:52.846Z","body":"Authentication operations have returned to normal consistently.","status":"resolved"}]},{"id":"5xrf04q42rh7","title":"Between 11:34 and 11:43 UTC, some projects in the us-east-2 (Ohio) region experienced degraded connectivity during a connection pooler maintenance upgrade","impact":"none","status":"resolved","startedAt":"2026-07-23T11:30:00.000Z","resolvedAt":"2026-07-23T11:30:00.000Z","updatedAt":"2026-07-23T14:48:41.994Z","components":[],"url":"https://stspg.io/5r7jzf2gjzcg","updates":[{"at":"2026-07-23T11:30:00.000Z","body":"Between 11:34 and 11:43 UTC, some projects in the us-east-2 (Ohio) region experienced degraded connectivity during a connection pooler maintenance upgrade. The affected cluster has since recovered, and connectivity is operating as expected.","status":"resolved"}]},{"id":"g0b5xz7b6xfv","title":"Log Ingestion Problems","impact":"minor","status":"resolved","startedAt":"2026-07-22T16:29:39.510Z","resolvedAt":"2026-07-22T20:10:00.797Z","updatedAt":"2026-07-22T20:10:00.812Z","components":["Dashboard"],"url":"https://stspg.io/q9j4p9ntqct8","updates":[{"at":"2026-07-22T16:29:39.584Z","body":"We are experiencing a problem with log ingestion. Customers may experience a lack of new logs being visible from their projects. We are investigating.","status":"investigating"},{"at":"2026-07-22T16:56:02.820Z","body":"We have identified the issue and are working to re-enable the ingestion of logs.","status":"identified"},{"at":"2026-07-22T17:49:13.041Z","body":"We have implemented a fix, and log ingestion has returned to normal. We will continue to monitor this issue to ensure it stays stable.","status":"monitoring"},{"at":"2026-07-22T18:40:31.702Z","body":"We are continuing to monitor log ingestion to ensure it remains stable.","status":"monitoring"},{"at":"2026-07-22T20:10:00.797Z","body":"This issue is now resolved. Log ingestion has returned to normal and customers can now view project logs.","status":"resolved"}]},{"id":"xhs8d4l3wtsc","title":"Project Actions Failing Across Multiple Regions","impact":"major","status":"resolved","startedAt":"2026-07-17T17:49:58.794Z","resolvedAt":"2026-07-18T01:41:45.142Z","updatedAt":"2026-07-18T01:41:45.158Z","components":["Database","Management API"],"url":"https://stspg.io/xf7wf1421m7x","updates":[{"at":"2026-07-17T17:49:58.848Z","body":"Certain project actions are failing. We are actively investigating to determine the regions impacted and source of the issue.","status":"investigating"},{"at":"2026-07-17T18:16:46.655Z","body":"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.","status":"investigating"},{"at":"2026-07-17T18:47:55.541Z","body":"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.","status":"investigating"},{"at":"2026-07-17T19:20:33.877Z","body":"We are testing mitigation options to attempt to restore project action performance.","status":"investigating"},{"at":"2026-07-17T19:45:29.886Z","body":"We have identified a problem with a specific job in us-east-1, we have mitigated the job and are observing the results.","status":"identified"},{"at":"2026-07-17T20:21:37.707Z","body":"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.","status":"monitoring"},{"at":"2026-07-18T01:41:45.142Z","body":"Project actions have been sustained at normal performance. This incident is resolved.","status":"resolved"}]},{"id":"5cbt09m9y46n","title":"S3 endpoints for keys with special characters broken","impact":"minor","status":"resolved","startedAt":"2026-07-16T17:55:01.955Z","resolvedAt":"2026-07-16T18:49:00.432Z","updatedAt":"2026-07-16T18:49:00.448Z","components":["Storage"],"url":"https://stspg.io/5hhtsgdcw6ql","updates":[{"at":"2026-07-16T17:55:02.019Z","body":"We have identified an issue where S3 endpoints for keys with special characters will be broken. We are actively investigating the correct mitigation for this issue.","status":"identified"},{"at":"2026-07-16T18:23:28.529Z","body":"A likely mitigation has been identified and we are discussing the proper implementation method.","status":"identified"},{"at":"2026-07-16T18:32:02.500Z","body":"We have implemented a PR rollback to mitigate this issue. We will actively monitor its progress","status":"identified"},{"at":"2026-07-16T18:49:00.432Z","body":"This incident has been resolved. A recent API Gateway deployment altered how certain special characters in S3 object key paths were encoded before reaching storage, causing signature verification failures (403) for affected requests.\n\nThe change has been reverted and issue is now fixed.","status":"resolved"}]},{"id":"xmg8tmj6lsk4","title":"Projects in stuck state in EU-CENTRAL-1 (Frankfurt)","impact":"major","status":"resolved","startedAt":"2026-07-16T07:00:12.328Z","resolvedAt":"2026-07-16T11:35:45.526Z","updatedAt":"2026-07-16T11:35:45.543Z","components":[],"url":"https://stspg.io/qtq3dlkph9hd","updates":[{"at":"2026-07-16T07:00:12.395Z","body":"Our infrastructure provider experienced a connectivity issue in the EU-CENTRAL-1 (Frankfurt) Region, between 4:11 PM PDT and 6:24 PM PDT, which has now been resolved. \nAs a result of this incident, a number of Supabase projects were left in a stuck state. \nOur team is actively working through the list of impacted projects to restore normal functionality as quickly as possible.\nWe will continue to provide updates as restoration work progresses.","status":"identified"},{"at":"2026-07-16T07:02:10.624Z","body":"We are continuing to work on a fix for this issue.","status":"identified"},{"at":"2026-07-16T07:42:36.714Z","body":"The majority of impacted projects have now been recovered, and functionality has been restored for most customers.\nOur team continues to work through the remaining affected projects individually to restore normal functionality as quickly as possible.\nWe will continue to provide updates as this work progresses.","status":"identified"},{"at":"2026-07-16T09:16:27.853Z","body":"The majority of impacted projects have now been recovered, and functionality has been restored for most customers.\nOur team continues to work through the remaining affected projects individually to restore normal functionality as quickly as possible.\nWe will continue to provide updates as this work progresses.","status":"identified"},{"at":"2026-07-16T10:14:13.672Z","body":"All impacted projects have now been successfully restarted, and functionality has been restored.\nWe are moving this incident to Monitoring for an additional hour while we continue to ensure stability.\nIf you believe your project in eu-central-1 (Frankfurt) is still impacted by this issue, please open a support ticket and we'll work with you directly to investigate.","status":"monitoring"},{"at":"2026-07-16T11:35:45.526Z","body":"The mitigation work for this incident has been completed, and we have not observed any further impact following the restoration of affected projects.\nThis incident is now resolved.\nIf you continue to experience issues that you believe are related to this incident in eu-central-1 (Frankfurt), please open a support ticket and our team will investigate.","status":"resolved"}]},{"id":"052r8klt6799","title":"Errors configuring authentication providers","impact":"minor","status":"resolved","startedAt":"2026-07-15T00:04:18.442Z","resolvedAt":"2026-07-15T00:50:10.597Z","updatedAt":"2026-07-15T00:50:10.640Z","components":["Dashboard"],"url":"https://stspg.io/h8tdtc7cn8g7","updates":[{"at":"2026-07-15T00:04:18.529Z","body":"We are currently investigating an issue affecting the ability to view and manage authentication providers in the Supabase dashboard.","status":"investigating"},{"at":"2026-07-15T00:25:56.761Z","body":"We have identified the issue and are actively working on a fix. We will share another update as soon as we have more information.","status":"identified"},{"at":"2026-07-15T00:34:06.140Z","body":"A fix has been deployed for the issue that affects configuring Authentication Providers. We are monitoring the results to confirm the issue has been fully resolved.","status":"monitoring"},{"at":"2026-07-15T00:50:10.597Z","body":"This issue has been resolved.","status":"resolved"}]},{"id":"4c35n31q7qhs","title":"Degraded log ingestion","impact":"minor","status":"resolved","startedAt":"2026-07-09T23:34:46.793Z","resolvedAt":"2026-07-10T03:48:32.886Z","updatedAt":"2026-07-10T03:48:32.929Z","components":["Analytics"],"url":"https://stspg.io/p9h7xq5tx44r","updates":[{"at":"2026-07-09T23:34:46.935Z","body":"We are currently investigating an issue affecting log ingestion across all regions. During this time, some logs may be delayed or unavailable.","status":"investigating"},{"at":"2026-07-10T00:02:09.580Z","body":"We are continuing to investigate the issue affecting log ingestion across all regions. Logs may be delayed or unavailable. We will provide another update as soon as more information becomes available.","status":"investigating"},{"at":"2026-07-10T00:36:54.351Z","body":"We are continuing to investigate the issue affecting log ingestion across all regions. Logs may be delayed or unavailable. We will provide another update as soon as more information becomes available.","status":"investigating"},{"at":"2026-07-10T01:25:15.166Z","body":"We continue to investigate an issue affecting log visibility that began at approximately 22:15 UTC. During this time, logs may be delayed or unavailable. \nOur team continues to investigate the underlying cause and will provide another update as more information becomes available.\n\nIf you need access to logs from the affected period, please contact Support and we will work with you to retrieve them.","status":"investigating"},{"at":"2026-07-10T02:53:13.648Z","body":"We've identified the issue and are implementing a fix. \n\nIf you need access to logs from the affected period (starting at approximately 22:15 UTC), please contact Support and we will work with you to retrieve them.","status":"identified"},{"at":"2026-07-10T03:03:08.366Z","body":"We have implemented a fix for the issue affecting log visibility that began at approximately 22:15 UTC. Log ingestion has returned to normal. We are monitoring the system to ensure the issue is fully resolved.\n\nIf you continue to experience missing or delayed logs from the affected period, please contact Support for assistance.","status":"monitoring"},{"at":"2026-07-10T03:48:32.886Z","body":"This issue has been resolved. Log ingestion and log visibility have returned to normal operation.\n\nIf you experience missing or delayed logs from the affected time period, please contact Support and we'll be happy to assist.","status":"resolved"}]},{"id":"3tx3nnmbwyh9","title":"Project status change failures in multiple regions","impact":"major","status":"resolved","startedAt":"2026-06-30T03:08:41.000Z","resolvedAt":"2026-07-13T16:00:12.198Z","updatedAt":"2026-07-13T16:00:12.248Z","components":["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-1","eu-west-2","eu-west-3","sa-east-1","us-east-1","us-east-2","us-west-1"],"url":"https://stspg.io/v2kqtvng9qnt","updates":[{"at":"2026-06-30T02:38:13.665Z","body":"We are currently investigating an issue affecting project creation in multiple regions.","status":"investigating"},{"at":"2026-06-30T02:43:49.605Z","body":"Project creation is impacted across multiple regions, we are investigating the root cause.","status":"investigating"},{"at":"2026-06-30T03:08:41.000Z","body":"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.","status":"investigating"},{"at":"2026-06-30T03:38:57.890Z","body":"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.","status":"identified"},{"at":"2026-06-30T04:32:20.308Z","body":"We are continuing to work on a fix for the issue and will provide updates as more information is available.","status":"identified"},{"at":"2026-06-30T05:11:59.121Z","body":"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.","status":"identified"},{"at":"2026-06-30T06:49:02.924Z","body":"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.","status":"identified"},{"at":"2026-06-30T11:20:04.037Z","body":"Additional capacity has been made available in the majority of regions, and we're seeing reduced failure rates in terms of project creation, project resizing, branch provisioning, and project restarts.\nWe are still experiencing limited instance capacity in ap-northeast-2, ap-south-1, and eu-north-1. \nAs a result, project operations that require capacity in these regions, including project creation, resizing, branch provisioning, restarts, may continue to fail.\nWe are actively working to restore full capacity and will provide another update as soon as more information is available.","status":"identified"},{"at":"2026-06-30T18:58:41.275Z","body":"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.","status":"identified"},{"at":"2026-06-30T22:22:56.000Z","body":"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.","status":"identified"},{"at":"2026-07-01T03:23:43.758Z","body":"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). \n\nProject 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.","status":"identified"},{"at":"2026-07-01T10:12:44.187Z","body":"We continue to experience intermittent capacity related issues across all regions, impacting operations such as project creation, project resizing, branch provisioning, and project restarts.\nThese operations may fail intermittently or require one or more retries to complete successfully.\nOur team is actively investigating ways to improve the situation and is implementing a number of mitigation measures to reduce the impact on affected operations.\nWe will provide another update as soon as more information becomes available.","status":"identified"},{"at":"2026-07-01T16:58:37.000Z","body":"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.\n\nOur team is actively implementing mitigation measures to increase capacity and restore normal service. \nWe will provide further updates as the situation evolves.\n\nIf you'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.\nThis issue does not affect existing running projects or their availability.","status":"identified"},{"at":"2026-07-02T01:30:02.361Z","body":"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.\n\nOur team is actively implementing mitigation measures to increase capacity and restore normal service. \nWe will provide further updates as the situation evolves.\n\nIf you'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.\n\nThis issue does not affect existing projects or their availability unless the instance undergoes restarts, restores, or database upgrades.","status":"identified"},{"at":"2026-07-02T05:53:07.089Z","body":"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.\n\nRunning projects are unaffected and stay available. The issue has only surfaced during a restart, restore, or database upgrade.\n\nWe are still addressing an issue with Read Replicas and continuing to increase capacity to restore normal service in full with highest priority.","status":"identified"},{"at":"2026-07-02T10:40:45.333Z","body":"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.\n\nOur team is actively working to restore the remaining affected projects. We will provide further updates as this work progresses.\n\nThis 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","status":"identified"},{"at":"2026-07-02T15:08:17.312Z","body":"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.\n\nWe 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.\n\nThis issue does not affect existing projects or their availability unless the instance has undergone restarts or resizes while the incident has been in progress.","status":"identified"},{"at":"2026-07-03T09:43:42.752Z","body":"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. \n\nWe 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.\n\nThis issue does not affect existing projects or their availability unless the instance has undergone restarts or resizes while the incident has been in progress.","status":"identified"},{"at":"2026-07-03T16:03:14.470Z","body":"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.\n\nWe 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.\nThe remaining impact is primarily limited to Medium instances running PostgreSQL versions earlier than 17.6.1.121. \nNew project deployments should succeed, but restarts or resizes for projects matching this profile may fail.\n\nExisting projects are not affected unless they have been restarted or resized during this incident.","status":"identified"},{"at":"2026-07-03T19:57:30.048Z","body":"We'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.\n\nCapacity 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.\n\nIf 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's infrastructure settings: https://supabase.com/dashboard/project/_/settings/infrastructure\n\nIf your project is affected and you're unable to resize or restart, our support team can help.\n\nWe'll update this page as the situation materially changes.","status":"identified"},{"at":"2026-07-04T04:34:48.011Z","body":"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.\n\nIf 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's infrastructure settings here: https://supabase.com/dashboard/project/_/settings/infrastructure\n\nIf your project is affected and you're unable to resize or restart, our support team can help.\n\nWe'll update this page as the situation materially changes.","status":"identified"},{"at":"2026-07-04T22:40:14.593Z","body":"We are continuing to monitor available capacity in all regions.\n\nIf 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's infrastructure settings here: https://supabase.com/dashboard/project/_/settings/infrastructure\n\nIf your project is affected and you're unable to resize or restart, our support team can help.\n\nWe'll update this page as the situation materially changes.","status":"identified"},{"at":"2026-07-06T11:32:36.654Z","body":"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.\n\nThe 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.\n\nIf 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's infrastructure settings here: https://supabase.com/dashboard/project/_/settings/infrastructure\nIf you're still unable to resize or restart after upgrading, our support team can help.\n\nWe will update this page as the situation materially changes.","status":"identified"},{"at":"2026-07-06T16:36:49.148Z","body":"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.\n\nWe 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.\n\nWe will be monitoring this for the next day or two at least just to ensure the ongoing work is effective and we don't have any re-occurrence of these or similar issues before we resolve this entirely.\n\nIf you continue to receive errors relating to capacity, please notify our support team via https://supabase.help and reference this status page.","status":"monitoring"},{"at":"2026-07-08T16:41:39.000Z","body":"We continue to monitor capacity recovery across all regions. \n\nWe 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.\n\nWe will be monitoring this thru the rest of the week to ensure ongoing work is effective and we don't have any re-occurrence of these or similar issues before we resolve this entirely.","status":"monitoring"},{"at":"2026-07-10T18:41:44.953Z","body":"We continue to monitor capacity across all regions.\n\nThe additional mitigations and machine types available to all Postgres versions are contributing to capacity stability. We continue to work to improve our resiliency.\n\nWe will continue monitoring closely to ensure ongoing work is effective and we don't have any re-occurrence of these or similar issues before we resolve this entirely.","status":"monitoring"},{"at":"2026-07-13T16:00:12.198Z","body":"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.\n\nOut 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.","status":"resolved"}]}]}