Historial de interrupciones de Paddle

1. July 16, 2026 at 8:25 AM UTCidentified

   Hemos identificado un problema que afecta el acceso al flujo de registro de tableros de Paddle en [vendors.paddle.com](http://vendors.paddle.com "vendors.paddle.com") y [sandbox-vendors.paddle.com](http://sandbox-vendors.paddle.com "sandbox-vendors.paddle"). Los usuarios que ya están firmados no se ven afectados. La cuestión sólo afecta a nuevos intentos de entrada. Nos disculpamos por cualquier perturbación que esto pueda haber causado. Si tiene alguna pregunta o inquietud, póngase en contacto con nosotros en [[email protected]](mailto:[email protected] "[email protected]").

2. July 16, 2026 at 8:30 AM UTCresolved

   El incidente que afectó el acceso al registro de tablero de Paddle seller ha sido resuelto completamente. Todos los servicios funcionan normalmente. Estamos monitoreando de cerca la plataforma para asegurar la estabilidad continua. Nos disculpamos por cualquier perturbación que esto pueda haber causado. Si tiene alguna pregunta o inquietud, por favor contacte con nuestro equipo de Atención al Cliente en [email protected].

Traducido automáticamente desde la actualización oficial del incidente.

1. June 25, 2026 at 1:07 AM UTCidentified

   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]](mailto:[email protected] "[email protected]") should you have any questions.

2. June 25, 2026 at 3:18 AM UTCinvestigating

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

3. June 25, 2026 at 3:35 AM UTCmonitoring

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

4. June 25, 2026 at 5:16 AM UTCresolved

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

1. June 18, 2026 at 3:18 PM UTCidentified

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

2. June 18, 2026 at 3:41 PM UTCidentified

   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]](mailto:[email protected] "[email protected]").

3. June 18, 2026 at 4:02 PM UTCmonitoring

   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]](mailto:[email protected] "[email protected]").

4. June 18, 2026 at 4:15 PM UTCresolved

   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]](mailto:[email protected] "[email protected]").

1. June 1, 2026 at 8:38 AM UTCmonitoring

   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]](mailto:[email protected] "[email protected]").

2. June 1, 2026 at 8:59 AM UTCresolved

   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]](mailto:[email protected] "[email protected]").

3. June 1, 2026 at 9:38 AM UTCidentified

   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]](mailto:[email protected] "[email protected]").

4. June 1, 2026 at 10:23 AM UTCresolved

   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]](mailto:[email protected] "[email protected]").

1. April 28, 2026 at 3:41 PM UTCinvestigating

   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]](mailto:[email protected] "[email protected]").

2. April 28, 2026 at 4:45 PM UTCidentified

   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]](mailto:[email protected] "[email protected]").

3. April 30, 2026 at 2:07 PM UTCresolved

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

1. April 21, 2026 at 2:02 PM UTCmonitoring

   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]](mailto:[email protected] "[email protected]").

2. April 21, 2026 at 2:11 PM UTCresolved

   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]](mailto:[email protected] "[email protected]").

1. April 21, 2026 at 11:00 AM UTCidentified

   We have identified the issue affecting Email, Webhooks & Alerts that began around 11:40. We are actively working to resolve the root cause and restore normal service as soon as possible. We will update the status once a fix has been deployed. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [email protected].

2. April 21, 2026 at 11:43 AM UTCmonitoring

   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]](mailto:[email protected] "[email protected]").

3. April 21, 2026 at 2:22 PM UTCresolved

   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]](mailto:[email protected] "[email protected]").

1. March 30, 2026 at 9:23 AM UTCinvestigating

   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]](mailto:[email protected] "[email protected]") should you have any questions.

2. March 30, 2026 at 9:48 AM UTCmonitoring

   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]](mailto:[email protected] "[email protected]").

3. March 30, 2026 at 1:38 PM UTCresolved

   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]](mailto:[email protected] "[email protected]").

1. March 20, 2026 at 6:59 PM UTCidentified

   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]](mailto:[email protected] "[email protected]").

2. March 20, 2026 at 7:27 PM UTCresolved

   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]](mailto:[email protected] "[email protected]").

3. March 21, 2026 at 4:04 PM UTCresolved

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

4. March 21, 2026 at 4:05 PM UTCresolved

   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] "[email protected]").

1. February 27, 2026 at 3:23 PM UTCinvestigating

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

2. February 27, 2026 at 3:32 PM UTCresolved

   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]](mailto:[email protected] "[email protected]").

3. February 27, 2026 at 4:25 PM UTCresolved

   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]](mailto:[email protected] "[email protected]")**.

1. February 6, 2026 at 12:40 PM UTCinvestigating

   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]](mailto:[email protected] "[email protected]") should you have any questions.

2. February 6, 2026 at 1:57 PM UTCinvestigating

   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]](mailto:[email protected] "[email protected]") should you have any questions

3. February 6, 2026 at 2:32 PM UTCresolved

   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]](mailto:[email protected] "[email protected]").

4. February 7, 2026 at 12:27 PM UTCresolved

   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]](mailto:[email protected] "[email protected]").

1. December 11, 2025 at 2:00 AM UTCinvestigating

   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 reach out to our Customer Support team via [email protected] should you have any questions.

2. December 11, 2025 at 2:10 AM UTCmonitoring

   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 [email protected].

3. December 11, 2025 at 9:16 AM UTCresolved

   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 and emails to buyers. During the incident we saw an average delay of around 20 minutes for these notifications. No notifications were lost and all were processed 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]](mailto:[email protected] "[email protected]").

1. December 5, 2025 at 8:59 AM UTCinvestigating

   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 [email protected] should you have any questions.

