GitHub Enterprise Cloud US incident

Incident with Pull Requests

Minor Resolved View vendor source →

GitHub Enterprise Cloud US experienced a minor incident on October 15, 2026 affecting prod-cus-01 - Pull Requests (Pull Requests), lasting 13h 12m. The incident has been resolved; the full update timeline is below.

Started
Oct 15, 2026, 11:58 AM UTC
Resolved
Oct 16, 2026, 01:10 AM UTC
Duration
13h 12m
Detected by Pingoru
Oct 15, 2026, 11:58 AM UTC

Affected components

prod-cus-01 - Pull Requests (Pull Requests)

Update timeline

  1. investigating Oct 15, 2026, 11:58 AM UTC

    We are investigating reports of degraded performance for Pull Requests

  2. investigating Oct 15, 2026, 12:06 PM UTC

    We are investigating reports of pull requests lists not showing accurate count or state.

  3. investigating Oct 15, 2026, 12:49 PM UTC

    We've identified the issue causing stale results for pull requests lists, and are working through mitigations.

  4. investigating Oct 15, 2026, 01:32 PM UTC

    We've identified a capacity issue that is causing pull requests lists to remain stale. We're working on adding capacity so that new pull requests will correctly show in pull request lists.

  5. investigating Oct 15, 2026, 02:37 PM UTC

    We've deployed a change that unblocks our ability to increase capacity, and are adding that capacity now. Once that capacity is added, we expect new pull requests and pull request state changes to start to be reflected in pull requests lists.

  6. investigating Oct 15, 2026, 03:43 PM UTC

    We're currently reindexing data into our new infrastructure, which is expected to complete within 2 hours. After that, fresh data should appear in pull requests lists again (partial mitigation). In parallel, we're executing a full reindex that will include data from the ~20 hour incident window (...

  7. investigating Oct 15, 2026, 04:51 PM UTC

    The reindexing process is ongoing, and we expect partial mitigation in 1 hour, when fresh data will appear in pull requests lists. Full mitigation is estimated to complete in ~5 hours, when pull requests lists will include changes from the ~20 hour incident window.

  8. investigating Oct 15, 2026, 04:55 PM UTC

    The reindexing process is ongoing, and we expect partial mitigation in 1 hour, when fresh data will appear in pull requests lists. Full mitigation is estimated to complete in ~5 hours, when all stale or missing data will be up to date.

  9. investigating Oct 15, 2026, 06:34 PM UTC

    Partial mitigation is complete after cutting over to our new infrastructure, so newly created and updated pull requests should now be reflected in pull requests lists. Full mitigation is estimated to complete in ~4 hours.

  10. investigating Oct 15, 2026, 07:47 PM UTC

    The complete reconciliation effort for all pull request data is expected to complete within 8 hours (by 2026-10-16 04:00 UTC), but self-healing mechanisms will restore most customer-impacting experiences naturally, before the repair effort completes. In the meantime, any newly created or updated...

  11. investigating Oct 15, 2026, 10:42 PM UTC

    The complete reconciliation effort for all pull request data is still underway and expected to complete within 6 hours (by 2026-10-16 04:00 UTC), but self-healing mechanisms will restore most customer-impacting experiences naturally, before the repair effort completes. In the meantime, any newly...

  12. investigating Oct 16, 2026, 01:10 AM UTC

    The reconciliation process is complete and all pull request data is accurately reflected in the pull request list.

  13. resolved Oct 16, 2026, 01:10 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.