May <var data-var='date'>10</var>, <var data-var='time'>18:00</var> EDT Completed - The scheduled maintenance has been completed. May <var data-var='date'>10</var>, <var data-var='time'>17:00</var> EDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'>10</var>, <var data-var='time'>09:39</var> EDT Scheduled - We will be undergoing scheduled maintenance during this time.

Scheduled Maintenance - api.aptible.com and auth.aptible.com

May <var data-var='date'>10</var>, <var data-var='time'>06:00</var> EDT Completed - The scheduled maintenance has been completed. May <var data-var='date'> 4</var>, <var data-var='time'>17:37</var> EDT Scheduled - We will be performing scheduled maintenance on api.aptible.com and auth.aptible.com on May 10th between 5pm and 6pm EDT. During this window, there may be brief periods of degraded availability for the Aptible API and authentication services. Running applications and databases will not be affected. Users may experience brief interruptions when logging in or making API requests during this time. We expect total downtime to be minimal and well within the maintenance window. We will send updates as maintenance progresses.

Scheduled Maintenance — api.aptible.com and auth.aptible.com

May <var data-var='date'> 8</var>, <var data-var='time'>23:35</var> EDT Resolved - An upstream AWS issue affected infrastructure in a single Availability Zone in us-east-1. During the event, we blocked provisioning into the affected zone and monitored AWS’s recovery efforts. AWS has since recovered enough of the affected availability zone for the impacted Aptible infrastructure to recover. We have also completed recovery of any Aptible-managed resources that required follow-up action on our side. Any customers with directly affected resources have been notified of resolution. We are continuing normal platform monitoring, but we are marking this incident as resolved on our end. May <var data-var='date'> 8</var>, <var data-var='time'>10:02</var> EDT Monitoring - 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. May <var data-var='date'> 7</var>, <var data-var='time'>21:39</var> EDT Identified - We have blocked operations from provisioning into the specified availability zone May <var data-var='date'> 7</var>, <var data-var='time'>21:05</var> EDT Investigating - Due to an underlying issue in AWS we are experiencing instability in a certain availability zone in us-east-1. We are investigating this issue and will follow up with recommendations shortly

Instability in us-east-1

May <var data-var='date'> 8</var>, <var data-var='time'>11:35</var> EDT Resolved - This incident has been resolved. May <var data-var='date'> 8</var>, <var data-var='time'>01:02</var> EDT Monitoring - 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

Aptible response to CVE-2026-43284

Apr <var data-var='date'>29</var>, <var data-var='time'>18:40</var> EDT Resolved - Aptible is aware of CVE-2026-31431, also known as “Copy Fail,” 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 CVE and will take any additional action if needed. [0] https://copy.fail/

Aptible response to CVE-2026-31431

Apr <var data-var='date'>18</var>, <var data-var='time'>23:10</var> EDT Resolved - This incident has been resolved. Apr <var data-var='date'>18</var>, <var data-var='time'>22:54</var> EDT Monitoring - 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. Apr <var data-var='date'>18</var>, <var data-var='time'>22:03</var> EDT Investigating - We are investigating an incident impacting api.aptible.com. Viewing current resources and running operations are currently impacted, however running applications and databases are unaffected

Service degradation affecting api.aptible.com

Mar <var data-var='date'>22</var>, <var data-var='time'>22:20</var> EDT Completed - The scheduled maintenance has been completed. Mar <var data-var='date'>22</var>, <var data-var='time'>22:00</var> EDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'>19</var>, <var data-var='time'>16:57</var> EDT Scheduled - During this period we will be performing maintenance on our Git server, which is used for Dockerfile based (`git push`) deployments. The server may be unavailable for deploying new code for a short period (2-5 minutes) during this window, and some deployments happening during this window which are being streamed via the CLI may see the deployment logs disconnected from the CLI. However, those deployment operations already running will keep running normally, and their result can be verified in the Aptible Dashboard (https://app.aptible.com/) No other impact to running services or the Aptible platform is expected.

