[2026-04-28] Incident Thread #194219
Replies: 7 comments
-
UpdateAfter yesterday’s incident, we are investigating cases where /pulls and /repo/pulls pages are not showing all indexed pull requests. This is because our Elasticsearch cluster does not currently contain all indexed documents. No pull request data has been lost. As pull requests are updated, they will be reindexed. We are also working on accelerating a full reindex so these pages return complete results again. |
Beta Was this translation helpful? Give feedback.
-
UpdateWe are actively reindexing the remaining ElasticSearch indexes. Our priority is ensuring correctness and avoiding further impact. We are taking a measured approach to safely backfill data and will share additional updates as progress continues. |
Beta Was this translation helpful? Give feedback.
-
UpdateElastic search reindexing of pull requests is continuing. All data is preserved, but may not be available on pages relying on elasticsearch until the reindex is complete. Pages and APIs that do not rely on elasticsearch, including the GitHub CLI (gh pr list) and API (/repos/{owner}/{repo}/pulls), are not impacted and can be used to retrieve pull request data in the interim. |
Beta Was this translation helpful? Give feedback.
-
UpdateWe have made an interim mitigation to improve availability for some impacted repositories while reindexing continues, and we are actively monitoring the indexing progress. |
Beta Was this translation helpful? Give feedback.
-
UpdateMitigation is in progress, with full recovery of impacted pull request listings expected within approximately 24 hours. |
Beta Was this translation helpful? Give feedback.
-
UpdateWe have restored search/indexing functionality for over 99% of impacted pull requests. We are continuing to address the remaining affected pull requests and are reviewing outstanding gaps as part of the restoration process. |
Beta Was this translation helpful? Give feedback.
-
UpdateWe have repaired the missing search records for affected Pull Requests and are working to identify and repair records left in a stale state after the recovery. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
❗ An incident has been declared:
Incomplete pull request results in repositories
Subscribe to this Discussion for updates on this incident. Please upvote or emoji react instead of commenting +1 on the Discussion to avoid overwhelming the thread. Any account guidance specific to this incident will be shared in thread and on the Incident Status Page.
Beta Was this translation helpful? Give feedback.
All reactions