GitHub outage: Disruption with some GitHub services

1. resolvedJul 16, 2026, 12:20 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.

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.

• Mux: video live and playback issuesCritical · Jul 15, 2026, 19:13 UTC
• Cursor: Investigating Grok 4.5 degradationCritical · Jul 16, 2026, 07:01 UTC
• Tailscale: Admin console and pkgs.tailscale.com are unavailableCritical · Jul 16, 2026, 08:13 UTC
• Supabase: Projects in stuck state in EU-CENTRAL-1 (Frankfurt)Major · Jul 16, 2026, 07:00 UTC
• Cursor: Authentication System degradationMajor · Jul 16, 2026, 08:32 UTC
• Vercel: SAML Single Sign-On (SSO) errorsMajor · Jul 16, 2026, 08:39 UTC
• Plaid: Elevated dashboard.plaid.com error ratesMajor · Jul 16, 2026, 08:48 UTC
• RevenueCat: Some users unable to login via single-sign-on (SSO)Major · Jul 16, 2026, 09:13 UTC
• Anthropic: Enterprise SSO sign-in failuresMajor · Jul 16, 2026, 09:23 UTC
• OVHcloud: [BHS/GRA][Identity, Security & Operations] - Logs Data Platform incident notificationMajor · Jul 16, 2026, 12:03 UTC

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