Skip to content
GitHub · Developer toolsFeb 23, 2026, 19:59 UTC

Code search experiencing degraded performance

MinorNetworkUpdated 18h ago
Feb 23, 19:59 UTCFeb 24, 00:46 UTC
Duration
4h 47m
Impact
Minor
Root cause
Network
GitHub, 90 days
68 incidents
Affected
Not listed by the vendor.
Status page

Final update

Between 2026-02-23 19:10 and 2026-02-24 00:46 UTC, all lexical code search queries in GitHub.com and the code search API were significantly slowed, and during this incident, between 5 and 10% of search queries timed out. This was caused by a single customer who had created a network of hundreds of orchestrated accounts which searched with a uniquely expensive search query. This search query concentrated load on a single hot shard within the search index, slowing down all queries. After we identified the source of the load and stopped the traffic, latency returned to normal. To avoid this situation occurring again in the future, we are making a number of improvements to our systems, including: improved rate limiting that accounts for highly skewed load on hot shards, improved system resilience for when a small number of shards time out, improved tooling to recognize abusive actors, and capabilities that will allow us to shed load on a single shard in emergencies.

Timeline

  1. Resolved · Feb 24, 00:46 UTC
    Between 2026-02-23 19:10 and 2026-02-24 00:46 UTC, all lexical code search queries in GitHub.com and the code search API were significantly slowed, and during this incident, between 5 and 10% of search queries timed out. This was caused by a single customer who had created a network of hundreds of orchestrated accounts which searched with a uniquely expensive search query. This search query concentrated load on a single hot shard within the search index, slowing down all queries. After we identified the source of the load and stopped the traffic, latency returned to normal. To avoid this situation occurring again in the future, we are making a number of improvements to our systems, including: improved rate limiting that accounts for highly skewed load on hot shards, improved system resilience for when a small number of shards time out, improved tooling to recognize abusive actors, and capabilities that will allow us to shed load on a single shard in emergencies.

More from GitHub

Full history
StartedIncidentDuration
Sep 2310:11 UTCIncident across several servicesOngoing
Sep 2022:13 UTCIncident with Pull Requests1h 9m
Sep 1720:59 UTCElevated rate of errors for OpenAI models provided by Copilot50m
Sep 1607:20 UTCDegradation with Gemini 3.8 Flash10h 28m
Sep 1519:11 UTCDisruption with some GitHub services49m
Sep 1509:47 UTCDisruption with some GitHub services1h 30m

Also caused by network

All
StartedIncidentDuration
Sep 1901:36 UTCElevated errors in Ashburn, VA (IAD)Cloudflare0m
Sep 1411:59 UTCIncreased wait times for macOS jobsCircleCI1h
Sep 410:57 UTCIncreased errors on High Performance Edge Network - FRA RegionNetlify0m
Sep 214:18 UTCUpstream network issuesFly.io1h 39m
Sep 116:11 UTCService degradation in GCP us-central-1ClickHouse19m
Sep 114:44 UTCMultiple products in us-central1-b are experiencing network service degradation.Google Cloud4h 8m

From vendors' own status pages and disclosures. Times as reported. Logos via logo.dev; trademarks belong to their owners.

Weekly: the week's major outages, postmortems and breaches, Saturday mornings.