- Level
- confirmed
- Worst impact
- Degraded
- Components
- Webhooks
- Down Index
- 19of 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 46m it lasted.
Anything that failed between 2025-10-14 13:57 UTC and 2025-10-14 14:43 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 3
- investigating
We are investigating issues with delivery of outbound webhooks
provider
- resolved
This incident has been resolved.
provider
- postmortem
Between approximately 13:42 and 14:18 UTC attempted webhook deliveries failed while our webhooks database was unavailable due to an unplanned outage. Webhooks messages during that period were lost and will not be delivered. We’ve prioritized work to make webhooks more resilient to this sort of failure. Email message sending was not impacted during this event.
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-67584574e1
Is Loops still down?
No, this incident was resolved 2025-10-14 14:43 UTC. For Loops's live state, see https://down.guide/loops.
How long did it last?
46m, from 2025-10-14 13:57 UTC to 2025-10-14 14:43 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.