Multiple services have elevated errors and endpoint failures when checking feature flags

What to do

• Check whether your product depends on GitHub. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 38m it lasted.

  Anything that failed between 2026-06-15 18:32 UTC and 2026-06-15 19:10 UTC may need a replay.

• Subscribe to GitHub's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=github works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from GitHub 4

1. investigatingJun 15, 2026, 6:32 PM UTC

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

   provider

2. monitoringJun 15, 2026, 7:02 PM UTC

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

   provider

3. monitoringJun 15, 2026, 7:10 PM UTC

   We identified an issue with feature flag checks that caused elevated errors and endpoint failures across multiple GitHub Copilot services. Customers may have experienced failed requests or degraded functionality. A fix has been deployed and error rates are steadily decreasing. All affected services are now mitigated and we are monitoring recovery.

   provider

4. resolvedJun 15, 2026, 7:10 PM UTC

   Between 17:38 UTC and 18:22 UTC on June 15, 2026, approximately 83% of requests to the analytics endpoint serving the /chronicle feature failed.  The cause was an internal feature-flag service that encountered a transient error and failed to recover, causing feature flag checks to fail. The analytics endpoint was gated behind one of these flags, resulting in requests being rejected. We restored service health by removing the feature flag gating the analytics endpoint and deploying that change. To avoid recurrence of similar incidents, we have changed the feature-flag client so that errors that are not known to be permanent are retried, and we are improving alerting and startup behavior so this class of failure is detected and recovered from faster.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.