Resolved -
All residual domains have been processed. We will continue to monitor this moving forward, but this specific incident is resolved.
As mentioned before, if you are having issues regarding this problem, please contact support.
Feb 20, 21:51 PST
Monitoring -
The backlog processor has cycled through 100% of the domains. We will continue monitoring this issue and implement fixes and safety measures where necessary to ensure this does not happen again.
If you are still experiencing certificate expiration issues, please contact Ontraport Support.
Feb 20, 12:59 PST
Update -
The backlog process is at 98% complete.
Feb 20, 12:20 PST
Update -
The backlog processor is 90% complete.
Feb 20, 08:27 PST
Update -
The backlog processor is 81% complete.
Feb 19, 18:58 PST
Update -
The backlog processor is 72% complete.
Feb 19, 13:50 PST
Update -
The backlog continues to process and is at 62% complete.
Feb 19, 07:32 PST
Update -
The renewal processor is continuing to run through the backlog. The backlog is currently 30% complete at the time of this update.
While an exact ETA is not known, we are estimating another 12-16 hours for the backlog to be fully processed.
Feb 18, 15:58 PST
Identified -
An isolated grouping of HTTPS certificates have failed to renew resulting in browsers displaying "insecure site" messages. The primary affected certificates are clustered around the "ontralink.com" tracking link domain; there are also some non-tracking domains impacted.
The "ontralink.com" certificates have been repaired/renewed (roughly 99%), and the repair/renewal for other impacted domains is already underway (roughly 25% completed at the time of writing). While the renewal queue is processing, if you need an immediate fix, contact Ontraport Support and they can fast-track domains upon request.
This does not affect any new certificate issuances and should not affect certificates issued within the past 80 days.
We are continuing to investigate the root cause and will update this issue as more progress is made.
This notice is backdated to the earliest observed instance.
Feb 17, 21:00 PST