Atlassian Loom Outage History
6 incidents recorded over the last 365 days, 6 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.
Every Recorded Atlassian Loom Incident
| Date | Incident | Duration | Status |
|---|---|---|---|
| May 8, 2026 | Multiple Atlassian services are experiencing issuesAll dates and times below are in UTC unless stated otherwise. ### Summary On May 8, 2026 between 00:22 and 06:08, one of our hosting providers suffered a significant incident in a specific availability zone in… | 16h 45m | Resolved |
| Apr 29, 2026 | Degraded performance of Loom appThe Team has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services. | 50 min | Resolved |
| Feb 3, 2026 | Confluence, Jira Mobile and Forge users may experience authentication issuesTeam has identified the root cause and the issue has now been resolved, and the impacted services are operating normally. Team will continue to monitor the impacted services. | 30 min | Resolved |
| Nov 19, 2025 | Some Loom users experiencing no audio when viewing recordingsThe rollout of the fix for impacted videos without audio has now completed. Customers should now be able to review existing videos without audio and see that it has been properly restored. If you are continuing to… | 7h 7m | Resolved |
| Oct 27, 2025 | Loom performance degraded### Summary On October 27, 2025 between 12:30 and 20:55 UTC, Loom was significantly degraded for all customers. Users also experienced short periods of degradation on October 28, 2025 from 20:26 to 20:33 UTC and… | 0 min | Resolved |
| Oct 20, 2025 | Atlassian Cloud Services impacted### Postmortem publish date: Nov 19th, 2025 ### Summary All dates and times below are in UTC unless stated otherwise. Customers utilizing Atlassian products experienced elevated error rates and degraded performance… | 21h 28m | Resolved |
Hear about the next one while it is open
Everything above is a record written after the fact. We can email you when the next Atlassian Loom incident opens instead, at the point where knowing still changes what you do.
Free, no password, no card. Unsubscribe in one click.
How to Read This Atlassian Loom Incident Log
Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before Atlassian Loom acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.
Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.
The longest single Atlassian Loom outage in this window ran 21h 28m, against a mean recovery of 7h 47m. If you depend on Atlassian Loom in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.