- Level
- confirmed
- Worst impact
- Operational
- Components
- Loops, API, Campaigns, App, Transactional, SMTP Relay
What to do
Check whether you use Loops Loops, API, Campaigns, App and 2 more. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 1h 52m it lasted.
Anything that failed between 2025-01-29 16:05 UTC and 2025-01-29 17:57 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 an issue with an upstream provider, we're working to mitigate the impact.
provider
- monitoring
We're seeing signs of recovery and continuing to monitor while we wait for an "all-clear" from our upstream provider.
provider
- resolved
All good!
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-bd5a19cb76
Is Loops still down?
No, this incident was resolved 2025-01-29 17:57 UTC. For Loops's live state, see https://down.guide/providers/loops.
How long did it last?
1h 52m, from 2025-01-29 16:05 UTC to 2025-01-29 17:57 UTC, by the times Loops posted.
What was affected?
Loops named Loops, API, Campaigns, App and 2 more.
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.