Paddle Outage History

Started Oct 21, 2026, 08:04 PM UTC· resolved Oct 22, 2026, 12:09 AM UTC

1. identified Oct 21, 2026, 08:04 PM UTC

   We have identified the issue affecting metrics and reporting in the vendor dashboard, which began around 19:37 UTC, due to an outage with a third party provider. We will update the status once the issue has been resolved. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [email protected].

2. resolved Oct 22, 2026, 12:09 AM UTC

   The incident affecting metrics and reporting in the seller dashboard 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 [email protected]: mailto:[email protected].

Read the full incident report →

Started Sep 02, 2026, 08:31 PM UTC· resolved Sep 02, 2026, 09:04 PM UTC

1. investigating Sep 02, 2026, 08:31 PM UTC

   Our engineers are currently investigating an issue affecting report downloads in the Paddle Dashboard. Some users may encounter an error when attempting to download generated reports. We are working to identify the root cause and restore normal service as soon as possible. We’ll provide another update when more information is available. We appreciate your patience. Please reach out to our Customer Support team via [email protected] should you have any questions.

2. resolved Sep 02, 2026, 09:04 PM UTC

   The incident affecting report downloads in the Paddle Dashboard has been fully resolved. Our engineers deployed a fix, and the generated reports can now be downloaded as expected. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact our Customer Support team at [email protected] "[email protected]": mailto:[email protected].

Read the full incident report →

Started Aug 24, 2026, 08:35 AM UTC· resolved Aug 24, 2026, 09:22 AM UTC

1. identified Aug 24, 2026, 08: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 [email protected].

2. monitoring Aug 24, 2026, 09: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 [email protected].

3. resolved Aug 24, 2026, 09: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 [email protected].

Read the full incident report →

Started Jul 16, 2026, 08:00 AM UTC· resolved Jul 16, 2026, 08:24 AM UTC

1. identified Jul 16, 2026, 08:00 AM UTC

   We’ve identified an issue affecting access to the Paddle seller dashboard sign-in flow at vendors.paddle.com "vendors.paddle.com": http://vendors.paddle.com and sandbox-vendors.paddle.com "sandbox-vendors.paddle.com": http://sandbox-vendors.paddle.com, caused by a third-party incident. Users who are already signed in are not affected. The issue is only impacting new sign-in attempts. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [email protected] "[email protected]": mailto:[email protected].

2. resolved Jul 16, 2026, 08:24 AM UTC

   The incident affecting access to the Paddle seller dashboard sign-in has been fully resolved. All services are now operating normally. We are closely monitoring the platform to ensure continued stability. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact our Customer Support team at [email protected].

Read the full incident report →

Started Jun 25, 2026, 01:07 AM UTC· resolved Jun 25, 2026, 05:16 AM UTC

1. identified Jun 25, 2026, 01:07 AM UTC

   Our engineers are currently investigating an issue affecting checkout loading across Paddle Classic and Paddle Billing. This is causing some sellers to experience checkouts not loading as expected, and we are working to identify the root cause. We will update the status as soon as we have more information. We appreciate your patience. Please reach out to my team via [email protected] "[email protected]": mailto:[email protected] should you have any questions.

2. investigating Jun 25, 2026, 03:18 AM UTC

   We are continuing to investigate the issue. We appreciate your patience. Please reach out to our Customer Support team via [email protected] should you have any questions.

3. monitoring Jun 25, 2026, 03:35 AM UTC

   We have deployed a fix for the issue that was affecting Paddle Billing Checkouts. We are closely monitoring the platform to ensure continued stability. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [email protected].

4. resolved Jun 25, 2026, 05:16 AM UTC

   The incident affecting Checkouts 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 [email protected].

Read the full incident report →

Started Jun 18, 2026, 03:18 PM UTC· resolved Jun 18, 2026, 04:15 PM UTC

1. identified Jun 18, 2026, 03:18 PM UTC

   We have identified the issue affecting checkouts. We are actively working to resolve the root cause and restore normal service as soon as possible. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [email protected].

2. identified Jun 18, 2026, 03:41 PM UTC

   We have identified the root cause of the issue affecting checkouts, which is related to a third-party provider. Our team is currently implementing mitigations to resolve the issue and restore normal service as soon as possible. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [email protected] "[email protected]": mailto:[email protected].

3. monitoring Jun 18, 2026, 04:02 PM UTC

   We have implemented mitigations to address the issue affecting checkouts, and services are recovering. Our team is now actively monitoring the situation to ensure that normal service is fully restored and remains stable. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [email protected] "[email protected]": mailto:[email protected].

4. resolved Jun 18, 2026, 04:15 PM UTC

   The issue affecting checkouts has been resolved. The third-party provider has restored their services, and we have removed the temporary mitigations. All systems are now operating normally, and checkouts are processing as expected. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [email protected] "[email protected]": mailto:[email protected].

Read the full incident report →

Started Jun 01, 2026, 08:38 AM UTC· resolved Jun 01, 2026, 10:23 AM UTC