2. December 5, 2025 at 9:16 AM UTCmonitoring

   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 [email protected]

3. December 5, 2025 at 9:45 AM UTCresolved

   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.

1. November 18, 2025 at 12:17 PM UTCinvestigating

   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 [[email protected]](mailto:[email protected] "[email protected]") should you have any questions.

2. November 18, 2025 at 12:37 PM UTCinvestigating

   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 Customer Support team via [[email protected]](mailto:[email protected] "[email protected]") should you have any questions.

3. November 18, 2025 at 1:28 PM UTCmonitoring

   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 caused. If you have any questions or concerns, please contact us at [email protected].

4. November 18, 2025 at 2:51 PM UTCresolved

   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 [email protected].

1. November 10, 2025 at 6:01 PM UTCinvestigating

   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 process. We apologize for any disruption this may be causing. If you have any questions or concerns, please contact us at [[email protected]](mailto:[email protected] "[email protected]")

2. November 10, 2025 at 6:23 PM UTCinvestigating

   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 cause and implement a solution. We will provide further updates as soon as they are available. We apologize for any disruption this may be causing. If you have any questions or concerns, please contact us at [[email protected]](mailto:[email protected] "[email protected]")

3. November 10, 2025 at 6:54 PM UTCmonitoring

   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 apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [email protected].

4. November 10, 2025 at 7:28 PM UTCinvestigating

   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 any disruption this may be causing. If you have any questions or concerns, please contact us at [[email protected]](mailto:[email protected] "[email protected]")

5. November 10, 2025 at 7:48 PM UTCmonitoring

   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 apologize for the disruption this has caused. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [[email protected]](mailto:[email protected] "[email protected]").

6. November 10, 2025 at 9:04 PM UTCmonitoring

   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 [email protected].

7. November 10, 2025 at 9:14 PM UTCresolved

   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 [[email protected]](mailto:[email protected] "[email protected]").

1. October 20, 2025 at 7:36 AM UTCinvestigating

   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. Please reach out to our Customer Support team via [email protected] should you have any questions.

2. October 20, 2025 at 8:09 AM UTCidentified

   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 are fully operational, meaning payments are still being taken. We are actively working to mitigate 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].

3. October 20, 2025 at 8:30 AM UTCidentified

   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 are fully operational, meaning payments are still being taken. We are actively working to mitigate the root cause and restore normal service as soon as possible. We apologize for any disruption this may have caused. While our customer support is currently algo being impacted by the incident, if you have any questions or concerns, please contact us at [[email protected]](mailto:[email protected] "[email protected]"). We will respond as soon as we’re able.

4. October 20, 2025 at 8:36 AM UTCinvestigating

   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. Checkouts are fully operational, meaning payments are still being taken. Our team is still working on mitigating the impact of the AWS outage. Our support systems are also impacted by this and we are currently unable to receive or respond to any customer queries. In the meantime, please reach out to [[email protected]](mailto:[email protected] "[email protected]") and we will respond as soon as we can. We apologize for any disruption this is causing.

5. October 20, 2025 at 8:49 AM UTCinvestigating

   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. Checkouts are fully operational, meaning payments are still being taken. Our team is still working on mitigating the impact of the AWS outage. Our support systems are also impacted by this and we are currently unable to receive or respond to any customer queries. We apologize for any disruption this is causing.

6. October 20, 2025 at 9:28 AM UTCidentified

   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 to process them now. Post-payment actions are recovering, which means some customers may not receive emails and webhooks. Subscription processing of recurring payments will be processed as soon as the platform is fully recovered. Checkouts remain fully operational, meaning payments are still being taken. Our support systems are now fully operational, if you have any questions, please reach out to [email protected]. We apologize for any disruption this is causing.

7. October 20, 2025 at 10:29 AM UTCmonitoring

   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 are processed. Post-payment actions were recovered, which means customers are now receiving emails and webhooks. Subscription processing of recurring payments is active again and going through the backlog. Checkouts remain fully operational, meaning payments are still being taken. Our support systems are now fully operational, if you have any questions, please reach out to [[email protected]](mailto:[email protected] "[email protected]").

8. October 20, 2025 at 2:09 PM UTCmonitoring

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

9. October 20, 2025 at 3:17 PM UTCmonitoring

   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.

10. October 21, 2025 at 5:23 PM UTCresolved

    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 normally. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact our Customer Support team at [[email protected]](mailto:[email protected] "[email protected]").

1. October 16, 2025 at 3:53 PM UTCinvestigating

   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, preventing customers from completing transactions using PayPal. The issue began around 15:22 UTC and is ongoing, with only brief periods of successful processing. Buyers who are trying to checkout via PayPal will receive an error which states: "unable to take payment, please try another payment method". Other payment methods remain unaffected. We will update here with more information.

2. October 16, 2025 at 5:29 PM UTCmonitoring

   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 briefly stopped payment processing, preventing customers from completing transactions using PayPal. We appreciate your patience during this time. If you have any questions or concerns, please contact our Customer Support team at [[email protected]](mailto:[email protected] "[email protected]").

3. October 16, 2025 at 5:47 PM UTCresolved

   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 [email protected].

1. October 3, 2025 at 11:44 AM UTCmonitoring

   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 updates here if any further action is required. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [email protected].

2. October 5, 2025 at 10:00 PM UTCresolved

   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 any questions or concerns, please contact us at [[email protected].](http://[email protected]./ "[email protected].")

1. September 29, 2025 at 1:15 PM UTCresolved

   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 have any questions or concerns, please contact us at [email protected]

2. September 29, 2025 at 1:15 PM UTCidentified

   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 reprocessing these emails.

3. September 29, 2025 at 1:15 PM UTCmonitoring

   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.