Loom status history
Current state: operational — “All Systems Operational” per https://loom.status.atlassian.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Loom incidents last?
From 9 incidents with a vendor-posted start and resolve time. Longest on record: Atlassian Cloud Services impacted — 21.5 h (2025-10-20 07:56 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-05-08 03:00 UTC | Multiple Atlassian services are experiencing issues | postmortem | minor | 16 h 45 min |
| 2026-04-29 07:00 UTC | Degraded performance of Loom app | resolved | minor | 50 min |
| 2026-02-03 10:19 UTC | Confluence, Jira Mobile and Forge users may experience authentication issues | resolved | minor | 30 min |
| 2025-11-19 22:32 UTC | Some Loom users experiencing no audio when viewing recordings | resolved | major | 7 h 07 min |
| 2025-10-27 15:35 UTC | Loom performance degraded | postmortem | major | 6 h 24 min |
| 2025-10-20 07:56 UTC | Atlassian Cloud Services impacted | postmortem | none | 21 h 28 min |
| 2025-09-12 20:43 UTC | Issue with Loom Meeting Recordings in Zoom | resolved | major | 1 h 30 min |
| 2025-09-08 21:46 UTC | Issues with Recording on Loom Chrome Extension | resolved | none | 0 min |
| 2025-08-15 19:35 UTC | Loom Intermittent Issues | resolved | major | 23 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 Loom with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"loom"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}