Git server maintenance

Mar <var data-var='date'>17</var>, <var data-var='time'>19:33</var> EDT Resolved - This incident has been resolved. Mar <var data-var='date'>17</var>, <var data-var='time'>19:02</var> EDT Monitoring - 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. Mar <var data-var='date'>17</var>, <var data-var='time'>18:33</var> EDT Investigating - We are currently observing intermittent DNS resolution failures affecting infrastructure in us-east-1. These resolver errors may cause some Aptible Deploy operations (such as deploys, restarts, SSH, or container provisioning) to fail or time out. Applications running on Aptible Deploy that rely on network hostname resolution may also experience intermittent connection failures related to DNS resolution. We are actively working with our infrastructure providers to investigate the issue and will provide updates here as they are available.

us-east-1 Intermittent DNS Resolution Errors

Mar <var data-var='date'>14</var>, <var data-var='time'>22:12</var> EDT Completed - The scheduled maintenance has been completed. Mar <var data-var='date'>14</var>, <var data-var='time'>22:00</var> EDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'>13</var>, <var data-var='time'>12:32</var> EDT Scheduled - During this period we will be performing maintenance on our Git server, which is used for Dockerfile based (`git push`) deployments. The server may be unavailable for deploying new code for a short period (2-5 minutes) during this window, and some deployments happening during this window which are being streamed via the CLI may see the deployment logs disconnected from the CLI. However, those deployment operations already running will keep running normally, and their result can be verified in the Aptible Dashboard (https://app.aptible.com/) No other impact to running services or the Aptible platform is expected.

Mar <var data-var='date'>13</var>, <var data-var='time'>07:35</var> EDT Completed - The scheduled maintenance has been completed. Mar <var data-var='date'>13</var>, <var data-var='time'>07:00</var> EDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Mar <var data-var='date'>10</var>, <var data-var='time'>12:24</var> EDT Scheduled - Our team will be performing an upgrade on the bastion hosts for all Dedicated Stacks at March 13th at 7AM ET. The expected impact is that Ephemeral SSH sessions and Database Tunnels will be disconnected, but should immediately be available to reconnect. Operation logs being streamed via the CLI will also be interrupted, but the operations will continue without being impacted. App connectivity, Database connectivity, and internet connectivity will not be impacted by this maintenance. While the maintenance window to complete all upgrades is scheduled for 2 hours, the expected duration of impact of each stack is approximately 5 minutes.

Dedicated stack Bastion maintenance

