Minor impactResolvedDevOps

GitHub incident: Incident with Actions, Issues, API Requests and Pull Requests

GitHub reported this minor-impact incident on its official status page on Oct 26, 2026, 18:48 UTC. It was resolved after 9 min.

Right now GitHub is operational. Live GitHub status →

🔔 Get alerted when GitHub has issuesFree · email alerts · no credit card
Oct 26, 2026, 18:48 UTC
started
Oct 26, 2026, 18:57 UTC
resolved
9 min
duration
Minor
impact

Affected components

  • API Requests
  • Actions
  • Issues
  • Pull Requests
  1. resolvedOct 26, 2026, 18:57 UTC

    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.

  2. monitoringOct 26, 2026, 18:54 UTC

    We 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.<br /><br />We mitigated the issue and all services have recovered.

  3. monitoringOct 26, 2026, 18:50 UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  4. investigatingOct 26, 2026, 18:48 UTC

    We are investigating reports of degraded performance for API Requests, Actions, Issues and Pull Requests

What APIStatus.watch saw

Our 5-minute checks didn't record a change in GitHub's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does GitHub have incidents?

GitHub reported 62 incidents in the last 90 days, 20 of them major or critical. A typical incident lasted 1h 18m. See GitHub's uptime and incident history

GitHub incident on Oct 26, 2026: Incident with Actions, Issues, API Requests and Pull Requests · APIStatus.watch