rewindex

CompaniesGitHub CopilotIncidents

GitHub Copilot: Incident With Actions

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatewww.githubstatus.com (opens in new tab)

Timeline of updates

  1. resolved

    Due to a degradation of one instance of our internal message delivery service, a percentage of jobs started between 06/30/2025 19:18 UTC and 06/30/2025 19:50 UTC failed, and are no longer retry-able. Runners assigned to these jobs will automatically recover within 24 hours, but deleting and recreating the runner will free up the runner immediately.

From GitHub Copilot’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on www.githubstatus.com (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by GitHub Copilot, started 2025-06-30 19:00 UTC, resolved after 0 min, 1 update(s).

Title
Incident With Actions
Vendor
GitHub Copilot
Date
URL
https://rewindex.com/company/github-copilot/incidents/crd2y6xy6knn

GitHub Copilot profileRecent GitHub Copilot incidentsAll outages on June 30, 2025GitHub Copilot in June 2025MarkdownJSON