Jan <var data-var='date'>31</var>, <var data-var='time'>20:02</var> EST Completed - The scheduled maintenance has been completed. Jan <var data-var='date'>12</var>, <var data-var='time'>16:02</var> EST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jan <var data-var='date'>12</var>, <var data-var='time'>16:01</var> EST Scheduled - Impacted database types: Elasticsearch, Redis, InfluxDB, MongoDB, RabbitMQ, CouchDB The above listed database types will need to be restarted to load a newly issued *.aptible.in certificate. The current certificate is set to expire February 2, 2026. You may restart your impacted database at any time of your choosing before January 31st in order to load the new certificate. Aptible's SRE team will identify any and all databases still using the expiring certificate, and restart them on January 31st, between 8:00 PM and 11:59 PM Eastern. -------- This notice pertains to one of three windows scheduled. The full timeline for Database certificate updates process is as follows: Jan 5 : New Database Certificate will be available on Shared Stacks. You may restart your impacted databases at any time before the maintenance time to complete the update on their own schedule. (Completed) Jan 11 8:00 PM EST: All remaining Shared Stack databases will be restarted to load the new certificate (Completed) Jan 12 4:00 PM EST : The new certificate will be available for all Dedicated Stacks. (Completed) Jan 12 through Jan 31: You may restart any impacted Databases on your Dedicated Stacks at your convenience to update the certificate. Jan 31: Aptible's SRE team will identify any and all databases using the expiring certificate, and restart them between 8:00 PM and 11:59 PM EST -------- FAQ: Q: Do I need to test anything? A: While we do not expect any compatibility issues (we're using the same issuer as the past several years), we have seen in rare occasions client applications may also need to be restarted after a database due to issues unrelated to the certificate. Q: Do I need to "restart", or can I "reload" my databases? A: Either "restart" or "reload" operations will suffice, through "reload" will be quicker. If you need to restart your database for any reason, either to scale the disk size or container size, the certificate will be updated. Q: How do I tell if my Database needs to be restarted to update the certificate? A: During the maintenance window for Dedicated stacks, you should use the Aptible CLI command `aptible maintenance:dbs` to track which databases are required to be restarted. Please note that you need at least "read" permissions to see the databases requiring a restart. To ensure you are viewing information for all environments, its best this is reviewed by an Account Owner, Aptible Deploy Owner, or any user with privileges to all environments. Q: What happens if I don't take any action, or miss restarting a Database? A: Aptible's SRE team will identify any remaining Databases on January 31st, and restart them between 8:00PM and 11:59PM Eastern. Q: What about PostgreSQL and MySQL? A: PostgreSQL and MySQL Databases hosted on Aptible use self-signed certificates, and no action is required for them at this time. https://www.aptible.com/docs/core-concepts/managed-databases/managing-databases/database-encryption/database-encryption-in-transit

Database SSL Certificate Rotation - Dedicated Stack Database self-service window

Jan <var data-var='date'>17</var>, <var data-var='time'>22:31</var> EST Completed - The scheduled maintenance has been completed. Jan <var data-var='date'>17</var>, <var data-var='time'>22:00</var> EST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jan <var data-var='date'>15</var>, <var data-var='time'>12:03</var> EST Scheduled - In order to upgrade key infrastructure backing our api.aptible.com, we will need to block operations for 3-5 minutes during this maintenance window. If you request an operation while the block in in place, you will receive the error 'Our Reliability Team has temporarily blocked this operation'. No running operations will be interrupted, and no other impact is expected.

Scheduled maintenance for api.aptible.com

Jan <var data-var='date'>17</var>, <var data-var='time'>22:30</var> EST Completed - The scheduled maintenance has been completed. Jan <var data-var='date'>17</var>, <var data-var='time'>22:00</var> EST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jan <var data-var='date'>15</var>, <var data-var='time'>12:00</var> EST Scheduled - During this period we will be performing maintenance on our Git server, which is used for Dockerfile based (`git push`) deployments. The server may be unavailable for deploying new code for a short period (2-5 minutes) during this window, and some deployments happening during this window which are being streamed via the CLI may see the deployment logs disconnected from the CLI. However, those deployment operations already running will keep running normally, and their result can be verified in the Aptible Dashboard (https://app.aptible.com/) No other impact to running services or the Aptible platform is expected.

Jan <var data-var='date'>11</var>, <var data-var='time'>20:40</var> EST Completed - The scheduled maintenance has been completed. Jan <var data-var='date'>11</var>, <var data-var='time'>20:00</var> EST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jan <var data-var='date'> 5</var>, <var data-var='time'>15:33</var> EST Scheduled - Impacted database types: Elasticsearch, Redis, InfluxDB, MongoDB, RabbitMQ, CouchDB The above listed database types will need to be restarted to load a newly issued *.aptible.in certificate. The current certificate is set to expire February 2, 2026. Aptible will restart the impacted Databases on Shared Stacks for you on Sunday January 11th. -------- Additional maintenance periods will be scheduled for updating Databases hosted on Dedicated Stacks. The full timeline for Database certificate updates process is as follows: Jan 5 : New Database Certificate will be available on Shared Stacks. You may restart your impacted databases at any time before the maintenance time to complete the update on their own schedule. Jan 11 8:00 PM EST: All remaining Shared Stack databases will be restarted to load the new certificate Jan 12 4:00 PM EST : The new certificate will be available for all Dedicated Stacks. Jan 12 through Jan 31: You may restart any impacted Databases on your Dedicated Stacks at your convenience to update the certificate. Jan 31: Aptible's SRE team will identify any and all databases using the expiring certificate, and restart them between 8:00 PM and 11:59 PM EST -------- FAQ: Q: Do I need to test anything? A: While we do not expect any compatibility issues (we're using the same issuer as the past several years), we have seen in rare occasions client applications may also need to be restarted after a database due to issues unrelated to the certificate. Q: Do I need to "restart", or can I "reload" my databases? A: Either "restart" or "reload" operations will suffice, through "reload" will be quicker. If you need to restart your database for any reason, either to scale the disk size or container size, the certificate will be updated. Q: How do I tell if my Database needs to be, and can be, restarted to update the certificate? A: During the maintenance window for Dedicated stacks, you should use the Aptible CLI command `aptible maintenance:dbs` to track which databases are required to be restarted. Please note that you need at least "read" permissions to see the databases requiring a restart. To ensure you are viewing information for all environments, its best this is reviewed by an Account Owner, Aptible Deploy Owner, or any user with privileges to all environments. Q: What happens if I don't take any action, or miss restarting a Database? A: Aptible's SRE team will identify any remaining Databases on January 31st, and restart them between 8:00PM and 11:59PM EST. Q: What about PostgreSQL and MySQL? A: PostgreSQL and MySQL Databases hosted on Aptible use self-signed certificates, and no action is required for them at this time. https://deploy-docs.aptible.com/docs/database-encryption-in-transit

Database SSL Certificate Rotation - Shared Stacks Database restarted automatically

Jan <var data-var='date'> 6</var>, <var data-var='time'>22:50</var> EST Completed - The scheduled maintenance has been completed. Jan <var data-var='date'> 6</var>, <var data-var='time'>22:37</var> EST Verifying - Verification is currently underway for the maintenance items. Jan <var data-var='date'> 6</var>, <var data-var='time'>22:00</var> EST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Dec <var data-var='date'>30</var>, <var data-var='time'>16:04</var> EST Scheduled - Our team will be performing an upgrade on the bastion hosts for all Dedicated Stacks at January 6th at 10PM EST. The expected impact is that Ephemeral SSH sessions and Database Tunnels will be disconnected, but should immediately be available to reconnect. Operation logs being streamed via the CLI will also be interrupted, but the operations will continue without being impacted. App connectivity, Database connectivity, and internet connectivity will not be impacted by this maintenance. While the maintenance window to complete all upgrades is scheduled for 2 hours, the expected duration of impact of each stack is approximately 5 minutes.

Jan <var data-var='date'> 2</var>, <var data-var='time'>21:15</var> EST Completed - The scheduled maintenance has been completed. Jan <var data-var='date'> 2</var>, <var data-var='time'>21:00</var> EST In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Dec <var data-var='date'>30</var>, <var data-var='time'>15:56</var> EST Scheduled - Our team will be performing an upgrade on the bastion hosts for all Shared Stacks. The expected impact is that Ephemeral SSH sessions and Database Tunnels will be disconnected, but should immediately be available to reconnect. Dedicated stacks will not be impacted at this time, and that maintenance will be scheduled separately for a later date.

Shared Stack Maintenance

Dec <var data-var='date'>31</var>, <var data-var='time'>09:49</var> EST Resolved - This incident has been resolved. Dec <var data-var='date'>31</var>, <var data-var='time'>06:33</var> EST Monitoring - Performance has improved since our mitigations. We are still monitoring the situation for continued degradation. Dec <var data-var='date'>31</var>, <var data-var='time'>05:48</var> EST Investigating - We are aware of degraded performance affecting auth.aptible.com. This affects all actions that interact with our APIs including login, viewing and managing resources, etc.

Performance issues on auth.aptible.com

Dec <var data-var='date'>30</var>, <var data-var='time'>12:15</var> EST Resolved - This incident has been resolved. Dec <var data-var='date'>29</var>, <var data-var='time'>21:14</var> EST Monitoring - The Aptible Security Team is aware of the recently disclosed vulnerability CVE-2025-14847 (https://github.com/advisories/GHSA-4742-mr57-2r9j) affected all MongoDB versions. The vulnerability could allow an attacker with network access to a MongoDB database to exfiltrate data, including sensitive data and/or credentials, without authenticating to the database. In response to the vulnerability, we have updated our supported MongoDB versions to prevent exploitations of this vulnerability. In addition, we have proactively restarted databases matching either of the following criteria, to ensure they are running on the latest protected versions: * All databases in shared-tenancy stacks, and * All databases with customer-created public endpoints that do not have access restricted to an IP allow list Since Aptible databases run on private networks by default, most Aptible managed MongoDB databases are not accessible from the internet or by other Aptible customers, and so are not vulnerable to CVE-2025-14847. As such, we did not proactively restart these databases. Customers may restart their databases at any time to update to the latest protected versions.

CVE-2025-14847: MongoDB unauthenticated information leak

Dec <var data-var='date'> 8</var>, <var data-var='time'>11:52</var> EST Resolved - This incident has been resolved. Dec <var data-var='date'> 5</var>, <var data-var='time'>09:39</var> EST Investigating - We are aware of the recently disclosed critical vulnerability CVE-2025-55182 (https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components) affecting React Server Components, which could allow remote code execution under certain conditions. This vulnerability affects certain React 19.x and frameworks that implement React Server Components, including Next.js. *Aptible Platform Impact:* Aptible has reviewed all infrastructure components that we manage and has confirmed that all are unaffected by this vulnerability. *Customer Application Impact:* If you are running applications on Aptible that use React Server Components, you may be affected. We have seen active exploitation of this vulnerability, and we recommend upgrading to the patched versions immediately. Specifically, applications using: - React 19.0.0, 19.1.0, 19.1.1, or 19.2.0 with react-server-dom-webpack, react-server-dom-turbopack, or react-server-dom-parcel - Next.js versions 14.3.0-canary.77 and all subsequent 14.3.x canary releases, 15.0.0, 15.0.1, 15.0.2, 15.0.3, 15.0.4, 15.1.0, 15.1.1, 15.1.2, 15.1.3, 15.1.4, 15.1.5, 15.1.6, 15.1.7, 15.1.8, 15.2.0, 15.2.1, 15.2.2, 15.2.3, 15.2.4, 15.2.5, 15.3.0, 15.3.1, 15.3.2, 15.3.3, 15.3.4, 15.3.5, 15.4.0, 15.4.1, 15.4.2, 15.4.3, 15.4.4, 15.4.5, 15.4.6, 15.4.7, 15.5.0, 15.5.1, 15.5.2, 15.5.3, 15.5.4, 15.5.5, 15.5.6, 15.6.0-canary.0 through 15.6.0-canary.57, 16.0.0, 16.0.1, 16.0.2, 16.0.3, 16.0.4, 16.0.5, 16.0.6 - Other frameworks implementing React Server Components including Vite, Parcel, React Router, RedwoodSDK, Waku *Additional Resources:* React Security Advisory: https://github.com/facebook/react/security/advisories/GHSA-fv66-9v8q-g76r Next.js Security Advisory: https://github.com/vercel/next.js/security/advisories/GHSA-9qr9-h5gf-34mp We will continue to update this incident page as more information becomes available.

CVE-2025-55182: React server component vulnerability

Nov <var data-var='date'> 5</var>, <var data-var='time'>11:07</var> EST Resolved - This incident has been resolved. Nov <var data-var='date'> 5</var>, <var data-var='time'>11:05</var> EST Monitoring - A fix has been implemented and we are monitoring the results. The operation block has been lifted. Nov <var data-var='date'> 5</var>, <var data-var='time'>10:59</var> EST Identified - We are investigating an issue causing degraded performance for the Aptible Platform API. As part of the mitigation, a temporary operation block across all regions is in place which prevents new operations from starting. This includes deployments, scaling actions, SSH sessions, and database tunnels. Running apps and databases are not affected. Next update We will provide an update by 11:30 ET or sooner.

Platform API Performance Degradation

Oct <var data-var='date'>29</var>, <var data-var='time'>17:50</var> EDT Resolved - This incident has been resolved. Oct <var data-var='date'>29</var>, <var data-var='time'>17:33</var> EDT Monitoring - A fix has been implemented and we are monitoring the results. Oct <var data-var='date'>29</var>, <var data-var='time'>17:17</var> EDT Investigating - We are currently experiencing failures when provisioning new hosts across all regions. This impacts operations that require new capacity, including but not limited to: app deploys, scaling events, and new database creation. Existing running workloads are not affected. Our team is actively investigating and working to restore normal operation performance. We will provide an update by no later than 5:45pm EST.

Operations Impacted by Host Provisioning Failures

Oct <var data-var='date'>28</var>, <var data-var='time'>17:08</var> EDT Resolved - This incident has been resolved. Oct <var data-var='date'>28</var>, <var data-var='time'>14:35</var> EDT Monitoring - 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. Oct <var data-var='date'>28</var>, <var data-var='time'>13:53</var> EDT Identified - We are now seeing additional broader EC2 provisioning issues in the AWS us-east-1 region that are outside the scope of our mitigation. Additional delays/failures on operations that require new capacity in us-east-1 may still occur at this time. We will provide our next update by 2:30 pm EST. Oct <var data-var='date'>28</var>, <var data-var='time'>13:32</var> EDT Monitoring - 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. Oct <var data-var='date'>28</var>, <var data-var='time'>13:09</var> EDT Investigating - We are seeing significantly increased provisioning times in the AWS us-east-1 region. This is affecting operations that require new capacity, including deployments, scaling, and creation of new resources. These operations may time out and fail. Our team is actively investigating and working to mitigate the impact. We will provide our next update by 2 pm EST.

Delays and failures for provisioning-related operations in us-east-1

Oct <var data-var='date'>20</var>, <var data-var='time'>19:04</var> EDT Resolved - AWS has marked the underlying issue in us-east-1 as resolved, and we’ve confirmed continued stability across all EC2-related operations. All Aptible operations are functioning normally, and this incident is now closed. Oct <var data-var='date'>20</var>, <var data-var='time'>16:03</var> EDT Update - Platform operations in us-east-1 are fully operational at this time. We continue to actively monitor EC2-related operations for any elevated error rates. We’ll keep this incident open while AWS’s own outage remains active and will close it once AWS has resolved their incident and we’ve confirmed continued stability across all operations in us-east-1. Oct <var data-var='date'>20</var>, <var data-var='time'>14:55</var> EDT Monitoring - We have lifted the operation block in us-east-1 as we are now seeing a sustained increase in successful EC2-related operations. While some operations may still fail as AWS recovery continues, the overall success rate has improved significantly. We are observing that EC2-related actions are taking longer to complete than usual, so users may experience increased delays in operation completion times. Given this progress, new operations have been re-enabled. We’ll continue to monitor closely and will update the incident status once failure rates and operation times have fully stabilized. Oct <var data-var='date'>20</var>, <var data-var='time'>14:04</var> EDT Update - We are starting to see EC2 provisioning operations in us-east-1 succeed again as AWS recovery efforts progress. We’re continuing to monitor closely, and if this trend holds, we expect to lift the operational block in the region shortly. We will provide another update as soon as the block is lifted or if conditions change. Oct <var data-var='date'>20</var>, <var data-var='time'>11:44</var> EDT Update - We are seeing continued widespread impact from the AWS outage in us-east-1. AWS has confirmed ongoing network and API failures within the EC2 internal network that are preventing new instance launches across multiple Availability Zones. To avoid any operation failures that could leave resources in a transitional state, we have implemented an operation block for all new operations in the us-east-1 region. Apps and databases already running on existing capacity continue to operate normally at this time. We are actively monitoring AWS recovery efforts and will lift the block once we confirm increased stability in the us-east-1 region. Further updates will be posted as they become available. Oct <var data-var='date'>20</var>, <var data-var='time'>11:16</var> EDT Update - We’re continuing to see widespread impact from the ongoing AWS outage in us-east-1. Most requests for new EC2 instances in this region are currently failing. As a result, any operations that require additional instance capacity, such as service scales, deployments, and other scaling-related actions, are likely to fail. This remains an evolving AWS issue, and we’ll provide updates as more information becomes available. At this time, apps and databases operating with existing capacity appear to be running normally without impact. Oct <var data-var='date'>20</var>, <var data-var='time'>09:56</var> EDT Update - We continue to see fall out from the AWS outage this morning. Operations that result in scaling capacity such as service scales, deployments, etc. may be impacted, resulting in failing operations. We recommend periodically retrying such operations. Oct <var data-var='date'>20</var>, <var data-var='time'>07:53</var> EDT Identified - AWS is experiencing an issue with their APIs in us-east-1, and many services are impacted at this time. This may lead to failed operations. There is currently no impact to availability for apps and databases running on Aptible at this time.

Operation failures due to AWS Outage

Oct <var data-var='date'>20</var>, <var data-var='time'>05:46</var> EDT Resolved - This incident has been resolved. Oct <var data-var='date'>20</var>, <var data-var='time'>05:30</var> EDT Update - 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. Oct <var data-var='date'>20</var>, <var data-var='time'>04:31</var> EDT Monitoring - 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. Oct <var data-var='date'>20</var>, <var data-var='time'>03:47</var> EDT Identified - AWS is experiencing an issue with their APIs in us-east-1, and many services are impacted at this time. This may lead to failed operations, but there appears to be no impact to availability for apps and databases running on Aptible at this time.

Operation failures to to AWS API incident

Oct <var data-var='date'>11</var>, <var data-var='time'>23:40</var> EDT Resolved - This incident has been resolved. Oct <var data-var='date'>11</var>, <var data-var='time'>23:40</var> EDT Update - 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. Oct <var data-var='date'>11</var>, <var data-var='time'>22:42</var> EDT Monitoring - A fix has been implemented and we are monitoring the results. Oct <var data-var='date'>11</var>, <var data-var='time'>22:30</var> EDT Investigating - One of our internal queuing systems observed a failure that has affected several operations enqueued in us-east-1. Our Reliability Team is restoring the queueing system and investigating the root cause of the failure.

Is Aptible down?

Aptible status is UP

Lastest published events

Scheduled Maintenance - api.aptible.com and auth.aptible.com

Scheduled Maintenance — api.aptible.com and auth.aptible.com

Instability in us-east-1

Aptible Services, Components and Regions

Recent Aptible events

Scheduled Maintenance - api.aptible.com and auth.aptible.com

Scheduled Maintenance — api.aptible.com and auth.aptible.com

Instability in us-east-1

Aptible response to CVE-2026-43284

Aptible response to CVE-2026-31431

Service degradation affecting api.aptible.com

Get your FREE account now,
5 monitors included!

Is Aptible down?

Aptible status is UP

Lastest published events

Scheduled Maintenance - api.aptible.com and auth.aptible.com

Scheduled Maintenance — api.aptible.com and auth.aptible.com

Instability in us-east-1

Aptible Services, Components and Regions

Recent Aptible events

Scheduled Maintenance - api.aptible.com and auth.aptible.com

Scheduled Maintenance — api.aptible.com and auth.aptible.com

Instability in us-east-1

Aptible response to CVE-2026-43284

Aptible response to CVE-2026-31431

Service degradation affecting api.aptible.com

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!