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

  Anything that failed between 2026-07-16 09:13 UTC and 2026-07-16 12:20 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. investigatingJul 16, 2026, 9:13 AM UTC

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

   provider

2. monitoringJul 16, 2026, 9:30 AM UTC

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

   provider

3. monitoringJul 16, 2026, 10:17 AM UTC

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

   provider

4. resolvedJul 16, 2026, 12:20 PM UTC

   On July 16, 2026, between 08:50 UTC and 09:50 UTC, the GitHub MCP Server’s web_search tool experienced elevated failures. The average error rate was 42% and peaked at 82% of requests to the tool. Other GitHub MCP Server tools were unaffected. This was caused by degradation at a downstream web search provider. The incident was mitigated when the downstream provider recovered, after which we confirmed that the tool’s success rate had returned to normal. We are improving the tool’s resilience and failure handling to reduce the customer impact and duration of similar incidents.

   provider

Corrections

None so far.

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