- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Recording
- Down Index
- 33of 100
What to do
Check whether you use Loom Recording. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 31m it lasted.
Anything that failed between 2025-09-12 20:43 UTC and 2025-09-12 22:14 UTC may need a replay.Subscribe to Loom's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=loom works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Loom 2
- monitoring
From 5:03 AM ET to 4:15 PM ET, some customers were unable to record Zoom meetings using Loom Meeting Recordings. Attempts made during this time may appear in your library but will not be playable, as no recording was captured. Unfortunately, these recordings cannot be recovered. We have released a fix and we are monitoring recovery.
provider
- resolved
The issue has been resolved and the service is operating normally.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-01fa977ca9
Is Loom still down?
No, this incident was resolved 2025-09-12 22:14 UTC. For Loom's live state, see https://down.guide/loom.
How long did it last?
1h 31m, from 2025-09-12 20:43 UTC to 2025-09-12 22:14 UTC, by the times Loom posted.
What was affected?
Loom named Recording.
What caused it?
Loom hasn't published a root cause. If it does, it shows here.
Where does this come from?
Loom's official status page, https://loom.status.atlassian.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.