We started checking Paddle on November 2, 2026, which is 7 days ago. Everything below covers that period, not the full 90 days a longer-tracked service would show.
Email me when Paddle reports an incident on its status page, and again when it reports it resolved.
01
The last 24 hours
What happened most recently, on one time axis: our own probe readings by surface, how many people reported a problem, and what Paddle's own status page declared. Below it, any public chatter we saw about Paddle and the extra probe it triggered.
The last 24 hours on one axis: what our probes read for each surface we check, how many people reported a problem, and what Paddle's own status page declared. Three records side by side; none of them changes another.
Our probes, web
Our probes, api (primary)
Unverified user reportsNo reports about Paddle in the last 24 hours, which is not evidence that nothing is wrong.
Paddle's status pageNo incident declared in the last 24 hours.
24h ago18h ago12h ago6h agonow
Each check cell is the worst reading across every region in that quarter hour: one region that did not answer colours the cell, never an average. An amber cell is a reading that answered, but at three times or more its 7-day median for three checks running: slow is not down, and we say which. A filtered reading stays neutral, because a refused check is not a failed check. Report bars count reports as submitted; we do not check who sent them, and they never change our reading. The status-page lane is Paddle's own declaration, shown as they made it.
Third-party chatter, labeled
Public posts from the last hour that mention Paddle next to an outage word (“down”, “outage”, “not working”). This is what other people said in public, collected by keyword: not something we measured, and not the user reports above. It never affects the verdict.
No matching public posts in the last hour from the sources we watch.
02
Checks passing by region
Checks passing is the checks that passed, divided by every check we attempted, per region. Not interpolated, not smoothed, and never computed for a region with zero recorded samples.
Region
Checks passing
Probes recorded
US-East
0.00%
730
US-West
0.00%
578
Europe
0.00%
528
Asia-Pacific
0.00%
319
Their declared record
Paddle's own incident history, taken from their public status feed. This is their account of what happened, not our check reading.
Issue affecting metrics and reporting in the seller dashboardMinor incident
Oct 21, 2026, 8:04 PM UTC to Oct 22, 2026, 12:09 AM UTC (4h 5m)resolved
their latest update (Oct 22, 2026, 12:09 AM UTC): 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 [seller…
Report downloads unavailable in the Paddle DashboardMinor incident
Sep 2, 2026, 8:31 PM UTC to Sep 2, 2026, 9:04 PM UTC (33 min)resolved
their latest update (Sep 2, 2026, 9:04 PM UTC): The incident affecting report downloads in the Paddle Dashboard has been fully resolved. Our engineers deployed a fix, and the generated reports can now be downloaded as expected.
We apologize for any disruption this may have caused. If you have any questions or concerns, please…
RetainPartial outage
Aug 24, 2026, 8:35 AM UTC to Aug 24, 2026, 9:22 AM UTC (47 min)resolved
their latest update (Aug 24, 2026, 9:22 AM UTC): The incident affecting Retain has been fully resolved. All services are now operating normally.
We apologize for any disruption this may have caused. If you have any questions or concerns, please contact our Customer Support team at sellers@paddle.com.
Seller dashboard logins are failing with timeoutsMinor incident
Jul 16, 2026, 8:00 AM UTC to Jul 16, 2026, 8:24 AM UTC (24 min)resolved
their latest update (Jul 16, 2026, 8:24 AM UTC): The incident affecting access to the Paddle seller dashboard sign-in has been fully resolved. All services are now operating normally.
We are closely monitoring the platform to ensure continued stability. We apologize for any disruption this may have caused.
If you have any que…
Jun 25, 2026, 1:07 AM UTC to Jun 25, 2026, 5:16 AM UTC (4h 9m)resolved
their latest update (Jun 25, 2026, 5:16 AM UTC): The incident affecting Checkouts has been fully resolved. All services are now operating normally.
We apologize for any disruption this may have caused. If you have any questions or concerns, please contact our Customer Support team at sellers@paddle.com.
Partial Checkout OutageMinor incident
Jun 18, 2026, 3:18 PM UTC to Jun 18, 2026, 4:15 PM UTC (57 min)resolved
their latest update (Jun 18, 2026, 4:15 PM UTC): The issue affecting checkouts has been resolved. The third-party provider has restored their services, and we have removed the temporary mitigations. All systems are now operating normally, and checkouts are processing as expected.
We apologize for any disruption this may have c…
Card payment issues on Paddle Billing and Paddle Classic checkoutMinor incident
Jun 1, 2026, 8:38 AM UTC to Jun 1, 2026, 8:59 AM UTC (21 min)resolved
their latest update (Jun 1, 2026, 10:23 AM UTC): The issue has now been resolved, and our team is monitoring the situation to ensure normal service continues.
We apologize for any disruption this may have caused. If you have any questions or concerns, please reach out to us at [sellers@paddle.com](mailto:sellers@paddle.com "se…
New Sellers might be unable to access Retain settings and the ProfitWell Metrics dashboardPartial outage
Apr 28, 2026, 3:36 PM UTC to Apr 30, 2026, 2:07 PM UTC (1d 22h)resolved
their latest update (Apr 30, 2026, 2:07 PM UTC): The incident affecting Retain settings and Metrics in the dashboard has been fully resolved. All services are now operating normally.
We apologize for any disruption this may have caused. If you have any questions or concerns, please contact our Customer Support team at sell…
Discount service degradation causing discount application failuresMinor incident
Apr 21, 2026, 2:02 PM UTC to Apr 21, 2026, 2:11 PM UTC (9 min)resolved
their latest update (Apr 21, 2026, 2:11 PM UTC): We are pleased to confirm that this issue has been resolved, and normal service has now been fully restored.
Our team will continue to monitor the situation closely over the next 24 hours to ensure ongoing stability.
We sincerely apologize for any disruption this may have cause…
Webhook & Email DeliveryMinor incident
Apr 21, 2026, 11:00 AM UTC to Apr 21, 2026, 2:22 PM UTC (3h 22m)resolved
their latest update (Apr 21, 2026, 2:22 PM UTC): The underlying issue affecting Email, Webhooks & Alerts has been resolved. The service became fully operational again, processing new webhooks and outbound emails at 12:07 BST, and all delayed webhooks and outbound emails were successfully reprocessed by 12:12 BST.
Our teams will…
Showing the 10 most recent of 25 incidents Paddle has declared in the history we hold.
These entries are Paddle's own declarations, taken from their public status feed, shown separately from our own check readings. Their page publishes what they choose to publish: an incident missing here means they did not declare one, not that nothing happened, and an incident here is their account, not our measurement. Neither record ever changes the other.
Paddle's own status feed works, so its declared incidents are the record and our probe events are not listed or counted. Our check results by region are above, as a reading beside the statement.
Full detail on what a probe does and does not prove is in the methodology page.