Aptible status history
Current state: operational — “All Systems Operational” per https://status.aptible.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Aptible incidents last?
From 19 incidents with a vendor-posted start and resolve time. Longest on record: Security Patching of Systemd Vulnerabilities — 15.1 days (2026-06-08 18:28 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (19)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-07-27 10:31 UTC | Operation failures due to AWS Outage | resolved | major | 4 h 40 min |
| 2026-07-16 22:31 UTC | Delayed and Timed-out requests to the Aptible LLM Gateway | resolved | minor | 18 h 32 min |
| 2026-06-08 18:28 UTC | Security Patching of Systemd Vulnerabilities | resolved | minor | 15 d 3 h |
| 2026-06-03 16:02 UTC | Partial Service Degradation with Mezmo Log Drains | resolved | minor | 3 h 13 min |
| 2026-05-08 05:02 UTC | Aptible response to CVE-2026-43284 | resolved | none | 10 h 32 min |
| 2026-05-08 01:05 UTC | Instability in us-east-1 | resolved | none | 26 h 30 min |
| 2026-04-29 22:40 UTC | Aptible response to CVE-2026-31431 | resolved | none | 0 min |
| 2026-04-19 02:03 UTC | Service degradation affecting api.aptible.com | resolved | none | 1 h 06 min |
| 2026-03-17 22:33 UTC | us-east-1 Intermittent DNS Resolution Errors | postmortem | minor | 59 min |
| 2025-12-31 10:48 UTC | Performance issues on auth.aptible.com | resolved | critical | 4 h 00 min |
| 2025-12-30 02:14 UTC | CVE-2025-14847: MongoDB unauthenticated information leak | resolved | none | 15 h 01 min |
| 2025-12-05 14:39 UTC | CVE-2025-55182: React server component vulnerability | resolved | none | 3 d 2 h |
| 2025-11-05 15:59 UTC | Platform API Performance Degradation | resolved | minor | 7 min |
| 2025-10-29 21:17 UTC | Operations Impacted by Host Provisioning Failures | resolved | minor | 33 min |
| 2025-10-28 17:09 UTC | Delays and failures for provisioning-related operations in us-east-1 | resolved | none | 3 h 59 min |
| 2025-10-20 11:53 UTC | Operation failures due to AWS Outage | resolved | none | 11 h 11 min |
| 2025-10-20 07:47 UTC | Operation failures to to AWS API incident | resolved | minor | 1 h 58 min |
| 2025-10-12 02:30 UTC | Delays and queued operations in us-east-1 | resolved | none | 1 h 10 min |
| 2025-10-10 15:53 UTC | Redis Security Advisory (CVE-2025-49844) | resolved | none | 0 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch Aptible with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"aptible"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}