← Back to GitHub History
major✓ Resolved

Disruption with GitHub's code search

GitHubWed, Apr 1, 2026, 03:02 PM
Status
resolved
Duration
8h 47m
Updates
5
Coverage
0 articles

INCIDENT TIMELINE

✓ ResolvedWed, Apr 1, 2026, 11:50 PM
This incident has been resolved.
investigatingWed, Apr 1, 2026, 10:00 PM
We have stabilized Code Search infrastructure, and are in the final stages of validation before slowly reintroducing production traffic.
investigatingWed, Apr 1, 2026, 07:37 PM
We are still working on recovering back to a serviceable state and expect to have a more substantial update within another two hours.
investigatingWed, Apr 1, 2026, 05:48 PM
We are observing some recovery for Code Search queries, but customers should be aware that the data being served may be stale, especially for changes that took place after 07:00 UTC today (1 April 2026). We are still working on recovering our ingestion pipeline, and synchronizing the indexed data.<br /><br />We will update again within 2 hours.
investigatingWed, Apr 1, 2026, 04:00 PM
We identified an issue in our ingestion pipeline that degraded the freshness of Code Search results. While fixing the issue with the ingestion pipeline, a deployment caused a loss of dynamic configuration which is causing most requests for Code Search results to fail. We are working to restore the service and to re-ingest the misaligned data.
investigatingWed, Apr 1, 2026, 03:02 PM
We are investigating reports of impacted performance for some GitHub services.

📊 TECHNICAL DETAILS

Internal ID
c119589e-5de6-4ffc-8e52-714d2c2111d5
External ID
xs2p9z3b73r3
🕐 Started
Wed, Apr 1, 2026, 03:02 PM
🔄 Last Updated
Wed, Apr 1, 2026, 11:50 PM
✓ Resolved
Wed, Apr 1, 2026, 11:50 PM
MAJOR
Impact Level
8h 47m
Total Duration
5
Status Updates
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we automatically generate one.
0 / 100 requests100 more needed