Vercel: GitHub deployments degraded
Timeline of updates
- resolved
Between 22:58 and 23:33 UTC, an internal service degradation caused deployments triggered by GitHub to not be properly processed. Service has been fully restored, but impacted customers need to re-trigger deployments attempted during this interval.
From Vercel’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.vercel-status.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Vercel, started 2025-06-27 23:13 UTC, resolved after 0 min, 1 update(s).
- Title
- GitHub deployments degraded
- Vendor
- Vercel
- Date
- URL
- https://rewindex.com/company/vercel/incidents/7ltvp0vlcrmx
Vercel profileRecent Vercel incidentsAll outages on June 27, 2025Vercel in June 2025MarkdownJSON