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 13 Nov 15:47 UTC, last seen today 09:01 UTC.

Unknown Duration: the provider stated no start
8Updates posted
6Other incidents at the same time

What it affected

As the provider names it

Pull Requests

What the provider posted

Newest first
  1. 13 Nov 18:29 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. 13 Nov 17:46 UTCUpdateWe continue to monitor the stability of merge requests.
  3. 13 Nov 17:28 UTCMonitoringThe degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
  4. 13 Nov 16:52 UTCUpdateWe’re continuing to investigate and monitor ~1% of merge requests timing out.
  5. 13 Nov 16:12 UTCUpdateWe’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.
  6. 13 Nov 16:09 UTCUpdatePull Requests is experiencing degraded performance. We are continuing to investigate.
  7. 13 Nov 15:49 UTCUpdateWe’re investigating an issue with Pull Requests where some attempts to merge are timing out.
  8. 13 Nov 15:47 UTCInvestigatingWe are investigating reports of degraded availability for Pull Requests

Around it

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

Keep track

What changed

  1. 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 (9)

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

  1. 13 Nov 2026 · 18:30:41 UTC StageMonitoring → Resolved
  2. 13 Nov 2026 · 18:30:41 UTC Observed stateOngoing → Ended
  3. 13 Nov 2026 · 18:30:41 UTC SummaryWe continue to monitor the stability of merge 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.
  4. 13 Nov 2026 · 17:49:17 UTC SummaryThe degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability. → We continue to monitor the stability of merge requests.
  5. 13 Nov 2026 · 17:28:02 UTC StageInvestigating → Monitoring
  6. 13 Nov 2026 · 17:28:02 UTC SummaryWe’re continuing to investigate and monitor ~1% of merge requests timing out. → The degradation affecting Pull Requests has been mitigated. We are monitoring to ensure stability.
  7. 13 Nov 2026 · 16:56:51 UTC SummaryWe’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. → We’re continuing to investigate and monitor ~1% of merge requests timing out.
  8. 13 Nov 2026 · 16:16:03 UTC SummaryPull Requests is experiencing degraded performance. We are continuing to investigate. → 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.
  9. 13 Nov 2026 · 16:10:55 UTC SummaryWe’re investigating an issue with Pull Requests where some attempts to merge are timing out. → Pull Requests is experiencing degraded performance. We are continuing to investigate.
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 14 Nov 08:15 UTC · 274 of 275 readable · 269 fully read · documentation 469/469 current