Dev APIs / Payments / Paddle

Paddle

OPERATIONAL

Since Sep 2025 · 25 incidents · paddlestatus.com · checked just now

User reportsVisitors who said it's down for them, per hour over 24 hours. Not from the status page. Never counted in grades.
…
CompareAdd to stackStatus page
GradeA+Last 90 days
A+PRODA+SHIP

Overview

30d90d1y
Admitted uptimeCustomer time not hit, by the provider's own account. Regional and partial incidents count in part.
100.000%Grade A+
IncidentsEverything posted on the status page except scheduled maintenance.
30 Sev 1
Fully downMost customers down, by the provider's own account.
0m
Median fixMedian time to resolve. Half of incidents were fixed faster.
47m
LongestLongest Sev 1–2 incident, start to resolved.
–
Since lastTime since the last counted incident was resolved.
3d 6h

By area

A+Production
0INCIDENTS
0mAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 90dNothing.
Better. 3 in the last 6 months, 10 in the 6 before.
A+Shipping
1INCIDENTS
47mAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 90d
SEV 3Aug 24, 2026 · 47m · one model or featureRetain
Worse. 2 in the last 6 months, 0 in the 6 before.
CleanSev 3–4Sev 1–2No data

Trend, last 12 months

Better. 7 in the last 6 months, 11 in the 6 before.

Severity mix

Sev 1 · Lights outProd site, API or database down, or data loss0
Sev 2 · BleedingProd degraded or partly down0
Sev 3 · Can't shipCan't deploy, build or manage it1
Sev 4 · PapercutDocs, status page, slow dashboard2

When it breaks

Start times, last 12 months, UTC.

What breaks

No components named in the last 12 months.

Communication

Updates eachStatus page updates per incident, on average.
4.6Last 12 months
Update gapMedian time between status page updates during an incident.
29mLast 12 months
PostmortemsSev 1–2 incidents with a published write-up.
0 of 13Sev 1–2

Incident history

Oct 21, 20264h 05mSEV 4
Issue affecting metrics and reporting in the seller dashboardSeller dashboard metrics and reporting stopped working from about 19:37 UTC after an outage at a third-party provider. Paddle said all services returned to normal when the incident was resolved about four hours later.AI-graded · one model or feature
Why this grade
  1. RULES · SEV 4
    Sev 4 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · SINGLE · HIGH CONFIDENCE · BACK AFTER 4H 05M
    Metrics and reporting in the seller dashboard were broken for about four hours due to a third-party outage; payments and APIs were not described as affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 20:04 UTC · identified
    We have identified the issue affecting metrics and reporting in the seller dashboard, which began around 19:37 UTC, due to an outage with a third party provider. We will update the status once the issue has been resolved. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [email protected].
  2. 00:09 UTC · resolved
    The incident affecting metrics and reporting in the seller 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]](mailto:[email protected]).
Source
Sep 2, 202633mSEV 4
Report downloads unavailable in the Paddle DashboardReport downloads in the Paddle Dashboard failed for some users from 20:31 to 21:04 UTC on 2 September 2026. The provider deployed a fix and reports could be downloaded again.AI-graded · some customers
Why this grade
  1. RULES · SEV 4
    Sev 4 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · SUBSET · HIGH CONFIDENCE · BACK AFTER 33M
    Some users got errors downloading generated reports in the Paddle Dashboard for about 33 minutes; API and checkout not described as affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 20:31 UTC · investigating
    Our engineers are currently investigating an issue affecting report downloads in the Paddle Dashboard. Some users may encounter an error when attempting to download generated reports. We are working to identify the root cause and restore normal service as soon as possible. We’ll provide another update when more information is available. We appreciate your patience. Please reach out to our Customer Support team via [email protected] should you have any questions.
  2. 21:04 UTC · resolved
    The incident affecting report downloads in the Paddle Dashboard has been fully resolved. Our engineers deployed a fix, and the generated reports can now be downloaded as expected. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact our Customer Support team at [[email protected]](mailto:[email protected] "[email protected]").
