THIS IS A SCHEDULED EVENT Oct <var data-var='date'>5</var>, <var data-var='time'>22:00</var> - <var data-var='time'>22:30</var> EDT Oct <var data-var='date'> 5</var>, <var data-var='time'>12:21</var> EDT Scheduled - During this period we will be performing maintenance on our Git server (git.aptible.com and beta.aptible.com), 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

Sep <var data-var='date'>23</var>, <var data-var='time'>23:15</var> EDT Resolved - This incident has been resolved. Sep <var data-var='date'>23</var>, <var data-var='time'>17:07</var> EDT Update - We are continuing to investigate this issue. We will update this notice when we restore SSH on Shared Stacks, or by 9 am ET, 2026-09-24. Sep <var data-var='date'>23</var>, <var data-var='time'>11:12</var> EDT Investigating - Aptible SSH sessions on Shared Stacks are temporarily unavailable. We disabled these sessions while we assess a recently reported Linux kernel vulnerability. We have not confirmed any impact to Aptible at this time, but continue our investigation today. Apps, databases, deploys, and endpoints on Shared Stacks are operating as usual. Aptible SSH on Dedicated Stacks remains available. No action is needed. We will update this notice when we restore SSH on Shared Stacks, or by 5pm ET, 2026-09-23.

Aptible SSH sessions on Shared Stacks are temporarily disabled

Sep <var data-var='date'>18</var>, <var data-var='time'>23:15</var> EDT Completed - The scheduled maintenance has been completed. Sep <var data-var='date'>18</var>, <var data-var='time'>23:00</var> EDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Sep <var data-var='date'>18</var>, <var data-var='time'>21:22</var> EDT Scheduled - During this period we will be performing maintenance on our Git server (git.aptible.com and beta.aptible.com), 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.

Jul <var data-var='date'>27</var>, <var data-var='time'>11:12</var> EDT Resolved - This incident has been resolved. Jul <var data-var='date'>27</var>, <var data-var='time'>09:43</var> EDT Monitoring - We have applied a mitigation and re-enabled operations in us-east-1. We are monitoring for stability and will resolve this incident once we confirm conditions remain stable. Jul <var data-var='date'>27</var>, <var data-var='time'>08:55</var> EDT Update - Operations remain disabled in us-east-1 while we continue to investigate AWS networking issues in the region. We are testing mitigations and will restore operations as soon as it is safe to do so. We will provide another update no later than 10:00 AM Eastern Time. Jul <var data-var='date'>27</var>, <var data-var='time'>06:31</var> EDT Investigating - 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. To avoid further issues, we have disabled operations in this region while we understand the full impact.

Operation failures due to AWS Outage

Jul <var data-var='date'>17</var>, <var data-var='time'>13:04</var> EDT Resolved - Following the fixes deployed per the previous update, we have seen stable performance on the LLM Gateway since 7:12 EDT and are resolving the issue. The root cause of this issue was a severe performance degradation in 3 specific endpoints: • `GET /models` • `GET /v1/models` • `GET /metadata/models` ...all of which return a list of available models. The performance issue on these endpoints was severe enough to cause significant request queueing and degraded performance for other unaffected endpoints. The fix we deployed added caching on this endpoint to ensure fast responses. Since those fixes have been deployed, we are no longer seeing request queueing or impacts to other LLM Gateway API endpoints. Jul <var data-var='date'>17</var>, <var data-var='time'>08:14</var> EDT Update - After a regression in performance starting at 9:57 UTC (5:57 EDT) and lasting until 11:12 UTC (7:12 EDT), we've deployed a potential fix and updated our service scaling. We are continuing to monitor whether these changes fully resolve the issue before closing this incident. Jul <var data-var='date'>16</var>, <var data-var='time'>20:02</var> EDT Monitoring - We have increased resource capacity, and we are monitoring the results. Jul <var data-var='date'>16</var>, <var data-var='time'>18:31</var> EDT Identified - We are aware of delayed and timed-out requests to the LLM Gateway. We have made some changes to help minimize the impact while engineers continue to address the root cause.

Delayed and Timed-out requests to the Aptible LLM Gateway

Jun <var data-var='date'>23</var>, <var data-var='time'>17:48</var> EDT Resolved - This incident has been resolved. Jun <var data-var='date'> 8</var>, <var data-var='time'>14:28</var> EDT Investigating - As part of our security policy and ongoing commitment to protecting customer workloads, we are applying patches for a newly disclosed Systemd vulnerability (CVE-2026-40226) across our platform. This patching will be rolled out automatically over the next several days. During this process, you may experience a momentary network disruption to running applications and databases. Customers configured for high-availability with horizontally-scaled services should experience little to no disruption from this update. No action is required on your part. If you have any questions or concerns, please reach out to our Support team at https://contact.aptible.com/.

Security Patching of Systemd Vulnerabilities

