Minor impactResolvedDevOps

GitHub incident: Disruption with some GitHub services - Signup Flow

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

Right now GitHub is operational. Live GitHub status →

🔔 Get alerted when GitHub has issuesFree · email alerts · no credit card
Jun 30, 2026, 15:38 UTC
started
Jun 30, 2026, 15:49 UTC
resolved
11 min
duration
Minor
impact

Timeline

updates from GitHub's status page ↗
  1. resolvedJun 30, 2026, 15:49 UTC

    Between 15:19 UTC and 15:49 UTC on June 30, 2026, users were unable to complete the signup flow for GitHub.com/signup. Approximately 62% of new user signups failed for about 30 minutes during this window.This was caused by a configuration change to the signup flow that unintentionally blocked users from completing signup.We mitigated the incident by reverting the change, which restored successful signups. To reduce the likelihood and impact of similar issues, we are adopting staged, incremental rollouts for changes on the signup path, improving our ability to test these changes before they reach production, and adding checks to verify signup health before and during any change that affects this flow.

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

← Previous: Disruption with some GitHub services (Jun 28, 2026)Next: Delays in copilot budget limits resets for some users (Jul 1, 2026) →
GitHub incident on Jun 30, 2026: Disruption with some GitHub services - Signup Flow · APIStatus.watch