- Level
- confirmed
- Worst impact
- Partial outage
- Components
- Transactional
- Regions
- us, us-east-1
- Down Index
- 37of 100
What to do
Check whether you use Loops Transactional in us, us-east-1. 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 2h 17m it lasted.
Anything that failed between 2025-10-20 08:30 UTC and 2025-10-20 10:47 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 5
- monitoring
An issue in AWS is causing transactional emails to fail.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- monitoring
We are continuing to monitor for any further issues.
provider
- resolved
This incident has been resolved.
provider
- postmortem
On October 20 2025, Loops was impacted by AWS’s outage in the US-EAST-1 region. We observed a variety of misbehaviors during that time, some more serious than others. Overall, the impact to Loops fell within the wider window provided by AWS \(06:49 UTC to 22:53 UTC\). During the outage, we experienced temporary but notable impact to, * Transactional email sending. * Webhook delivery. * Incoming request routing to our SMTP service. **Transactional email** Between 7:02 UTC and 9:18 UTC, transactional email sending was impacted. During this window the Loops API may have accepted transactional requests but failed to send them. Impacted messages were not resent later as we do not store the raw payloads. Timeline: * 7:02 UTC: We began experiencing elevated error rates related to transactional email sending, manifesting as increasing rates of HTTP 500 responses from AWS APIs. * 9:18 UTC: AWS API error rates subside. Transactional sending returns to normal. **Webhooks** Between 9:30 UTC and 10:31 UTC webhook delivery was impacted due to the inability to provision sufficient EC2 capacity. Timeline: * 9:30 UTC: Error rates between the Loops API and our backend webhooks service rise. * 10:01 UTC: The issue is identified as insufficient capacity for the webhooks service due to EC2 provisioning scarcity. * 10:31 UTC: Error rates subside as we change our autoscaling configurations to accept a wider range of EC2 instance types and sizes. **SMTP availability** Between approximately 19:33 UTC and 21:35 UTC an incorrect DNS entry was returned in the results for the network load balancer \(NLB\) used by our SMTP service. During this window, one of three IP addresses returned by DNS responses were unable to accept connections. Attempts to connect to the incorrect IP address manifested as timeouts. Timeline: * ~19:33 UTC: An IP address returned NLB DNS requests stops accepting connections. DNS requests that select the impacted IP address fail to connect and time out. * ~21:35 UTC: The DNS for the NLB corrects itself and begins returning correct responses.
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-3477c502d5
Is Loops still down?
No, this incident was resolved 2025-10-20 10:47 UTC. For Loops's live state, see https://down.guide/loops.
How long did it last?
2h 17m, from 2025-10-20 08:30 UTC to 2025-10-20 10:47 UTC, by the times Loops posted.
What was affected?
Loops named Transactional in us, us-east-1.
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.