Netlify: Failed lambda function invocations
Timeline of updates
- resolved
Between 1405 and 1705 UTC today, function invocations for some sites were passed incorrect parameters, which led to failed execution in some cases. This was caused by a bug in a deploy of our proxying service which we rolled back.
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 2019-12-10 14:00 UTC, resolved after 0 min, 1 update(s).
- Title
- Failed lambda function invocations
- Vendor
- Netlify
- Date
- URL
- https://rewindex.com/company/netlify/incidents/7dfvjlj24b3c
Netlify profileRecent Netlify incidentsAll outages on December 10, 2019Netlify in December 2019MarkdownJSON