1. monitoring Jun 01, 2026, 08:38 AM UTC

   We identified an issue affecting card payments on Paddle Billing and Paddle Classic checkout between 09:07 and 09:21 GMT. Wallet payments and subscriptions do not appear to have been affected. The issue has now been resolved, and our team is monitoring the situation to ensure normal service continues. We apologize for any disruption this may have caused. If you have any questions or concerns, please reach out to us at [email protected] "[email protected]": mailto:[email protected].

2. resolved Jun 01, 2026, 08:59 AM UTC

   We identified an issue affecting card payments on Paddle Billing and Paddle Classic checkout between 09:07 and 09:21 GMT. Wallet payments and subscriptions do not appear to have been affected. The issue has now been resolved, and our team is monitoring the situation to ensure normal service continues. We apologize for any disruption this may have caused. If you have any questions or concerns, please reach out to us at [email protected] "[email protected]": mailto:[email protected].

3. identified Jun 01, 2026, 09:38 AM UTC

   We identified another issue affecting card payments on Paddle Billing and Paddle Classic. Wallet payments and subscriptions do not appear to have been affected. We apologize for any disruption this may have caused. If you have any questions or concerns, please reach out to us at [email protected] "[email protected]": mailto:[email protected].

4. resolved Jun 01, 2026, 10:23 AM UTC

   The issue has now been resolved, and our team is monitoring the situation to ensure normal service continues. We apologize for any disruption this may have caused. If you have any questions or concerns, please reach out to us at [email protected] "[email protected]": mailto:[email protected].

Read the full incident report →

Started Apr 28, 2026, 03:36 PM UTC· resolved Apr 30, 2026, 02:07 PM UTC

1. investigating Apr 28, 2026, 03:36 PM UTC

   We have identified an issue affecting new sellers’ access to the ProfitWell Metrics. 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 [email protected] "[email protected]": mailto:[email protected].

2. identified Apr 28, 2026, 04:45 PM UTC

   We have identified an issue affecting access to Retain settings and Metrics for some new Paddle Billing signups in the dashboard. A fix has been scheduled for deployment for new signups, and the access for sellers who signed up earlier is being gradually restored. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [email protected] "[email protected]": mailto:[email protected].

3. resolved Apr 30, 2026, 02:07 PM UTC

   The incident affecting Retain settings and Metrics in the dashboard 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 [email protected].

Read the full incident report →

Started Apr 21, 2026, 02:02 PM UTC· resolved Apr 21, 2026, 02:11 PM UTC

1. monitoring Apr 21, 2026, 02:02 PM UTC

   We have identified an issue affecting customers who are attempting to add a discount at checkout. They may encounter a timeout, which can prevent the discount from being applied, but it should not prevent the transaction from being completed. This began at approximately 13:15 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 [email protected] "[email protected]": mailto:[email protected].

2. resolved Apr 21, 2026, 02:11 PM UTC

   We are pleased to confirm that this issue has been resolved, and normal service has now been fully restored. Our team will continue to monitor the situation closely over the next 24 hours to ensure ongoing stability. We sincerely apologize for any disruption this may have caused. If you have any further questions or concerns, please don’t hesitate to reach out to my team at [email protected] "[email protected]": mailto:[email protected].

Read the full incident report →

Started Apr 21, 2026, 11:00 AM UTC· resolved Apr 21, 2026, 02:22 PM UTC

1. identified Apr 21, 2026, 11:00 AM UTC

   We have identified the issue affecting Email, Webhooks & Alerts that began around 11:40. 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 [email protected].

2. monitoring Apr 21, 2026, 11:43 AM UTC

   A fix has been deployed and the underlying issue affecting Email, Webhooks & Alerts has been internally resolved. The service became fully operational again, processing new webhooks and outbound emails at 12:07 BST. Furthermore, all delayed webhooks and outbound emails were successfully reprocessed by 12:12 BST. We are continuing to monitor the situation to ensure full stability before marking this incident as completely resolved. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [email protected] "[email protected]": mailto:[email protected].

3. resolved Apr 21, 2026, 02:22 PM UTC

   The underlying issue affecting Email, Webhooks & Alerts has been resolved. The service became fully operational again, processing new webhooks and outbound emails at 12:07 BST, and all delayed webhooks and outbound emails were successfully reprocessed by 12:12 BST. Our teams will continue to monitor the services closely to ensure ongoing stability. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [email protected] "[email protected]": mailto:[email protected].

Read the full incident report →

Started Mar 20, 2026, 06:59 PM UTC· resolved Mar 21, 2026, 04:05 PM UTC

1. identified Mar 20, 2026, 06:59 PM UTC

   We have identified an issue affecting our checkout service that began around 18:20 GMT. Our team has confirmed the service experienced approximately 11 minutes of errors, with normal service restored by 18:31 GMT. We apologize for any disruption this may have caused. If you have any questions or concerns, please reach out to us at [email protected] "[email protected]": mailto:[email protected].

