Is Aptible down?
Last checked 4m agoActive incident: Security Patching of Systemd Vulnerabilities
Aptible is reporting degraded performance right now (last checked 4m ago). Services are up but slower or partially failing.
Real-time Aptible status, recent outages, and incident history — pulled directly from Aptible's official status page at https://status.aptible.com every 5 minutes. Pingoru tracks 20 Aptible services and has captured 10 incidents in the last 90 days (99.83% uptime). Get email, Slack, Discord, or webhook alerts the moment Aptible reports a new incident — free for 5 monitors, no credit card.
Active incident 1
- Aptible Deploy
Timeline · 1 update
- investigating · Jun 08, 2026, 06:28 PM UTC
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/.
Latest: 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 …
-
Recent outages & incidents
Past 90 days- Aptible Deploy
Timeline · 2 updates
- investigating · Jun 03, 2026, 04:02 PM UTC
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.
- resolved · Jun 03, 2026, 07:16 PM UTC
As of 18:42 UTC the upstream provider began to accept log messages again consistently and this issue is now remediated.
Latest: As of 18:42 UTC the upstream provider began to accept log messages again consistently and this issue is now remediated.
-
-
Timeline · 2 updates
- monitoring · May 08, 2026, 05:02 AM UTC
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
- resolved · May 08, 2026, 03:35 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
- Aptible Deploy
Timeline · 4 updates
- investigating · May 08, 2026, 01:05 AM UTC
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
- identified · May 08, 2026, 01:39 AM UTC
We have blocked operations from provisioning into the specified region
- monitoring · May 08, 2026, 02:02 PM UTC
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.
- resolved · May 09, 2026, 03:35 AM UTC
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.
Latest: 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 recov…
-
-
Timeline · 1 update
- resolved · Apr 29, 2026, 10:40 PM UTC
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/
Latest: 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…
-
- api.aptible.com
Timeline · 3 updates
- investigating · Apr 19, 2026, 02:03 AM UTC
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
- monitoring · Apr 19, 2026, 02:54 AM UTC
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.
- resolved · Apr 19, 2026, 03:10 AM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
See the full Aptible outage history
2 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.
Browse Aptible outage history →Or sign up free to get alerts when Aptible breaks · 10 free monitors · No credit card
- Started Jun 08, 2026, 06:28 PM UTC · ● 5d 5h
- Started Jun 03, 2026, 04:02 PM UTC · Resolved Jun 03, 2026, 07:16 PM UTC · 3h 13m
- Aptible response to CVE-2026-43284 ResolvedStarted May 08, 2026, 05:02 AM UTC · Resolved May 08, 2026, 03:35 PM UTC · 10h 32m
- Instability in us-east-1 ResolvedStarted May 08, 2026, 01:05 AM UTC · Resolved May 09, 2026, 03:35 AM UTC · 1d 2h
- Aptible response to CVE-2026-31431 ResolvedStarted Apr 29, 2026, 10:40 PM UTC · Resolved Apr 29, 2026, 10:40 PM UTC · —
- Started Apr 19, 2026, 02:03 AM UTC · Resolved Apr 19, 2026, 03:10 AM UTC · 1h 6m
- Started Mar 17, 2026, 10:33 PM UTC · Resolved Mar 17, 2026, 11:33 PM UTC · 59m