CompaniesModern TreasuryIncidents
Modern Treasury: Database Maintenance
Affected components: Platform/API
Timeline of updates
- identified
We are planning for a scheduled maintenance during that time..
Changes Rewindex caught on this incident
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. That proves these records existed by then and have not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-11-08 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
893039ad26d8b379…Version 2 captured
In the 2026-11-09 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
2368acf2d71da3e6…
Rewindex captured a newer version after the last checkpoint; the next run () commits it.
Impact, status and times are the vendor’s own, as last archived. View on status.moderntreasury.com (opens in new tab).
Cite this
Maintenance posted by Modern Treasury, started 2026-11-15 17:30 UTC, not resolved, 1 update(s); edited after publishing.
- Title
- Database Maintenance
- Vendor
- Modern Treasury
- Date
- URL
- https://rewindex.com/company/modern-treasury/incidents/cmw87yx2v000z13oa3ufy3ukk
Modern Treasury profileRecent Modern Treasury incidentsMarkdownJSON