---
id: "INC-github-93njd414rpbx"
kind: "incident"
aliases: []
title: "GitHub: Incident with Actions, Pull Requests and Issues"
severity: "medium"
cvss: null
epss: null
exploited: false
status: "resolved"
category: "vendor"
products: [{"name": "GitHub", "fixed": [], "affected": "", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["ci", "git", "github", "incident", "ops", "vendor"]
not_affected_if: []
published_at: "2026-10-12T12:21:47+00:00"
first_seen_at: "2026-10-23T19:12:22+00:00"
updated_at: "2026-10-23T20:17:58+00:00"
sources: [{"source": "statuspage", "url": "https://stspg.io/flldq0dn2wdz", "first_seen_at": "2026-10-23T19:12:22+00:00"}]
---

# GitHub: Incident with Actions, Pull Requests and Issues

## Affected

- vendor:GitHub affected ? fixed ?

## Timeline

- 2026-10-23T19:12:22+00:00 statuspage https://stspg.io/flldq0dn2wdz

## From the sources

On October 12th 2026 11:51 UTC GitHub experienced elevated 500 responses across several application pages. This caused failures on Issues and Pull Requests as well as Projects and Actions. Customers also experienced delayed notifications in their web inbox and via email. The immediate impact to Issues, Pull Requests, Projects, and Actions was mitigated by 12:41 UTC on October 12th. Notifications deliveries to the web inbox and via email were recovering at 15:27 UTC and fully mitigated by 20:16 UTC. The incident was triggered through a latent condition in our notifications delivery pipeline that put a high volume of an expensive query on our sharded database replicas. This reduced available database capacity to serve requests for Issues, Pull Requests, Projects, and Actions.We have fixed the notifications pipeline’s code path that issued the expensive query. We are also improving resilience of the database layer to reduce the likelihood and impact of similar incidents.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_