outages.live
Live
GitHubIncident ·

Degraded performance for multiple GitHub services

DegradedOfficial update
0

Issues, Actions, and Pages have degraded performance on GitHub. GitHub also reports errors on Git operations and API access. GitHub applied a mitigation and sees recovery. GitHub monitors the services to confirm stability.

State

Monitoring

Started

Ongoing for

35 min

Worst impact

Degraded

Timeline

3 updates
23:3623:4423:5300:0200:10
DegradedUpdate postedTimes in UTC

Investigating

33 min 95%

Monitoring

2 min 5%

Updates

Times in UTC

As posted by GitHub

Monitoring

We've applied a mitigation and are seeing recovery across affected services, including Git operations, Issues, Actions, and API access. We're monitoring to confirm stability and will post another update by 00:35 UTC.

Investigating

Issues is experiencing degraded performance. We are continuing to investigate.

Investigating

We're investigating degraded performance and errors affecting several GitHub services, including Git operations, Issues, Actions, and API access. Some users may see failed requests or slow responses. We'll post another update by 00:05 UTC.

Affected components

3
IssuesActionsPages

GitHub in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

55

Days with an incident

39

Median duration

1 h 16 min

This incident

54% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

20 h 7 min
median 1 h 16 min
90 days agoToday

Other GitHub incidents

All incidents

GitHub·Incident with Actions

GitHub Actions had degraded performance. Some workflow runs had delays or errors when they started. GitHub reports that the incident is resolved and that it lasted 52 minutes.

Resolved

GitHub·Incident with Actions

GitHub Actions had degraded availability. The incident affected the Actions component. GitHub reports that the incident is resolved. It lasted 36 minutes.

Resolved

GitHub·Incident with Actions and Pages

GitHub reports degraded performance and availability for Actions, Pages, and Webhooks. GitHub identified the issue, applied mitigations, and monitored recovery. The incident is resolved and lasted about 56 minutes.

Resolved

GitHub·Incident with Pull Requests, Git Operations and Issues

GitHub reports a partial outage that affects Pull Requests, Git Operations, Issues, API Requests, and Actions. GitHub mitigated the degradation and then monitored stability. GitHub states that the incident is resolved. The incident lasted 120 minutes.

Resolved

GitHub·Increased task-related errors for Copilot Mission Control

Copilot Mission Control had increased errors in listing and creating tasks. GitHub reports that the incident is resolved. The incident lasted about 77 minutes.

Resolved · 1 affected

Follow GitHub

Your coding agent knows when GitHub is down, and tells you when a failure is theirs, not yours. You can also get GitHub incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "github" and tell me if GitHub has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=github
Slack
/feed subscribe https://outages.live/feed.xml?providers=github

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane