Incident with Pull Requests
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.
We continue to monitor the stability of merge requests.
The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
We’re continuing to investigate and monitor ~1% of merge requests timing out.
We’ve taken mitigating action to resolve the problem of merge requests timing out. This issue initially impacted 3% of requests and is now down to less than 1%. We continue to monitor recovery.
Pull Requests is experiencing degraded performance. We are continuing to investigate.
We’re investigating an issue with Pull Requests where some attempts to merge are timing out.
We are investigating reports of degraded availability for Pull Requests
About this data
Where does the incident data for GitHub come from?
Data comes from the GitHub official status page, syncs every 5 minutes, and covers 90 days. The detail page links to the original report.
How do I read the component status bars?
Each block is one day. Green means no issue was reported, yellow means degraded performance, red means a major outage, and gray means no data. Availability covers the last 90 days.
Why is history missing for some services?
Only services with a public official status page are included.
How is duration calculated?
Duration runs from the official start time to recovery, or to the current time for ongoing incidents. Incidents spanning multiple days appear on each affected day.
See the full service list and live status in the status overview