rewindex

CompaniesNetlifyIncidents

Netlify: Some deploys failed - 500 errors

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

Timeline of updates

  1. resolved

    Between 15:14 UTC and 15:16 UTC, requests for uncached content may have failed with a 500 or 502 errors. Some deployments may have failed during this time. Our systems have quickly recovered and all deployments are completing successfully.

From Netlify’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.netlifystatus.com (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Netlify, started 2022-03-30 15:14 UTC, resolved after 0 min, 1 update(s).

Title
Some deploys failed - 500 errors
Vendor
Netlify
Date
URL
https://rewindex.com/company/netlify/incidents/xb3blkj2x4zn

Netlify profileRecent Netlify incidentsAll outages on March 30, 2022Netlify in March 2022MarkdownJSON