Braze: Connectivity to US cluster seeming due to AWS incident
Timeline of updates
- resolved
Device collection had been re-enabled shortly after the last update however we had noticed that one job queue shard was not functioning at 100%. We fixed that issue and all services normalized shortly thereafter. We continued to monitor US-EAST-01 cluster and are now resolving this incident.
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 2017-08-15 18:01 UTC, resolved after 4.2 h, 1 update(s).
- Title
- Connectivity to US cluster seeming due to AWS incident
- Vendor
- Braze
- Date
- URL
- https://rewindex.com/company/braze/incidents/rf9gv2yydp5f
Braze profileRecent Braze incidentsAll outages on August 15, 2017Braze in August 2017MarkdownJSON