Aptible: A small number of deployments failed with an internal error
Timeline of updates
- resolved
During a routine software update, one server in one of Aptible's non-production infrastructure stacks didn't receive updated software, and as a result, app deployments that were scheduled there did not succeed. Due to the limited scope of the issue, only a very small number of apps and deployments were affected (respectively 7 apps over 14 deployments). If you're investigating a deployment failure, you can identify affected deployments by an internal error logged in your deployment output immediately after attempting to lock ports. Running apps were not affected (neither in production nor development environments).
From Aptible’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.aptible.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by Aptible, started 2017-02-06 21:13 UTC, resolved after 0 min, 1 update(s).
- Title
- A small number of deployments failed with an internal error
- Vendor
- Aptible
- Date
- URL
- https://rewindex.com/company/aptible/incidents/pqft0r1t495q
Aptible profileRecent Aptible incidentsAll outages on February 6, 2017Aptible in February 2017MarkdownJSON