GitHub Copilot status: API, auth, latency & outage reports

GitHub Copilot is operational right now. DownForAI checks GitHub Copilot every ~75 minutes across 2 monitored surfaces, with 0 community reports in the last 24 hours.

Operational

Last probe 13 min ago·2 surfaces

Official statusHigh confidence

📡 Official status page →📚 Docs →💳 Pricing →

100.0%

24h Uptime

75ms

p50 Network Latencyⓘ

214ms

p95 Network Latencyⓘ

Incidents (30d)

DownForAI monitors GitHub Copilot across two surfaces: Copilot Chat and Copilot Extension. Current status: operational — all surfaces are responding normally. Measured uptime over the last 24 hours: 100.0%. Median response time (24 h): 58 ms; p95: 204 ms.

DownForAI has not recorded any GitHub Copilot development tooling disruptions. The service is probed approximately every 75 minutes; no user reports have been received in the last 24 hours.

Data confidence: HighLast checked 13 min ago · 2 monitored surfaces · 2 with 24 h latency data

Current Status

✅

Operational

Everything works normally

✓Checked by our probes · 285ms

Verified 13m ago

✓No major incident reported

ⓘNo reports in the last 24h

Having issues?

Help other users by reporting if GitHub Copilot is not working for you.

0reports in the last 24 hours

Surface Health

Copilot ChatOperational

HTTP 200p50 58ms13m ago

Copilot ExtensionOperational

HTTP 200p50 92ms28m ago

Uptime — last 24h

100.0%

Network latency — last 20 probes

Loading…

What DownForAI can verify about GitHub Copilot

No confirmed provider-side issue detected

DownForAI currently sees GitHub Copilot as operational based on available monitoring signals.

Signal source: official status API · Monitoring confidence: High

Still having trouble?

The issue may be account-specific, regional, network-related, or related to authentication, billing, quota, or rate limits.

Incident history (30d)

✓No incidents recorded in the past 30 days.

Reported symptoms

No user reports for GitHub Copilot in the last 24 hours.

Community reports

What users are saying right now

Anonymous💬 down47d ago

VS Code's GitHub Copilot agents are not working.

Known error signatures

Common failure patterns and how to diagnose them

Provider details

GitHub Copilot is GitHub's AI coding assistant (IDE autocomplete, chat, coding agent, code review, CLI). Uses included and premium models depending on feature and plan; model availability varies by feature.

Community channels

⚫ GitHub Community Copilot✓🟠 r/GithubCopilot✓✕ @github✓

What we monitor

Copilot IDE completions — Inline code completions

Copilot Chat — Chat interface

Copilot coding agent — Autonomous PR generation

Copilot code review — PR inline suggestions

Copilot CLI — CLI copilot command

GitHub Auth / SSO — Copilot depends on GitHub session

VS Code Marketplace — Extension updates

Status page segments

CopilotAPI RequestsActionsGit Operations

Model families

Model availability varies by feature and planIncluded models (covered by base plan) vs premium models (count against premium request quota)User can switch model in Chat for some features

Common limits & quotas

Copilot Free: up to 2,000 inline suggestion requests and up to 50 premium requests per month
Copilot Pro ($10/mo): unlimited completions, 300 premium requests/month
Copilot Pro+ ($39/mo): higher premium request quota
Copilot Business ($19/user/mo): org controls, audit logs
Copilot Enterprise ($39/user/mo): org policies, custom models
Premium request counters reset on the 1st of each month at 00:00:00 UTC

Ecosystem dependencies

Depends on: GitHub auth, VS Code (or JetBrains) extension host, upstream model backendsOften confused with: Microsoft Copilot (separate product)Cascading failures: if GitHub auth fails, Copilot + Actions + Codespaces all fail togetherGitHub org policy can disable CLI/features independently of the base subscription

Operator notes

A significant share of user-reported Copilot incidents turn out to be auth, licensing, or org-policy issues rather than a platform-wide outage
The githubstatus.com Copilot component is separate from API and Actions — verify you're reading the right component
api.githubcopilot.com must be whitelisted in enterprise proxies; TLS cert interception by corporate proxies is a common silent failure mode
Enterprise admins can disable Copilot at org level — a whole team suddenly losing Copilot is often a policy change, not an outage
Copilot CLI is officially documented and available on all paid plans subject to org policy

Diagnostic signals

$ copilot --version — verify CLI installed and authenticated$ Check GitHub auth status in IDE: reload window, check sign-in in command palette$ curl -I https://api.githubcopilot.com — verify api.githubcopilot.com reachable$ Check githubstatus.com Copilot component specifically (not just overall GitHub status)

Fallback alternatives

What to use if this service is down

Copilot IDE completions unavailable

GitHub Chat on the web (github.com/copilot) can reduce downtime while IDE extension is failing

Easy switch

Copilot IDE completions unavailable (need new IDE)

Cursor or Windsurf/Codeium can reduce downtime for active coding sessions

Moderate effort

Copilot Chat down but completions work

Continue with completions, use claude.ai or chatgpt.com for chat separately

Easy switch

Premium requests exhausted

Switch to included models in Chat picker

Easy switch

Air-gapped or highly regulated environments

Continue.dev + Ollama (local open-weight models)

Zero dependency after setup

Major migration

How we monitor

DownForAI checks monitored AI service surfaces on a rotating schedule, roughly every 75 minutes per surface, from a single centralized probe infrastructure. For services with an official machine-readable status page, we use that official status signal when available. For other services, we perform a basic public-surface check. Some services block datacenter probes; in those cases we mark them as “Monitoring limited” instead of treating a failed probe as a confirmed outage. Status is classified as Operational, Degraded, or Outage. Network latency (check response time) measures how long the monitored endpoint took to respond to our probe — it is not model inference speed, time-to-first-token, or tokens-per-second performance. We are independent of all providers listed and receive no compensation to report any particular status.

Embed this status badgeREADME · docs ▾

Markdown

[![GitHub Copilot status](https://downforai.com/api/badge/github-copilot.svg)](https://downforai.com/github-copilot)

HTML

<a href="https://downforai.com/github-copilot"><img src="https://downforai.com/api/badge/github-copilot.svg" alt="GitHub Copilot status" /></a>

More badge options (stack, compact, open dataset) →

Community Discussion

No comments yet. Be the first to share your experience!

Still having issues with GitHub Copilot?

Let the community know and help others experiencing the same problem.