Increased 500 errors

What to do

• Check whether you use Loops Loops, API, Campaigns, App and 3 more. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 30m it lasted.

  Anything that failed between 2025-09-03 08:14 UTC and 2025-09-03 08:44 UTC may need a replay.

• Subscribe to Loops's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=loops works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Loops 5

1. investigatingSep 3, 2025, 8:14 AM UTC

   We are currently investigating this issue.

   provider

2. identifiedSep 3, 2025, 8:33 AM UTC

   The issue has been identified and a fix is being implemented.

   provider

3. monitoringSep 3, 2025, 8:38 AM UTC

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

   provider

4. resolvedSep 3, 2025, 8:44 AM UTC

   This incident has been resolved.

   provider

5. postmortemSep 4, 2025, 2:00 PM UTC

   Between Sept 3 03:40 UTC and Sept 3 08:30 UTC Loops experienced a period of elevated error rates where API requests intermittently returned 500’s due to high CPU use on our primary database. We resolved the issue and additionally made monitoring and process changes to speed responses in the future.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.