Braze: Database Failure
Timeline of updates
- resolved
All data processing and message sending in the affected data center caught up within a few minutes of the last status update, and all has remained stable since then. API calls from approximately 2:04pm until 2:09pm ET had elevated error rates, and data processing and message sending was queued for approximately 20 minutes starting at 2:13pm ET while we took backups and failed over services. As mentioned in the last status update, we believe this to have been a hypervisor issue with one of our machines.
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 2016-11-05 18:12 UTC, resolved after 1.6 h, 1 update(s).
- Title
- Database Failure
- Vendor
- Braze
- Date
- URL
- https://rewindex.com/company/braze/incidents/44hzc1fhv26t
Braze profileRecent Braze incidentsAll outages on November 5, 2016Braze in November 2016MarkdownJSON