Some customers are experiencing issues with our buyer emails

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 0m it lasted.

  Anything that failed between 2025-09-29 13:15 UTC and 2025-09-08 15:34 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. identifiedSep 7, 2025, 10:23 AM UTC

   Our engineers are currently investigating an issue with our Notification Service for Paddle Classic. Due to an issue with a downstream provider, emails sent from 3pm UTC to 5pm UTC on September 6th were affected, with approximately 3000 events being delayed. We are currently reprocessing these emails.

   provider

2. monitoringSep 7, 2025, 10:25 AM UTC

   The issue with our Notification Service for Paddle Classic has been identified and fixed. The service is now operating normally, and all delayed events have been processed. We will continue to monitor for stability.

   provider

3. resolvedSep 8, 2025, 3:34 PM UTC

   After a period of monitoring, the issue with the Notification Service for Paddle Classic has been fully resolved. The service continues to work as expected, so we are closing this incident. We appreciate your patience and apologize for any disruption this may have caused. If you have any questions or concerns, please contact us 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.