# Loops: Elevated error rates for app.loops.so

- Impact (vendor’s label): minor
- Status: resolved
- Started: 2025-11-18 12:15 UTC · Resolved: 2025-11-18 15:37 UTC · Duration: 3.4 h
- Updates: 7 · Affected components: API, App, SMTP Relay, Webhooks
- [Vendor status page: https://stspg.io/cmtb2tc2cl0g](https://stspg.io/cmtb2tc2cl0g)
- [Company: Loops](https://rewindex.com/company/loops.md)

## Part of an outage event

- [Cloudflare outage, Nov 18, 2025: 77 vendors, 81 incidents](https://rewindex.com/events/2025-11-18-cloudflare)
- This incident blames Cloudflare as the cause. (hop 1, posted +45 min vs the first vendor naming Cloudflare)
- Evidence: “…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…”

```mermaid
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
```

_Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._

## Timeline of updates

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


---
Canonical: https://rewindex.com/company/loops/incidents/0h95bpxwbn7v · Markdown: https://rewindex.com/company/loops/incidents/0h95bpxwbn7v.md · JSON: https://rewindex.com/api/v1/companies/loops/incidents/0h95bpxwbn7v · Generated 2026-10-19T23:15:29.981Z