Source
Aug 24, 202647mSEV 3
RetainPaddle reported an issue affecting its Retain product starting around 07:56 UTC on 24 August 2026. It deployed a fix and marked the incident resolved at 09:22 UTC. The updates do not describe the symptoms or how many customers were hit.AI-graded · one model or feature
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · SINGLE · LOW CONFIDENCE
    Paddle Retain, an add-on churn-recovery product, was affected for about 47 minutes; the update does not say what broke or how many sellers were hit.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
3 updates
  1. 08:35 UTC · identified
    We have identified the issue affecting Retain that began around 7:56 UTC. We are actively working to resolve the root cause and restore normal service as soon as possible. We will update the status once a fix has been deployed. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [email protected].
  2. 09:11 UTC · monitoring
    We have deployed a fix for the issue that was affecting Retain. We are closely monitoring the platform to ensure continued stability. We apologize for any disruption this may have caused. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [email protected].
  3. 09:22 UTC · resolved
    The incident affecting Retain has been fully resolved. All services are now operating normally. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact our Customer Support team at [email protected].
Source
Jul 16, 20260mSEV 3
Seller dashboard logins are failing with timeoutsPaddle seller dashboard sign-in was failing with timeouts for new login attempts at the live and sandbox dashboards, caused by a third-party incident. Users already signed in were not affected. Paddle reported all services operating normally at 08:24 UTC on 16 July 2026.AI-graded
Why this grade
  1. RULES · SEV 4
    Sev 4 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE · BACK AFTER -1M
    New seller dashboard sign-ins at vendors and sandbox-vendors failed with timeouts; already signed-in users were unaffected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 08:00 UTC · identified
    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 third-party incident. Users who are already signed in are not affected. The issue is only impacting new sign-in attempts. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [[email protected]](mailto:[email protected] "[email protected]").
  2. 08:24 UTC · resolved
    The incident affecting access to the Paddle seller dashboard sign-in has been fully resolved. All services are now operating normally. We are closely monitoring the platform to ensure continued stability. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact our Customer Support team at [email protected].
Source
Jun 25, 20264h 09mSEV 2
Intermittent Checkout Loading IssuesCheckout loading failed intermittently for some sellers across Paddle Classic and Paddle Billing starting 01:07 UTC. Investigation continued; a fix for Paddle Billing checkouts was deployed at 03:35 UTC and the incident was resolved at 05:16 UTC. Root cause was not stated in the updates.AI-graded · some customers
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Checkouts failed to load for some sellers on Paddle Classic and Billing for about four hours; no data loss reported.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
4 updates
  1. 01:07 UTC · identified
    Our engineers are currently investigating an issue affecting checkout loading across Paddle Classic and Paddle Billing. This is causing some sellers to experience checkouts not loading as expected, and we are working to identify the root cause. We will update the status as soon as we have more information. We appreciate your patience. Please reach out to my team via [[email protected]](mailto:[email protected] "[email protected]") should you have any questions.
  2. 03:18 UTC · investigating
    We are continuing to investigate the issue. We appreciate your patience. Please reach out to our Customer Support team via [email protected] should you have any questions.
  3. 03:35 UTC · monitoring
    We have deployed a fix for the issue that was affecting Paddle Billing Checkouts. We are closely monitoring the platform to ensure continued stability. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [email protected].
  4. 05:16 UTC · resolved
    The incident affecting Checkouts has been fully resolved. All services are now operating normally.  We apologize for any disruption this may have caused. If you have any questions or concerns, please contact our Customer Support team at [email protected].
