Is Recharge Down?

No — Recharge is up

Reachable from all 8 checked regions

Average response time: 273ms

Last checked 3 hours ago · checks run every 6 hours

Official status page: https://status.getrecharge.com

Recharge uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

217ms

Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 19 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

19-day clean streak

Sep 13 Today

No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

gru

365ms

DNS 314ms TCP 2ms TLS 9ms TTFB 347ms

iad

167ms

DNS 116ms TCP 1ms TLS 9ms TTFB 150ms

jnb

729ms

DNS 197ms TCP 0ms TLS 8ms TTFB 498ms

lax

191ms

DNS 135ms TCP 2ms TLS 9ms TTFB 168ms

lhr

138ms

DNS 69ms TCP 2ms TLS 15ms TTFB 121ms

nrt

158ms

DNS 44ms TCP 1ms TLS 8ms TTFB 147ms

ord

206ms

DNS 155ms TCP 2ms TLS 9ms TTFB 190ms

sin

234ms

DNS 195ms TCP 1ms TLS 8ms TTFB 223ms

What Recharge does

Recharge runs recurring orders for online stores, mostly on Shopify and BigCommerce. It charges subscribers on schedule, creates the resulting orders in the store, and gives shoppers a portal to skip, swap or cancel. For subscription brands it is the system that turns next month's revenue into actual orders, so an incident lands directly on cash flow and fulfilment.

What an outage looks like

Scheduled charges do not run, or run late in a batch. Orders that should appear in Shopify after a successful charge are missing. Subscribers cannot open the customer portal to skip or cancel, and contact support instead. The merchant portal loads slowly or not at all. Webhooks to connected apps stop arriving, so downstream fulfilment and analytics fall out of step.

What to do about it

Check status.getrecharge.com, which reports Charge Processing, Checkout, Customer Portal, Merchant Portal, API, Webhooks and Analytics separately, alongside Shopify and BigCommerce rows. If the Shopify row is degraded, the cause may be the store platform rather than Recharge. Do not manually re-process charges in bulk until Charge Processing recovers, or subscribers can be billed twice.

Is it down for everyone, or just you?

If this page says Recharge is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Recharge outage FAQ

Will Recharge retry charges that failed during an outage?

Recharge retries failed charges on its own. Its support documentation says a failed charge is retried the next day and that retry timing adjusts to the error type. Charges that were never attempted because of an incident are a different case, so after recovery check the upcoming and errored order lists before assuming everything will catch up without intervention.

Is it Recharge or Shopify that is down?

The Recharge status page tracks Shopify Admin, Storefront, API and third-party services as their own rows, so check both groups. If Shopify is degraded, orders Recharge creates can fail to post even though the charge succeeded. If only Recharge Platform rows are affected, the store itself keeps selling one-time products normally.

Why can my customers not cancel their subscription?

The Customer Portal is a separate component, so it can fail while charges run normally. That is the uncomfortable case: a subscriber who could not cancel may still be billed. Publish a support address somewhere visible and handle cancellation requests manually after recovery, dated to when the customer first tried.

Are webhooks lost during a Recharge incident?

Treat them as possibly missed. Webhooks is its own row on the status page, and an incident there means connected apps may not hear about charges, cancellations or new subscriptions. After recovery, reconcile fulfilment and analytics tools against the Recharge merchant portal rather than trusting the event history they received.

Does a Recharge outage stop one-time purchases?

Not usually. One-time products check out through the store's own checkout, which does not depend on Recharge. Subscription sign-ups can still be affected, because the Recharge Checkout component is reported separately and handles the subscription option at purchase time, so a shopper choosing subscribe-and-save can hit an error.

How we measure this

We request Recharge's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
Response times average only the regions that actually served the page, so a timeout never inflates the number.
Where Recharge publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Recharge goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring

Free plan available No credit card required