Mattermost: This is an example incident
Timeline of updates
- monitoring
Let your users know once a fix is in place, and keep communication clear and precise.
- identified
As you continue to work through the incident, update your customers frequently.
- resolved
Empathize with those affected and let them know everything is operating as normal.
- investigating
When your product or service isn’t functioning as expected, let your customers know by creating an incident. Communicate early, even if you don’t know exactly what’s going on.
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 this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-17 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
6c876924d5dc0ba2…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Mattermost, started 2020-08-19 18:46 UTC, resolved after -1424 min, 4 update(s).
- Title
- This is an example incident
- Vendor
- Mattermost
- Date
- URL
- https://rewindex.com/company/mattermost/incidents/5y3nhvn8tx1h
Mattermost profileRecent Mattermost incidentsAll outages on August 19, 2020Mattermost in August 2020MarkdownJSON