Source
Jun 18, 202657mSEV 2
Partial Checkout OutagePaddle checkouts were partially failing from 15:18 to 16:15 UTC on June 18, 2026. Paddle said the root cause was a third-party provider. Mitigations were applied, the provider restored its services, and checkouts were processing normally again at resolution.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Checkouts were partly failing for about an hour due to a third-party provider; the text does not say how many customers were hit.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
4 updates
  1. 15:18 UTC · identified
    We have identified the issue affecting checkouts. We are actively working to resolve the root cause and restore normal service as soon as possible. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [email protected].
  2. 15:41 UTC · identified
    We have identified the root cause of the issue affecting checkouts, which is related to a third-party provider. Our team is currently implementing mitigations to resolve the issue and restore normal service as soon as possible. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [[email protected]](mailto:[email protected] "[email protected]").
  3. 16:02 UTC · monitoring
    We have implemented mitigations to address the issue affecting checkouts, and services are recovering. Our team is now actively monitoring the situation to ensure that normal service is fully restored and remains stable. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [[email protected]](mailto:[email protected] "[email protected]").
  4. 16:15 UTC · resolved
    The issue affecting checkouts has been resolved. The third-party provider has restored their services, and we have removed the temporary mitigations. All systems are now operating normally, and checkouts are processing as expected. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [[email protected]](mailto:[email protected] "[email protected]").
Source
Jun 1, 202621mSEV 2
Card payment issues on Paddle Billing and Paddle Classic checkoutCard payments at Paddle Billing and Paddle Classic checkout failed in two windows on 1 June 2026, first 09:07 to 09:21 GMT, then again later. Wallet payments and subscriptions were not affected. Paddle reported both issues resolved and is monitoring. No cause was given.AI-graded
Why this grade
  1. RULES · SEV 4
    Sev 4 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Card payments failed at checkout on Paddle Billing and Classic in two windows; wallet payments and subscriptions were reportedly unaffected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
4 updates
  1. 08:38 UTC · monitoring
    We identified an issue affecting card payments on Paddle Billing and Paddle Classic checkout between 09:07 and 09:21 GMT. Wallet payments and subscriptions do not appear to have been affected. The issue has now been resolved, and our team is monitoring the situation to ensure normal service continues. We apologize for any disruption this may have caused. If you have any questions or concerns, please reach out to us at [[email protected]](mailto:[email protected] "[email protected]").
  2. 08:59 UTC · resolved
    We identified an issue affecting card payments on Paddle Billing and Paddle Classic checkout between 09:07 and 09:21 GMT. Wallet payments and subscriptions do not appear to have been affected. The issue has now been resolved, and our team is monitoring the situation to ensure normal service continues. We apologize for any disruption this may have caused. If you have any questions or concerns, please reach out to us at [[email protected]](mailto:[email protected] "[email protected]").
  3. 09:38 UTC · identified
    We identified another issue affecting card payments on Paddle Billing and Paddle Classic. Wallet payments and subscriptions do not appear to have been affected. We apologize for any disruption this may have caused. If you have any questions or concerns, please reach out to us at [[email protected]](mailto:[email protected] "[email protected]").
  4. 10:23 UTC · resolved
    The issue has now been resolved, and our team is monitoring the situation to ensure normal service continues. We apologize for any disruption this may have caused. If you have any questions or concerns, please reach out to us at [[email protected]](mailto:[email protected] "[email protected]").
Source
Apr 28, 202646h 30mSEV 4
New Sellers might be unable to access Retain settings and the ProfitWell Metrics dashboardSome new Paddle Billing sellers were unable to access Retain settings and ProfitWell Metrics in the dashboard. Access for earlier sellers was gradually restored while a fix was deployed for new signups. Provider reported full resolution on April 30.AI-graded · some customers
Why this grade
  1. RULES · SEV 4
    Sev 4 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · SUBSET · MEDIUM CONFIDENCE · BACK AFTER 46H 30M
    Some new Paddle Billing signups could not access Retain settings and ProfitWell Metrics in the dashboard for about two days; existing sellers were gradually restored.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
