Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Incident with Pull Requests

Posted today 11:59 UTC, last seen today 21:41 UTC.

Unknown Duration: the provider stated no start
12Updates posted
5Other incidents at the same time

What it affected

As the provider names it

Pull RequestsActions

What the provider posted

Newest first
  1. today 16:26 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.
  2. today 16:16 UTCUpdateWe’ve mitigated the issue affecting pull request merges and Actions workflow start times by reducing load on affected systems. Pull Requests and Actions have recovered, and we’re continuing to monitor their performance.
  3. today 16:07 UTCMonitoringThe degradation affecting Actions and Pull Requests has been mitigated. We are monitoring to ensure stability.
  4. today 15:55 UTCUpdateWe’re seeing early signs of improvement in pull request merge times & workflow start times, but recovery is not yet confirmed. Users may still have difficulty merging pull requests. We’re reducing load on affected systems and monitoring the impact. We’ll share another update as we learn more.
  5. today 15:46 UTCUpdateWe’re seeing early signs of improvement in pull request merge times, but recovery is not yet confirmed. The last confirmed timeout rate was 2.5%, compared with a baseline near 0.2%, so some users may still have difficulty merging pull requests. We’ll share another update as we learn more.
  6. today 15:33 UTCUpdateActions is experiencing degraded performance. We are continuing to investigate.
  7. today 15:03 UTCUpdateWe’re continuing to investigate elevated pull request merge timeouts. The latest reported rate is 4.75%, compared with a baseline near 0.2%, so some users may have difficulty merging pull requests. We’ll share another update as we learn more.
  8. today 14:06 UTCUpdateWe’re continuing to investigate elevated pull request merge timeouts. Approximately 3% of merges are timing out, compared with a baseline near 0.2%. Mitigations so far have not materially improved performance, and our teams are working to reduce load and restore normal service. We’ll share another update as we learn more.
  9. today 13:24 UTCUpdateWe’re continuing to investigate elevated pull request merge timeouts. Approximately 2–3% of merges are timing out, compared with a baseline near 0.2%. Mitigations so far have not restored normal performance, and our teams are continuing to investigate. We’ll share another update as we learn more.
  10. today 12:35 UTCUpdateWe’re continuing to investigate elevated pull request merge timeouts. Approximately 2–3% of merges are timing out, compared with a baseline near 0.2%. We’ll share another update as we learn more.
  11. today 12:00 UTCUpdateWe’re investigating elevated timeouts when merging pull requests. Some users may be unable to merge pull requests successfully; timeouts are occurring at a higher rate than usual. We’re working to identify the cause and restore normal performance.
  12. today 11:59 UTCInvestigatingWe are investigating reports of degraded performance for Pull Requests

Around it

From the sources ChangeIntel reads; a match in time is not a cause

Earlier incidents in the 14 days before

Changed in the 14 days before

Keep track

What changed

  1. Services: Pull Requests → Pull Requests, Actions · Status: Monitoring → Resolved · Incident state: Ongoing → Ended
  2. Status: Investigating → Monitoring
Page history

Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.

Cite this version
Field-level log (15)