2. resolved Mar 20, 2026, 07:27 PM UTC

   We are pleased to confirm that the issue affecting our checkout service has been resolved. Normal service has been fully restored. Our team will continue to monitor the situation closely over the next 24 hours to ensure stability. We apologize for any disruption this may have caused. If you have any further questions or concerns, please don't hesitate to reach out to us at [email protected] "[email protected]": mailto:[email protected].

3. resolved Mar 21, 2026, 04:04 PM UTC

   Following 24 hours of monitoring, we are happy to confirm that this incident is now closed. Our checkout service remains fully stable with no further issues detected. Thank you for your patience while we worked through this. If you have any questions, please don't hesitate to reach out to us at [email protected]: mailto:[email protected].

4. resolved Mar 21, 2026, 04:05 PM UTC

   Following 24 hours of monitoring, we are happy to confirm that this incident is now closed. Our checkout service remains fully stable with no further issues detected. Thank you for your patience while we worked through this. If you have any questions, please don't hesitate to reach out to us at [email protected] "[email protected]": mailto:[email protected].

Read the full incident report →

Started Feb 27, 2026, 03:23 PM UTC· resolved Feb 27, 2026, 04:25 PM UTC

1. investigating Feb 27, 2026, 03:23 PM UTC

   Our engineers are currently investigating an issue affecting Retain. This is causing some service disruption, and we are working to identify the root cause. We will update the status as soon as we have more information. We appreciate your patience. Please reach out to our Customer Support team via [email protected] should you have any questions.

2. resolved Feb 27, 2026, 03:32 PM UTC

   The incident affecting Retain has been fully resolved. All services are now operating normally. We will continue to monitor for the next 24 hours to ensure stability. During the incident between 2:56 PM UTC and 3:25 PM UTC, the following areas may have been affected: • Metrics dashboard • Payment retries • Dunning emails • Cancelling past-due subscriptions • Cancellation flows not rendering correctly (Customer Portal fell back to the default cancellation modal) • The Retain section in the Paddle Billing dashboard We apologize for any disruption this may have caused. If you have any questions or concerns, please contact our Customer Support team at [email protected] "[email protected]": mailto:[email protected].

3. resolved Feb 27, 2026, 04:25 PM UTC

   The incident affecting Retain has been resolved, and service has recovered. We will continue monitoring to ensure everything remains stable. If you have any questions, please contact our Customer Support team at [email protected] "[email protected]": mailto:[email protected].

Read the full incident report →

Started Feb 06, 2026, 12:40 PM UTC· resolved Feb 07, 2026, 12:27 PM UTC

1. investigating Feb 06, 2026, 12:40 PM UTC

   Our engineers are currently investigating an issue affecting AliPay payments. This is preventing buyers from completing payments using this payment method, and we are working to identify the root cause. We will update the status as soon as we have more information. We appreciate your patience. Please reach out to our Customer Support team via [email protected] "[email protected]": mailto:[email protected] should you have any questions.

2. investigating Feb 06, 2026, 01:57 PM UTC

   Our engineers are currently investigating an issue affecting AliPay payments. This is preventing buyers from completing payments using this payment method, and we are working to identify the root cause. We will update the status as soon as we have more information. While we're still working on this, buyers may experience difficulties completing their purchase at checkout. We appreciate your patience. Please reach out to our Customer Support team via [email protected] "[email protected]": mailto:[email protected] should you have any questions

3. resolved Feb 06, 2026, 02:32 PM UTC

   We have identified and addressed the issue affecting AliPay payments. We are no longer observing errors, and as a result, we have re-enabled the payment method for 100% of our traffic. We will continue to monitor the situation closely to ensure full stability. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [email protected] "[email protected]": mailto:[email protected].

4. resolved Feb 07, 2026, 12:27 PM UTC

   After a period of monitoring, we can confirm that the issue affecting AliPay payments has been fully resolved, and the payment method is successfully processing for all buyers. Between 12.40pm and 01.57pm GMT on 6 Feb, we experienced an issue that prevented buyers from completing payments using AliPay. During the incident, this payment method was unavailable at checkout or resulted in errors for attempted transactions. Normal service was restored once the issue was resolved. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [email protected] "[email protected]": mailto:[email protected].

Read the full incident report →

Started Dec 11, 2025, 02:00 AM UTC· resolved Dec 11, 2025, 09:16 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Dec 05, 2025, 08:59 AM UTC· resolved Dec 05, 2025, 09:45 AM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Nov 18, 2025, 12:17 PM UTC· resolved Nov 18, 2025, 02:51 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Nov 10, 2025, 05:39 PM UTC· resolved Nov 10, 2025, 07:04 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Oct 20, 2025, 07:36 AM UTC· resolved Oct 21, 2025, 05:23 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →

Started Oct 16, 2025, 03:53 PM UTC· resolved Oct 16, 2025, 05:47 PM UTC

No vendor updates were posted for this incident.

Read the full incident report →