3 updates
  1. 15:36 UTC · investigating
    We have identified an issue affecting new sellers’ access to the ProfitWell Metrics. We are actively working to resolve the root cause and restore normal service as soon as possible. We will update the status once a fix has been deployed. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [[email protected]](mailto:[email protected] "[email protected]").
  2. 16:45 UTC · identified
    We have identified an issue affecting access to Retain settings and Metrics for some new Paddle Billing signups in the dashboard. A fix has been scheduled for deployment for new signups, and the access for sellers who signed up earlier is being gradually restored. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [[email protected]](mailto:[email protected] "[email protected]").
  3. 14:07 UTC · resolved
    The incident affecting Retain settings and Metrics in the dashboard has been fully resolved. All services are now operating normally.  We apologize for any disruption this may have caused. If you have any questions or concerns, please contact our Customer Support team at [email protected].
Source
Apr 21, 20269mSEV 2
Discount service degradation causing discount application failuresCustomers adding a discount at checkout hit timeouts that stopped the discount being applied, starting around 13:15 UTC. Transactions could still complete. Service was reported fully restored at 14:11 UTC, with monitoring continuing for 24 hours. No cause was given.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Discount application at checkout timed out for customers for about 10 minutes; transactions could still complete.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 14:02 UTC · monitoring
    We have identified an issue affecting customers who are attempting to add a discount at checkout. They may encounter a timeout, which can prevent the discount from being applied, but it should not prevent the transaction from being completed. This began at approximately 13:15 UTC. We are actively working to resolve the root cause and restore normal service as soon as possible. We will update the status once a fix has been deployed. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [[email protected]](mailto:[email protected] "[email protected]").
  2. 14:11 UTC · resolved
    We are pleased to confirm that this issue has been resolved, and normal service has now been fully restored. Our team will continue to monitor the situation closely over the next 24 hours to ensure ongoing stability. We sincerely apologize for any disruption this may have caused. If you have any further questions or concerns, please don’t hesitate to reach out to my team at [[email protected]](mailto:[email protected] "[email protected]").
Source
Apr 21, 20263h 22mSEV 2
Webhook & Email DeliveryPaddle's webhooks and outbound emails were disrupted from about 11:40 UTC on 21 April 2026. The service was fully operational again by 12:07 BST, and all delayed webhooks and emails were reprocessed by 12:12 BST. The text gives no root cause.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE · BACK AFTER 43M
    Webhooks and outbound emails were delayed or not processed for about an hour; all were later reprocessed, and the text does not say how many customers were hit.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
3 updates
  1. 11:00 UTC · identified
    We have identified the issue affecting Email, Webhooks & Alerts that began around 11:40. We are actively working to resolve the root cause and restore normal service as soon as possible. We will update the status once a fix has been deployed. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [email protected].
  2. 11:43 UTC · monitoring
    A fix has been deployed and the underlying issue affecting Email, Webhooks & Alerts has been internally resolved. The service became fully operational again, processing new webhooks and outbound emails at 12:07 BST. Furthermore, all delayed webhooks and outbound emails were successfully reprocessed by 12:12 BST. We are continuing to monitor the situation to ensure full stability before marking this incident as completely resolved. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [[email protected]](mailto:[email protected] "[email protected]").
  3. 14:22 UTC · resolved
    The underlying issue affecting Email, Webhooks & Alerts has been resolved. The service became fully operational again, processing new webhooks and outbound emails at 12:07 BST, and all delayed webhooks and outbound emails were successfully reprocessed by 12:12 BST. Our teams will continue to monitor the services closely to ensure ongoing stability. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at [[email protected]](mailto:[email protected] "[email protected]").
