Part of GitHub

GitHub Pages Outage History

GitHub Pages is up right now

GitHub Pages had 4 outages in the last 2 years totaling 5h 22m of downtime — averaging 0.2 incidents per month.

There were 4 GitHub Pages outages since April 13, 2026 totaling 5h 22m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://www.githubstatus.com

Minor July 2, 2026

Incident with Pages

Detected by Pingoru
Jul 02, 2026, 04:54 PM UTC
Resolved
Jul 02, 2026, 06:25 PM UTC
Duration
1h 31m
Affected: Pages
Timeline · 4 updates
  1. investigating Jul 02, 2026, 04:54 PM UTC

    We are investigating reports of degraded performance for Pages

  2. investigating Jul 02, 2026, 04:56 PM UTC

    We are investigating reports of slow and failing Pages deployments. Access to Pages is unaffected.

  3. investigating Jul 02, 2026, 05:57 PM UTC

    Pages deployment latency is recovering. The team continues working toward full mitigation and a return to nominal state.

  4. resolved Jul 02, 2026, 06:25 PM 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.

Read the full incident report →

Critical May 26, 2026

Incident with Actions and Pages

Detected by Pingoru
May 26, 2026, 10:57 AM UTC
Resolved
May 26, 2026, 01:18 PM UTC
Duration
2h 21m
Affected: ActionsPages
Timeline · 8 updates
  1. investigating May 26, 2026, 10:57 AM UTC

    We are investigating reports of degraded performance for Actions and Pages

  2. investigating May 26, 2026, 11:19 AM UTC

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

  3. investigating May 26, 2026, 11:53 AM UTC

    We are investigating authentication issues leading to failure in starting Actions runs and downloading actions. At this time the majority of Actions runs is impacted.

  4. investigating May 26, 2026, 12:17 PM UTC

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

  5. investigating May 26, 2026, 12:37 PM UTC

    We have identified the cause of the authentication issues affecting GitHub Actions and are actively working on mitigation

  6. monitoring May 26, 2026, 01:00 PM UTC

    The degradation affecting Actions and Pages has been mitigated. We are monitoring to ensure stability.

  7. monitoring May 26, 2026, 01:01 PM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  8. resolved May 26, 2026, 01:18 PM 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.

Read the full incident report →

Critical May 15, 2026

Actions is experiencing degraded availability

Detected by Pingoru
May 15, 2026, 08:13 AM UTC
Resolved
May 15, 2026, 08:48 AM UTC
Duration
34m
Affected: ActionsPages
Timeline · 7 updates
  1. investigating May 15, 2026, 08:13 AM UTC

    We are investigating reports of degraded availability for Actions

  2. investigating May 15, 2026, 08:14 AM UTC

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

  3. investigating May 15, 2026, 08:26 AM UTC

    The degradation affecting Actions has been mitigated. We are monitoring to ensure stability.

  4. investigating May 15, 2026, 08:27 AM UTC

    The degradation affecting Pages has been mitigated. We are monitoring to ensure stability.

  5. investigating May 15, 2026, 08:29 AM UTC

    We are monitoring an issue that was affecting GitHub Actions and causing downstream issues in GitHub Coding Agent and GitHub Code Review Agent. The issue has resolved now but we are closely monitoring our systems for full recovery.

  6. monitoring May 15, 2026, 08:41 AM UTC

    The degradation has been mitigated. We are monitoring to ensure stability.

  7. resolved May 15, 2026, 08:48 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.

Read the full incident report →