- Detected by Pingoru
- Sep 02, 2026, 09:04 PM UTC
- Resolved
- Sep 02, 2026, 09:04 PM UTC
- Duration
- —
Affected: Production - BillingProduction - BillingProduction - Billing
Timeline · 2 updates
-
investigating Sep 02, 2026, 08:31 PM UTC
Status: Investigating 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. Affected components Production - Billing (Degraded performance)
-
resolved Sep 02, 2026, 09:04 PM UTC
Status: Resolved 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]. Affected components Production - Billing (Operational)
Read the full incident report →
- Detected by Pingoru
- Aug 24, 2026, 09:22 AM UTC
- Resolved
- Aug 24, 2026, 09:22 AM UTC
- Duration
- —
Affected: Production - ClassicProduction - ClassicProduction - BillingProduction - BillingProduction - ClassicProduction - ClassicProduction - Billing
Timeline · 3 updates
-
identified Aug 24, 2026, 08:35 AM UTC
Status: Identified 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]. Affected components Production - Billing (Partial outage) Production - Classic (Partial outage)
-
monitoring Aug 24, 2026, 09:11 AM UTC
Status: Monitoring 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]. Affected components Production - Billing (Operational) Production - Classic (Operational)
-
resolved Aug 24, 2026, 09:22 AM UTC
Status: Resolved 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]. Affected components Production - Billing (Operational) Production - Classic (Operational)
Read the full incident report →
- Detected by Pingoru
- Jul 16, 2026, 08:24 AM UTC
- Resolved
- Jul 16, 2026, 08:24 AM UTC
- Duration
- —
Affected: Production - ClassicProduction - ClassicSandbox - ClassicProduction - ClassicProduction - BillingProduction - BillingSandbox - BillingProduction - ClassicProduction - ClassicSandbox - ClassicSandbox - ClassicProduction - BillingSandbox - Billing
Timeline · 2 updates
-
identified Jul 16, 2026, 08:00 AM UTC
Status: Identified 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]. Affected components Sandbox - Classic (Degraded performance) Production - Classic (Degraded performance) Production - Billing (Degraded performance) Sandbox - Billing (Degraded performance)
-
resolved Jul 16, 2026, 08:24 AM UTC
Status: Resolved 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]. Affected components Production - Billing (Operational) Sandbox - Billing (Operational) Sandbox - Classic (Operational) Production - Classic (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 25, 2026, 05:16 AM UTC
- Resolved
- Jun 25, 2026, 05:16 AM UTC
- Duration
- —
Affected: Production - ClassicProduction - BillingProduction - ClassicProduction - ClassicProduction - Billing
Timeline · 4 updates
-
identified Jun 25, 2026, 01:07 AM UTC
Status: Identified 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)
-
investigating Jun 25, 2026, 03:18 AM UTC
Status: Investigating 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. Affected components Production - Billing (Degraded performance) Production - Classic (Degraded performance)
-
monitoring Jun 25, 2026, 03:35 AM UTC
Status: Monitoring 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]. Affected components Production - Classic (Operational) Production - Billing (Operational)
-
resolved Jun 25, 2026, 05:16 AM UTC
Status: Resolved 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]. Affected components Production - Classic (Operational) Production - Billing (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 18, 2026, 04:15 PM UTC
- Resolved
- Jun 18, 2026, 04:15 PM UTC
- Duration
- —
Affected: Production - ClassicProduction - ClassicSandbox - ClassicSandbox - ClassicProduction - BillingSandbox - Billing
Timeline · 4 updates
-
identified Jun 18, 2026, 03:18 PM UTC
Status: Identified 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]. Affected components Production - Billing (Degraded performance) Sandbox - Billing (Degraded performance) Sandbox - Classic (Degraded performance) Production - Classic (Degraded performance)
-
identified Jun 18, 2026, 03:41 PM UTC
Status: Identified 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]. Affected components Production - Classic (Degraded performance) Production - Billing (Degraded performance) Sandbox - Billing (Degraded performance) Sandbox - Classic (Degraded performance)
-
monitoring Jun 18, 2026, 04:02 PM UTC
Status: Monitoring 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]. Affected components Production - Classic (Operational) Production - Billing (Operational) Sandbox - Billing (Operational) Sandbox - Classic (Operational)
-
resolved Jun 18, 2026, 04:15 PM UTC
Status: Resolved 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]. Affected components Production - Classic (Operational) Production - Billing (Operational) Sandbox - Billing (Operational) Sandbox - Classic (Operational)
Read the full incident report →
- Detected by Pingoru
- Jun 01, 2026, 10:23 AM UTC
- Resolved
- Jun 01, 2026, 10:23 AM UTC
- Duration
- —
Affected: Production - ClassicProduction - ClassicProduction - BillingProduction - ClassicProduction - Billing
Timeline · 4 updates
-
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)
-
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)
-
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)
-
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 →
- Detected by Pingoru
- Apr 30, 2026, 02:07 PM UTC
- Resolved
- Apr 30, 2026, 02:07 PM UTC
- Duration
- —
Affected: Production - ClassicProduction - ClassicProduction - BillingProduction - 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 →
- 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
-
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 →
- Detected by Pingoru
- Apr 21, 2026, 02:11 PM UTC
- Resolved
- Apr 21, 2026, 02:11 PM UTC
- Duration
- —
Affected: Production - ClassicProduction - ClassicProduction - BillingProduction - ClassicSandbox - 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 →
- Detected by Pingoru
- Mar 21, 2026, 04:05 PM UTC
- Resolved
- Mar 21, 2026, 04:05 PM UTC
- Duration
- —
Affected: Production - ClassicProduction - ClassicProduction - BillingProduction - ClassicSandbox - 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 →
- 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 →
- 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
Read the full incident report →
- Detected by Pingoru
- Dec 11, 2025, 02:00 AM UTC
- Resolved
- Dec 11, 2025, 09:16 AM UTC
- Duration
- 7h 15m
Read the full incident report →
- Detected by Pingoru
- Dec 05, 2025, 08:59 AM UTC
- Resolved
- Dec 05, 2025, 09:45 AM UTC
- Duration
- 45m
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 12:17 PM UTC
- Resolved
- Nov 18, 2025, 02:51 PM UTC
- Duration
- 2h 33m
Read the full incident report →
Critical November 10, 2025 - Detected by Pingoru
- Nov 10, 2025, 05:39 PM UTC
- Resolved
- Nov 10, 2025, 07:04 PM UTC
- Duration
- 1h 24m
Read the full incident report →
Critical October 20, 2025 - Detected by Pingoru
- Oct 20, 2025, 07:36 AM UTC
- Resolved
- Oct 21, 2025, 05:23 PM UTC
- Duration
- 1d 9h
Read the full incident report →
- Detected by Pingoru
- Oct 16, 2025, 03:53 PM UTC
- Resolved
- Oct 16, 2025, 05:47 PM UTC
- Duration
- 1h 54m
Read the full incident report →
- Detected by Pingoru
- Oct 03, 2025, 11:44 AM UTC
- Resolved
- Oct 05, 2025, 10:00 PM UTC
- Duration
- 2d 10h
Read the full incident report →