- Level
- confirmed
- Worst impact
- Major outage
- Regions
- us
- Down Index
- 44of 100
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 1h 25m it lasted.
Anything that failed between 2025-11-10 17:39 UTC and 2025-11-10 19:04 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 10
- investigating
We are currently investigating an issue affecting our Retain platform. This is causing problems with the functionality of Retain widgets, including Payment recovery, Cancellation, Reactivation and Term optimization. Our engineering team is actively working to identify the root cause and implement a solution. We will provide further updates as soon as they are available. We apologize for any disruption this may be causing. If you have any questions or concerns, please contact us at [sellers@paddle.com](mailto:sellers@paddle.com "sellers@paddle.com")
provider
- investigating
We are currently investigating an issue causing increased latency and affecting availability with our Retain service. Our team is working to adjust our infrastructure to stabilize performance. While service availability is improving, requests may still take longer than usual to process. We apologize for any disruption this may be causing. If you have any questions or concerns, please contact us at [sellers@paddle.com](mailto:sellers@paddle.com "sellers@paddle.com")
provider
- investigating
We are currently investigating an issue affecting our Retain platform. This is causing problems with the functionality of Retain widgets, including Payment recovery, Cancellation, Reactivation and Term optimization. Our engineering team is actively working to identify the root cause and implement a solution. We will provide further updates as soon as they are available. We apologize for any disruption this may be causing. If you have any questions or concerns, please contact us at [sellers@paddle.com](mailto:sellers@paddle.com "sellers@paddle.com")
provider
- monitoring
A fix has been implemented and we are observing a recovery. Requests are now processing successfully, and our team will continue to monitor the service closely to ensure performance remains stable. We will post another update once we can confirm the issue is fully resolved. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at sellers@paddle.com.
provider
- resolved
We have confirmed that the service is now stable and operating normally. The issue is now resolved. We sincerely apologize for the disruption and appreciate your patience. If you have any further questions, please don't hesitate to contact us at [sellers@paddle.com](mailto:sellers@paddle.com "sellers@paddle.com").
provider
- investigating
We are currently investigating an issue causing increased latency with our Retain service. Our team is working to adjust our infrastructure to stabilize performance. While service availability is improving, requests may still take longer than usual to process. We apologize for any disruption this may be causing. If you have any questions or concerns, please contact us at [sellers@paddle.com](mailto:sellers@paddle.com "sellers@paddle.com")
provider
- monitoring
A fix has been implemented, and we are observing a recovery. Requests are now being processed successfully, and our team will continue to closely monitor the service to ensure stable performance. We will post another update once we can confirm the issue is fully resolved. We apologize for the disruption this has caused. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [sellers@paddle.com](mailto:sellers@paddle.com "sellers@paddle.com").
provider
- resolved
We have confirmed that the service is now stable and operating normally. The issue is now resolved. We sincerely apologize for the disruption and appreciate your patience. If you have any further questions, please don't hesitate to contact us at [sellers@paddle.com](mailto:sellers@paddle.com "sellers@paddle.com").
provider
- monitoring
We adjusted our platform resources to handle an increased load on our database caused by manually triggered jobs that were affecting other parts of our application. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at sellers@paddle.com.
provider
- resolved
We have confirmed that the service is now stable and operating normally. The issue is now resolved. We sincerely apologize for the disruption and appreciate your patience. If you have any further questions, please don't hesitate to contact us at [sellers@paddle.com](mailto:sellers@paddle.com "sellers@paddle.com").
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-f8083bafbb
Is Paddle still down?
No, this incident was resolved 2025-11-10 19:04 UTC. For Paddle's live state, see https://down.guide/paddle.
How long did it last?
1h 25m, from 2025-11-10 17:39 UTC to 2025-11-10 19:04 UTC, by the times Paddle posted.
What was affected?
Paddle named in us.
What caused it?
Paddle hasn't published a root cause. If it does, it shows here.
Where does this come from?
Paddle's official status page, https://paddlestatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.