Paddle Outage History

There were 7 Paddle outages since February 6, 2026. Each is summarised below — incident details, duration, and resolution information.

Source: https://paddlestatus.com

Minor April 30, 2026

New Sellers might be unable to access Retain settings and the ProfitWell Metrics dashboard

Detected by Pingoru: Apr 30, 2026, 02:07 PM UTC
Resolved: Apr 30, 2026, 02:07 PM UTC
Duration: —

Affected: Production - ClassicProduction - Billing

Timeline · 3 updates

investigating Apr 28, 2026, 03:36 PM UTC

Status: Investigating 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]. Affected components Production - Billing (Partial outage) Production - Billing (Operational) Production - Classic (Operational)
identified Apr 28, 2026, 04:45 PM UTC

Status: Identified 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]. Affected components Production - Billing (Partial outage) Production - Billing (Operational) Production - Classic (Operational)
resolved Apr 30, 2026, 02:07 PM UTC

Status: Resolved 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]. Affected components Production - Billing (Operational) Production - Billing (Operational) Production - Classic (Operational)

Read the full incident report →

Minor April 21, 2026

Webhook & Email Delivery

Detected by Pingoru: Apr 21, 2026, 02:22 PM UTC
Resolved: Apr 21, 2026, 02:22 PM UTC
Duration: —

Affected: Production - BillingSandbox - Billing

Timeline · 3 updates

identified Apr 21, 2026, 11:00 AM UTC

Status: Identified 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]. Affected components Production - Billing (Degraded performance) Production - Billing (Degraded performance) Sandbox - Billing (Degraded performance) Sandbox - Billing (Degraded performance)
monitoring Apr 21, 2026, 11:43 AM UTC

Status: Monitoring 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]. Affected components Sandbox - Billing (Operational) Sandbox - Billing (Operational) Production - Billing (Operational) Production - Billing (Operational)
resolved Apr 21, 2026, 02:22 PM UTC

Status: Resolved 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]. Affected components Production - Billing (Operational) Production - Billing (Operational) Sandbox - Billing (Operational) Sandbox - Billing (Operational)

Read the full incident report →

Minor April 21, 2026

Discount service degradation causing discount application failures

Detected by Pingoru: Apr 21, 2026, 02:11 PM UTC
Resolved: Apr 21, 2026, 02:11 PM UTC
Duration: —

Affected: Production - ClassicProduction - ClassicProduction - BillingSandbox - BillingSandbox - Classic

Timeline · 2 updates

monitoring Apr 21, 2026, 02:02 PM UTC

Status: Monitoring 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]. Affected components Production - Classic (Degraded performance) Production - Billing (Degraded performance) Sandbox - Billing (Degraded performance) Sandbox - Classic (Degraded performance)
resolved Apr 21, 2026, 02:11 PM UTC

Status: Resolved 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]. Affected components Production - Classic (Operational) Production - Billing (Operational) Sandbox - Billing (Operational) Sandbox - Classic (Operational)

Read the full incident report →

Minor March 30, 2026

Intermittent Checkout Loading Issues

Detected by Pingoru: Mar 30, 2026, 01:38 PM UTC
Resolved: Mar 30, 2026, 01:38 PM UTC
Duration: —

Affected: Production - ClassicProduction - ClassicProduction - Billing

Timeline · 3 updates

investigating Mar 30, 2026, 09:23 AM UTC

Status: Investigating 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. Affected components Production - Classic (Degraded performance) Production - Billing (Degraded performance)
monitoring Mar 30, 2026, 09:48 AM UTC

Status: Monitoring We are pleased to confirm that the issue affecting checkout loading across Paddle Classic and Paddle Billing has been resolved, and normal service has now been fully restored. A small number of sellers were impacted during this time. 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]. Affected components Production - Billing (Degraded performance) Production - Classic (Degraded performance)
resolved Mar 30, 2026, 01:38 PM UTC

Status: Resolved We are pleased to confirm that the issue affecting checkout loading across Paddle Classic and Paddle Billing has been resolved, and normal service has now been fully restored. A small number of sellers were impacted during this time. 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]. Affected components Production - Classic (Operational) Production - Billing (Operational)

Read the full incident report →

Minor March 21, 2026

Checkout Service Incident

Detected by Pingoru: Mar 21, 2026, 04:05 PM UTC
Resolved: Mar 21, 2026, 04:05 PM UTC
Duration: —

Affected: Production - ClassicProduction - ClassicProduction - BillingSandbox - BillingSandbox - Classic

Timeline · 4 updates

identified Mar 20, 2026, 06:59 PM UTC

Status: Identified 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]. Affected components Production - Classic (Degraded performance) Production - Billing (Degraded performance) Sandbox - Billing (Degraded performance) Sandbox - Classic (Degraded performance)
resolved Mar 20, 2026, 07:27 PM UTC

Status: Resolved 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]. Affected components Production - Classic (Operational) Production - Billing (Operational) Sandbox - Billing (Operational) Sandbox - Classic (Operational)
resolved Mar 21, 2026, 04:04 PM UTC

Status: Resolved 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]. Affected components Production - Billing (Operational) Sandbox - Billing (Operational) Sandbox - Classic (Operational) Production - Classic (Operational)
resolved Mar 21, 2026, 04:05 PM UTC

Status: Resolved 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]. Affected components Production - Classic (Operational) Production - Billing (Operational) Sandbox - Billing (Operational) Sandbox - Classic (Operational)

Read the full incident report →

Minor February 27, 2026

Intermittent issues with Retain

Detected by Pingoru: Feb 27, 2026, 04:25 PM UTC
Resolved: Feb 27, 2026, 04:25 PM UTC
Duration: —

Affected: Production - ClassicProduction - ClassicProduction - Billing

Timeline · 3 updates

investigating Feb 27, 2026, 03:23 PM UTC

Status: Investigating 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. Affected components Production - Billing (Degraded performance) Production - Classic (Degraded performance)
resolved Feb 27, 2026, 03:32 PM UTC

Status: Resolved 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]. Affected components Production - Billing (Operational) Production - Classic (Operational)
resolved Feb 27, 2026, 04:25 PM UTC

Status: Resolved 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]. Affected components Production - Billing (Operational) Production - Classic (Operational)

Read the full incident report →

Minor February 7, 2026

Checkout Payment Failures for AliPay

Detected by Pingoru: Feb 07, 2026, 12:27 PM UTC
Resolved: Feb 07, 2026, 12:27 PM UTC
Duration: —

Affected: Production - ClassicProduction - ClassicProduction - Billing

Timeline · 4 updates

investigating Feb 06, 2026, 12:40 PM UTC

Status: Investigating 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. Affected components Production - Classic (Partial outage) Production - Billing (Partial outage)
investigating Feb 06, 2026, 01:57 PM UTC

Status: Investigating 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 Affected components Production - Classic (Partial outage) Production - Billing (Partial outage)
resolved Feb 06, 2026, 02:32 PM UTC

Status: Resolved 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]. Affected components Production - Billing (Operational) Production - Classic (Operational)
resolved Feb 07, 2026, 12:27 PM UTC

Status: Resolved 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]. Affected components Production - Classic (Operational) Production - Billing (Operational)

Read the full incident report →

Looking to track Paddle downtime and outages?

Pingoru polls Paddle's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.

Real-time alerts when Paddle reports an incident
Email, Slack, Discord, Microsoft Teams, and webhook notifications
Track Paddle alongside 5,000+ providers in one dashboard
Component-level filtering
Notification groups + maintenance calendar

Start monitoring Paddle for free

5 free monitors · No credit card required