Paddle status

How we check Paddle

We watch cdn.paddle.com from all five of our probe regions, every 2 minutes. A region that sees a failure does not make this page say "down" on its own: a second region has to agree first, the same confirmation rule every YoPingMe monitor uses.

We watch the real static asset Paddle's own checkout overlay loads from its CDN, rather than an API root that would answer an anonymous request with a 401 on a perfectly normal day and mislead a monitor that expected a plain 2xx into calling it downtime.

What is Paddle?

Paddle is a merchant-of-record payments platform: rather than a business handling its own card processing, tax calculation, and compliance directly, Paddle sits in as the legal seller of record for every transaction, collects the payment, remits the applicable sales tax and VAT across jurisdictions, and pays the underlying business the net amount. For a software business selling internationally, that removes an enormous amount of tax and compliance work that a direct payment processor alone does not handle.

That merchant-of-record role is what makes a Paddle outage distinct from an ordinary payment processor going down. When checkout fails, it is not just one integration failing, it is the entire sale, including the parts Paddle handles on the seller's behalf, that has not happened yet. A business relying on Paddle sees the same symptom any payment outage produces: pricing pages and marketing still load fine, but the actual checkout overlay either never opens or opens and fails partway through without ever completing.

Because Paddle also owns the subscription lifecycle for the plans it processes, an outage can ripple slightly past the moment of failure. A renewal attempt that would normally happen automatically during an incident may need to retry once the platform recovers, and a business running its own dunning or reminder emails off subscription state should expect that state to lag briefly behind reality until Paddle's own processing catches up.

Paddle's checkout overlay is the part worth watching most closely if you are debugging a reported failure, since it is what a paying customer actually interacts with. If the board above shows Paddle healthy and a customer still cannot complete a purchase, the more likely explanation is a configuration issue on the seller's own product or price setup rather than a Paddle-side incident.

Frequently asked questions

Is Paddle down right now?

Check the board above; it reflects our own probes, refreshed every couple of minutes from all five of our regions.

What happens to my checkout if Paddle goes down?

Paddle's checkout overlay, the widget a customer sees when they go to pay, either fails to load or fails partway through, which stops a purchase completely for the duration. Because Paddle is the merchant of record for sellers who use it, this is more than a payment processor going down, it is the entire sale transaction stalling.

Does a Paddle outage affect subscriptions that are already active?

Not usually right away. Existing subscriptions are billed on a schedule Paddle processes internally, and a short outage typically delays that processing rather than skipping a renewal outright. A longer outage can push some renewal attempts later than expected, worth checking in the Paddle dashboard after any extended incident.

How is this different from Paddle's own status page?

Theirs reflects incidents Paddle's own team has confirmed and posted. Ours reflects what we measure independently from outside their infrastructure, on a fixed schedule regardless of whether an official update has gone up yet.