Is Recharge Down?

No — Recharge is up

Recharge's status page: Operational · no open incidents
FlareWarden checks: Website reachable · 8 of 8 regions · 145 ms

Right now

The verdict is the worse of these two. How we decide

Recharge's status page

status.getrecharge.com · read 3 minutes ago · checked every 3 minutes

Operational

Recharge's components, as its status page reports them
Component	Status
Shopify Admin	Operational
Shopify API & Mobile	Operational
Shopify Storefront	Operational
Shopify Third party services	Operational
Recharge Analytics	Operational
Recharge API	Operational
Recharge Charge Processing	Operational
Recharge Checkout	Operational
Recharge Customer Portal	Operational
Recharge Merchant Portal	Operational
Recharge Webhooks	Operational
BigCommerce	Operational

1 more, all operational · show all 13

All of Recharge's components
Component	Status
Shopify
Shopify Admin	Operational
Shopify API & Mobile	Operational
Shopify Storefront	Operational
Shopify Third party services	Operational
Recharge Platform
Recharge Analytics	Operational
Recharge API	Operational
Recharge Charge Processing	Operational
Recharge Checkout	Operational
Recharge Customer Portal	Operational
Recharge Merchant Portal	Operational
Recharge Webhooks	Operational
BigCommerce
BigCommerce	Operational
Recharge Support
In-App Support	Operational

Open their status page

FlareWarden checks

getrecharge.com from 8 regions · when you open this page (at most every 30 minutes), otherwise every 6 hours

Reachable

Regions up: 8 of 8
Response: 145 ms
Checked: 5 hours ago

By region

Chicago reachable, 167 ms
London reachable, 102 ms
Los Angeles reachable, 220 ms
San Jose reachable, 218 ms
Singapore reachable, 133 ms
Sydney reachable, 52 ms
Tokyo reachable, 118 ms
Toronto reachable, 155 ms

Timing by region

Connection timing for each region that loaded the page
Region	DNS	TCP	TLS	TTFB
Chicago	136 ms	2 ms	9 ms	163 ms
London	65 ms	2 ms	8 ms	97 ms
Los Angeles	181 ms	1 ms	10 ms	215 ms
San Jose	186 ms	1 ms	7 ms	214 ms
Singapore	86 ms	4 ms	9 ms	128 ms
Sydney	20 ms	1 ms	8 ms	49 ms
Tokyo	75 ms	1 ms	8 ms	115 ms
Toronto	126 ms	2 ms	7 ms	151 ms

We check that getrecharge.com loads, not every feature behind it. Test it yourself

History

Incidents Recharge reported

Since Oct 22, 4 days · from status.getrecharge.com

Incidents: 0
Major or critical: 0
Median to resolve: —

No incidents reported in this window.

Recharge website availability

Measured by FlareWarden · getrecharge.com

Last 7 days: 100%
Last 30 days: 100%
Last 90 days: 100%
Avg response, 30 days: 207ms

Last 30 days

33-day clean streak

Sep 26 Today

No downtime Partial Downtime Not measurable No data

Measured by FlareWarden's own checks of getrecharge.com from multiple regions every 6 hours. Recharge's status page sets the verdict above when it reports trouble, but never these figures. Percentages count only checks that returned an availability answer — 33 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

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. When you open this page and our last check is more than 30 minutes old, we check again on the spot; those checks update the verdict, never the availability figures.
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. Our checks only change their 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, and the verdict is the worse of what it reports and what our checks see: a major outage of Recharge itself is Down, trouble with one part of it is Degraded, problems at a few of a provider's many locations change nothing, and a security notice that marks nothing down is shown but changes nothing either. We check the feed every 3 minutes and read it again within minutes of any change to its incidents or components; a reading counts for 45 minutes after the last check that found nothing changed. The availability figures above are our measurement alone.

Get alerted when Recharge goes down

We check Recharge every 6 hours, and again when you open this page if that was more than 30 minutes ago. 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