Lemon Squeezy status

How we check Lemon Squeezy

We watch api.lemonsqueezy.com/v1/health 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 hit the health endpoint of the versioned API directly rather than guessing at a plain 2xx from the account root, which many modern APIs reject for an unauthenticated caller even while completely healthy.

What is Lemon Squeezy?

Lemon Squeezy is a merchant-of-record platform aimed squarely at indie software makers and small SaaS teams: rather than integrating a payment processor directly and handling sales tax and VAT compliance across every country a customer might buy from, a seller routes checkout through Lemon Squeezy, which becomes the legal seller on the transaction and takes that compliance burden off the seller's plate entirely. It became a particularly common choice for solo developers and small teams shipping their first paid product, in part because it was designed from the start for that audience rather than adapted from an enterprise product.

Because Lemon Squeezy sits between a customer and the actual purchase, its outages look different from most infrastructure failures. A seller's marketing site, documentation, and everything else about their product keeps working normally, only the moment someone tries to actually pay breaks. That makes an outage here easy to miss without direct monitoring, since nothing about the seller's own server logs or uptime checks would show anything unusual, the failure lives entirely inside a checkout widget served from Lemon Squeezy's own infrastructure.

For a small, often solo-run business, the practical cost of missing an outage quickly is proportionally larger than it would be for a company with a dedicated support team watching for exactly this pattern. A few hours of failed checkouts can be a meaningful fraction of a day's revenue for a smaller product, and the first sign is often a confused email from a customer rather than any internal alert.

Because Lemon Squeezy also owns the subscription billing lifecycle for plans sold through it, a longer outage can push some renewal attempts later than a seller's own churn or dunning tooling expects. If the board above shows Lemon Squeezy healthy and a customer still cannot check out, the more likely cause is a misconfigured product or price on the seller's own side rather than a platform-level incident.

Frequently asked questions

Is Lemon Squeezy 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 Lemon Squeezy goes down?

Like Paddle, Lemon Squeezy is a merchant of record, so it is the entire sale, tax handling included, that stalls rather than only a payment step. A customer trying to buy sees the checkout fail to load or fail partway through, and no purchase completes until the platform recovers.

Does an outage affect existing subscriptions?

Not usually right away. Renewals are processed on Lemon Squeezy's own schedule, and a short outage typically delays that processing rather than skipping a charge. Worth checking your dashboard for any renewal attempts that landed later than expected after a longer incident.

Is this the same thing as Lemon Squeezy's own status page?

No. Theirs reflects incidents their own team has confirmed and posted. Ours is measured independently from outside their infrastructure on a fixed schedule, regardless of whether an official update exists yet.