‹ Back to status overview

GitHub incident history

Official incident history for GitHub over the last 90 days. 69 records include timing, duration, affected components, and vendor updates.

GitHub current status: OperationalAll 12 official components are operational. Last synced: 2026-11-22 20:54:53

GitHub

Components: 12 · 官方状态页:正常

  • ✓Git Operationsi99.76% availabilityOperational
  • ✓Webhooksi99.27% availabilityOperational
  • ✓Visit www.githubstatus.com for more informationi100.00% availabilityOperational
  • ✓API Requestsi98.34% availabilityOperational
  • ✓Issuesi98.84% availabilityOperational
  • ✓Pull Requestsi97.96% availabilityOperational
  • ✓Actionsi97.43% availabilityOperational
  • ✓Packagesi99.49% availabilityOperational
  • ✓Pagesi99.35% availabilityOperational
  • ✓Copiloti99.86% availabilityOperational
  • ✓Codespacesi100.00% availabilityOperational
  • ✓Copilot AI Model Providersi98.82% availabilityOperational

November 2026

Incidents: 25

October 2026

Incidents: 5

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