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
GradeALast 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.
99.998%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.
47m
Since lastTime since the last counted incident was resolved.
2d 15h

By area

A+Production
1INCIDENTS
47mAFFECTED
Your users are hit: apps, APIs, databases, inference
Worst, 90d
SEV 2Aug 24, 2026 · 47m · one model or featureRetain
Better. 4 in the last 6 months, 9 in the 6 before.
A+Shipping
0INCIDENTS
0mAFFECTED
You can't deploy, build or manage: CI, CLI, dashboard, auth, billing
Worst, 90dNothing.
Better. 1 in the last 6 months, 2 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 down1
Sev 3 · Can't shipCan't deploy, build or manage it0
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

Show all 22
Oct 21, 20264h 05mSEV 4
Issue affecting metrics and reporting in the seller dashboardPaddle's seller dashboard metrics and reporting were affected starting about 19:37 UTC on 2026-10-21 because of a third-party provider outage. Paddle said all services returned to normal by 00:09 UTC on 2026-10-22. No other impact was described.AI-graded
Why this grade
  1. RULES · SEV 4
    Sev 4 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · UNCLEAR · MEDIUM 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 reported affected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 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 starting at 20:31 UTC on 2 September 2026. Engineers deployed a fix and downloads worked again by 21:04 UTC. The root cause was not described.AI-graded
Why this grade
  1. RULES · SEV 4
    Sev 4 from the incident title (no components listed)
  2. CLAUDE · SEV 4 · UNCLEAR · MEDIUM CONFIDENCE
    Some users got errors downloading generated reports in the Paddle Dashboard for about 33 minutes; no other impact was reported.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 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 2
RetainPaddle's Retain add-on, which handles subscription cancellation saves, had an issue starting around 07:56 UTC. A fix was deployed at 09:11 UTC and the incident was resolved at 09:22 UTC. The provider did not describe the impact on customers or the root cause.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 · LOW CONFIDENCE
    Paddle's Retain add-on had an unspecified issue for about 85 minutes; the update text gives no detail on how many customers were hit.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 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 attempts failed with timeouts because of a third-party incident, affecting only new logins at vendors.paddle.com and sandbox-vendors.paddle.com. Users already signed in were not affected. Paddle later reported the sign-in flow fully resolved and all services operating normally.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 timed out due to a third-party incident; already signed-in users were unaffected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 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 IssuesPaddle checkouts intermittently failed to load for some sellers on Paddle Classic and Paddle Billing starting 01:07 UTC on 25 June 2026. A fix for the Paddle Billing checkout issue was deployed around 03:35 UTC, and the incident was resolved at 05:16 UTC. 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
    Checkout loading failed intermittently for some sellers across Paddle Classic and Billing for about four hours; the scope was not fully specified.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 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 traced the cause to a third-party provider and applied mitigations. The third party restored service, the temporary mitigations were removed, and checkouts returned to normal.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 share of affected customers is not stated.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 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 between 09:07 and 09:21 GMT. A second card payment issue followed at 09:38 GMT. Wallet payments and subscriptions were unaffected. The cause was not described, and the incident was marked resolved at 10:23 GMT.AI-graded · some customers
Why this grade
  1. RULES · SEV 4
    Sev 4 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · SUBSET · MEDIUM CONFIDENCE
    Card payments failed at Paddle Billing and Classic checkout in two episodes; wallet payments and subscriptions were not affected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 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 3
New Sellers might be unable to access Retain settings and the ProfitWell Metrics dashboardSome new Paddle Billing signups were unable to access Retain settings and the ProfitWell Metrics dashboard from April 28 to April 30, 2026. A fix was deployed for new signups while access for earlier sellers was gradually restored. Paddle later reported full resolution.AI-graded · some customers
Why this grade
  1. RULES · SEV 4
    Sev 4 from the incident title (no components listed)
  2. CLAUDE · SEV 3 · SUBSET · MEDIUM CONFIDENCE
    Some new Paddle Billing sellers could not access Retain settings and Metrics in the dashboard for about two days; existing sellers were gradually restored.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 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, though transactions still completed. Issue began around 13:15 UTC and was resolved about 14:11 UTC on 21 April 2026. Cause and scope beyond checkout discounts were not detailed.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 timed out at checkout for some customers for about 10 minutes; transactions still completed.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 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 Email, Webhooks and Alerts service stopped processing new webhooks and outbound emails for about an hour. The provider deployed a fix, reported full operation again at 12:07 BST, and reprocessed all delayed webhooks and emails by 12:12 BST. The text does not give the cause or the number of customers affected.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
    Webhook and outbound email processing was delayed for roughly an hour; the provider says all delayed items were later reprocessed.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 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 30, 20264h 15mSEV 2
