Skip to content
UpButler
ProductAgentsStatus pagesDocsPricing
Sign inStart free

Is Loops down?

Right now

No. Loops is operational.

No incidents reported.

Read from status.loops.so · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/loops/status.agent.json

MCP: upstream_status {"service":"loops"}

Product and transactional email for SaaS.

What Loops reports

Operational

Taken as is from Loops's own status page API. Incident titles and component names below are theirs.

Open status.loops.so

UpButler's independent probe

There is no keyless endpoint of Loops that says anything useful, so UpButler does not probe it. To check your own Loops account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Loops components

7 operational

Email Sending

  • LoopsOperational
  • CampaignsOperational
  • TransactionalOperational
  • APIOperational
  • AppOperational
  • SMTP RelayOperational
  • WebhooksOperational

Loops incidents, last 90 days

No finished incidents on record yet. UpButler keeps what Loops publishes for 90 days from the day it starts tracking a service.

Tell your outage from Loops's

Declare that your project depends on Loops. When one of your monitors fails while Loops has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start freeHow it works
upbutler.yaml
# upbutler.yaml
dependencies:
  - loops
Ask before you retry
curl -s https://upbutler.com/status/loops/status.agent.json
status.agent.json (live)
{
  "schema": "upbutler.upstream-status/v1",
  "service": "loops",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Loops down right now?
No. As of 2026-10-10 05:08 UTC, Loops is operational. This page reads the status again every 2 minutes.
Where does this status come from?
From Loops's own status page API at https://status.loops.so. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Loops's words.
How can my agent or app check Loops status?
Fetch https://upbutler.com/status/loops/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"loops"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Loops's?
Add "loops" to the dependencies of your UpButler workspace. When one of your monitors fails while Loops has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

More in email

UpButler is not affiliated with Loops. Status and incident text belong to Loops and are read from their public status source; the probe result is UpButler's own measurement.