GitHub incident

Incomplete pull request results in repositories

Minor Resolved View vendor source →
Started
Apr 28, 2026, 02:17 PM UTC
Resolved
May 01, 2026, 04:15 AM UTC
Duration
2d 13h
Detected by Pingoru
Apr 28, 2026, 02:17 PM UTC

Affected components

Pull Requests

Update timeline

  1. investigating Apr 28, 2026, 02:17 PM UTC

    We are investigating reports of degraded performance for Pull Requests

  2. investigating Apr 28, 2026, 02:51 PM UTC

    After 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.

  3. investigating Apr 28, 2026, 03:58 PM UTC

    We 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.

  4. investigating Apr 28, 2026, 09:43 PM UTC

    Elastic 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.

  5. investigating Apr 28, 2026, 10:46 PM UTC

    We have made an interim mitigation to improve availability for some impacted repositories while reindexing continues, and we are actively monitoring the indexing progress.

  6. investigating Apr 29, 2026, 12:40 AM UTC

    Mitigation is in progress, with full recovery of impacted pull request listings expected within approximately 24 hours.

  7. investigating Apr 29, 2026, 10:22 PM UTC

    We 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.

  8. investigating Apr 30, 2026, 03:49 AM UTC

    We 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.

  9. investigating May 01, 2026, 04:11 AM UTC

    This incident has been resolved. Search and indexing functionality for pull requests are now fully restored. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

  10. resolved May 01, 2026, 04:15 AM UTC

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

Looking to track GitHub downtime and outages?

Pingoru polls GitHub's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

  • Real-time alerts when GitHub reports an incident
  • Email, Slack, Discord, Microsoft Teams, and webhook notifications
  • Track GitHub alongside 5,000+ providers in one dashboard
  • Component-level filtering
  • Notification groups + maintenance calendar
Start monitoring GitHub for free

5 free monitors · No credit card required