Primary database outage

What to do

• Check whether you use Loops Loops, API, Campaigns, App and 2 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 39m it lasted.

  Anything that failed between 2024-09-16 14:16 UTC and 2024-09-16 14:54 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 6

1. investigatingSep 16, 2024, 2:16 PM UTC

   We are currently investigating this issue.

   provider

2. monitoringSep 16, 2024, 2:32 PM UTC

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

   provider

3. monitoringSep 16, 2024, 2:37 PM UTC

   We are continuing to monitor for any further issues.

   provider

4. monitoringSep 16, 2024, 2:54 PM UTC

   We are continuing to monitor for any further issues.

   provider

5. resolvedSep 16, 2024, 2:54 PM UTC

   This incident has been resolved.

   provider

6. postmortemSep 16, 2024, 2:55 PM UTC

   A misconfiguration by our database vendor prevented our database from restarting successfully. The misconfiguration was identified and remedied. Campaigns scheduled to send during the outage are now sent. Loop emails scheduled to send during the outage are now sent. Transactional emails or API calls made during the outage window need to be retried.

   provider

Corrections

None so far.

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