rewindex

CompaniesVercelIncidents

Vercel: GitHub deployment and login errors

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatewww.vercel-status.com (opens in new tab)
Part of an outage event

GitHub outage, Apr 21, 2020 · 6 vendors, 8 incidents

Vercel’s incident blames GitHub as the cause. (hop 1, posted +0 min vs GitHub’s own post)

“…GitHub deployment and login errors Due to a problem with GitHub, we experienced delayed deployments made with Vercel for GitHub and issues when using GitHub login. The issue was resolved after GitHub…”

Swipe sideways to see the whole diagram.

GitHubposted 15:45 UTCWithin an hour4 vendors, 4 blamed GitHubv0, Vercel, Travis CI, SentryVercel (this incident)posted +0 min
GitHubposted 15:45 UTCWithin an hour4 vendors, 4 blamed GitHubv0, Vercel, Travis CI, SentryVercel (this incident)posted +0 min
Vercel is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["GitHub<br/>posted 15:45 UTC"]:::root
  h1["Within an hour<br/>4 vendors, 4 blamed GitHub<br/>v0, Vercel, Travis CI, Sentry"]:::blames
  root --> h1
  me["Vercel (this incident)<br/>posted +0 min"]:::me
  h1 --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Timeline of updates

  1. resolved

    Due to a problem with GitHub, we experienced delayed deployments made with Vercel for GitHub and issues when using GitHub login. The issue was resolved after GitHub applied a fix.

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 2020-04-21 15:45 UTC, resolved after 0 min, 1 update(s).

Title
GitHub deployment and login errors
Vendor
Vercel
Date
URL
https://rewindex.com/company/vercel/incidents/7gmr4383svq7

Vercel profileRecent Vercel incidentsAll outages on April 21, 2020Vercel in April 2020MarkdownJSON