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/.
Jun 08, 2026 - 14:28 EDT
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.
Related
No incidents or maintenance related to this downtime.
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. Posted on
May 29, 2026 - 11:52 EDT
Completed -
The scheduled maintenance has been completed.
Jun 9, 12:00 EDT
In progress -
Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jun 9, 11:00 EDT
Update -
We will be undergoing scheduled maintenance during this time.
Jun 1, 17:01 EDT
Scheduled -
As previously announced, 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 • June 1, 2026: Enforcement begins on Shared Stacks. • 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.
Resolved -
As of 18:42 UTC the upstream provider began to accept log messages again consistently and this issue is now remediated.
Jun 3, 15:16 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.
Jun 3, 12:02 EDT