Braze: Database migration
Timeline of updates
- resolved
Due to an unforeseen complication during a database migration, between 10:51pm ET and 11:22pm ET, some data may not have been processed from our /users/track API endpoint, and some local time campaigns may not have been delivered to eligible users during that time. We are updating our migration processes to prevent and detect this type of error in the future.
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 2015-07-16 02:51 UTC, resolved after 0 min, 1 update(s).
- Title
- Database migration
- Vendor
- Braze
- Date
- URL
- https://rewindex.com/company/braze/incidents/f4cknp94k9sc
Braze profileRecent Braze incidentsAll outages on July 16, 2015Braze in July 2015MarkdownJSON