Braze: Database host failover
Timeline of updates
- resolved
This morning at approximately 9:24am ET, one of our physical database hosts had a RAM failure. Secondary database servers automatically took over by 9:26am ET. During this two-minute period, there was an increase in 50x error codes by our APIs. Service is functioning normally, and our data center technicians will swap out the faulty RAM in the server.
From Braze’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 braze.statuspage.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Braze, started 2015-06-26 13:24 UTC, resolved after 0 min, 1 update(s).
- Title
- Database host failover
- Vendor
- Braze
- Date
- URL
- https://rewindex.com/company/braze/incidents/0mk3fq7qtqzs
Braze profileRecent Braze incidentsAll outages on June 26, 2015Braze in June 2015MarkdownJSON