# Braze: Database shard failover

> Braze status incident “Database shard failover” on 2015-01-19: impact none (vendor’s label), 0 min, 1 update(s). Archived by Rewindex.

Canonical: https://rewindex.com/company/braze/incidents/037dctzwcpsd
Last updated: 2015-01-19T02:08:00Z

- Impact (vendor’s label): none
- Status: resolved
- Started: 2015-01-19 02:08 UTC · Resolved: 2015-01-19 02:08 UTC · Duration: 0 min
- Updates: 1
- [Vendor status page: https://braze.statuspage.io/incidents/037dctzwcpsd](https://braze.statuspage.io/incidents/037dctzwcpsd)
- [Company: Braze](https://rewindex.com/company/braze.md)

## Timeline of updates

- **resolved** 2015-01-19 02:08 UTC: 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 the vendor’s published history: only the final update text is available for incidents before Rewindex began polling this page._

## 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).

- Canonical URL: https://rewindex.com/company/braze/incidents/037dctzwcpsd
- Citation: Braze, “Database shard failover” (2015-01-19 02:08 UTC). Archived by Rewindex: https://rewindex.com/company/braze/incidents/037dctzwcpsd (CC BY 4.0).
- Markdown link: `[Braze: Database shard failover (2015-01-19)](https://rewindex.com/company/braze/incidents/037dctzwcpsd)`


---
Canonical: https://rewindex.com/company/braze/incidents/037dctzwcpsd · Markdown: https://rewindex.com/company/braze/incidents/037dctzwcpsd.md · JSON: https://rewindex.com/api/v1/companies/braze/incidents/037dctzwcpsd · Data licensed CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) · Generated 2026-11-05T13:59:01.475Z