Aptible Status

System Status

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

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 18, 2025 - 16:00 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 March 15, 2025.

The new certificate will be available on Dedicated Stacks starting Tuesday Feb 18th at 4:00 PM Eastern. After this time, customers may restart impacted Databases on their Dedicated Stacks at their convenience to update the certificate.

During this window 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.

If you choose to take no action, Aptible's SRE team will identify any and all databases using the expiring certificate, and restart them on March 9th 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:

Feb 10 : New Database Certificate will be available on Shared Stacks. You may restart your database at any time before the maintenance time to complete the update on your own schedule.

Feb 16 : All Shared Stack databases will be restarted to load the new certificate

Feb 18 4:00 PM EST : The new certificate will be available for all Dedicated Stacks.

Feb 18 through March 9: Customers should restart impacted Databases on their Dedicated Stacks at their convenience to update the certificate.

March 9: 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 Eastern

--------

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: Please use the command `aptible db:restart`. 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 March 9th, 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://deploy-docs.aptible.com/docs/database-encryption-in-transit
Feb 18, 2025 16:00 - Mar 9, 2025 17:00 EDT

Uptime over the past 90 days. View historical uptime.

api.aptible.com Operational

90 days ago

100.0 % uptime

Today

auth.aptible.com Operational

90 days ago

100.0 % uptime

Today

dashboard.aptible.com Operational

90 days ago

100.0 % uptime

Today

Aptible Deploy Under Maintenance

90 days ago

99.98 % uptime

Today

Let's Encrypt Operational

AWS EC2 Operational

AWS EC2 (us-east-1 — Virginia) Operational

AWS EC2 (us-west-2 — Oregon) Operational

AWS EC2 (us-west-1 — California) Operational

AWS EC2 (us-east-2 — Ohio) Operational

AWS EC2 (ca-central-1 — Canada) Operational

AWS EC2 (sa-east-1 — São Paulo) Operational

AWS EC2 (eu-central-1 — Frankfurt) Operational

AWS EC2 (eu-west-1 — Ireland) Operational

AWS EC2 (eu-west-2 — London) Operational

AWS EC2 (eu-west-3 — Paris) Operational

AWS EC2 (ap-south-1 — Mumbai) Operational

AWS EC2 (ap-southeast-1 — Singapore) Operational

AWS EC2 (ap-southeast-2 — Sydney) Operational

AWS EC2 (ap-northeast-2 — Seoul) Operational

AWS EC2 (ap-northeast-1 — Tokyo) Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Scheduled Maintenance

Instance upgrades for Shared tenancy Stacks Feb 23, 2025 22:00-23:59 EST

Between 10:00 PM and 11:59 PM UTC on Feb 23rd, we will be performing an upgrade of the operating system for EC2 instances on shared stacks. The upgrade process will involve restarting Databases which were created prior to 2025, or haven't been restarted yet in 2025.

This impacts approximately 40% of databases on the shared stacks, and you can use the Aptible CLI command `aptible maintenance:dbs` to check which, if any, of your databases are impacted. You are free to restart them yourself at any time this week.
Posted on Feb 18, 2025 - 13:53 EST

Database SSL Certificate Rotation - Dedicated Stack Database restarts Mar 9, 2025 20:00 - Mar 10, 2025 00:00 EDT

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 March 15, 2025.

Aptible's SRE team will identify any and all databases still using the expiring certificate, and restart them on March 9th between 8:00 PM and 11:59 PM Eastern.

You may of course restart the database at any time of your choosing after Feb 18th in order to avoid this automated restart.

--------

This notice pertains to one of three windows scheduled. The full timeline for Database certificate updates process is as follows:

Feb 10 : New Database Certificate will be available on Shared Stacks. You may restart your database at any time before the maintenance time to complete the update on your own schedule.

Feb 16 : All Shared Stack databases will be restarted to load the new certificate

Feb 18 4:00 PM EST : The new certificate will be available for all Dedicated Stacks.

Feb 18 through March 9: Customers should restart impacted Databases on their Dedicated Stacks at their convenience to update the certificate.

March 9: 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 Eastern

--------

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: Please use the command `aptible db:restart`. 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 March 9th, 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://deploy-docs.aptible.com/docs/database-encryption-in-transit
Posted on Feb 10, 2025 - 17:49 EST

Past Incidents

Feb 18, 2025

Unresolved incident: Database SSL Certificate Rotation - Dedicated Stack Database self-service window.

Feb 17, 2025

Database SSL Certificate Rotation - Shared Stacks Database restarted automatically

Completed - The scheduled maintenance has been completed.
Feb 17, 00:00 EST

In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 16, 20:00 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 March 15, 2025.

Aptible will restart the impacted Databases on Shared Stacks for you on Friday February 16th.

Additional maintenance periods will be scheduled for updating Databases hosted on Dedicated Stacks.

--------

This notice pertains to one of three windows scheduled. The full timeline for Database certificate updates process is as follows:

Feb 10 : New Database Certificate will be available on Shared Stacks. You may restart your database at any time before the maintenance time to complete the update on your own schedule.

Feb 16 : All Shared Stack databases will be restarted to load the new certificate

Feb 18 4:00 PM EST : The new certificate will be available for all Dedicated Stacks.

Feb 18 through March 9: Customers should restart impacted Databases on their Dedicated Stacks at their convenience to update the certificate.

March 9: 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 Eastern

--------

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: Please use the command `aptible db:restart`. 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 March 9th, 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://deploy-docs.aptible.com/docs/database-encryption-in-transit
Feb 10, 17:49 EST

Feb 16, 2025

Feb 15, 2025

No incidents reported.

Feb 14, 2025

No incidents reported.

Feb 13, 2025

Operations blocked - Route 53 propagation delays

Resolved - This incident has been resolved.
Feb 13, 19:48 EST

Monitoring - 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.
Feb 13, 19:26 EST

Identified - 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.

In order to prevent Apps and Databases DNS records from reaching an inconsistent state, we are temporarily blocking Operations.

Performance and reachability of existing Apps and Database is not impacted.
Feb 13, 18:51 EST

Feb 12, 2025

No incidents reported.

Feb 11, 2025

No incidents reported.

Feb 10, 2025

No incidents reported.

Feb 9, 2025

No incidents reported.

Feb 8, 2025

No incidents reported.

Feb 7, 2025

No incidents reported.

Feb 6, 2025

No incidents reported.

Feb 5, 2025

Database provision errors

Resolved - This incident has been resolved.
Feb 5, 15:13 EST

Update - We are continuing to work on a fix for this issue.
Feb 5, 15:03 EST

Identified - We've identified an error blocking the creation of new Databases on the platform, and our team is applying a fix.

Reachability of your existing databases, and the ability to scale or restart them is not impacted.
Feb 5, 15:02 EST

Feb 4, 2025

No incidents reported.

Related