Source
Mar 20–30, 20269d 18hSEV 2
Checkout Service Incident2 incidents
  1. Fri, Mar 20 18:59 UTC28mSEV 2
    Checkout Service IncidentPaddle's checkout service had about 11 minutes of errors starting around 18:20 GMT on March 20, 2026. Service was restored by 18:31 GMT. The provider did not describe a cause. The incident was closed after 24 hours of monitoring.AI-graded
    Why this grade
    1. RULES · SEV 2
      Sev 2 from the incident title (no components listed)
    2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE · BACK AFTER 28M
      Checkout service returned errors for about 11 minutes; the text does not say how many customers or regions were hit.
    3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
    4 updates
    1. 18:59 UTC · identified
      We have identified an issue affecting our checkout service that began around 18:20 GMT. Our team has confirmed the service experienced approximately 11 minutes of errors, with normal service restored by 18:31 GMT. We apologize for any disruption this may have caused. If you have any questions or concerns, please reach out to us at [[email protected]](mailto:[email protected] "[email protected]").
    2. 19:27 UTC · resolved
      We are pleased to confirm that the issue affecting our checkout service has been resolved. Normal service has been fully restored. Our team will continue to monitor the situation closely over the next 24 hours to ensure stability. We apologize for any disruption this may have caused. If you have any further questions or concerns, please don't hesitate to reach out to us at [[email protected]](mailto:[email protected] "[email protected]").
    3. 16:04 UTC · resolved
      Following 24 hours of monitoring, we are happy to confirm that this incident is now closed. Our checkout service remains fully stable with no further issues detected. Thank you for your patience while we worked through this. If you have any questions, please don't hesitate to reach out to us at [[email protected]](mailto:[email protected]).
    4. 16:05 UTC · resolved
      Following 24 hours of monitoring, we are happy to confirm that this incident is now closed. Our checkout service remains fully stable with no further issues detected. Thank you for your patience while we worked through this. If you have any questions, please don't hesitate to reach out to us at [[email protected]](mailto:[email protected] "[email protected]").
    Source
  2. Mon, Mar 30 09:23 UTC4h 15mSEV 2
    Intermittent Checkout Loading IssuesCheckouts intermittently failed to load across Paddle Classic and Paddle Billing from 09:23 to about 13:38 UTC on March 30, 2026. Only a small number of sellers were impacted. Paddle reported normal service restored; the root cause was not described in the updates.AI-graded · some customers
    Why this grade
    1. RULES · SEV 2
      Sev 2 from the incident title (no components listed)
    2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE · BACK AFTER 26M
      Checkout loading failed intermittently across Paddle Classic and Billing for a small number of sellers for about four hours.
    3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
    3 updates
    1. 09:23 UTC · investigating
      Our engineers are currently investigating an issue affecting checkout loading across Paddle Classic and Paddle Billing. This is causing some sellers to experience checkouts not loading as expected, and we are working to identify the root cause. We will update the status as soon as we have more information. We appreciate your patience. Please reach out to my team via [[email protected]](mailto:[email protected] "[email protected]") should you have any questions.
    2. 09:48 UTC · monitoring
      We are pleased to confirm that the issue affecting checkout loading across Paddle Classic and Paddle Billing has been resolved, and normal service has now been fully restored. A small number of sellers were impacted during this time. Our team will continue to monitor the situation closely over the next 24 hours to ensure ongoing stability. We sincerely apologize for any disruption this may have caused. If you have any further questions or concerns, please don’t hesitate to reach out to my team at [[email protected]](mailto:[email protected] "[email protected]").
    3. 13:38 UTC · resolved
      We are pleased to confirm that the issue affecting checkout loading across Paddle Classic and Paddle Billing has been resolved, and normal service has now been fully restored. A small number of sellers were impacted during this time. Our team will continue to monitor the situation closely over the next 24 hours to ensure ongoing stability. We sincerely apologize for any disruption this may have caused. If you have any further questions or concerns, please don’t hesitate to reach out to my team at [[email protected]](mailto:[email protected] "[email protected]").
    Source