Jun <var data-var='date'>15</var>, <var data-var='time'>00:51</var> EDT Completed - The scheduled maintenance has been completed. Jun <var data-var='date'>15</var>, <var data-var='time'>00:47</var> EDT Verifying - Verification is currently underway for the maintenance items. Jun <var data-var='date'>14</var>, <var data-var='time'>20:00</var> EDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. May <var data-var='date'>29</var>, <var data-var='time'>11:52</var> EDT Scheduled - Between 8:00 PM and 12:00 AM Eastern (00:00–04:00 UTC) on Sunday, June 14th, we will perform an in-place upgrade of the load balancers that front Database Endpoints, migrating them to Network Load Balancers. This change improves performance and reliability, and is part of our ongoing infrastructure modernization. There is no scheduled downtime. New connections to your database endpoints will be accepted throughout the maintenance window. However, during the upgrade each endpoint's existing connections will be closed once and will need to be re-established. Most clients and connection poolers detect a dropped connection and reconnect automatically, so the typical impact is a brief, self-healing interruption with no intervention required. No action is required for the majority of customers. You can find your database endpoint details in the Aptible dashboard. If you have questions about how this affects a specific workload, please reach out to Aptible Support ahead of the window, and we'll be happy to answer any questions you have about this upgrade.

In-Place Upgrade of Database Endpoint Load Balancers

Jun <var data-var='date'> 9</var>, <var data-var='time'>12:00</var> EDT Completed - The scheduled maintenance has been completed. Jun <var data-var='date'> 9</var>, <var data-var='time'>11:00</var> EDT In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jun <var data-var='date'> 1</var>, <var data-var='time'>17:01</var> EDT Update - We will be undergoing scheduled maintenance during this time. Jun <var data-var='date'> 1</var>, <var data-var='time'>15:58</var> EDT Scheduled - As <a href="https://www.aptible.com/changelog/introducing-endpoint-and-image-deployment-settings" target="_blank">previously announced</a>, we are completing the migration away from managing endpoint behavior and image deployment details through app environment variables. These settings are now managed as dedicated Endpoint Settings and Image Deployment Settings. Rollout schedule &bull; June 1, 2026: Enforcement begins on Shared Stacks. &bull; June 9, 2026: Enforcement begins on Dedicated Stacks. What changes After enforcement begins on a stack, any deploy or configure operation that submits one of the impacted variables below with a value will be rejected with the error "Deprecated environment variable used," and the operation will not complete. This is triggered by what your deploy tooling sends on each operation, not by values already stored on your app, so an outdated CLI or a pre-v5 GitHub deploy action will fail because it resends these variables every time. Once your tooling no longer sends these variables, your deploys and configures succeed as normal. At that point any of these values still present in your app environment are migrated to the appropriate Endpoint or Image Deployment Settings and removed from the app environment automatically, with no change to how your apps and endpoints behave. What you need to do Most users can resolve this by updating their tooling: &bull; Update the Aptible CLI to v0.26.6 or later: <a href="https://www.aptible.com/docs/reference/aptible-cli/overview" target="_blank">https://www.aptible.com/docs/reference/aptible-cli/overview</a> &bull; Update the Aptible GitHub Deploy Action to v5: <a href="https://github.com/marketplace/actions/deploy-to-aptible" target="_blank">https://github.com/marketplace/actions/deploy-to-aptible</a> &bull; If you use Terraform, update to the aptible/aptible v0.10.0 provider, which accepts these as parameters on the aptible_endpoint and aptible_app resources: <a href="https://github.com/aptible/terraform-provider-aptible/releases/tag/v0.10.0" target="_blank">https://github.com/aptible/terraform-provider-aptible/releases/tag/v0.10.0</a> Impacted variables APTIBLE_DOCKER_IMAGE, APTIBLE_PRIVATE_REGISTRY_USERNAME, APTIBLE_PRIVATE_REGISTRY_PASSWORD, DISABLE_WEAK_CIPHER_SUITES, FORCE_SSL, IDLE_TIMEOUT, MAINTENANCE_PAGE_URL, RELEASE_HEALTHCHECK_TIMEOUT, SHOW_ELB_HEALTHCHECKS, SSL_CIPHERS_OVERRIDE, SSL_PROTOCOLS_OVERRIDE, STRICT_HEALTH_CHECKS For background and migration guidance, see: &bull; <a href="https://www.aptible.com/changelog/introducing-endpoint-and-image-deployment-settings" target="_blank">https://www.aptible.com/changelog/introducing-endpoint-and-image-deployment-settings</a> &bull; <a href="https://www.aptible.com/docs/core-concepts/apps/deploying-apps/configuration" target="_blank">https://www.aptible.com/docs/core-concepts/apps/deploying-apps/configuration</a> If you have questions, contact Aptible Support.

Enforcing deprecation of legacy app config variables

Jun <var data-var='date'> 3</var>, <var data-var='time'>15:16</var> EDT Resolved - As of 18:42 UTC the upstream provider began to accept log messages again consistently and this issue is now remediated. Jun <var data-var='date'> 3</var>, <var data-var='time'>12:02</var> EDT Investigating - There is some partial service degradation with log drains configured to send to Mezmo where not all log messages are being sent. Mezmo is rejecting logs over a certain size. We are actively investigating this issue with the upstream provider.

Partial Service Degradation with Mezmo Log Drains

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.

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.

Is Aptible down?

Aptible status is UP

Lastest published events

Git server maintenance

Aptible SSH sessions on Shared Stacks are temporarily disabled

Git server maintenance

Aptible Services, Components and Regions

Recent Aptible events

Git server maintenance

Aptible SSH sessions on Shared Stacks are temporarily disabled

Git server maintenance

Operation failures due to AWS Outage

Delayed and Timed-out requests to the Aptible LLM Gateway

Security Patching of Systemd Vulnerabilities