‹ Back to incident history

Incident with Actions, Issues, API Requests and Pull Requests

ResolvedMinor incidentGitHub
Tuesday, October 27, 2026 02:48 – Tuesday, October 27, 2026 02:57 (8 min)
Affected components
API Requests
Issues
Pull Requests
Actions
Updates
ResolvedTuesday, October 27, 2026 02:57

On October 26, 2026, between 17:52 and 18:49 UTC, some customers experienced slower response times across the Checks API, Issues, Pull Requests, GraphQL, Notifications, and related services. Impact was limited to requests served from one of our datacenter sites. Some GraphQL requests failed, and some notifications were delayed. Among GraphQL requests served from the affected site, the average error rate was 5.68%, with a peak five-minute error rate of 14.32%. <br /><br />Unusually large requests for contribution history overwhelmed part of our database infrastructure, causing a backlog. Requests continued reaching the slow component rather than being redirected to healthy systems. Restarting the component restored its performance. The incident was marked mitigated at 18:46 UTC and resolved at 18:57 UTC. <br /><br />We are adding limits to these requests, improving alerts to detect overload sooner, and strengthening automatic redirection to healthy systems.

MonitoringTuesday, October 27, 2026 02:54

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.

MonitoringTuesday, October 27, 2026 02:50

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

InvestigatingTuesday, October 27, 2026 02:48

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

Incident data from the GitHub official status page:Read the official incident

About this data

Where does the incident data for GitHub come from?

Data comes from the GitHub official status page, syncs every 5 minutes, and covers 90 days. The detail page links to the original report.

How do I read the component status bars?

Each block is one day. Green means no issue was reported, yellow means degraded performance, red means a major outage, and gray means no data. Availability covers the last 90 days.

Why is history missing for some services?

Only services with a public official status page are included.

How is duration calculated?

Duration runs from the official start time to recovery, or to the current time for ongoing incidents. Incidents spanning multiple days appear on each affected day.

See the full service list and live status in the status overview