GitHub Status · History · Incident #4637

RESOLVED

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

Minor · Started Jun 15, 2026 · 6:32 PM

  • Duration

    38m

  • Severity

    Minor

  • Detection lead

  • User reports

Summary

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

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.


  • Started

    Jun 15, 2026 · 6:32 PM

  • Resolved

    Jun 15, 2026 · 7:10 PM

  • Duration

    38m

  • Severity

    Minor

Event timeline

How this incident unfolded

  • Investigating

    Jun 15 · 6:32 PM GitHub

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

  • Monitoring

    Jun 15 · 7:02 PM GitHub

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

  • Monitoring

    Jun 15 · 7:10 PM GitHub

    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.

  • Resolved

    Jun 15 · 7:10 PM GitHub

    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.

Get alerted before the next GitHub outage.

Pulsetic catches degradations minutes before vendors acknowledge them.

Start monitoring free