Pull Requests and Issues unavailable for signed-out users

Summary

Pull Requests and Issues unavailable for signed-out users

On June 8, 2026, between approximately 06:30 UTC and 08:36 UTC, signed-out users experienced sustained elevated HTTP 504 errors when accessing Pull Requests, Issues, releases, patch diffs, and other related GitHub.com pages. During the incident, approximately 17% of unauthenticated requests to the affected GitHub.com endpoints returned gateway timeout errors, peaking at roughly 34% of requests at around 06:50 UTC. Some GitHub Actions workflows were also affected when they depended on release downloads or related GitHub.com endpoints. The impact lasted approximately two hours and was isolated to unauthenticated traffic; signed-in users were not affected. <br /><br />The issue was caused by a significant increase in abusive traffic to specific GitHub.com endpoints. This degraded our ability to respond to unauthenticated requests, causing requests to queue beyond timeout thresholds and return gateway timeout errors. <br /><br />We mitigated the incident by identifying the anomalous traffic pattern and applying targeted blocks at the load balancer and application layers. Error rates returned to normal and affected services were fully restored by 08:36 UTC. <br /><br />To reduce the likelihood and impact of similar incidents in the future, we are improving automated detection and blocking for these traffic patterns, improving our emergency traffic-blocking deployment path, and evaluating routing changes for endpoints used by both signed-out users and automated workflows.

• Started

  Jun 8, 2026 · 7:11 AM

• Resolved

  Jun 8, 2026 · 8:36 AM

• Duration

  1h 24m

• Severity

  Critical

• ◐

  Investigating

  Jun 8 · 7:11 AM GitHub

  We are investigating reports of impacted performance for some GitHub services.

• ◐

  Investigating

  Jun 8 · 7:14 AM GitHub

  Issues is experiencing degraded availability. We are continuing to investigate.

• ◐

  Investigating

  Jun 8 · 7:31 AM GitHub

  Issues is experiencing degraded performance. We are continuing to investigate.

• ◐

  Investigating

  Jun 8 · 7:32 AM GitHub

  Pull Requests is experiencing degraded performance. We are continuing to investigate.

• ◐

  Investigating

  Jun 8 · 8:13 AM GitHub

  Following investigation, we are seeing that impact is limited to unauthenticated users when accessing Pull Requests, Issues, or Actions. Our team continues to work towards mitigation with more updates to follow as we have them.

• ◐

  Investigating

  Jun 8 · 8:27 AM GitHub

  Actions is experiencing degraded performance. We are continuing to investigate.

• ◉

  Monitoring

  Jun 8 · 8:35 AM GitHub

  The degradation affecting Actions, Issues and Pull Requests has been mitigated. We are monitoring to ensure stability.

• ✓

  Resolved

  Jun 8 · 8:36 AM GitHub

  On June 8, 2026, between approximately 06:30 UTC and 08:36 UTC, signed-out users experienced sustained elevated HTTP 504 errors when accessing Pull Requests, Issues, releases, patch diffs, and other related GitHub.com pages. During the incident, approximately 17% of unauthenticated requests to the affected GitHub.com endpoints returned gateway timeout errors, peaking at roughly 34% of requests at around 06:50 UTC. Some GitHub Actions workflows were also affected when they depended on release downloads or related GitHub.com endpoints. The impact lasted approximately two hours and was isolated to unauthenticated traffic; signed-in users were not affected. <br /><br />The issue was caused by a significant increase in abusive traffic to specific GitHub.com endpoints. This degraded our ability to respond to unauthenticated requests, causing requests to queue beyond timeout thresholds and return gateway timeout errors. <br /><br />We mitigated the incident by identifying the anomalous traffic pattern and applying targeted blocks at the load balancer and application layers. Error rates returned to normal and affected services were fully restored by 08:36 UTC. <br /><br />To reduce the likelihood and impact of similar incidents in the future, we are improving automated detection and blocking for these traffic patterns, improving our emergency traffic-blocking deployment path, and evaluating routing changes for endpoints used by both signed-out users and automated workflows.