Incident with Git Operations, Issues, Actions and Pull Requests

Timeline

1. 12 Oct · 19:19 UTC 🟠 Resolved atom

   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

2. 07 Oct · 18:04 UTC 🟡 Resolved atom

   Oct 7, 18:04 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 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

3. 07 Oct · 18:00 UTC 🔴 Identified atom

   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

4. 07 Oct · 17:50 UTC 🔴 Monitoring atom

   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

5. 07 Oct · 17:27 UTC 🔴 Monitoring atom

   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 shortly.
   
   Oct 7, 17:17 UTC
   Investigating - We are investigating reports of degraded performance for Actions, Git Operations, Issues and Pull Requests

6. 07 Oct · 17:25 UTC 🔴 Identified atom

   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 shortly.
   
   Oct 7, 17:17 UTC
   Investigating - We are investigating reports of degraded performance for Actions, Git Operations, Issues and Pull Requests

7. 07 Oct · 17:17 UTC 🟡 Investigating atom

   Oct 7, 17:17 UTC
   Investigating - We are investigating reports of degraded performance for Actions, Git Operations, Issues and Pull Requests