Is Lemon Squeezy down?
Right now
No. Lemon Squeezy is operational.
No incidents reported.
Read from status.lemonsqueezy.com · every 300s
For agents
proceed
Proceed.
GET upbutler.com/status/lemonsqueezy/status.agent.json
MCP: upstream_status {"service":"lemonsqueezy"}
Merchant-of-record checkout, subscriptions and license keys.
What Lemon Squeezy reports
Operational
Taken as is from Lemon Squeezy's own incident feed. Incident titles and component names below are theirs.
Open status.lemonsqueezy.comUpButler's independent probe
There is no keyless endpoint of Lemon Squeezy that says anything useful, so UpButler does not probe it. To check your own Lemon Squeezy account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.
Lemon Squeezy incidents, last 90 days
No finished incidents on record yet. UpButler keeps what Lemon Squeezy publishes for 90 days from the day it starts tracking a service.
Tell your outage from Lemon Squeezy's
Declare that your project depends on Lemon Squeezy. When one of your monitors fails while Lemon Squeezy has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- lemonsqueezycurl -s https://upbutler.com/status/lemonsqueezy/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "lemonsqueezy",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": null
}Questions
- Is Lemon Squeezy down right now?
- No. As of 2026-10-10 05:10 UTC, Lemon Squeezy is operational. This page reads the status again every 5 minutes.
- Where does this status come from?
- From Lemon Squeezy's own incident feed at https://status.lemonsqueezy.com. UpButler reads it once for everyone (not once per visitor) every 300 seconds with conditional requests, and shows it unchanged: incident titles and component names are Lemon Squeezy's words.
- How can my agent or app check Lemon Squeezy status?
- Fetch https://upbutler.com/status/lemonsqueezy/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"lemonsqueezy"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Lemon Squeezy's?
- Add "lemonsqueezy" to the dependencies of your UpButler workspace. When one of your monitors fails while Lemon Squeezy has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in payments and commerce
UpButler is not affiliated with Lemon Squeezy. Status and incident text belong to Lemon Squeezy and are read from their public status source; the probe result is UpButler's own measurement.