Retain

What to do

• Check whether you use Paddle in us. 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 47m it lasted.

  Anything that failed between 2026-08-24 08:35 UTC and 2026-08-24 09:22 UTC may need a replay.

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

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

Updates from Paddle 3

1. identifiedAug 24, 2026, 8:35 AM UTC

   We have identified the issue affecting Retain that began around 7:56 UTC. We are actively working to resolve the root cause and restore normal service as soon as possible. We will update the status once a fix has been deployed. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at sellers@paddle.com.

   provider

2. monitoringAug 24, 2026, 9:11 AM UTC

   We have deployed a fix for the issue that was affecting Retain. We are closely monitoring the platform to ensure continued stability. We apologize for any disruption this may have caused. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at sellers@paddle.com.

   provider

3. resolvedAug 24, 2026, 9:22 AM UTC

   The incident affecting Retain has been fully resolved. All services are now operating normally. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact our Customer Support team at sellers@paddle.com.

   provider

Corrections

None so far.

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