Braze: Database shard failover
Timeline of updates
- resolved
On Sunday, January 18th at approximately 9:08pm ET, one of database shards on a cluster that hosts less than 10% of our customers experienced a failure, affecting data collection from the SDKs intermittently for approximately 3 minutes for these customers. Our secondary database quickly took over for the failed component and the system healed itself. Our DBAs are investigating the source of the failure.
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-01-19 02:08 UTC, resolved after 0 min, 1 update(s).
- Title
- Database shard failover
- Vendor
- Braze
- Date
- URL
- https://rewindex.com/company/braze/incidents/037dctzwcpsd
Braze profileRecent Braze incidentsAll outages on January 19, 2015Braze in January 2015MarkdownJSON