Feb 27, 20269mSEV 2
Intermittent issues with RetainPaddle's Retain feature had intermittent disruption from about 2:56 to 3:25 PM UTC on February 27, 2026. Affected were payment retries, dunning emails, cancelling past-due subscriptions, the Customer Portal cancellation flow, and the Retain dashboard and metrics. The provider later reported all services operating normally.AI-graded
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE
    Retain payment retries, dunning emails and past-due cancellations were disrupted for about 30 minutes; the text does not say how many customers were hit.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
3 updates
  1. 15:23 UTC · investigating
    Our engineers are currently investigating an issue affecting Retain. This is causing some service disruption, and we are working to identify the root cause. We will update the status as soon as we have more information. We appreciate your patience. Please reach out to our Customer Support team via [email protected] should you have any questions.
  2. 15:32 UTC · resolved
    The incident affecting Retain has been fully resolved. All services are now operating normally. We will continue to monitor for the next 24 hours to ensure stability. During the incident between **2:56 PM UTC and 3:25 PM UTC**, the following areas may have been affected: • Metrics dashboard • Payment retries • Dunning emails • Cancelling past-due subscriptions • Cancellation flows not rendering correctly (Customer Portal fell back to the default cancellation modal) • The Retain section in the Paddle Billing dashboard We apologize for any disruption this may have caused. If you have any questions or concerns, please contact our Customer Support team at [[email protected]](mailto:[email protected] "[email protected]").
  3. 16:25 UTC · resolved
    The incident affecting Retain has been resolved, and service has recovered. We will continue monitoring to ensure everything remains stable. If you have any questions, please contact our Customer Support team at **[[email protected]](mailto:[email protected] "[email protected]")**.
Source
Feb 6, 20261h 52mSEV 2
Checkout Payment Failures for AliPayFrom 12:40 to 13:57 GMT on 6 February, buyers could not complete AliPay payments at checkout, or attempts returned errors. Paddle disabled the method during the incident, re-enabled it at 14:32 once errors stopped, and confirmed full resolution the next day. No root cause was given.AI-graded · one model or feature
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SINGLE · HIGH CONFIDENCE
    AliPay checkout payments failed or were unavailable for buyers for about 1 hour 17 minutes; other payment methods were not reported affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
4 updates
  1. 12:40 UTC · investigating
    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. 13:57 UTC · investigating
    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. 14:32 UTC · resolved
    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. 12:27 UTC · resolved
    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]").
Source
Dec 11, 20257h 16mSEV 2
Delayed notificationsPaddle experienced delayed delivery of webhooks and buyer emails between about 01:09 and 02:06 GMT, averaging around 20 minutes of delay. The cause was not stated in the updates. No notifications were lost, and all were processed after the fix.AI-graded
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · MEDIUM CONFIDENCE · BACK AFTER 10M
    Webhooks and buyer emails were delayed by about 20 minutes on average for roughly an hour; no notifications were lost.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
3 updates
  1. 02:00 UTC · investigating
    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. 02:10 UTC · monitoring
    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. 09:16 UTC · resolved
    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]").
Source
Dec 5, 202546mSEV 2
Some customers are experiencing issuesPaddle reported issues affecting some of its services starting 08:59 UTC on 5 December 2025, tied to a Cloudflare incident. Services were reported operational at 09:16 and fully returned to normal by 09:45. The text does not specify which services or customers were affected.AI-graded · some customers
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · LOW CONFIDENCE
    Some Paddle services failed for under an hour during a Cloudflare incident; the text does not say which services or customers were hit.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
3 updates
  1. 08:59 UTC · investigating
    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. 09:16 UTC · monitoring
    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. 09:45 UTC · resolved
    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.
