Service status dashboard

Aug 9, 07:10 UTC Resolved - This incident has been resolved. Aug 9, 06:42 UTC Monitoring - A fix has been implemented and we are monitoring the results Aug 9, 06:03 UTC Update - We’ve deployed an additional mitigation to further reduce Corrosion retry pressure and are seeing improvement; we’re continuing to monitor while remaining affected nodes catch up. Aug 9, 04:58 UTC Update - We’ve applied a mitigation to reduce the impact from Corrosion batch insertion retries and are continuing to monitor while affected nodes catch up. Aug 9, 03:50 UTC Identified - We have identified the issue as failed insertions in a subset of Corrosion batches. These failures trigger retries, which can cause timeouts for other batches. Aug 9, 02:50 UTC Investigating - We are currently investigating app-not-found errors returned by Machines API calls made shortly after creating new applications.

Aug 5, 20:41 UTC Resolved - Etcd is stable. Services are back to normal. Aug 5, 20:26 UTC Identified - High CPU pressure on a shared etcd instance is causing lags on MPG creation in the IAD region

Aug 11, 20:06 UTC Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. Aug 11, 20:06 UTC Update - We have identified and mitigated increased error rates affecting GraphQL API requests. A fix to increase service capacity has been deployed and error rates have returned to normal levels. We are resolving this incident. Aug 11, 16:49 UTC Monitoring - The degradation affecting API Requests has been mitigated. We are monitoring to ensure stability. Aug 11, 16:49 UTC Update - We have returned to a healthy baseline on GraphQL API requests. We will continue to work on investigations into the errors seen during this incident. Aug 11, 15:28 UTC Update - We are investigating reports of a small increase in error rates affecting GraphQL API requests. We are working on increasing capacity and continue to investigate the increased errors. We will provide another update when we have more information Aug 11, 14:50 UTC Investigating - We are investigating reports of degraded performance for API Requests

Aug 10, 21:50 UTC Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. Aug 10, 21:50 UTC Update - We have deployed and validated the fix to prevent immediate reoccurrence. We will be performing additional work to limit these kinds of failures in the future. Aug 10, 21:19 UTC Update - The issue has been mitigated across all affected environments. We are currently deploying on a fix to prevent reoccurrence. We will provide another update once the fix has been deployed. Aug 10, 20:49 UTC Update - The degradation has been mitigated. We are monitoring to ensure stability. Aug 10, 20:39 UTC Monitoring - We are currently investigating reports of some Copilot users experiencing issues accessing certain models. Affected users may see errors or degraded functionality when attempting to use specific models. We are actively working on a fix and will provide updates as we have more information. Aug 10, 20:27 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Aug 10, 18:46 UTC Resolved - This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available. Aug 10, 18:22 UTC Update - We identified the source of the issue affecting creation of fine-grained personal access tokens and have applied a mitigation. Users should now be able to create new fine-grained tokens successfully. We are continuing to monitor to confirm full recovery. Aug 10, 18:21 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Aug 10, 18:09 UTC Update - We are investigating reports of users being unable to create fine-grained Personal Access Tokens. Attempting to create a new token redirects the user back to the token overview page without an error message, but the token was not created. Aug 10, 18:02 UTC Investigating - We are investigating reports of impacted performance for some GitHub services.

Aug 11, 18:30 UTC Resolved - Customers should now be able to connect to branch environments via MCP normally. Aug 11, 17:48 UTC Update - 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. Aug 11, 16:33 UTC Monitoring - UPDATE: We are currently pushing a fix to address the root cause. We'll provide another update once the fix has been fully deployed. Aug 11, 15:52 UTC Update - We're still working on implementing a fix for the identified root cause. Aug 11, 15:09 UTC Identified - 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. Aug 11, 14:37 UTC Investigating - We're currently investigating an issue that is impacting MCP connections to branch environments.

