GitHub reported "Disruption with some Copilot services" on its status page at 2026-10-28 14:12 UTC.

GitHub lists these components: Copilot.

When did the incident start and end?

It started at 2026-10-28 14:12 UTC and ended at 2026-10-28 15:28 UTC. It lasted 1 h 15 min.

How do I get alerts for GitHub?

Subscribe to the GitHub live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of GitHub. outages.live reads it every few minutes and keeps every update.

GitHubIncident · 2026-10-28 14:12 UTC

Disruption with some Copilot services

ResolvedOfficial update

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.

The latest update from GitHub.

State

Resolved

Started

4 d ago

2026-10-28 14:12 UTC

Lasted

1 h 15 min

until 2026-10-28 15:28 UTC

Worst impact

Major outage

Timeline

8 updates

14:1214:3114:5015:0915:28

Major outageUpdate postedTimes in UTC

Investigating

1 h 13 min 97%

Monitoring

2 min 3%

Updates

Times in UTC

As posted by GitHub

Resolved2026-10-28 15:28 UTC

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.

Monitoring2026-10-28 15:26 UTC

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

Investigating2026-10-28 15:24 UTC

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

Investigating2026-10-28 15:15 UTC

We have applied the mitigation and are seeing signs of recovery. We will continue to monitor and expect full resolution soon.

Investigating2026-10-28 14:55 UTC

We are experiencing degraded availability for the GPT-5.3-Codex, GPT-5.6 Luna, GPT-6.1 Sol, GPT-5.6 Terra, GPT-6 Luna, and MAI Code 1.1 Flash models in Copilot products and IDE surfaces. We have identified the root cause and working to apply a mitigation. While we work to resolve the issue we recommend choosing another model to continue using Copilot.

Investigating2026-10-28 14:33 UTC

We are experiencing degraded availability for the GPT-5.3-Codex, GPT-5.6 Luna, GPT-6.1 Sol, GPT-5.6 Terra, GPT-6 Luna, and MAI Code 1.1 Flash models in Copilot products and IDE surfaces. This is due to an issue with an upstream model provider. While we work with them to resolve the issue we recommend choosing another model to continue using Copilot.

Investigating2026-10-28 14:15 UTC

We are experiencing issues with upstream model providers resulting in a degraded experience across Copilot services. The team is actively investigating the issue.

Investigating2026-10-28 14:12 UTC

We are investigating reports of impacted performance for some GitHub services.

Affected components

Copilot

GitHub in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

1 h 29 min

This incident

16% 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 29 min

90 days agoToday

Other GitHub incidents

All incidents

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.

Resolvedresolved 1 d ago

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.

Resolvedresolved 1 d ago

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.

Resolvedresolved 2 d ago

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.

Resolvedresolved 3 d ago

GitHub·Incident with Actions, Issues, API Requests and Pull Requests

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.

Resolvedresolved 5 d ago

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.cc/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.cc/feed.xml?providers=github

Slack

/feed subscribe https://outages.cc/feed.xml?providers=github

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane