System Status
Update - Scheduled maintenance is still in progress. We will provide updates as necessary.
Feb 20, 2024 - 14:07 EST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 16, 2024 - 16:00 EST
Scheduled - Impacted database types: Elasticsearch, Redis, InfluxDB, MongoDB, RabbitMQ, CouchDB

The above listed database types will need to be restarted to update load a newly issued *.aptible.in certificate. The current certificate is set to expire March 2, 2024.

The new certificate will be available on Dedicated Stacks starting Friday Feb 16th 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 us 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 1st 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 process is as follows:

Feb 14 : New Database Certificate will be available on Shared Stacks.

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

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

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

March 1: 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 year), 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: Both `aptible db:restart` or `aptible db:reload` will work. 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 us 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 1st, 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 16, 2024 16:00 - Mar 1, 2024 16:00 EST
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 Operational
90 days ago
100.0 % 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
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
Impacted database types: Elasticsearch, Redis, InfluxDB, MongoDB, RabbitMQ, CouchDB

The above listed database types will need to be restarted to update load a newly issued *.aptible.in certificate. The current certificate is set to expire March 2, 2024.

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

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

--------

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

Feb 14 : New Database Certificate will be available on Shared Stacks.

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

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

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

March 1: 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 year), 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: Both `aptible db:restart` or `aptible db:reload` will work. 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 us 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 1st, 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 14, 2024 - 13:09 EST
Past Incidents
Feb 24, 2024

No incidents reported today.

Feb 23, 2024

No incidents reported.

Feb 22, 2024

No incidents reported.

Feb 21, 2024

No incidents reported.

Feb 20, 2024

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

Feb 19, 2024

No incidents reported.

Feb 18, 2024
Completed - The scheduled maintenance has been completed.
Feb 18, 22:55 EST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 18, 22:00 EST
Scheduled - On February 18th, between 10:00 PM EDT and 11:00 PM EDT, we will be restarting some key backend infrastructure in all supported regions.

The impact of this maintenance is that Aptible will temporarily block creation of new Operations on all stacks (Shared and Dedicated alike) in all regions. This impact will last approximately 5-10 minutes for each region.

There will be no impact to running Apps or Databases.

Feb 8, 12:05 EST
Feb 17, 2024

No incidents reported.

Feb 16, 2024
Completed - All impacted Databases on Shared Stacks have been restarted at this time.
Feb 16, 13:24 EST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Feb 16, 12:00 EST
Scheduled - Impacted database types: Elasticsearch, Redis, InfluxDB, MongoDB, RabbitMQ, CouchDB

The above listed database types will need to be restarted to update load a newly issued *.aptible.in certificate. The current certificate is set to expire March 2, 2024.

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 process is as follows:

Feb 14 : New Database Certificate will be available on Shared Stacks.

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

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

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

March 1: 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 year), 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: Both `aptible db:restart` or `aptible db:reload` will work. 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 us 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 1st, 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 14, 13:08 EST
Feb 15, 2024

No incidents reported.

Feb 14, 2024

No incidents reported.

Feb 13, 2024

No incidents reported.

Feb 12, 2024

No incidents reported.

Feb 11, 2024

No incidents reported.

Feb 10, 2024

No incidents reported.