Disruption with some GitHub services

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 3h 34m it lasted.

  Anything that failed between 2026-06-03 03:13 UTC and 2026-06-03 06:46 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 5

1. investigatingJun 3, 2026, 3:13 AM UTC

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

   provider

2. investigatingJun 3, 2026, 3:45 AM UTC

   We are investigating reports of impacted performance for some GitHub services. --- Relevant stamps: dotcom

   provider

3. investigatingJun 3, 2026, 6:02 AM UTC

   We are investigating reports of issues with service(s): Spark. We will continue to keep users updated on progress towards mitigation.

   provider

4. monitoringJun 3, 2026, 6:45 AM UTC

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

   provider

5. resolvedJun 3, 2026, 6:46 AM UTC

   On June 2, 2026, between 21:54 UTC and June 3, 2026 06:45 UTC, the Spark service was degraded and users were unable to store or retrieve data for their Spark apps in one of our hosting regions. Users could still make changes to their app configuration during this time. The error rate peaked at 25% of affected requests to the service. Impact was limited to users whose requests were served through a single affected region; 43 users experienced errors during this window. The root cause was a configuration that referenced a service component by a fixed address rather than a dynamic service endpoint. When the component was replaced, requests could no longer reach the fixed address and began to fail. We resolved the incident by updating the configuration to use a our standard service endpoints that are resilient to component replacement. Recovery time was extended because replacing the component required overrides to a temporary deployment safeguard. We are working to add validation that prevents fixed infrastructure addresses from being used in application configuration outside of test environments and to improve our monitoring to reduce our time to detect.

   provider

Corrections

None so far.

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