Netlify: Message Queueing Failure
Timeline of updates
- resolved
One of the servers in our main message queueing cluster had an issue that caused connections to fail or work unreliably. This caused problems with hanging builds, in some cases failed cache purges and background processing tasks such as asset optimiation and notifications being delayed. All systems returned to normal, and we continued to investigate the cause of the message queue failures and worked on plans to prevent recurrence.
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: minor) posted by Netlify, started 2017-05-16 16:27 UTC, resolved after 0 min, 1 update(s).
- Title
- Message Queueing Failure
- Vendor
- Netlify
- Date
- URL
- https://rewindex.com/company/netlify/incidents/7825p71xpsd5
Netlify profileRecent Netlify incidentsAll outages on May 16, 2017Netlify in May 2017MarkdownJSON