rewindex

CompaniesSparkPostIncidents

SparkPost: Some Java connection errors

No impact listedStatus: resolvedStarted Resolved (6 min)1 updatestatus.sparkpost.com (opens in new tab)

Timeline of updates

  1. resolved

    We will do a follow up investigation into the change that affects some older Java and ASP clients.

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 2017-02-13 22:08 UTC, resolved after 6 min, 1 update(s).

Title
Some Java connection errors
Vendor
SparkPost
Date
URL
https://rewindex.com/company/sparkpost/incidents/zgqzs499skj4

SparkPost profileRecent SparkPost incidentsAll outages on February 13, 2017SparkPost in February 2017MarkdownJSON