SparkPost: Service Degradation - SMTP delivery
Timeline of updates
- resolved
We identified and resolved the issue that was causing an increased number of delays due to "no mx record found". We will continue to monitor the situation.
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: minor) posted by SparkPost, started 2016-06-17 10:41 UTC, resolved after 1.4 h, 1 update(s).
- Title
- Service Degradation - SMTP delivery
- Vendor
- SparkPost
- Date
- URL
- https://rewindex.com/company/sparkpost/incidents/4bb7dml4c43t
SparkPost profileRecent SparkPost incidentsAll outages on June 17, 2016SparkPost in June 2016MarkdownJSON