Aug 5, 17:33 UTC Resolved - Project upgrades have remained stable, we are resolving this incident. Aug 5, 14:58 UTC 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 UTC Update - We are continuing to test the fix to project upgrades. We will update again when the fix is applied. Aug 4, 15:30 UTC Update - 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 UTC Update - 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 UTC Update - We are developing a fix for the upgrade issues. Aug 3, 17:09 UTC Identified - We have identified the cause of the upgrade delays and are working on a fix. Aug 3, 16:19 UTC Update - We are continuing to investigate project upgrade issues. Aug 3, 15:28 UTC Investigating - We are investigating a potential issue that could result in a delay or failure in some users' project upgrades.

Aug 4, 20:00 UTC Resolved - After monitoring, we have confirmed that issues affecting Management API performance have been resolved. Aug 3, 22:36 UTC Update - We are continuing to monitor the the Management API to ensure no further intermittent occurrences appear. We will provide another update within 24 hours. Aug 1, 01:19 UTC Monitoring - 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. Jul 31, 22:55 UTC Update - We are continuing mitigation efforts for the intermittent issues with the Management API. Jul 31, 21:41 UTC Update - 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. Jul 31, 20:49 UTC Update - We've isolated the cause of the network issues with the Management API and we are working on a fix. Jul 31, 18:36 UTC Identified - 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.

Aug 6, 18:29 UTC Resolved - This incident has been resolved. Log drain delivery has recovered and remaining delayed deliveries have been processed. Aug 6, 18:19 UTC Monitoring - Log drain delivery has recovered. We are monitoring while remaining delayed deliveries are processed. Aug 6, 17:48 UTC Update - We are beginning to see recovery and continue to work on the issue. We will provide updates as they become available. Aug 6, 17:06 UTC Identified - We've identified the issue and are working on a fix. We will provide updates as they become available. Aug 6, 16:58 UTC Update - We continue to investigate this issue and will provide updates as they become available. Aug 6, 16:37 UTC Investigating - We've identified an issue causing delays in log drain delivery. We are investigating and will provide updates as they become available.

Jul 26, 17:46 UTC Resolved - Maintenance on Vercel Community has concluded. We thank you for your patience, and apologize for any inconvenience. Jul 25, 18:57 UTC Investigating - The Vercel Community forums are currently undergoing maintenance. We are working to restore access as soon as possible.

Jul 23, 19:00 UTC Resolved - Between 19:12 and 19:18 UTC on July 23, 2026, telemetry forwarded through Drains was not delivered. Traces and events forwarded via Drains during this window were dropped and are unrecoverable. Logs forwarded via Drains during this window were also not delivered, but remain accessible in the Logs UI dashboard, where they can also be exported. We have deployed a fix and are adding additional monitoring to detect and prevent this failure mode from happening in the future. We know how much you rely on this data, and we sincerely apologize for the disruption.

Jul 22, 10:05 UTC Resolved - This incident has been resolved. Jul 22, 09:01 UTC Monitoring - The affected Fly.io-hosted machines recovered at 08:48 UTC, and service availability has been restored. We are monitoring the systems to confirm continued stability. Jul 22, 08:50 UTC Identified - We are investigating connectivity issues affecting a subset of Redis databases hosted on Fly.io. The issue is related to an ongoing Fly.io infrastructure disruption in the DFW region (https://status.flyio.net/incidents/n4z2my6qw4sb). We are working to restore availability and will provide updates soon.

Jul 16, 06:30 UTC Resolved - Partial outage due to http parsing errors. Problem was resolved couple minutes later. If problem continues, refreshing the DNS cache is recommended.

Jun 25, 16:36 UTC Resolved - This incident has been resolved, we will publish RCA soon. Jun 25, 15:31 UTC Monitoring - A fix has been implemented and we are monitoring the results. Jun 25, 15:23 UTC Investigating - We are currently experiencing a partial service disruption affecting Upstash Redis in the following regions: * eu-central-1 * us-east-1 * us-west-1 Our team is investigating the issue and working to restore full service as soon as possible. We will share updates as more information becomes available.