SparkPost: 7/14/2016 incident: some unrecoverable transmissions
Timeline of updates
- resolved
At around 15:00 GMT 7/14/2016 some transmissions that were in the active or delayed queues at that time or scheduled transmissions submitted in the last week but not yet processed became unrecoverable due to a configuration error on a single MTA. We have taken corrective actions to fix the underlying issue and prevent it from happening again. You may use the Message Events API to confirm if a message was processed as expected or needs to be resubmitted.
From SparkPost’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 status.sparkpost.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by SparkPost, started 2016-07-15 16:23 UTC, resolved after 0 min, 1 update(s).
- Title
- 7/14/2016 incident: some unrecoverable transmissions
- Vendor
- SparkPost
- Date
- URL
- https://rewindex.com/company/sparkpost/incidents/wl8k76vyzxwm
SparkPost profileRecent SparkPost incidentsAll outages on July 15, 2016SparkPost in July 2016MarkdownJSON