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 Actions, Issues, API Requests and Pull Requests

Posted 26 Oct 18:48 UTC, last seen 12 Nov 19:33 UTC.

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

What it affected

As the provider names it

API RequestsIssuesPull RequestsActions

What the provider posted

Newest first
  1. 26 Oct 18:57 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. 26 Oct 18:54 UTCUpdateWe saw elevated latency affecting REST API requests, including Checks, and some Actions, Issues, Pull Requests, and GraphQL functionality. Some requests may have been slow or timed out, and notifications were delayed from 17:59 UTC - 18:40 UTC.We mitigated the issue and all services have recovered.
  3. 26 Oct 18:50 UTCMonitoringThe degradation has been mitigated. We are monitoring to ensure stability.
  4. 26 Oct 18:48 UTCInvestigatingWe are investigating reports of degraded performance for API Requests, Actions, Issues and Pull Requests

Around it

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

Earlier incidents in the 14 days before

Keep track

What changed

  1. Services: Pull Requests, API Requests, Actions, Issues → API Requests, Issues, Pull Requests, Actions
  2. Status: Monitoring → Resolved · Incident state: Ongoing → Ended
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 (4)

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

  1. 8 Nov 2026 · 16:47:15 UTC ServicesPull Requests, API Requests, Actions, Issues → API Requests, Issues, Pull Requests, Actions
  2. 26 Oct 2026 · 18:58:38 UTC StageMonitoring → Resolved
  3. 26 Oct 2026 · 18:58:38 UTC Observed stateOngoing → Ended
  4. 26 Oct 2026 · 18:58:38 UTC SummaryThe degradation has been mitigated. We are monitoring to ensure stability. → 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.
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 13 Nov 13:11 UTC · 274 of 275 readable · 273 fully read · documentation 469/469 current