outages.live
Live
GitHubIncident ·

Incident with API, Git, and Copilot requests

ResolvedOfficial update
0

GitHub reports degraded performance for API Requests, Issues, and Copilot. GitHub reports that the incident is resolved. The incident lasted 31 minutes.

State

Resolved

Started

Lasted

31 min

Worst impact

Degraded

Timeline

4 updates
13:2513:3313:4013:4813:56
DegradedUpdate postedTimes in UTC

Investigating

31 min 100%

Updates

Times in UTC

As posted by GitHub

Resolved

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.

Investigating

API Requests is operating normally.

Investigating

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

Investigating

We are investigating reports of degraded performance for Copilot

Affected components

3
API RequestsIssuesCopilot

GitHub in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

48

Days with an incident

36

Median duration

1 h 22 min

This incident

62% 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 22 min
90 days agoToday

Other GitHub incidents

All incidents

GitHub·Elevated errors on GPT-5.4 Nano

GPT-5.4 Nano had elevated errors in Copilot products and IDE surfaces. The Copilot AI Model Providers component was affected. GitHub reports the incident resolved after 38 minutes.

Resolved

GitHub·Incident with Dependabot

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.

Resolved

GitHub·Incident with Actions, Pages, and Webhooks

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.

Resolved

GitHub·Disruption with GitHub services

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.

Resolved

GitHub·Disruption with Copilot Cloud services

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.

Resolved

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