Loops

OPERATIONAL

Since Sep 2024 · 15 incidents · status.loops.so · checked just now

User reports

Visitors who said it's down for them, per hour over 24 hours. Not from the status page. Never counted in grades.

…

Compare Add to stack Status page

GradeA+Last 90 days

A+PRODA+SHIP

Overview

30d 90d 1y

Admitted uptime

Customer time not hit, by the provider's own account. Regional and partial incidents count in part.

100.000%Grade A+

Incidents

Everything posted on the status page except scheduled maintenance.

10 Sev 1

Fully down

Most customers down, by the provider's own account.

Median fix

Median time to resolve. Half of incidents were fixed faster.

1h 34m

Longest

Longest Sev 1–2 incident, start to resolved.

–

Since last

Time since the last counted incident was resolved.

43d 1h

By area

A+Production

0INCIDENTS

0mAFFECTED

Your users are hit: apps, APIs, databases, inference

Worst, 90dNothing.

Better. 0 in the last 6 months, 4 in the 6 before.

A+Shipping

0INCIDENTS

0mAFFECTED

You can't deploy, build or manage: CI, CLI, dashboard, auth, billing

Worst, 90dNothing.

Better. 0 in the last 6 months, 1 in the 6 before.

CleanSev 3–4Sev 1–2No data

Trend, last 12 months

Better. 1 in the last 6 months, 4 in the 6 before.

Severity mix

Sev 1 · Lights outProd site, API or database down, or data loss0

Sev 2 · BleedingProd degraded or partly down0

Sev 3 · Can't shipCan't deploy, build or manage it0

Sev 4 · PapercutDocs, status page, slow dashboard1

When it breaks

Start times, last 12 months, UTC.

Mon

Tue

Wed

Thu

Fri

Sat

Sun

0006121823

What breaks

App4 incidents

API3 incidents

Webhooks3 incidents

SMTP Relay2 incidents

Email Sending - Loops1 incident

Email Sending - Campaigns1 incident

Communication

Updates each

Status page updates per incident, on average.

5.6Last 12 months

Update gap

Median time between status page updates during an incident.

35mLast 12 months

Postmortems

Sev 1–2 incidents with a published write-up.

0 of 3Sev 1–2

Incident history

Sep 11, 20261h 34mSEV 4

Delay in email metric processingEmail metrics in the App dashboard were delayed or missing for about 90 minutes; no metrics were lost and email sending was not reported affected.AI-graded · App

Why this grade

RULES · SEV 4
Sev 4 because App had degraded performance
CLAUDE · SEV 4 · GLOBAL · HIGH CONFIDENCE · BACK AFTER 1H 34M
Email metrics in the App dashboard were delayed or missing for about 90 minutes; no metrics were lost and email sending was not reported affected.
Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record

3 updates

13:16 UTC · investigating
Email metrics may be slow to appear or not appear on refresh. We are currently investigating the issue.
14:40 UTC · identified
We're continuing to make progress processing a backlog of email metrics.
14:49 UTC · resolved
The metrics processing pipeline has caught up. No metrics were lost, this was only a delay in processing.

Source

Mar 2, 202646mSEV 2

increased rate of 500 level responsesAPI requests returned elevated 500 errors for about 46 minutes; the text does not say how many customers were hit.AI-graded · API +1

Why this grade

RULES · SEV 1
Sev 1 because API had a partial outage
CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
API requests returned elevated 500 errors for about 46 minutes; the text does not say how many customers were hit.
Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record

3 updates

22:58 UTC · investigating
We are currently investigating this issue.
23:09 UTC · identified
The issue has been identified and a fix is being implemented.
23:44 UTC · resolved
This incident has been resolved.

Source

Feb 10, 20267h 31mSEV 3

Webhook Delivery DelayedLoops webhook deliveries were delayed from about 11:05 to 18:36 UTC on February 10, 2026. The team worked through a backlog of webhook messages after implementing a fix, then resolved the incident. No data loss was reported.AI-graded · Webhooks

Why this grade

RULES · SEV 2
Sev 2 because Webhooks had degraded performance
CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE
Webhook deliveries to customer apps were delayed for several hours; no loss or outage was reported and the cause was not stated.
Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record

