Loops: Primary database outage
Affected components: APIEmail Sending - LoopsLoopsAppSMTP RelayCampaignsEmail Sending - CampaignsEmail Sending - TransactionalTransactional
Timeline of updates
- investigating
We are currently investigating this issue.
- monitoring
A fix has been implemented and we are monitoring the results.
- monitoring
We are continuing to monitor for any further issues.
- monitoring
We are continuing to monitor for any further issues.
- resolved
This incident has been resolved.
- postmortem
A misconfiguration by our database vendor prevented our database from restarting successfully. The misconfiguration was identified and remedied. Campaigns scheduled to send during the outage are now sent. Loop emails scheduled to send during the outage are now sent. Transactional emails or API calls made during the outage window need to be retried.
Changes Rewindex caught on this incident
- Sep 16, 2024Major incident: Primary database outage
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 18:53 UTC
In the 2026-10-19 checkpoint, timestamped by FreeTSA and DigiCert on Oct 20, 00:41 UTC. Record hash
18422e117ab6d663…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).