- Level
- confirmed
- Worst impact
- Degraded
- Components
- Webhooks
- Down Index
- 24of 100
What to do
Check whether you use Loops Webhooks. 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 7h 31m it lasted.
Anything that failed between 2026-02-10 11:05 UTC and 2026-02-10 18:36 UTC may need a replay.Subscribe to Loops's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=loops works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Loops 4
- investigating
We are currently investigating this issue.
provider
- identified
We are currently working through the backlog of webhook messages.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved.
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-ad8f0f502d
Is Loops still down?
No, this incident was resolved 2026-02-10 18:36 UTC. For Loops's live state, see https://down.guide/loops.
How long did it last?
7h 31m, from 2026-02-10 11:05 UTC to 2026-02-10 18:36 UTC, by the times Loops posted.
What was affected?
Loops named Webhooks.
What caused it?
Loops hasn't published a root cause. If it does, it shows here.
Where does this come from?
Loops's official status page, https://status.loops.so, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.