Skip to main content
Paddle logo

Is Paddle Down?

No — Paddle is up

Reachable from all 8 checked regions

Average response time: 450ms

Last checked · checks run every 6 hours

Official status page: https://paddlestatus.com

Paddle uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
454ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 55 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

55-day clean streak
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 31 checks
Sep 30: 100.00% uptime, 28 checks
Oct 1: 100.00% uptime, 30 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ams
240ms
DNS 135ms TCP 8ms TLS 22ms TTFB 186ms
lhr
108ms
DNS 39ms TCP 2ms TLS 15ms TTFB 70ms
nrt
404ms
DNS 357ms TCP 2ms TLS 12ms TTFB 380ms
ord
226ms
DNS 106ms TCP 11ms TLS 17ms TTFB 156ms
sin
89ms
DNS 56ms TCP 1ms TLS 9ms TTFB 74ms
sjc
178ms
DNS 142ms TCP 2ms TLS 10ms TTFB 162ms
syd
2130ms
DNS 195ms TCP 1ms TLS 9ms TTFB 800ms
yyz
227ms
DNS 102ms TCP 11ms TLS 26ms TTFB 164ms

What Paddle does

Paddle is a payments and billing platform for software and app businesses that acts as merchant of record, handling checkout, subscriptions, sales tax and compliance on the seller's behalf. Its own site names n8n, Letterboxd and AdGuard among the businesses it powers. Sellers depend on it to collect revenue rather than to serve their product to customers.

What an outage looks like

Checkout fails or will not open, so purchases stop while the product itself keeps running. Subscription renewals do not process, which surfaces later as billing gaps rather than as an error anyone sees at the time. Webhooks stop arriving, so entitlements and license keys are not granted after a payment succeeds. The seller dashboard is unavailable or reports stale figures.

What to do about it

paddlestatus.com separates Checkout and Hosted Checkout from the Paddle API, Order Processing, Subscription Processing, Webhooks and Alerts, License Delivery and Outbound Email, which is enough detail to tell a payment failure from a fulfilment one. If Webhooks and Alerts is the affected component, payments may be succeeding while access is not granted, so reconcile orders against entitlements once it clears.

Is it down for everyone, or just you?

If this page says Paddle is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Paddle outage FAQ

A customer paid but did not get access. Was the payment taken?
Check the Webhooks and Alerts component before issuing a refund. Paddle tracks payment processing and webhook delivery separately, so a charge can complete while the notification that grants access never arrives. Look the order up in the Paddle dashboard directly rather than relying on your own records, which are built from the webhooks that did not arrive.
Will failed subscription renewals retry?
A renewal that could not be attempted during an incident is not the same as one that was declined. Rather than re-charging customers yourself, wait for the Subscription Processing component to recover, then check which renewals are still outstanding and let your account's dunning settings handle them. Manual retries are how someone gets charged twice for one period.
Does a Paddle outage stop my software from working?
Only if your product checks a license with Paddle on every run. Paddle sits in the purchase and renewal path rather than in the path of your application serving its users, so existing customers normally keep working. If you do validate licenses online, an offline grace period is what stops a Paddle incident becoming an outage of your own.
Checkout is failing. Should I tell customers to retry?
Not immediately. Repeated attempts against a degraded checkout can leave duplicate authorisations that take days to fall off a customer's card. Post a short notice instead, point at paddlestatus.com, and invite buyers back once Checkout is listed as operational. Customers who see an honest status message are far less likely to raise a chargeback.
Can I still see my revenue figures during an incident?
Possibly not. Paddle lists the Seller Dashboard as its own component, so reporting can be unavailable or stale while payments themselves process normally. A flat revenue chart during an incident is not evidence that sales stopped. Wait for the dashboard component to recover before drawing any conclusion about the day's numbers.

How we measure this

  • We request Paddle's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Paddle publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Paddle goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required