Service status dashboard

Oct 13, 20:30 UTC Resolved - On October 13, around 20:42 UTC, an infrastructure failure caused GitHub Actions to have delays showing logs for workflow runs. No logs were lost and the issue has now been resolved and log processing has caught up. The actual workflows producing the logs were not impacted and ran normally and no run delays or check delays occurred.

Oct 12, 20:16 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. Oct 12, 19:28 UTC Update - Web and email notifications will be delayed for 1 more hour as we are close to completing the backlog of notifications. Oct 12, 17:34 UTC Update - Web and email notifications continue to be delayed as we work through a backlog of notifications. Oct 12, 15:50 UTC Update - Notifications have resumed but will continue to be delayed as we work through a backlog. Oct 12, 15:19 UTC Update - We have successfully applied a mitigation for notifications, and notifications have resumed but will continue to be delayed as we work through a backlog. Oct 12, 14:37 UTC Update - We have mitigated the issues with Actions, issues, and projects, and have a mitigation in progress to address the delay with notifications. Oct 12, 14:36 UTC Update - The degradation affecting Actions has been mitigated. We are monitoring to ensure stability. Oct 12, 14:35 UTC Update - The degradation affecting Issues has been mitigated. We are monitoring to ensure stability. Oct 12, 13:38 UTC Update - Our initial mitigation was not fully successful, and users may still experience delays and errors with Actions, issues and projects, and notifications are delayed. We're continuing to investigate the root cause and work on additional mitigations. Oct 12, 13:02 UTC Update - Pull Requests is operating normally. Oct 12, 12:57 UTC Update - We have a mitigation in progress and are monitoring for recovery. Users may also experience delayed web notifications as we mitigate. Oct 12, 12:33 UTC Update - Users may experience issues loading the Actions tab UI, interacting with the Checks API, queueing new Actions runs, creating and updating issues, and requesting PR reviews, including via REST and GraphQL APIs. Oct 12, 12:21 UTC Investigating - We are investigating reports of degraded performance for Actions, Issues and Pull Requests

Oct 7, 18:04 UTC Resolved - On October 7, 2026, from 16:52 to 17:01 UTC, GitHub experienced a recurrence of the write-operation outage from earlier that day. Both outages shared the same root cause. Please refer to the combined summary covering both incidents, their impact, and our prevention measures: https://www.githubstatus.com/incidents/djlmxz2zd0j7 Oct 7, 18:00 UTC Update - All systems have recovered. We have applied mitigations and do not anticipate another recurrence. Oct 7, 17:27 UTC Monitoring - The degradation has been mitigated. We are monitoring to ensure stability. Oct 7, 17:25 UTC Update - We observed widespread impact across GitHub services from 16:52 UTC to 17:01 UTC, and are investigating the root cause. All systems have recovered. This incident is a reoccurrence of the incident from earlier in the day https://www.githubstatus.com/incidents/djlmxz2zd0j7. Durable mitigation is in progress. We will provide another update in 30 minutes. Oct 7, 17:17 UTC Investigating - We are investigating reports of degraded performance for Actions, Git Operations, Issues and Pull Requests

Status: Resolved This has been resolved Affected components Logs (Operational)

Status: Resolved From approximately 2026-10-11 23:30 UTC through 2026-10-12 00:45 UTC some or all hosted sprites on the *.sprites.app subdomain were unavailable due to a certificate error. As of 00:45 UTC this incident has been resolved.

Status: Resolved The issue has been resolved. Affected components Sprites (Operational)

Oct 12, 20:11 UTC Resolved - This incident has been resolved. Oct 12, 19:56 UTC Monitoring - The backlog of deployment events has been processed. We will continue to monitor and provide additional updates as they become available. Oct 12, 18:33 UTC Update - Deployment events, such as updating the deployment status on pull requests, are delayed and the backlog is being processed. We will provide additional updates as they become available. Oct 12, 16:10 UTC Update - We are continuing to work on a fix. Due to an upstream incident at GitHub (https://www.githubstatus.com/incidents/93njd414rpbx), some builds and deployments for GitHub-connected projects are still failing. We will provide additional updates as they become available. Oct 12, 14:57 UTC Update - Build and deployment failure rates have decreased, but some builds remain queued and are taking longer to start. We are continuing to work on a fix. We will provide additional updates as they become available. Oct 12, 14:08 UTC Identified - We have identified the issue and are working on a fix. We will provide additional updates as they become available. Oct 12, 13:35 UTC Investigating - We've identified an issue where some customers may experience build failures or deployments that fail to start. We are investigating this issue. We will provide additional updates as they become available.

Oct 10, 01:37 UTC Resolved - All services have recovered. Oct 10, 01:12 UTC Monitoring - Delayed Drains deliveries, Observability data, and Build logs have been processed now. We are continuing to monitor and we will provide additional updates as they become available. Oct 10, 00:35 UTC Identified - A fix has been implemented and delivery has resumed. Delayed Drains deliveries and Observability data are being processed. We are continuing to monitor. Oct 10, 00:15 UTC Investigating - We've identified an issue where some customers may experience delayed drain delivery, delayed logs, metrics, and traces, and Workflow runs that remain pending in Washington (iad1). We are investigating this issue. We will provide additional updates as they become available.

Oct 6, 16:26 UTC Resolved - This incident has been resolved. Oct 6, 16:17 UTC Monitoring - A fix has been implemented and we are monitoring the results. Oct 6, 16:14 UTC Identified - The issue has been identified and a fix is being implemented. Oct 6, 16:10 UTC Investigating - We are investigating an issue causing Vercel Auth login failures for pages with Deployment Protection enabled. We will provide an update as more information becomes available.

Sep 29, 15:12 UTC Resolved - Between 15:12 and 15:16 UTC, we observed a brief increase in load on the connection proxy layer in us-east-1, which may have affected some existing and new connections. The team responded quickly and resolved the issue. All systems are now fully operational.

Sep 9, 12:00 UTC Resolved - Upstash Vector experienced a brief DNS resolution issue in the US East (us-east-1) region lasting approximately 20 minutes. During this period, new DNS resolution attempts may have failed. Existing connections and clients with cached DNS records were not affected. The issue has been resolved, and DNS resolution is operating normally.

Sep 3, 08:00 UTC Resolved - We experienced a brief issue affecting access to the Upstash Console. Our team quickly identified the cause and resolved the issue within minutes. The console is now operating normally.