Source
Nov 18, 20252h 33mSEV 2
Partial Checkout IssuesPaddle reported a small number of checkouts failing for customers paying with PayPal, caused by the Cloudflare outage. Monitoring began around 13:28 UTC and the incident was resolved at 14:51 UTC with all services operating normally.AI-graded · some customers
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    A small number of PayPal checkouts failed during the Cloudflare outage; other payment methods were not described as affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
4 updates
  1. 12:17 UTC · investigating
    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. 12:37 UTC · investigating
    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. 13:28 UTC · monitoring
    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. 14:51 UTC · resolved
    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].
Source
Nov 10, 20251h 25mSEV 2
Issue with the Retain widget functionalityPaddle's Retain service had widget failures and high latency from 17:39 to 19:04 UTC on 10 November 2025, affecting payment recovery, cancellation, reactivation and term optimization. Infrastructure was adjusted to stabilise performance. A second latency episode was resolved at 20:17 UTC. A database load spike from manually triggered jobs was addressed at 21:04 UTC.AI-graded · one model or feature
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SINGLE · MEDIUM CONFIDENCE
    Retain widgets for payment recovery, cancellation, reactivation and term optimization failed or ran slowly for about 1.5 hours across two windows; other Paddle products were not described as affected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
10 updates
  1. 17:39 UTC · investigating
    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]")
  2. 18:01 UTC · investigating
    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]")
  3. 18:23 UTC · investigating
    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]")
  4. 18:54 UTC · monitoring
    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].
  5. 19:04 UTC · resolved
    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]").
  6. 19:28 UTC · investigating
    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]")
  7. 19:48 UTC · monitoring
    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]").
  8. 20:17 UTC · resolved
    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]").
  9. 21:04 UTC · monitoring
    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].
  10. 21:14 UTC · resolved
    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]").
Source
Oct 20, 202533h 46mSEV 2
Checkout and Order Processing Issue ResolvedAn AWS outage on 20 October 2025 stopped Paddle from sending customer emails and webhooks and delayed recurring subscription processing. Checkout kept taking payments. Orders were captured and backlogs were worked through. Support was also briefly down. Monitoring continued until 21 October, when Paddle confirmed normal operation.AI-graded
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · GLOBAL · MEDIUM CONFIDENCE
    During an AWS outage, post-payment emails and webhooks were not sent and recurring subscription processing stalled for about two hours; checkout kept working.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
11 updates
  1. 07:36 UTC · investigating
    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. 08:09 UTC · identified
    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. 08:30 UTC · identified
    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. 08:36 UTC · investigating
    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. 08:49 UTC · investigating
    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. 09:28 UTC · identified
    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. 10:29 UTC · monitoring
    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. 12:29 UTC · monitoring
    Our platform remains stable and operational & our teams are continuing to monitor for any change in impact from AWS.
  9. 14:09 UTC · monitoring
    Our platform remains stable and operational & our teams are continuing to monitor for any change in impact from AWS.
  10. 15:17 UTC · monitoring
    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. 17:23 UTC · resolved
    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]").
Source
Oct 16, 20251h 54mSEV 2
Some customers were experiencing issues with PayPalPayPal payments through Paddle stopped from about 15:22 UTC, so buyers saw a payment error at checkout and subscription payments failed. The cause was an outage on PayPal's side. Processing recovered by 17:13 UTC, and Paddle marked the incident resolved at 17:47 UTC.AI-graded · one model or feature
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SINGLE · HIGH CONFIDENCE · BACK AFTER 1H 20M
    PayPal checkout and subscription payments failed for Paddle Classic and Billing for about two hours; other payment methods were unaffected.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
4 updates
  1. 15:53 UTC · investigating
    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. 17:13 UTC · monitoring
    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. 17:29 UTC · monitoring
    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]").
  4. 17:47 UTC · resolved
    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].
Source
Oct 3, 20252d 10hSEV 3
Some customers were experiencing issues with ProfitWellAn issue affected the ProfitWell web app and API, including the Paddle dashboard and Retain pages, for some customers. Widgets and payment recovery stayed functional. Engineers resolved it, monitored, and closed the incident on October 5 after confirming normal operation. The text gives no cause and does not say how many customers were hit.AI-graded · some customers
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · UNCLEAR · MEDIUM CONFIDENCE
    ProfitWell web app, API, Paddle dashboard and Retain pages were disrupted for some customers for roughly two days; widgets and payment recovery stayed up.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
