Is Polar down?
For agents
proceed
Proceed.
GET upbutler.com/status/polar/status.agent.json
MCP: upstream_status {"service":"polar"}
Merchant-of-record billing for developers: checkout, subscriptions, usage billing and webhooks.
What Polar reports
Operational
Taken as is from Polar's own status page API. Incident titles and component names below are theirs.
Open status.polar.shUpButler's independent probe
API edge is answeringHTTP 401 · 235 ms
One request without credentials to api.polar.sh every two minutes. An answer (the expected "not authenticated") shows the edge, TLS and routing work. It does not prove that authenticated calls succeed.
Checked · up since 2026-10-10 01:23 UTC
Polar components
12 operational
Production
- DashboardOperational
- APIOperational
- CheckoutOperational
- WorkersOperational
- WebhooksOperational
- DocsOperational
Sandbox
- DashboardOperational
- APIOperational
- Checkout PageOperational
- WorkersOperational
- WebhooksOperational
- DocsOperational
Polar incidents, last 90 days
No finished incidents on record yet. UpButler keeps what Polar publishes for 90 days from the day it starts tracking a service.
Tell your outage from Polar's
Declare that your project depends on Polar. When one of your monitors fails while Polar 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:
- polarcurl -s https://upbutler.com/status/polar/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "polar",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": {
"state": "up",
"statusCode": 401
}
}Questions
- Is Polar down right now?
- No. As of 2026-10-10 05:11 UTC, Polar is operational. This page reads the status again every 5 minutes.
- Where does this status come from?
- From Polar's own status page API at https://status.polar.sh. 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 Polar's words.
- What does UpButler's own Polar check prove?
- Every two minutes UpButler sends one request without credentials to the Polar API edge (api.polar.sh). Any answer from the edge, usually HTTP 401, shows that DNS, TLS and routing work. It does not prove that authenticated requests succeed, so it can say "reachable" while Polar reports degraded service. It is useful the other way round: when the probe fails before their status page changes.
- How can my agent or app check Polar status?
- Fetch https://upbutler.com/status/polar/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":"polar"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or Polar's?
- Add "polar" to the dependencies of your UpButler workspace. When one of your monitors fails while Polar 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 Polar. Status and incident text belong to Polar and are read from their public status source; the probe result is UpButler's own measurement.