Aptible Outage History

Aptible is aware of “Dirty Frag,” a recently disclosed Linux kernel vulnerability that may allow local privilege escalation under certain conditions [0]. We have taken action across the Aptible platform to protect all customer workloads against this vulnerability. No customer action is required at this time. We will continue to monitor upstream kernel, distribution, and security vendor guidance related to this vulnerability and will take any additional action if needed. [0] https://www.openwall.com/lists/oss-security/2026/05/07/8

We have unblocked operations from the specified region as we have seen successful provisioning and maintenance of new instance in that availability zone. Instances that were affected have not yet seen recovery, and the upstream AWS alert indicates they may still take hours of recovery.

A fix has been implemented and operations that were failing to enqueue during the availability outage have been retried. We will continue monitoring the situation.

We have observed DNS resolution error rates return to normal levels, and all dependent activities should be functioning normally. We will continue to monitor for an additional period to ensure the issue is fully resolved before closing the incident. Further updates will be posted here if we observe any recurrence.

Performance has improved since our mitigations. We are still monitoring the situation for continued degradation.

A fix has been implemented and we are monitoring the results. The operation block has been lifted.

A fix has been implemented and we are monitoring the results.

AWS has confirmed the issue with EC2 provisioning issues in us-east-1. Meanwhile, we have been able to implement a mitigation for affected customers. We will continue to leave this issue open and monitor its progress, and will provide any relevant updates as needed.

We are not currently seeing provisioning issues in AWS us-east-1. We are modifying the incident status to Monitoring, and will provide any relevant updates as needed.

Since the AWS issues seem serious, and to avoid any operation failures causing resources to get stuck in a transitional state, we are taking action to block all new operations on the platform at this time. We have identified no impact to acceibilty or preformance of running apps and database containers at this time.

AWS has indicated a fix has been applied, and we are re-enabling operations. We will continue to monitor for additional impact, as both Dockerhub and Quay.io were offline due to the AWS issue.

A fix has been implemented and we are monitoring the results.

No operation queueing issues have been observed since the last update. If you observed any operations that failed or were stuck in a "pending" state, please retry the operations and they should run without errors.

The errors have been resolved, however we are still monitoring

We've noticed that some Operations are failing due to Route53 record changes not propagating within the 10 minute time limit allowed by our platform. Running App and Databases are not impacted, but creation or deletion of Databases or Endpoints, as well as scaling services to/from zero containers may be impacted. We'll continue to monitor the situation and provide updates as we have any additional information to shre.

A fix has been implemented and we are monitoring the results.

We are experiencing intermittent failures in App and Database operations due to issues with an upstream provider. This issue only affects Apps and Databases with endpoints. Retrying the operation may resolve the issue. We are actively monitoring the situation and will provide updates once the problem is fully resolved.

We are noticing Route 53 record requests succeeding in a normal time frame, and are lifting the operation block at this time. We'll continue to observe running operations to ensure stability.