Speakap status history
Current state: operational — “All Systems Operational” per https://speakap.statuspage.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Speakap incidents last?
From 9 incidents with a vendor-posted start and resolve time. Longest on record: Issue with chat feature on latest iOS app — 17.0 h (2026-02-02 17:33 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 (9)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-08-18 09:30 UTC | Partial outage for EU environment | resolved | none | 0 min |
| 2026-02-11 08:08 UTC | Chat connectivity issues | resolved | minor | 2 h 32 min |
| 2026-02-09 13:42 UTC | Backend outage | resolved | critical | 1 h 22 min |
| 2026-02-02 17:33 UTC | Issue with chat feature on latest iOS app | resolved | major | 17 h 01 min |
| 2025-12-04 09:06 UTC | Degraded performance for EU | resolved | minor | 4 h 10 min |
| 2025-12-03 18:09 UTC | Outage in EU | resolved | critical | 3 h 05 min |
| 2025-11-30 18:58 UTC | Issue posting messages in USA environment | resolved | major | 8 min |
| 2025-11-20 09:14 UTC | Delay in processing | resolved | minor | 45 min |
| 2025-09-10 11:17 UTC | EU backend slow or unavailable | resolved | minor | 3 h 03 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 Speakap with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"speakap"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}