Braze: Message sending delays
Timeline of updates
- resolved
This issue has been resolved. The issue was caused by a spike in one of our data centers to one of our scheduled message sending clusters, and when our systems automatically scaled up, load on the cluster increased, worsening problems and causing the delays. We have made software updates to our job scheduling system to solve this issue and will also be following up with other infrastructure enhancements.
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: minor) posted by Braze, started 2016-11-05 15:56 UTC, resolved after 47 min, 1 update(s).
- Title
- Message sending delays
- Vendor
- Braze
- Date
- URL
- https://rewindex.com/company/braze/incidents/34t1mtwsdd0m
Braze profileRecent Braze incidentsAll outages on November 5, 2016Braze in November 2016MarkdownJSON