Braze: Intermittent API access for some customers
Timeline of updates
- resolved
Today at 5:29pm ET, one of our database servers that houses a very small fraction of our customers rapidly leaked memory and crashed, which caused some API calls to return 500 error codes. We quickly got the database operational and confirmed all API systems were fully back online for all customers by 5:36pm ET. Our DBAs have been investigating the root cause for past few hours and are escalating to the database vendor for support. We will update this page when we have a diagnosis. UPDATE: Our DBAs believe they have identified the issue due to a corrupted metadata file. The file has since been rebuilt successfully.
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 2014-11-19 22:29 UTC, resolved after 0 min, 1 update(s).
- Title
- Intermittent API access for some customers
- Vendor
- Braze
- Date
- URL
- https://rewindex.com/company/braze/incidents/8t94gmnw6ck5
Braze profileRecent Braze incidentsAll outages on November 19, 2014Braze in November 2014MarkdownJSON