4 updates

14:51 UTC · investigating
We are currently investigating this issue.
16:39 UTC · identified
We are currently working through the backlog of webhook messages.
17:22 UTC · monitoring
A fix has been implemented and we are monitoring the results.
18:36 UTC · resolved
This incident has been resolved.

Source

Jan 24, 20261h 18mSEV 2

Elevated error rates for app.loops.soElevated error rates hit email sending, SMTP relay and webhooks for about 77 minutes; the scope across customers was not stated.AI-graded · API +6

Why this grade

RULES · SEV 2
Sev 2 because API had degraded performance
CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
Elevated error rates hit email sending, SMTP relay and webhooks for about 77 minutes; the scope across customers was not stated.
Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record

3 updates

07:49 UTC · investigating
We are currently investigating this issue.
08:58 UTC · monitoring
A fix has been implemented and we are monitoring the results.
09:07 UTC · resolved
This incident has been resolved.

Source

Nov 18, 20253h 23mSEV 2

Elevated error rates for app.loops.soLoops experienced elevated 500 errors at app.loops.so from about 12:15 to 15:37 UTC on 18 November, caused by an upstream Cloudflare issue. Affected components included the API, app, SMTP relay and webhooks. A fix was implemented around 14:45 UTC, and a handful of errors persisted until the incident was resolved.AI-graded · API +3

Why this grade

RULES · SEV 1
Sev 1 because API had a partial outage
CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
Cloudflare-related 500 errors hit Loops API, SMTP relay and webhooks for about three hours; app access was also degraded.
Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record

7 updates

12:13 UTC · investigating
We are currently investigating Cloudflare related 500's at app.loops.so.
12:15 UTC · identified
An upstream issue has been identified with Cloudflare. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7
12:24 UTC · identified
We are continuing to work on a fix for this issue.
12:55 UTC · identified
We are continuing to work on a fix for this issue.
14:45 UTC · monitoring
A fix has been implemented and we are monitoring the results.
15:01 UTC · monitoring
Despite an initial suggestion that the issue was resolved at Cloudflare. We're still seeing a handful of errors.
15:37 UTC · resolved
This incident has been resolved.

Source

Oct 20, 20252h 17mSEV 2

Transactional email, webhooks, SMTP interruptionsDuring an AWS us-east-1 outage, Loops accepted transactional emails but failed to send some, 07:02-09:18 UTC. Webhook delivery failed 09:30-10:31 UTC from EC2 capacity shortage, fixed by widening autoscaling instance types. One of three SMTP load balancer IPs timed out 19:33-21:35 UTC from a bad DNS entry. Failed sends were not retried.AI-graded · regional · Email Sending - Transactional

Why this grade

RULES · SEV 1
Sev 1 because Email Sending - Transactional had a major outage
CLAUDE · SEV 2 · REGIONAL · MEDIUM CONFIDENCE
Transactional email sends, webhook delivery and one SMTP IP failed during the AWS us-east-1 outage, for periods of up to about two hours.
Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record

5 updates

08:30 UTC · monitoring
An issue in AWS is causing transactional emails to fail.
09:55 UTC · monitoring
We are continuing to monitor for any further issues.
10:46 UTC · monitoring
We are continuing to monitor for any further issues.
10:47 UTC · resolved
This incident has been resolved.
17:22 UTC · 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.

Postmortem Source

Oct 14, 202546mSEV 1

Outbound WebhooksOutbound webhook deliveries to customer apps failed for about 36 minutes during a webhooks database outage, and those messages were lost. Counted as Sev 1 for data loss or exposure.AI-graded · Webhooks

Why this grade

RULES · SEV 2
Sev 2 because Webhooks had degraded performance
CLAUDE · SEV 1 · UNCLEAR · HIGH CONFIDENCE · DATA LOSS
Outbound webhook deliveries to customer apps failed for about 36 minutes during a webhooks database outage, and those messages were lost.
Claude Haiku 5.5 · prompt v8 · Oct 23, 2026 · Raw record

3 updates

13:57 UTC · investigating
We are investigating issues with delivery of outbound webhooks
14:43 UTC · resolved
This incident has been resolved.
14:44 UTC · 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.

Postmortem Source