- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Recording, Viewing, Authentication, Loom AI
- Down Index
- 45of 100
What to do
Check whether you use Loom Recording, Viewing, Authentication, Loom AI. 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 24m it lasted.
Anything that failed between 2025-08-15 19:35 UTC and 2025-08-15 19:58 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 3
- identified
We are investigating reports of issues for Loom customers. Including names showing as IDs. We will provide more details once we identify the cause.
provider
- monitoring
We have identified the cause of the issues and we are monitoring recovery.
provider
- resolved
Between 18:45 and 19:35 UTC we experienced degraded functionality for Loom. 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-03178fa3da
Is Loom still down?
No, this incident was resolved 2025-08-15 19:58 UTC. For Loom's live state, see https://down.guide/loom.
How long did it last?
24m, from 2025-08-15 19:35 UTC to 2025-08-15 19:58 UTC, by the times Loom posted.
What was affected?
Loom named Recording, Viewing, Authentication, Loom AI.
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.