Investigating issues with Recurly Subscription Management

What to do

• Check whether your product depends on Recurly. 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 5h 39m it lasted.

  Anything that failed between 2026-08-18 13:49 UTC and 2026-08-18 19:28 UTC may need a replay.

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

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

Updates from Recurly 7

1. investigatingAug 18, 2026, 1:49 PM UTC

   We are investigating elevated 500 errors with Recurly Subscription Management.

   provider

2. identifiedAug 18, 2026, 2:20 PM UTC

   Our engineers have identified the issue and are actively remediating it.

   provider

3. investigatingAug 18, 2026, 2:35 PM UTC

   The team is investigating further into the 500s

   provider

4. investigatingAug 18, 2026, 2:52 PM UTC

   We're expanding the impacted components based on investigation

   provider

5. identifiedAug 18, 2026, 3:30 PM UTC

   The team has identified the issue and is continuing remediating it

   provider

6. monitoringAug 18, 2026, 4:56 PM UTC

   Issues impacting availability have been resolved. Some users may still experience delays in reporting and analytics.

   provider

7. resolvedAug 18, 2026, 7:28 PM UTC

   All services are operational and caught up.

   provider

Corrections

None so far.

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