Paddle 장애 기록

1. 2026년 10월 21일 오후 8:04 UTCidentified

   우리는 메트릭에 영향을 미치는 문제를 식별하고 판매자 대시보드에보고, 이는 19:37 UTC의 주위에 시작, 제 3 자 제공 업체와 정전. 문제가 해결되면 상태를 업데이트합니다. 우리는이 발생 할 수있는 모든 혼란에 대해 사과합니다. 질문이 있거나 우려 사항이 있으시면, [email protected]으로 문의하십시오.

2. 2026년 10월 22일 오전 12:09 UTCresolved

   판매자 대시보드의 메트릭 및 보고에 영향을 미치는 사건은 완전히 해결되었습니다. 모든 서비스는 현재 운영 중입니다. 우리는이 발생 할 수있는 모든 혼란에 대해 사과합니다. 질문이 있거나 우려 사항이 있으시면 [[email protected]](mailto:[email protected])에서 고객 지원 팀에 문의하십시오.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 9월 2일 오후 8:31 UTCinvestigating

   우리의 엔지니어는 현재 Paddle Dashboard의 보고서 다운로드에 영향을 미치는 문제점을 조사하고 있습니다. 일부 사용자는 생성 된 보고서를 다운로드 할 때 오류가 발생할 수 있습니다. 우리는 뿌리 원인을 확인하고 가능한 한 빨리 정상 서비스를 복원하기 위해 노력하고 있습니다. 더 많은 정보를 사용할 때 또 다른 업데이트가 제공됩니다. 우리는 당신의 인내를 평가합니다. 판매자@paddle.com을 통해 고객 지원 팀에 도달하면 질문이 있습니다.

2. 2026년 9월 2일 오후 9:04 UTCresolved

   Paddle Dashboard의 보고서 다운로드에 영향을 미치는 사건은 완전히 해결되었습니다. 우리의 엔지니어는 수정을 배포하고 생성 된 보고서는 현재 예상대로 다운로드 할 수 있습니다. 우리는이 발생 할 수있는 모든 혼란에 대해 사과합니다. 질문이 있거나 우려 사항이 있으시면 [[email protected]](mailto:[email protected] "[email protected]").

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 8월 24일 오전 8:35 UTCidentified

   우리는 7:56 UTC의 주위에 시작 Retain에 영향을 미치는 문제를 확인했습니다. 우리는 뿌리 원인을 해결하고 가능한 한 빨리 정상 서비스를 복원하기 위해 적극적으로 노력하고 있습니다. 수정이 배포되면 상태를 업데이트합니다. 우리는이 발생 할 수있는 모든 혼란에 대해 사과합니다. 질문이 있거나 우려 사항이 있으시면, [email protected]으로 문의하십시오.

2. 2026년 8월 24일 오전 9:11 UTCmonitoring

   우리는 Retain에 영향을 미치는 문제에 대한 수정을 배포했습니다. 우리는 지속적으로 안정성을 보장하기 위해 플랫폼을 감시하고 있습니다. 우리는이 발생 할 수있는 모든 혼란에 대해 사과합니다. 우리는이 발생 할 수있는 모든 혼란에 대해 사과합니다. 질문이 있거나 우려 사항이 있으시면, [email protected]으로 문의하십시오.

