Incident with Git Operations, Issues, Actions and Pull Requests

Git OperationsPull RequestsActionsIssues

1. 7 Oct 18:04 UTCResolvedOn 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
2. 7 Oct 18:04 UTCResolvedThis 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.
3. 7 Oct 18:00 UTCUpdateAll systems have recovered. We have applied mitigations and do not anticipate another recurrence.
4. 7 Oct 17:27 UTCMonitoringThe degradation has been mitigated. We are monitoring to ensure stability.
5. 7 Oct 17:25 UTCUpdateWe 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.
6. 7 Oct 17:25 UTCUpdateWe 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.
7. 7 Oct 17:17 UTCInvestigatingWe are investigating reports of degraded performance for Actions, Git Operations, Issues and Pull Requests

No field changes in the recorded history.

Cite this recorded revision to keep the same title, summary, facts and links when the page changes.

A day selects the latest observation by the end of that UTC day; today's selection can change until midnight. History starts when this installation records it.

• Service status now: every provider ChangeIntel reads, with ongoing incidents first.
• Status RSS feed: new and ended incidents as they happen.
• Everything about GitHub: its changes, known issues and incidents on one timeline.