Vendor Status Watch

← all vendors

Aptible status history

Current state: operational — “All Systems Operational” per https://status.aptible.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

0incidents, last 30 days
2incidents, last 90 days
19incidents on record
Incidents per week, last 12 weeks:

How long do Aptible incidents last?

4.0 hmedian incident duration19 measured
26.5 h90th percentile1 in 10 ran longer
4.3 hmedian, major/critical only2 incidents

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)

StartedIncidentStatusImpactDuration
2026-07-27 10:31 UTCOperation failures due to AWS Outageresolvedmajor4 h 40 min
2026-07-16 22:31 UTCDelayed and Timed-out requests to the Aptible LLM Gatewayresolvedminor18 h 32 min
2026-06-08 18:28 UTCSecurity Patching of Systemd Vulnerabilitiesresolvedminor15 d 3 h
2026-06-03 16:02 UTCPartial Service Degradation with Mezmo Log Drainsresolvedminor3 h 13 min
2026-05-08 05:02 UTCAptible response to CVE-2026-43284resolvednone10 h 32 min
2026-05-08 01:05 UTCInstability in us-east-1resolvednone26 h 30 min
2026-04-29 22:40 UTCAptible response to CVE-2026-31431resolvednone0 min
2026-04-19 02:03 UTCService degradation affecting api.aptible.comresolvednone1 h 06 min
2026-03-17 22:33 UTCus-east-1 Intermittent DNS Resolution Errorspostmortemminor59 min
2025-12-31 10:48 UTCPerformance issues on auth.aptible.comresolvedcritical4 h 00 min
2025-12-30 02:14 UTCCVE-2025-14847: MongoDB unauthenticated information leakresolvednone15 h 01 min
2025-12-05 14:39 UTCCVE-2025-55182: React server component vulnerabilityresolvednone3 d 2 h
2025-11-05 15:59 UTCPlatform API Performance Degradationresolvedminor7 min
2025-10-29 21:17 UTCOperations Impacted by Host Provisioning Failuresresolvedminor33 min
2025-10-28 17:09 UTCDelays and failures for provisioning-related operations in us-east-1resolvednone3 h 59 min
2025-10-20 11:53 UTCOperation failures due to AWS Outageresolvednone11 h 11 min
2025-10-20 07:47 UTCOperation failures to to AWS API incidentresolvedminor1 h 58 min
2025-10-12 02:30 UTCDelays and queued operations in us-east-1resolvednone1 h 10 min
2025-10-10 15:53 UTCRedis Security Advisory (CVE-2025-49844)resolvednone0 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
}