3. 2026년 8월 24일 오전 9:22 UTCresolved

   Retain에 영향을 미치는 사건은 완전히 해결되었습니다. 모든 서비스는 현재 운영 중입니다. 우리는이 발생 할 수있는 모든 혼란에 대해 사과합니다. 질문이 있거나 우려 사항이 있는 경우, 판매자@paddle.com에서 고객 지원 팀에 문의하십시오.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 7월 16일 오전 8:25 UTCidentified

   우리는 [vendors.paddle.com] (http://vendors.paddle.com] (http://vendors.paddle.com "vendors.paddle.com")의 Paddle 판매자 대시 보드 기호 인 흐름에 영향을 미치는 문제와 [sandbox-vendors.com] (http://sandbox-vendors.paddle.com "sandbox-vendors.paddle.com"), 제 3 자 사건에 의해 발생했습니다. 이미 로그인한 사용자는 영향을받지 않습니다. 문제는 새로운 서명 인 시도에만 영향을 미칩니다. 우리는이 발생 할 수있는 모든 혼란에 대해 사과합니다. 질문이 있거나 우려 사항이 있으시면 [[email protected]](mailto:[email protected] "[email protected]").

2. 2026년 7월 16일 오전 8:30 UTCresolved

   Paddle 판매자 대시보드에 접근하는 사건은 완전히 해결되었습니다. 모든 서비스는 현재 운영 중입니다. 우리는 지속적으로 안정성을 보장하기 위해 플랫폼을 감시하고 있습니다. 우리는이 발생 할 수있는 모든 혼란에 대해 사과합니다. 질문이 있거나 우려 사항이 있는 경우, 판매자@paddle.com에서 고객 지원 팀에 문의하십시오.

공식 인시던트 업데이트를 자동 번역했습니다.

1. 2026년 6월 25일 오전 1:07 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. 2026년 6월 25일 오전 3:18 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. 2026년 6월 25일 오전 3:35 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. 2026년 6월 25일 오전 5:16 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. 2026년 6월 18일 오후 3:18 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. 2026년 6월 18일 오후 3:41 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. 2026년 6월 18일 오후 4:02 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. 2026년 6월 18일 오후 4:15 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. 2026년 6월 1일 오전 8:38 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. 2026년 6월 1일 오전 8:59 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. 2026년 6월 1일 오전 9:38 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. 2026년 6월 1일 오전 10:23 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. 2026년 4월 28일 오후 3:41 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. 2026년 4월 28일 오후 4:45 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. 2026년 4월 30일 오후 2:07 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. 2026년 4월 21일 오후 2:02 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. 2026년 4월 21일 오후 2:11 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. 2026년 4월 21일 오전 11:00 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. 2026년 4월 21일 오전 11:43 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. 2026년 4월 21일 오후 2:22 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. 2026년 3월 30일 오전 9:23 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. 2026년 3월 30일 오전 9:48 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. 2026년 3월 30일 오후 1:38 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. 2026년 3월 20일 오후 6:59 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. 2026년 3월 20일 오후 7:27 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. 2026년 3월 21일 오후 4:04 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. 2026년 3월 21일 오후 4:05 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. 2026년 2월 27일 오후 3:23 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. 2026년 2월 27일 오후 3:32 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. 2026년 2월 27일 오후 4:25 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. 2026년 2월 6일 오후 12:40 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. 2026년 2월 6일 오후 1:57 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. 2026년 2월 6일 오후 2:32 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. 2026년 2월 7일 오후 12:27 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. 2025년 12월 11일 오전 2:00 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. 2025년 12월 11일 오전 2:10 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. 2025년 12월 11일 오전 9:16 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. 2025년 12월 5일 오전 8:59 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. 2025년 12월 5일 오전 9:16 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. 2025년 12월 5일 오전 9:45 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. 2025년 11월 18일 오후 12:17 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. 2025년 11월 18일 오후 12:37 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. 2025년 11월 18일 오후 1:28 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. 2025년 11월 18일 오후 2:51 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. 2025년 11월 10일 오후 6:01 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. 2025년 11월 10일 오후 6:23 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. 2025년 11월 10일 오후 6:54 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. 2025년 11월 10일 오후 7:28 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. 2025년 11월 10일 오후 7:48 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. 2025년 11월 10일 오후 9:04 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. 2025년 11월 10일 오후 9:14 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. 2025년 10월 20일 오전 7:36 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. 2025년 10월 20일 오전 8:09 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. 2025년 10월 20일 오전 8:30 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. 2025년 10월 20일 오전 8:36 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. 2025년 10월 20일 오전 8:49 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. 2025년 10월 20일 오전 9:28 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. 2025년 10월 20일 오전 10:29 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. 2025년 10월 20일 오후 2:09 UTCmonitoring

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

9. 2025년 10월 20일 오후 3:17 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. 2025년 10월 21일 오후 5:23 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. 2025년 10월 16일 오후 3:53 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. 2025년 10월 16일 오후 5:29 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. 2025년 10월 16일 오후 5:47 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].