2 updates
  1. 11:44 UTC · monitoring
    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. 22:00 UTC · resolved
    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].")
Source
Sep 29, 20250mSEV 4
Some customers are experiencing issues with our buyer emailsPaddle Classic's Notification Service was affected by a downstream provider issue, delaying about 3000 buyer emails sent between 3pm and 5pm UTC on September 6. The issue was fixed, delayed events were reprocessed, and the incident was closed on September 8.AI-graded · some customers
Why this grade
  1. RULES · SEV 2
    Sev 2 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · SUBSET · MEDIUM CONFIDENCE · BACK AFTER -31850M
    Buyer notification emails for Paddle Classic were delayed for about two hours on September 6; all delayed events were later processed.
  3. Claude Haiku 5.5 · prompt v11 · Oct 24, 2026 · Raw record
3 updates
  1. 10:23 UTC · identified
    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.
  2. 10:25 UTC · monitoring
    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. 15:34 UTC · resolved
    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]
Source

Older than a year

Sep 9, 2025 – Sep 24, 2024-503677mSEV 2
Some customers are experiencing issues with our Checkouts2 incidents
  1. Tue, Sep 9 11:36 UTC0mSEV 2
    Some customers are experiencing issues with our CheckoutsSome customers saw latency in Paddle Billing checkout from 3:05 to 4:54 PM UTC on September 23, 2024. Around 2,000 transactions completed without tax calculated. The root cause was fixed, and correct tax applies to later renewals.AI-graded · some customers
    Source
  2. Tue, Sep 9 11:37 UTC0mSEV 2
    Some customers are experiencing issues with our checkout in Paddle Billing and Paddle ClassicA third-party provider outage caused some Paddle checkouts, subscription renewals and unscheduled payments to fail from about 12:12 to 13:44 BST on 16 September. Payments were re-routed, and failed payments were automatically retried after recovery.AI-graded · some customers
    Source
Sep 9, 20250mSEV 2
Some customers are experiencing issues processing subscriptionsPaddle Billing had trouble processing subscriptions for some customers and Orders would not load in the dashboard. Webhooks for affected subscriptions were also delayed. Engineers implemented a fix, processed the affected subscriptions, and closed the incident after 24 hours of monitoring.AI-graded · some customers
Source

Peers, 90 days

Compare
MailerSendGrade A+100.00% up0 incidentsMTTR –MapboxGrade A+99.99% up2 incidentsMTTR 12h 38mPaddleGrade A+100.00% up3 incidentsMTTR 47mLoopsGrade A+100.00% up1 incidentMTTR 1h 34mKindeGrade A+99.99% up2 incidentsMTTR 1h 12mCloudinaryGrade A99.97% up5 incidentsMTTR 1h 47mAblyGrade A99.98% up7 incidentsMTTR 7mMailgunGrade A99.96% up9 incidentsMTTR 42mPusherGrade A99.97% up2 incidentsMTTR 3h 45mInngestGrade B99.63% up14 incidentsMTTR 43mClerkGrade C99.91% up10 incidentsMTTR 3h 26mResendGrade C99.85% up25 incidentsMTTR 24mStytchGrade C99.83% up6 incidentsMTTR 2h 29mWorkOSGrade C99.42% up21 incidentsMTTR 1h 05mTwilioGrade D99.10% up60 incidentsMTTR 6h 43mPlaidGrade D98.13% up18 incidentsMTTR 3h 38m

README badge

Paddle's live grade, for your README.

Paddle grade badge
[![paddle on downagain.dev](https://downagain.dev/badge/paddle.svg)](https://downagain.dev/p/paddle)