Developer Guide

GitHub Copilot Not Working? Debug Extension vs Service Issues

Copilot failures can come from local extension state or platform-side incidents. This checklist helps you separate them quickly.

Unknown

Live probe summary for GitHub Copilot (updates every 60s on this page)

Latency

--

HTTP

--

Region

--

Checked

--:--:-- UTC

Fresh probeRefreshing…

Last updated: 2026-02-27

High-probability causes

  • IDE extension not authenticated or stale session.
  • Temporary Copilot service degradation.
  • Enterprise policy/network restrictions blocking requests.

Debug order for speed

  1. Check service status first.
  2. Re-auth extension and restart IDE.
  3. Test in a clean workspace and alternate network.

Related pages

5-Minute Decision Matrix

SignalLikely MeaningAction Now
GitHub Copilot unavailable for most usersPlatform incident likelySwitch critical flows to backup and communicate ETA uncertainty.
Only specific account/session affectedAuth/session issue likelyRe-authenticate once and retry in private mode.
GitHub Copilot slow but not fully downDegraded performanceThrottle non-critical tasks and reroute priority tasks.

Incident Update Template (Copy/Paste)

[Incident update] GitHub Copilot reliability issue

- Current impact: [blocked/degraded] workflows
- Scope: [team/service/region]
- Verification: live monitor + official status check completed
- Mitigation: switched critical tasks to backup assistant
- Next check-in: [UTC time in 5-10 minutes]

Evidence Checklist Before Escalation

  • Exact timestamp (UTC) and affected workflow.
  • Error message or symptom pattern (with screenshot if relevant).
  • Whether issue reproduces across browser/network/device.
  • Current live status signal and official status reference.
  • Temporary workaround status (backup provider: ChatGPT, Claude, Gemini).

Related Articles