Minor impactResolvedDevOps

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

GitHub reported this minor-impact incident on its official status page on Jun 15, 2026, 18:32 UTC. It was resolved after 38 min.

Right now GitHub is operational. Live GitHub status →

🔔 Get alerted when GitHub has issuesFree · email alerts · no credit card
Jun 15, 2026, 18:32 UTC
started
Jun 15, 2026, 19:10 UTC
resolved
38 min
duration
Minor
impact
  1. resolvedJun 15, 2026, 19:10 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in GitHub's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does GitHub have incidents?

GitHub reported 66 incidents in the last 90 days, 26 of them major or critical. A typical incident lasted 1h 21m. See GitHub's uptime and incident history

GitHub incident on Jun 15, 2026: Multiple services have elevated errors and endpoint failures when checking feature flags · APIStatus.watch