Apaleo status history
Current state: operational — “All Systems Operational” per https://status.apaleo.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Apaleo incidents last?
From 18 incidents with a vendor-posted start and resolve time. Longest on record: Webhook Delivery Latency - Partial Degradation — 47.6 h (2025-08-20 09:12 UTC). Excluded, never estimated: 1 scheduled maintenance. 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-09-15 22:13 UTC | DB infrastructure upgrade still in progress | resolved | maintenance | 1 h 31 min |
| 2026-08-27 13:30 UTC | We are currently investigating an issue affecting our platform. | resolved | minor | 4 h 14 min |
| 2026-08-11 11:00 UTC | Intermittent login failures via Single Sign-On (SSO) | resolved | none | 0 min |
| 2026-07-20 11:21 UTC | Investigating performance issue on rate plan pricing | resolved | none | 1 h 48 min |
| 2026-06-30 16:34 UTC | We are currently investigating an issue affecting our platform. | resolved | none | 1 h 25 min |
| 2026-05-05 10:16 UTC | Incident Notice | resolved | minor | 38 min |
| 2026-03-10 08:27 UTC | Night Audit Processing Delays for Some Accounts | resolved | minor | 7 h 10 min |
| 2026-03-09 16:26 UTC | Invoice Creation Issues | resolved | minor | 26 min |
| 2026-03-06 08:21 UTC | Night Audit Processing Delays for Some Accounts | resolved | minor | 2 h 17 min |
| 2026-02-21 00:36 UTC | Certificate Renewal | resolved | critical | 17 min |
| 2026-02-20 19:00 UTC | Webhooks and Payments delayed | resolved | none | 0 min |
| 2026-02-17 21:39 UTC | Webhooks and Payments are experiencing delays | resolved | major | 35 min |
| 2026-02-11 14:30 UTC | Transient authorization issues | resolved | minor | 1 h 20 min |
| 2026-01-29 09:00 UTC | A smaller technical issue with GET /finance/v1/folios | resolved | none | 0 min |
| 2025-11-18 13:23 UTC | Login and payment availability issue | resolved | major | 4 h 29 min |
| 2025-11-05 08:30 UTC | UI and API perfomance degradation and occasional timeouts | resolved | none | 0 min |
| 2025-10-23 11:30 UTC | Folio payments are facing delays in processing | resolved | minor | 3 h 10 min |
| 2025-10-01 09:03 UTC | API and UI outage | resolved | critical | 3 h 09 min |
| 2025-08-20 09:12 UTC | Webhook Delivery Latency - Partial Degradation | resolved | minor | 47 h 38 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 Apaleo with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"apaleo"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}