How long does GitHub Copilot usually take to recover from an outage?

In the last 90 days of records, the median recovery time for GitHub Copilot incidents was 64m, and 9 out of 10 were resolved within 7.6h.

How often does GitHub Copilot have incidents?

Over the last 30 days, 4 incidents were recorded on the official status page, an average of 0.9 per week.

What if GitHub Copilot shows errors but the official page says it's fine?

Problems limited to some regions or features may be posted late or not at all. Try reloading, signing out and back in, and turning off a VPN. If it still fails, check whether you have hit a usage limit.

All service status

Is GitHub Copilot down? Server status

GitHub Copilot posted 4 incidents on its official status page in the last 30 days, usually resolved within 38m. Updated every 30 minutes.

Now: Operational

As of Nov 8, 23:46 UTC, the official status of GitHub Copilot is operational.

Recent trend

2 incidents in the last 7 days — within the usual range.

Incident forecast

Within 24 hours: 15%
Within 72 hours: 38%

We'll notify you on the site and by email when GitHub Copilot goes down or recovers.

Last 7 days11/2 – 11/8

Incidents: 2
Major+: 0
Days with issues: 2
Median recovery: —
Most recovered by: —

Core feature outageOutagePartial outageBrief outage
Non-core issue
Normal
No record

1 cell = 1 hour

Last 90 days8/11 – 11/8

Incidents: 13
Per week: 1
Major+: 5
Days with issues: 14
Median recovery: 64m
Most recovered by: 7.6h

Operational
Minor issue
Major issue
Critical outage
No record

1 cell = 1 day

Outage hours, last 12 weeks8/16 – 11/8

Core outage, weekly avg: 2.5h
Non-core issues, weekly avg: None

Core feature outage
Non-core issue
No record

1 bar = 1 week

Incident cause analysis

What was affected

API12
Other / unclear1

Cause (as far as the notice says)

Upstream service failure7
Cause not stated5
Demand & capacity1

Core use (chat, API and the like) was visibly affected in 13 of 13 labeled incidents.
Most common cause: Upstream service failure (7 of 13).

Recent incidentsTitles as published

APIIncident with API, Git, and Copilot requestsCore feature outage・lasted 31m
Nov 3, 13:25 UTC
APIElevated errors on GPT-5.4 NanoCore feature outage・lasted 38m
Nov 2, 17:46 UTC
Other / unclearDisruption with some Copilot servicesCore feature outage・lasted 75m
Oct 28, 14:12 UTC
APIGrok 4.6 and Grok 4.7 Service IssuesCore feature outage・lasted 42m
Oct 23, 23:41 UTC
APIUpstream service failureElevated rate of errors for OpenAI models provided by CopilotCore feature outage・lasted 50m
Sep 17, 20:59 UTC
APIDemand & capacityDegradation with Gemini 3.8 FlashCore feature outage・lasted 10.5h
Sep 16, 07:20 UTC
APIUpstream service failureDisruption with some GitHub servicesCore feature outage・lasted 1.5h
Sep 15, 09:47 UTC
APIUpstream service failureIncident with Grok Copilot AI Model ProviderCore feature outage・lasted 2.9h
Sep 3, 14:17 UTC
APIUpstream service failureElevated rate of errors for OpenAI models provided by CopilotCore feature outage・lasted 42m
Aug 31, 09:15 UTC
APIUpstream service failureIncident with Copilot AI Model ProvidersCore feature outage・lasted 2.1h
Aug 27, 10:04 UTC
APIUpstream service failureElevated errors on Fable 5 due to upstream providerCore feature outage・lasted 47m
Aug 24, 07:12 UTC
APIIncident with GitHub.comCore feature outage・lasted 7.6h
Aug 17, 13:40 UTC
APIUpstream service failureErrors with the Fable 5 Model in CopilotCore feature outage・lasted 64m
Aug 13, 14:43 UTC
App & webDemand & capacityIncident with CopilotCore feature outage・lasted 1.5h
Aug 3, 09:53 UTC

GitHub Copilot news

More news

GitHub Copilot FAQ

Is GitHub Copilot down right now?: As of Nov 8, 23:46 UTC, the official status of GitHub Copilot is operational.
How long does GitHub Copilot usually take to recover from an outage?: In the last 90 days of records, the median recovery time for GitHub Copilot incidents was 64m, and 9 out of 10 were resolved within 7.6h.
How often does GitHub Copilot have incidents?: Over the last 30 days, 4 incidents were recorded on the official status page, an average of 0.9 per week.
What if GitHub Copilot shows errors but the official page says it's fine?: Problems limited to some regions or features may be posted late or not at all. Try reloading, signing out and back in, and turning off a VPN. If it still fails, check whether you have hit a usage limit.

Sources and methodology

We collect incidents from GitHub Copilot's official status page every 30 minutes and keep them. Past incidents removed from the official page stay in this record.
Incident counts and recovery times cover only the period since we started recording. When that period is short, we show "97 days".
Affected features and incident causes are classified by AI from the incident notices.
The outage probability is a reference estimate from the last 60 days of records (newer weighted more) and the average across all services.
Maintenance notices are not counted as incidents. Providers post by different standards, so more notices don't necessarily mean less stable.

Source: GitHub Copilot official status page