- Level
- confirmed
- Worst impact
- Degraded
- Components
- Recording, Viewing, Authentication, Loom AI
- Down Index
- 37of 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 50m it lasted.
Anything that failed between 2026-04-29 07:00 UTC and 2026-04-29 07:50 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
- investigating
We are investigating degraded performance issues affecting Loom's core functionalities - authentication, recording, viewing and editing looms. We will provide more details within the next hour.
provider
- resolved
The 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.
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-e147464b61
Is Loom still down?
No, this incident was resolved 2026-04-29 07:50 UTC. For Loom's live state, see https://down.guide/loom.
How long did it last?
50m, from 2026-04-29 07:00 UTC to 2026-04-29 07:50 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.