Amplitude: SSL certificate rotated
Timeline of updates
- resolved
We upgraded our SSL certificate for api.amplitude.com, as this certificate had expired. The new bundle that our provider issued contained a different validation certificate. This caused problems for an extremely small number of iOS/Android SDK customers who pin the root certificate (an uncommon practice). These customers' applications did not recognized our new certificate, and were unable to send events to api.amplitude.com. Fortunately, we were able to have our provider issue a new certificate that used the old validation certificate. We installed this on our server on 2/18, which should have resolved the issue. In most cases, the affected SDKs should have sent any events once the correct certificate was uploaded. Our SDKs cache up to 1,000 customer events and will retry until they are successful. However, in a few cases, events may have been lost. We encourage any customers to reach out to us if they suspect they may have been affected.
From Amplitude’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.amplitude.com (opens in new tab).
Cite this
Status incident (vendor impact label: minor) posted by Amplitude, started 2020-02-14 20:00 UTC, resolved after 0 min, 1 update(s).
- Title
- SSL certificate rotated
- Vendor
- Amplitude
- Date
- URL
- https://rewindex.com/company/amplitude/incidents/dxtdykzr6s25
Amplitude profileRecent Amplitude incidentsAll outages on February 14, 2020Amplitude in February 2020MarkdownJSON