Paddle

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-09-02 20:31 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...

2. resolved 2026-09-02 21:04 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...

Excerpts are shortened. Read the full incident on Paddle's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-08-24 08:35 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...

2. monitoring 2026-08-24 09:11 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...

3. resolved 2026-08-24 09:22 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 sellers@paddle.com.

Excerpts are shortened. Read the full incident on Paddle's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-07-16 08:00 UTC

   We’ve identified an issue affecting access to the Paddle seller dashboard sign-in flow at [vendors.paddle.com](http://vendors.paddle.com "vendors.paddle.com") and [sandbox-vendors.paddle.com](http://sandbox-vendors.paddle.com "sandbox-vendors.paddle.com"), caused by a...

2. resolved 2026-07-16 08:24 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...

Excerpts are shortened. Read the full incident on Paddle's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-06-25 01:07 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...

2. investigating 2026-06-25 03:18 UTC

   We are continuing to investigate the issue. We appreciate your patience. Please reach out to our Customer Support team via sellers@paddle.com should you have any questions.

3. monitoring 2026-06-25 03:35 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...

4. resolved 2026-06-25 05:16 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 sellers@paddle.com.

Excerpts are shortened. Read the full incident on Paddle's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2026-06-18 15:18 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...

2. identified 2026-06-18 15:41 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...

3. monitoring 2026-06-18 16:02 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...

4. resolved 2026-06-18 16:15 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...

Excerpts are shortened. Read the full incident on Paddle's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2026-06-01 08:38 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...

2. resolved 2026-06-01 08:59 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...

3. identified 2026-06-01 09:38 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...

4. resolved 2026-06-01 10:23 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 [sellers@paddle.com](mailto:sellers@paddle.com...

Excerpts are shortened. Read the full incident on Paddle's status page.

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-04-28 15:36 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...

2. identified 2026-04-28 16:45 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...

3. resolved 2026-04-30 14:07 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...

Excerpts are shortened. Read the full incident on Paddle's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-04-21 14:02 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...

2. resolved 2026-04-21 14:11 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...

Excerpts are shortened. Read the full incident on Paddle's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. identified 2026-04-21 11:00 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...

2. monitoring 2026-04-21 11:43 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...

3. resolved 2026-04-21 14:22 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...

Excerpts are shortened. Read the full incident on Paddle's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-03-30 09:23 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...

2. monitoring 2026-03-30 09:48 UTC

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

3. resolved 2026-03-30 13:38 UTC

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

Excerpts are shortened. Read the full incident on Paddle's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2026-03-20 18:59 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...

2. resolved 2026-03-20 19:27 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...

3. resolved 2026-03-21 16:04 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...

4. resolved 2026-03-21 16:05 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...

Excerpts are shortened. Read the full incident on Paddle's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-27 15:23 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...

2. resolved 2026-02-27 15:32 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: •...

3. resolved 2026-02-27 16:25 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 **[sellers@paddle.com](mailto:sellers@paddle.com...

Excerpts are shortened. Read the full incident on Paddle's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-06 12:40 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...

2. investigating 2026-02-06 13:57 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...

3. resolved 2026-02-06 14:32 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...

4. resolved 2026-02-07 12:27 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...

Excerpts are shortened. Read the full incident on Paddle's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-12-11 02:00 UTC

   Our engineers are currently investigating an issue affecting notifications. This is causing delayed delivery of webhooks and emails, 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...

2. monitoring 2025-12-11 02:10 UTC

   The issue causing the delayed delivery of notifications has now been resolved, and all notifications have been processed. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at sellers@paddle.com.

3. resolved 2025-12-11 09:16 UTC

   After a period of monitoring, we can confirm that the issue causing the delayed delivery of notifications has been fully resolved, and all notifications have been processed. Between 01.09am and 02.06am GMT we experienced delays in the delivery of notifications for both webhooks...

Excerpts are shortened. Read the full incident on Paddle's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2025-12-05 08:59 UTC

   Our engineers are currently investigating an issue affecting some of our services. 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 sellers@paddle.com should you have any questions.

2. monitoring 2025-12-05 09:16 UTC

   Services are now operational. 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...

3. resolved 2025-12-05 09:45 UTC

   All services have returned to normal following the Cloudflare incident this morning. Our engineers will continue to monitor our services, but we do not expect any further problems.

Excerpts are shortened. Read the full incident on Paddle's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Cloudflare.

1. investigating 2025-11-18 12:17 UTC

   Our engineers are currently investigating an issue. 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 [sellers@paddle.com](mailto:sellers@paddle.com "sellers@paddle.com") should you have...

2. investigating 2025-11-18 12:37 UTC

   We're currently seeing a small number of checkouts being impacted for customers using PayPal due to the Cloudflare outage. We are actively monitoring the situation and will provide an update when we have more information. We appreciate your patience. Please reach out to our...

3. monitoring 2025-11-18 13:28 UTC

   We're currently seeing a small number of checkouts being impacted for customers using PayPal due to the Cloudflare outage. We are actively monitoring the situation and will provide an update as soon as we have more information. We apologize for any disruption this may have...

4. resolved 2025-11-18 14:51 UTC

   The incident 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 sellers@paddle.com.

Excerpts are shortened. Read the full incident on Paddle's status page.

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-10 17:39 UTC

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

2. investigating 2025-11-10 18:01 UTC

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

3. investigating 2025-11-10 18:23 UTC

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

4. monitoring 2025-11-10 18:54 UTC

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

5. resolved 2025-11-10 19:04 UTC

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

6. investigating 2025-11-10 19:28 UTC

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

7. monitoring 2025-11-10 19:48 UTC

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

8. resolved 2025-11-10 20:17 UTC

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

9. monitoring 2025-11-10 21:04 UTC

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

10. resolved 2025-11-10 21:14 UTC

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

Excerpts are shortened. Read the full incident on Paddle's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-20 07:36 UTC

   Our engineers are currently investigating an issue affecting Checkouts and Orders Processing. This is causing Checkout to not be completed, 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....

2. identified 2025-10-20 08:09 UTC

   As a result of an AWS outage that began around 8:00, we've seen a number of our services impacted. Post-payment actions are affected, which means customers won't receive emails, webhooks won't be sent and subscription processing of recurring payments will be impacted. Checkouts...

3. identified 2025-10-20 08:30 UTC

   As a result of an AWS outage that began around 8:00, we've seen a number of our services impacted. Post-payment actions are affected, which means customers won't receive emails, webhooks won't be sent and subscription processing of recurring payments will be impacted. Checkouts...

4. investigating 2025-10-20 08:36 UTC

   As a result of an AWS outage that began around 8:00 UTC, we've seen a number of our services impacted. Post-payment actions are affected, which means customers won't receive emails, webhooks won't be sent and subscription processing of recurring payments will be impacted....

5. investigating 2025-10-20 08:49 UTC

   As a result of an AWS outage that began around 8:00 UTC, we've seen a number of our services impacted. Post-payment actions are affected, which means customers won't receive emails, webhooks won't be sent and subscription processing of recurring payments will be impacted....

6. identified 2025-10-20 09:28 UTC

   As a result of an AWS outage that began around 8:00 UTC, we've seen a number of our services impacted. We’re now seeing a recovery from AWS and our services have started to recover. Orders received during the outage were captured, so our team will be working through the backlog...

7. monitoring 2025-10-20 10:29 UTC

   As a result of an AWS outage that began around 8:00 UTC, we've seen a number of our services impacted. We’re now seeing a recovery from AWS and our services have started to recover. Orders received during the outage were captured, and our team worked through the backlog and they...

8. monitoring 2025-10-20 12:29 UTC

   Our platform remains stable and operational & our teams are continuing to monitor for any change in impact from AWS.

9. monitoring 2025-10-20 14:09 UTC

   Our platform remains stable and operational & our teams are continuing to monitor for any change in impact from AWS.

10. monitoring 2025-10-20 15:17 UTC

    Our platform remains stable and operational. Our teams are continuing to monitor for any change in impact from AWS. We will only post a new update if something changes.

11. resolved 2025-10-21 17:23 UTC

    The incident related to an AWS disruption, which briefly impacted checkouts and order processing, is now fully resolved. Our teams have continued to monitor our platform since the AWS services stabilized and have confirmed that all checkouts and order processing are functioning...

Excerpts are shortened. Read the full incident on Paddle's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. investigating 2025-10-16 15:53 UTC

   Our engineers are currently investigating an issue with the payment method PayPal for both Paddle Classic and Paddle Billing for both checkout and subscription payments due to an outage on PayPal's end. PayPal payment processing has stopped in the production environment,...

2. monitoring 2025-10-16 17:13 UTC

   The incident affecting PayPal payment processing for both Paddle Classic and Paddle Billing is now resolved. PayPal services are fully operational, and payments are going through successfully. The issue, which began around 15:22 UTC, was due to an outage on PayPal's end and...

3. monitoring 2025-10-16 17:29 UTC

   The incident affecting PayPal payment processing for both Paddle Classic and Paddle Billing is now resolved. PayPal services are fully operational, and payments are going through successfully. The issue, which began around 15:22 UTC, was due to an outage on PayPal's end and...

4. resolved 2025-10-16 17:47 UTC

   The incident affecting PayPal payments 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 sellers@paddle.com.

Excerpts are shortened. Read the full incident on Paddle's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2025-10-03 11:44 UTC

   Our engineers recently resolved an issue that affected the Profitwell web app and API, including the Paddle dashboard, Retain pages. Widgets and payment recovery features remained fully functional. We are actively monitoring the services to ensure stability and will provide...

2. resolved 2025-10-05 22:00 UTC

   After a period of monitoring, the issue impacting the Profitwell web app and API has been fully resolved. The service continues to work as expected, so we are closing this incident. We appreciate your patience and apologize for any disruption this may have caused. If you have...

Excerpts are shortened. Read the full incident on Paddle's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2025-09-07 10:23 UTC

   Our engineers are currently investigating an issue with our Notification Service for Paddle Classic. Due to an issue with a downstream provider, emails sent from 3pm UTC to 5pm UTC on September 6th were affected, with approximately 3000 events being delayed. We are currently...

2. monitoring 2025-09-07 10:25 UTC

   The issue with our Notification Service for Paddle Classic has been identified and fixed. The service is now operating normally, and all delayed events have been processed. We will continue to monitor for stability.

3. resolved 2025-09-08 15:34 UTC

   After a period of monitoring, the issue with the Notification Service for Paddle Classic has been fully resolved. The service continues to work as expected, so we are closing this incident. We appreciate your patience and apologize for any disruption this may have caused. If you...

Excerpts are shortened. Read the full incident on Paddle's status page.

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

1. identified 2024-09-16 11:58 UTC

   Our engineers have discovered a performance issue that began at 12:11 PM BST due to an outage with our third-party provider. This issue is impacting a small portion of checkouts for both Paddle Billing and Paddle Classic. The impact is being looked into and we will update as...

2. identified 2024-09-16 12:19 UTC

   Our engineers have re-routed payments, and as of 12:42 BST, normal checkout processing has resumed. However, subscription renewals are being impacted. My team is actively investigating and monitoring the situation to resolve these issues as quickly as possible. Thank you for...

3. monitoring 2024-09-16 14:26 UTC

   As of 13:44 BST, we have successfully resolved the issue with processing subscription renewal payments. Everything is now functioning normally. Our engineers will continue to monitor the situation to ensure there are no further issues. If you have any questions or concerns,...

4. resolved 2024-09-17 14:10 UTC

   Following a period of monitoring, we can confirm that the issue was fully resolved as of September 16 at 13:44 BST. In summary, a third-party provider experienced an outage between 12:12 and 12:42 BST, affecting payment processing. During this time, some checkout payments,...

Excerpts are shortened. Read the full incident on Paddle's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. monitoring 2024-09-23 17:34 UTC

   Some customers experienced latency in our checkout services for Paddle Billing between 03:05 PM UTC and 04:54 PM UTC. The underlying issue has now been resolved. We have identified the root cause and applied a fix. The platform is functioning as expected, and we will continue to...

2. resolved 2024-09-24 17:00 UTC

   Following a period of monitoring, we can confirm that the issue was fully resolved on September 23 at 04:54 PM UTC. Between 3:05 PM and 04:54 PM UTC, some customers were able to complete their checkout without the tax being calculated. This impacted around 2,000 Paddle Billing...

Excerpts are shortened. Read the full incident on Paddle's status page.

Failure mode: Data delayed, stale, lost or corrupted, or needing replay after recovery. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2024-09-25 17:41 UTC

   Our engineers are currently investigating an issue processing subscriptions for Paddle Billing and loading Orders within Paddle.net. The impact is being looked into and we will update as soon as we know more, along with the steps we've taken to resolve the issue once our...

2. monitoring 2024-09-25 18:32 UTC

   Our engineers have identified the issue and implemented a fix. All affected subscriptions have now been processed. Additionally, there was a delay in sending webhooks for the affected subscriptions, which has now been fixed. We will continue to monitor the platform for the next...

3. resolved 2024-09-27 13:33 UTC

   After a period of monitoring, we can confirm that the issue is fully resolved. With this, the incident is closed. Please reach out to support via sellers@paddle.com should you have any questions or concerns.

Excerpts are shortened. Read the full incident on Paddle's status page.

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2024-10-01 01:07 UTC

   Our engineers are currently investigating an issue processing transactions for Paddle Billing. The impact is being looked into and we will update as soon as we know more, along with the steps we've taken to resolve the issue once our engineers have found the cause and restored...

2. monitoring 2024-10-01 02:43 UTC

   [Monitoring] Our engineers have identified the issue and implemented a fix. All affected transactions have now been processed. We will continue to monitor the platform for the next 24 hours before closing this incident. We apologize for the disruption to our service. If you have...

3. resolved 2024-10-02 09:06 UTC

   After a period of monitoring, we can confirm that the issue is fully resolved. With this, the incident is closed. Please reach out to support via sellers@paddle.com should you have any questions or concerns.

Excerpts are shortened. Read the full incident on Paddle's status page.