Up to 100 recent field edits are shown; older edits may be outside retention.

  1. 16 Nov 2026 · 16:30:52 UTC ServicesPull Requests → Pull Requests, Actions
  2. 16 Nov 2026 · 16:30:52 UTC StageMonitoring → Resolved
  3. 16 Nov 2026 · 16:30:52 UTC Observed stateOngoing → Ended
  4. 16 Nov 2026 · 16:30:52 UTC SummaryWe’ve mitigated the issue affecting pull request merges and Actions workflow start times by reducing load on affected systems. Pull Requests and Actions have recovered, and we’re continuing to monitor their performance. → 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.
  5. 16 Nov 2026 · 16:20:33 UTC SummaryThe degradation affecting Actions and Pull Requests has been mitigated. We are monitoring to ensure stability. → We’ve mitigated the issue affecting pull request merges and Actions workflow start times by reducing load on affected systems. Pull Requests and Actions have recovered, and we’re continuing to monitor their performance.
  6. 16 Nov 2026 · 16:10:02 UTC StageInvestigating → Monitoring
  7. 16 Nov 2026 · 16:10:02 UTC SummaryWe’re seeing early signs of improvement in pull request merge times & workflow start times, but recovery is not yet confirmed. Users may still have difficulty merging pull requests. We’re reducing load on affected systems and monitoring the impact. We’ll share another update as we learn more. → The degradation affecting Actions and Pull Requests has been mitigated. We are monitoring to ensure stability.
  8. 16 Nov 2026 · 15:59:51 UTC SummaryWe’re seeing early signs of improvement in pull request merge times, but recovery is not yet confirmed. The last confirmed timeout rate was 2.5%, compared with a baseline near 0.2%, so some users may still have difficulty merging pull requests. We’ll share another update as we learn more. → We’re seeing early signs of improvement in pull request merge times & workflow start times, but recovery is not yet confirmed. Users may still have difficulty merging pull requests. We’re reducing load on affected systems and monitoring the impact. We’ll share another update as we learn more.
  9. 16 Nov 2026 · 15:49:40 UTC SummaryActions is experiencing degraded performance. We are continuing to investigate. → We’re seeing early signs of improvement in pull request merge times, but recovery is not yet confirmed. The last confirmed timeout rate was 2.5%, compared with a baseline near 0.2%, so some users may still have difficulty merging pull requests. We’ll share another update as we learn more.
  10. 16 Nov 2026 · 15:34:25 UTC SummaryWe’re continuing to investigate elevated pull request merge timeouts. The latest reported rate is 4.75%, compared with a baseline near 0.2%, so some users may have difficulty merging pull requests. We’ll share another update as we learn more. → Actions is experiencing degraded performance. We are continuing to investigate.
  11. 16 Nov 2026 · 15:08:54 UTC SummaryWe’re continuing to investigate elevated pull request merge timeouts. Approximately 3% of merges are timing out, compared with a baseline near 0.2%. Mitigations so far have not materially improved performance, and our teams are working to reduce load and restore normal service. We’ll share another update as we learn more. → We’re continuing to investigate elevated pull request merge timeouts. The latest reported rate is 4.75%, compared with a baseline near 0.2%, so some users may have difficulty merging pull requests. We’ll share another update as we learn more.
  12. 16 Nov 2026 · 14:12:38 UTC SummaryWe’re continuing to investigate elevated pull request merge timeouts. Approximately 2–3% of merges are timing out, compared with a baseline near 0.2%. Mitigations so far have not restored normal performance, and our teams are continuing to investigate. We’ll share another update as we learn more. → We’re continuing to investigate elevated pull request merge timeouts. Approximately 3% of merges are timing out, compared with a baseline near 0.2%. Mitigations so far have not materially improved performance, and our teams are working to reduce load and restore normal service. We’ll share another update as we learn more.
  13. 16 Nov 2026 · 13:26:54 UTC SummaryWe’re continuing to investigate elevated pull request merge timeouts. Approximately 2–3% of merges are timing out, compared with a baseline near 0.2%. We’ll share another update as we learn more. → We’re continuing to investigate elevated pull request merge timeouts. Approximately 2–3% of merges are timing out, compared with a baseline near 0.2%. Mitigations so far have not restored normal performance, and our teams are continuing to investigate. We’ll share another update as we learn more.
  14. 16 Nov 2026 · 12:35:50 UTC SummaryWe’re investigating elevated timeouts when merging pull requests. Some users may be unable to merge pull requests successfully; timeouts are occurring at a higher rate than usual. We’re working to identify the cause and restore normal performance. → We’re continuing to investigate elevated pull request merge timeouts. Approximately 2–3% of merges are timing out, compared with a baseline near 0.2%. We’ll share another update as we learn more.
  15. 16 Nov 2026 · 12:05:21 UTC SummaryWe are investigating reports of degraded performance for Pull Requests → We’re investigating elevated timeouts when merging pull requests. Some users may be unable to merge pull requests successfully; timeouts are occurring at a higher rate than usual. We’re working to identify the cause and restore normal performance.
ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 21:28 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current