Intermittent Checkout Loading IssuesCheckouts intermittently failed to load across Paddle Classic and Billing for some sellers, starting 09:23 UTC on 30 March 2026. The provider said service was fully restored by 09:48 UTC, and the incident was marked resolved at 13:38 UTC. 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 some sellers for about 4.5 hours; the rest was unaffected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 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
Mar 20, 202628mSEV 2
Checkout Service IncidentPaddle's checkout service returned errors for about 11 minutes on March 20, 2026, from roughly 18:20 to 18:31 GMT. Service was restored by 18:31 GMT. The provider's monitoring period ended without further issues, and the cause was not described.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 0M
    Checkout service returned errors for about 11 minutes on March 20; the text does not say how many customers were hit.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 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
Feb 27, 20269mSEV 3
Intermittent issues with RetainPaddle's Retain product had intermittent disruption for about 30 minutes on 2026-02-27. Payment retries, dunning emails, and cancelling past-due subscriptions may have been affected, along with the Retain metrics dashboard and cancellation flows in the Customer Portal, which fell back to the default modal. Paddle reported the incident resolved and is monitoring for 24 hours. No root cause was given.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 3 · SINGLE · MEDIUM CONFIDENCE
    Paddle Retain payment retries, dunning and past-due cancellations were disrupted for about 30 minutes; the rest of the platform was unaffected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 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 Feb, buyers could not complete AliPay payments at checkout, or attempts returned errors. The cause was not stated in the updates. Paddle re-enabled AliPay for all traffic at 14:32 GMT and confirmed full resolution the next day after monitoring.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 payments failed at checkout for about 80 minutes; other payment methods were not reported as affected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 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's notification system delayed webhooks and buyer emails for about an hour on 11 December 2025, with an average delay of around 20 minutes. The provider did not describe the root cause. No notifications were lost, and all were processed once the issue was resolved.AI-graded
Why this grade
  1. RULES · SEV 1
    Sev 1 from the incident title (no components listed)
  2. CLAUDE · SEV 2 · UNCLEAR · HIGH CONFIDENCE · BACK AFTER 10M
    Webhook and buyer email notifications were delayed by about 20 minutes on average; none were lost and nothing failed outright.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 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 for about 45 minutes on December 5, 2025. The provider said the disruption followed a Cloudflare incident. Services were marked operational at 09:16 UTC and fully resolved at 09:45 UTC. The provider did not list affected components or describe which customer operations failed.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 · BACK AFTER 17M
    Paddle API issues hit some customers for about 45 minutes during a Cloudflare incident; scope and affected services were not specified.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 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 checkouts for customers paying with PayPal were partly impacted during a Cloudflare outage on 18 November 2025. Paddle said only a small number of checkouts were affected. It monitored the issue and marked it resolved about two and a half hours after it started, saying all services were 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
    Checkouts paid via PayPal partly failed during a Cloudflare outage; only a small number of checkouts were affected.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 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 affecting payment recovery, cancellation, reactivation and term optimization. Issues recurred over several hours. Infrastructure was adjusted and a later database load problem from manual jobs was addressed by adding resources. Retain was marked stable again at 20:17 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 (payment recovery, cancellation, reactivation, term optimization) failed or ran slowly for several hours; other Paddle products were not named.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 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 from about 08:00 UTC on 20 October disrupted Paddle. Checkouts initially failed, then stayed up while emails, webhooks and recurring payments were delayed. Support was unreachable. Orders were captured and backlogs were processed. Services were stable by 12:29 UTC, and the incident closed 21 October.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
    An AWS outage stalled checkout completion, customer emails, webhooks and recurring billing for hours; support was also down.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 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 stopped in Paddle production from about 15:22 UTC because of a PayPal outage, so buyers could not pay with PayPal, though other methods still worked. Payments were mostly failing, with brief successes. PayPal recovered 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 customers for about two hours due to a PayPal outage; other payment methods worked.
  3. Claude Haiku 5.5 · prompt v8 · Oct 23, 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

Peers, 90 days

Compare
MailerSendGrade A+100.00% up0 incidentsMTTR –LoopsGrade A+100.00% up1 incidentMTTR 1h 34mKindeGrade A+99.99% up2 incidentsMTTR 1h 12mCloudinaryGrade A99.97% up5 incidentsMTTR 1h 47mPaddleGrade A99.99% up3 incidentsMTTR 47mAblyGrade A99.98% up7 incidentsMTTR 7mMailgunGrade A99.96% up9 incidentsMTTR 42mPusherGrade A99.96% up2 incidentsMTTR 3h 45mResendGrade B99.87% up25 incidentsMTTR 24mInngestGrade B99.75% up14 incidentsMTTR 43mMapboxGrade C99.91% up2 incidentsMTTR 12h 38mClerkGrade C99.92% up10 incidentsMTTR 3h 26mWorkOSGrade C99.49% up21 incidentsMTTR 1h 05mStytchGrade C99.79% up7 incidentsMTTR 57mPlaidGrade F98.16% up18 incidentsMTTR 3h 38mTwilioGrade F96.40% up56 incidentsMTTR 7h 26m

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)