Netlify: Incorrect function deployments affecting some Starter accounts
Timeline of updates
- resolved
On July 3rd between 10:34 - 12:06, and on July 4th between 09:07 - 10:29 (UTC times), our build system produced incorrect function deployments for a small subset of customers, which resulted in runtime errors with the 502 status code. This only affected a small subset of Starter accounts. We’ve fixed the underlying problem and we’re working on improving our monitoring and alerting on the matter. Meanwhile affected customers can fix the problem by redeploying.
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 2024-07-04 09:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Incorrect function deployments affecting some Starter accounts
- Vendor
- Netlify
- Date
- URL
- https://rewindex.com/company/netlify/incidents/t6v0d90ljgd5
Netlify profileRecent Netlify incidentsAll outages on July 4, 2024Netlify in July 2024MarkdownJSON