Paddle Outage History

Paddle is up right now

Paddle had 16 outages in the last 2 years totaling 105h 55m of downtime — averaging 0.7 incidents per month.

There were 16 Paddle outages since September 29, 2025 totaling 105h 55m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://paddlestatus.com

Minor June 1, 2026

Card payment issues on Paddle Billing and Paddle Classic checkout

Detected by Pingoru
Jun 01, 2026, 10:23 AM UTC
Resolved
Jun 01, 2026, 10:23 AM UTC
Duration
Affected: Production - ClassicProduction - Billing
Timeline · 4 updates
  1. monitoring Jun 01, 2026, 08:38 AM UTC

    Status: Monitoring 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]. Affected components Production - Classic (Degraded performance) Production - Billing (Degraded performance)

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

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

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

    Status: Identified 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]. Affected components Production - Classic (Degraded performance) Production - Billing (Degraded performance)

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

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

Read the full incident report →

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 - BillingProduction - Billing
Timeline · 3 updates
  1. 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)

  2. 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)

  3. 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 - BillingProduction - BillingSandbox - Billing
Timeline · 3 updates
  1. 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)

  2. 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)

  3. 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 - BillingProduction - ClassicSandbox - ClassicProduction - BillingSandbox - BillingSandbox - Classic
Timeline · 2 updates
  1. 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)

  2. 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 - BillingProduction - ClassicProduction - Billing
Timeline · 3 updates
  1. 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)

  2. 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)

  3. 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 - BillingProduction - ClassicSandbox - ClassicProduction - BillingSandbox - BillingSandbox - Classic
Timeline · 4 updates
  1. 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)

  2. 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)

  3. 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)

  4. 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
  1. 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)

  2. 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)

  3. 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 →