Where does this status come from?

From Paddle's own status page API at https://paddlestatus.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Paddle's words.

How can my agent or app check Paddle status?

Fetch https://upbutler.com/status/paddle/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":"paddle"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Paddle's?

Add "paddle" to the dependencies of your UpButler workspace. When one of your monitors fails while Paddle 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.

Is Paddle down?

Right now

No. Paddle is operational.

No incidents reported.

Read from paddlestatus.com 3 s ago · every 120s

For agents

proceed

Proceed.

GET upbutler.com/status/paddle/status.agent.json

MCP: upstream_status {"service":"paddle"}

Merchant-of-record billing: checkout, subscriptions and webhooks.

What Paddle reports

Operational

Taken as is from Paddle's own status page API. Incident titles and component names below are theirs.

Open paddlestatus.com

UpButler's independent probe

There is no keyless endpoint of Paddle that says anything useful, so UpButler does not probe it. To check your own Paddle account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Open at Paddle

Scheduled Retain & Profitwell Metrics Database Maintenancescheduled maintenance
Starts 2026-09-29 15:27 UTC
We will be performing scheduled maintenance on the databases that support Retain and ProfitWell Metrics on Wednesday, October 14th, 2026, starting at 07:00 UTC. The maintenance is expected to be completed by 10:00 UTC. During this maintenance window, some services may experience brief interruptions or degraded performance. Retain and ProfitWell Metrics may be briefly unavailable, and new data may take longer than usual to appear. Checkout, payment processing and other Paddle services are not af…
Scheduled Maintenencescheduled maintenance
Starts 2026-09-21 08:57 UTC
We will be performing scheduled maintenance on the database that supports payment processing on Monday, October 5th, 2026, starting at 07:00 UTC. The maintenance is expected to be completed by 08:00 UTC. During this maintenance window, some services may experience brief interruptions or degraded performance. Payments taken through Checkout, subscription renewals, refunds and payment method updates may fail for a short period and can be retried. Webhooks for payment events may be delayed and wil…

Text written by Paddle, shown unchanged.

Paddle components

25 operational

Production - BillingOperational
Production - ClassicOperational
Sandbox - BillingOperational
Sandbox - ClassicOperational
Production - BillingOperational
Production - ClassicOperational
Sandbox - BillingOperational
Sandbox - ClassicOperational
Production - BillingOperational
Production - ClassicOperational
Sandbox - BillingOperational
Sandbox - ClassicOperational
Production - BillingOperational
Production - ClassicOperational
Sandbox - BillingOperational
Sandbox - ClassicOperational
Production - BillingOperational
Production - ClassicOperational
Sandbox - BillingOperational
Sandbox - ClassicOperational
Production - BillingOperational
Production - ClassicOperational
Sandbox - BillingOperational
Sandbox - ClassicOperational
Production - BillingOperational

Paddle incidents, last 90 days

No finished incidents on record yet since 2026-10-10. UpButler keeps what Paddle publishes for 90 days from the day it starts tracking a service.

Tell your outage from Paddle's

Declare that your project depends on Paddle. When one of your monitors fails while Paddle 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.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - paddle

Ask before you retry

curl -s https://upbutler.com/status/paddle/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "paddle",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Paddle down right now?: No. As of 2026-10-10 05:12 UTC, Paddle is operational. This page reads the status again every 2 minutes.
Where does this status come from?: From Paddle's own status page API at https://paddlestatus.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are Paddle's words.
How can my agent or app check Paddle status?: Fetch https://upbutler.com/status/paddle/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":"paddle"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Paddle's?: Add "paddle" to the dependencies of your UpButler workspace. When one of your monitors fails while Paddle 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 Paddle. Status and incident text belong to Paddle and are read from their public status source; the probe result is UpButler's own measurement.