CompaniesAtlassian LoomIncidents
Atlassian Loom: Some Loom users experiencing no audio when viewing recordings
Affected components: AuthenticationLoom AIRecordingViewing
Timeline of updates
- identified
We are aware of some customers that are experiencing no audio when viewing their Loom recordings. Our team has identified this issue and is working urgently to restore the audio for these recordings.
Please rest assured that the audio has been recorded correctly, and we expect this to be fully available when this incident is resolved.
New recordings are no longer impacted by this issue.
We will provide an update within two hours with our progress as the team continues to investigate. - identified
Our team believes that we have identified the cause of the issue impacting audio during playback of videos for some customers.
As mentioned in our previous updates, new recordings will be working as expected, however videos recorded between 19 Nov 16:51 UTC and 19 Nov 21:30 UTC are expected to be impacted by this issue.
A fix for this issue to restore audio to these recordings is now being developed and tested, and we expect to have further update within 2 hours on progress for this resolution. - identified
The fix to resolve issues on audio recordings impacted by this incident is now being prepared for deployment.
Currently the expected duration of the rollout is 3 hours, at which point we expect the audio from the impacted recordings to be fully restored.
We will provide further update at that time with the progress of the restoration and provide any additional information that may be required. - resolved
The 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 see any issues with playback of your videos, please reach out to Loom support for assistance.
We apologize for any inconvenience caused by this issue.
Changes Rewindex caught on this incident
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured
In the 2026-10-22 checkpoint, timestamped by FreeTSA and DigiCert on . Record hash
3454485f1d5603d0…
Impact, status and times are the vendor’s own, as last archived. View on loom.status.atlassian.com (opens in new tab).
Cite this
Status incident (vendor impact label: major) posted by Atlassian Loom, started 2025-11-20 05:39 UTC, resolved after 0 min, 4 update(s).
- Title
- Some Loom users experiencing no audio when viewing recordings
- Vendor
- Atlassian Loom
- Date
- URL
- https://rewindex.com/company/atlassian-loom/incidents/t5rsnfks8vpt
Atlassian Loom profileRecent Atlassian Loom incidentsAll outages on November 20, 2025Atlassian Loom in November 2025MarkdownJSON