Rewindex

CompaniesLoopsIncidents

Loops: Elevated error rates for app.loops.so

MinorStatus: resolvedStarted Resolved (3.4 h)7 updatesstspg.io (opens in new tab)
Part of an outage event

Cloudflare outage, Nov 18, 2025 · 77 vendors, 81 incidents

Loops’s incident blames Cloudflare as the cause. (hop 1, posted +45 min vs the first vendor naming Cloudflare)

“…implemented and we are monitoring the results. An upstream issue has been identified with Cloudflare. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7 Despite an initial suggestion that the iss…”

Swipe sideways to see the whole diagram.

Cloudflareown incident not archivedWithin an hour13 vendors, 13 blamed CloudflareStytch, Zed, NordLayer +101 to 4 hours later19 vendors, 19 blamed CloudflareGitLab, Gorgias, Cursor +16Later7 vendors, 7 blamed CloudflareRudderStack, Brex, Maven Central +4Loops (this incident)posted +45 min
Cloudflareown incident not archivedWithin an hour13 vendors, 13 blamedCloudflareStytch, Zed, NordLayer +101 to 4 hours later19 vendors, 19 blamedCloudflareGitLab, Gorgias, Cursor +16Later7 vendors, 7 blamed CloudflareRudderStack, Brex, MavenCentral +4Loops (this incident)posted +45 min
Loops is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Cloudflare<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>13 vendors, 13 blamed Cloudflare<br/>Stytch, Zed, NordLayer +10"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>19 vendors, 19 blamed Cloudflare<br/>GitLab, Gorgias, Cursor +16"]:::blames
  root --> h4
  later["Later<br/>7 vendors, 7 blamed Cloudflare<br/>RudderStack, Brex, Maven Central +4"]:::blames
  root --> later
  me["Loops (this incident)<br/>posted +45 min"]:::me
  h1 --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: APIAppSMTP RelayWebhooks

Timeline of updates

  1. investigating

    We are currently investigating Cloudflare related 500's at app.loops.so.

  2. identified

    An upstream issue has been identified with Cloudflare. https://www.cloudflarestatus.com/incidents/8gmgl950y3h7

  3. identified

    We are continuing to work on a fix for this issue.

  4. identified

    We are continuing to work on a fix for this issue.

  5. monitoring

    A fix has been implemented and we are monitoring the results.

  6. monitoring

    Despite an initial suggestion that the issue was resolved at Cloudflare. We're still seeing a handful of errors.

  7. resolved

    This incident has been resolved.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Loops profileRecent Loops incidentsMarkdownJSON