Braze: Minor REST API impact due to subprocessor performance issue
Timeline of updates
- resolved
Between 16:22 UTC and 17:51 UTC, Fastly, our subprocessor used as a CDN, experienced an incident that resulted in connection timeouts and other errors. https://status.fastly.com/incidents/f6nxztsb89fl (opens in new tab) At this point, that incident is resolved, and you should no longer be experiencing intermittent errors while connecting to Braze's APIs.
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 2020-01-22 17:30 UTC, resolved after 54 min, 1 update(s).
- Title
- Minor REST API impact due to subprocessor performance issue
- Vendor
- Braze
- Date
- URL
- https://rewindex.com/company/braze/incidents/cbvlc2wn321j
Braze profileRecent Braze incidentsAll outages on January 22, 2020Braze in January 2020MarkdownJSON