Is Loops Down?

No — Loops is up

Loops's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 438 ms

Right now

The verdict is the worse of these two. How we decide

Loops's status page

status.loops.so · read 3 minutes ago · checked every 3 minutes

Operational

Loops's components, as its status page reports them
Component	Status
Loops the service itself	Operational
Campaigns	Operational
Transactional	Operational
API	Operational
App	Operational
SMTP Relay	Operational
Webhooks	Operational
Status page	Operational

Open their status page

FlareWarden checks

loops.so from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 438 ms
Checked: 4 hours ago

By region

Amsterdam reachable, 297 ms
Chicago reachable, 464 ms
San Jose reachable, 1138 ms
Singapore reachable, 411 ms
Stockholm reachable, 451 ms
Sydney reachable, 70 ms
Tokyo reachable, 262 ms
Toronto reachable, 413 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Amsterdam	211 ms	3 ms	15 ms	275 ms
Chicago	254 ms	2 ms	8 ms	436 ms
San Jose	1001 ms	3 ms	10 ms	1109 ms
Singapore	334 ms	2 ms	9 ms	396 ms
Stockholm	224 ms	1 ms	10 ms	417 ms
Sydney	18 ms	1 ms	7 ms	54 ms
Tokyo	193 ms	1 ms	8 ms	248 ms
Toronto	258 ms	2 ms	15 ms	393 ms

We check that loops.so loads, not every feature behind it. Test it yourself

History

Incidents Loops reported

Since Oct 22, 15 days · from status.loops.so

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Loops website availability

Measured by FlareWarden · loops.so

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 408ms

Last 30 days

57-day clean streak

Oct 7 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of loops.so from multiple regions every 6 hours. Loops's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 57 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

What Loops does

Loops is an email platform aimed at software companies, covering both the automated messages a product sends to one person and the campaigns a team sends to a list. Applications connect through an API or an SMTP relay, and Loops reports delivery events back by webhook, so it sits on the path of password resets and receipts as well as newsletters.

What an outage looks like

Password resets, sign-in links and receipts stop arriving, which surfaces as users unable to get into your product rather than as an email problem. Campaigns may fail to send or stall part way through a list. Applications calling the API receive errors or timeouts, and delivery webhooks stop arriving, so your own records of who received what quietly stop updating.

What to do about it

Read status.loops.so, which reports Email Sending, Loops, Campaigns, Transactional, API, App, SMTP Relay and Webhooks as separate components. Match the symptom to the row. If only Campaigns is affected, transactional mail such as password resets continues, which is the half that blocks users. Do not resend a campaign that reported a partial send until you can confirm who already received it.

Is it down for everyone, or just you?

If this page says Loops is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Loops outage FAQ

Users cannot log in because reset emails are not arriving. Is that a Loops outage?

It can be, and it is the failure worth spotting quickly because it looks like an authentication bug rather than an email one. Loops reports Transactional as a component separate from Campaigns, so password resets and sign-in links can fail while marketing sends normally. Check the Transactional and Email Sending rows on status.loops.so before you start investigating your own login flow.

Will emails sent during a Loops outage eventually arrive?

Some will and some will not, depending on where the failure sat. A message accepted by Loops before a delivery problem is generally retried onward, while a send attempt that never reached the API was never queued at all. Loops does not publish retry behaviour for every component, so check your own send logs for calls that returned an error and treat those specific messages as unsent.

My send looks successful but nothing was delivered. What happened?

That pattern usually means the interface accepted the instruction while the layer that actually sends did not complete it. Loops lists Email Sending as a component separate from App and API for this reason. Resending immediately is what creates duplicates, so confirm the true state on the status page and in your delivery records before sending again, particularly for a campaign that may have partially gone out.

My delivery webhooks stopped. Is my data now wrong?

Probably incomplete rather than wrong. Webhooks is its own component, so delivery, open and click events can stop reaching your application while the mail itself sends normally. Your own database then shows fewer delivered messages than were actually delivered. Treat reporting from the incident window as understated, and check with Loops before you reconcile records or re-trigger anything based on missing events.

Is it Loops or my SMTP configuration?

Compare scope and the path. Loops reports SMTP Relay separately from API, so a failure on only one of those points at the integration path rather than at sending as a whole. A wrong credential or a blocked port affects one application and returns a specific authentication or connection error. Check which component is affected before changing SMTP settings during an incident.

How we measure this

We request Loops's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. Our checks only change their verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Loops publishes an official status feed we read it too, and the verdict is the worse of what it reports and what our checks see: a major outage of Loops itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Loops goes down

We check Loops every 6 hours, and again when you open this page if that was more than 30 minutes ago. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required