Incident with Pull Requests /pulls
- Started
- 2026-03-02 19:11 UTC
- Resolved
- 2026-03-02 22:04 UTC
- Duration
- 173 minutes
- Date
- 2026-03-02
Incident Timeline
We are investigating reports of degraded performance for Pull Requests
We are investigating reports of degraded performance for Pull Requests
We are investigating reports of degraded performance for Pull Requests
We are investigating reports of degraded performance for Pull Requests
We are investigating reports of degraded performance for Pull Requests
We are investigating reports of degraded performance for Pull Requests
We are investigating reports of degraded performance for Pull Requests
We are investigating reports of degraded performance for Pull Requests
We are investigating reports of degraded performance for Pull Requests
We are investigating reports of degraded performance for Pull Requests
We are investigating reports of degraded performance for Pull Requests
We are seeing a degraded experience when attempting to filter the /pulls dashboard. We are working on a mitigation.
We are seeing a degraded experience when attempting to filter the /pulls dashboard. We are working on a mitigation.
We are seeing a degraded experience when attempting to filter the /pulls dashboard. We are working on a mitigation.
We are seeing a degraded experience when attempting to filter the /pulls dashboard. We are working on a mitigation.
We are seeing a degraded experience when attempting to filter the /pulls dashboard. We are working on a mitigation.
We are seeing a degraded experience when attempting to filter the /pulls dashboard. We are working on a mitigation.
We are seeing a degraded experience when attempting to filter the /pulls dashboard. We are working on a mitigation.
We are seeing a degraded experience when attempting to filter the /pulls dashboard. We are working on a mitigation.
We are seeing a degraded experience when attempting to filter the /pulls dashboard. We are working on a mitigation.
We are seeing a degraded experience when attempting to filter the /pulls dashboard. We are working on a mitigation.
We are seeing a degraded experience when attempting to filter the /pulls dashboard. We are working on a mitigation.
We are experiencing issues with the Pull Requests dashboard that prevent users from filtering their pull requests. We have identified a mitigation and are deploying a fix. We'll post another update by 21:00 UTC.
We are experiencing issues with the Pull Requests dashboard that prevent users from filtering their pull requests. We have identified a mitigation and are deploying a fix. We'll post another update by 21:00 UTC.
We are experiencing issues with the Pull Requests dashboard that prevent users from filtering their pull requests. We have identified a mitigation and are deploying a fix. We'll post another update by 21:00 UTC.
We are experiencing issues with the Pull Requests dashboard that prevent users from filtering their pull requests. We have identified a mitigation and are deploying a fix. We'll post another update by 21:00 UTC.
We are experiencing issues with the Pull Requests dashboard that prevent users from filtering their pull requests. We have identified a mitigation and are deploying a fix. We'll post another update by 21:00 UTC.
We are experiencing issues with the Pull Requests dashboard that prevent users from filtering their pull requests. We have identified a mitigation and are deploying a fix. We'll post another update by 21:00 UTC.
We are experiencing issues with the Pull Requests dashboard that prevent users from filtering their pull requests. We have identified a mitigation and are deploying a fix. We'll post another update by 21:00 UTC.
We are experiencing issues with the Pull Requests dashboard that prevent users from filtering their pull requests. We have identified a mitigation and are deploying a fix. We'll post another update by 21:00 UTC.
We are experiencing issues with the Pull Requests dashboard that prevent users from filtering their pull requests. We have identified a mitigation and are deploying a fix. We'll post another update by 21:00 UTC.
We are experiencing issues with the Pull Requests dashboard that prevent users from filtering their pull requests. We have identified a mitigation and are deploying a fix. We'll post another update by 21:00 UTC.
We are experiencing issues with the Pull Requests dashboard that prevent users from filtering their pull requests. We have identified a mitigation and are deploying a fix. We'll post another update by 21:00 UTC.
We're deploying a fix for pull request filtering. Full rollout across all regions is expected within 60 minutes.
We're deploying a fix for pull request filtering. Full rollout across all regions is expected within 60 minutes.
We're deploying a fix for pull request filtering. Full rollout across all regions is expected within 60 minutes.
We're deploying a fix for pull request filtering. Full rollout across all regions is expected within 60 minutes.
We're deploying a fix for pull request filtering. Full rollout across all regions is expected within 60 minutes.
We're deploying a fix for pull request filtering. Full rollout across all regions is expected within 60 minutes.
We're deploying a fix for pull request filtering. Full rollout across all regions is expected within 60 minutes.
We're deploying a fix for pull request filtering. Full rollout across all regions is expected within 60 minutes.
We're deploying a fix for pull request filtering. Full rollout across all regions is expected within 60 minutes.
We're deploying a fix for pull request filtering. Full rollout across all regions is expected within 60 minutes.
We're deploying a fix for pull request filtering. Full rollout across all regions is expected within 60 minutes.
The issue on https://github.com/pulls is now fully resolved. All tabs are working again.
The issue on https://github.com/pulls is now fully resolved. All tabs are working again.
The issue on https://github.com/pulls is now fully resolved. All tabs are working again.
The issue on https://github.com/pulls is now fully resolved. All tabs are working again.
The issue on https://github.com/pulls is now fully resolved. All tabs are working again.
The issue on https://github.com/pulls is now fully resolved. All tabs are working again.
The issue on https://github.com/pulls is now fully resolved. All tabs are working again.
The issue on https://github.com/pulls is now fully resolved. All tabs are working again.
The issue on https://github.com/pulls is now fully resolved. All tabs are working again.
The issue on https://github.com/pulls is now fully resolved. All tabs are working again.
The issue on https://github.com/pulls is now fully resolved. All tabs are working again.
On March 2nd, 2026, between 7:10 UTC and 22:04 UTC the pull requests service was degraded. Users navigating between tabs on the pull requests dashboard were met with 404 errors or blank pages.<br /><br />This was due to a configuration change deployed on February 27th at 11:03 PM UTC. We mitigated the incident by reverting the change.<br /><br />We’re working to improve monitoring for the page to automatically detect and alert us to routing failures.
On March 2nd, 2026, between 7:10 UTC and 22:04 UTC the pull requests service was degraded. Users navigating between tabs on the pull requests dashboard were met with 404 errors or blank pages.<br /><br />This was due to a configuration change deployed on February 27th at 11:03 PM UTC. We mitigated the incident by reverting the change.<br /><br />We’re working to improve monitoring for the page to automatically detect and alert us to routing failures.
On March 2nd, 2026, between 7:10 UTC and 22:04 UTC the pull requests service was degraded. Users navigating between tabs on the pull requests dashboard were met with 404 errors or blank pages.<br /><br />This was due to a configuration change deployed on February 27th at 11:03 PM UTC. We mitigated the incident by reverting the change.<br /><br />We’re working to improve monitoring for the page to automatically detect and alert us to routing failures.
On March 2nd, 2026, between 7:10 UTC and 22:04 UTC the pull requests service was degraded. Users navigating between tabs on the pull requests dashboard were met with 404 errors or blank pages.<br /><br />This was due to a configuration change deployed on February 27th at 11:03 PM UTC. We mitigated the incident by reverting the change.<br /><br />We’re working to improve monitoring for the page to automatically detect and alert us to routing failures.
On March 2nd, 2026, between 7:10 UTC and 22:04 UTC the pull requests service was degraded. Users navigating between tabs on the pull requests dashboard were met with 404 errors or blank pages.<br /><br />This was due to a configuration change deployed on February 27th at 11:03 PM UTC. We mitigated the incident by reverting the change.<br /><br />We’re working to improve monitoring for the page to automatically detect and alert us to routing failures.
On March 2nd, 2026, between 7:10 UTC and 22:04 UTC the pull requests service was degraded. Users navigating between tabs on the pull requests dashboard were met with 404 errors or blank pages.<br /><br />This was due to a configuration change deployed on February 27th at 11:03 PM UTC. We mitigated the incident by reverting the change.<br /><br />We’re working to improve monitoring for the page to automatically detect and alert us to routing failures.
On March 2nd, 2026, between 7:10 UTC and 22:04 UTC the pull requests service was degraded. Users navigating between tabs on the pull requests dashboard were met with 404 errors or blank pages.<br /><br />This was due to a configuration change deployed on February 27th at 11:03 PM UTC. We mitigated the incident by reverting the change.<br /><br />We’re working to improve monitoring for the page to automatically detect and alert us to routing failures.
On March 2nd, 2026, between 7:10 UTC and 22:04 UTC the pull requests service was degraded. Users navigating between tabs on the pull requests dashboard were met with 404 errors or blank pages.<br /><br />This was due to a configuration change deployed on February 27th at 11:03 PM UTC. We mitigated the incident by reverting the change.<br /><br />We’re working to improve monitoring for the page to automatically detect and alert us to routing failures.
On March 2nd, 2026, between 7:10 UTC and 22:04 UTC the pull requests service was degraded. Users navigating between tabs on the pull requests dashboard were met with 404 errors or blank pages.<br /><br />This was due to a configuration change deployed on February 27th at 11:03 PM UTC. We mitigated the incident by reverting the change.<br /><br />We’re working to improve monitoring for the page to automatically detect and alert us to routing failures.
On March 2nd, 2026, between 7:10 UTC and 22:04 UTC the pull requests service was degraded. Users navigating between tabs on the pull requests dashboard were met with 404 errors or blank pages.<br /><br />This was due to a configuration change deployed on February 27th at 11:03 PM UTC. We mitigated the incident by reverting the change.<br /><br />We’re working to improve monitoring for the page to automatically detect and alert us to routing failures.
On March 2nd, 2026, between 7:10 UTC and 22:04 UTC the pull requests service was degraded. Users navigating between tabs on the pull requests dashboard were met with 404 errors or blank pages.<br /><br />This was due to a configuration change deployed on February 27th at 11:03 PM UTC. We mitigated the incident by reverting the change.<br /><br />We’re working to improve monitoring for the page to automatically detect and alert us to routing failures.