On this page
Is Recharge Down? How to Tell and What to Do
Recharge is a subscription management platform used by direct-to-consumer brands on Shopify to power recurring billing, subscription boxes, and membership programs. When it goes down, subscription renewals fail silently, checkout doesn't work for new subscribers, and merchants lose recurring revenue with no visibility into what went wrong.
Statusfield brings reported Recharge incidents into the same workspace as your other monitors. Select supported components and route relevant changes to your team. Vendor reports can lag an incident, so check your own application as well.
Follow Recharge incidents with your team
Statusfield brings reported status for Recharge together with your other critical tools. Choose the changes that should alert your team. Eligible new accounts can start a free trial — no credit card required.
Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.
Common Signs of a Recharge Outage
| Symptom | What's likely happening |
|---|---|
| Subscriptions not renewing on schedule | Recharge's billing engine is degraded |
| Checkout widget not loading on Shopify | Recharge's checkout infrastructure is down |
| New subscriptions failing at payment | Payment processing integration is degraded |
| Subscription portal inaccessible to customers | Customer portal infrastructure is failing |
| Webhooks not firing for order events | Recharge's webhook delivery system is degraded |
| Merchant dashboard not loading | Recharge's web app or API is down |
| Bulk actions (pause, cancel, skip) failing | Subscription management API is degraded |
How to Confirm It's Recharge, Not Your Setup
1. Test the Recharge API directly
curl -s -o /dev/null -w "%{http_code}" \
-H "X-Recharge-Access-Token: YOUR_API_KEY" \
https://api.rechargeapps.com/subscriptions?limit=1A 5xx response or connection failure means Recharge's API is down. A 401 means the API is up but your token is invalid — check your API key, not the outage status.
2. Check a subscription's portal link
Send yourself a customer portal magic link and test whether it loads. If the portal is completely unreachable, the customer-facing infrastructure is down, not just the merchant dashboard.
3. Manually trigger a renewal attempt
From the Recharge merchant dashboard, attempt a manual charge on a test subscription. If it fails immediately with a system error (not a payment method error), Recharge's billing engine is degraded.
4. Check Shopify for checkout errors
Place a test subscription order in your Shopify store. If the Recharge checkout widget doesn't load or the order fails after payment, the Shopify integration or Recharge checkout layer is down.
The Problem With Silent Subscription Failures
Recharge outages are uniquely damaging because subscription failures are often invisible until the end of the billing cycle. Renewals that should have processed during the outage window are marked as failed, triggering dunning sequences — which can cause customers to cancel rather than update their payment method.
Recharge's own status page may not reflect degradations that affect specific merchant segments, payment processors, or geographic regions.
Follow reported status for Recharge with Statusfield. Choose the supported components you use and route detected changes to your team. Vendor reports may lag an incident. Track Recharge's live status at statusfield.com/services/recharge.
Follow Recharge incidents with your team
Follow reported incidents for Recharge in Statusfield and send relevant updates to your configured channels. Eligible new accounts can start a free trial — no credit card required.
Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.
What to Do During a Recharge Outage
Immediate (first 5 minutes)
- Confirm via API call — use a direct API call to confirm the issue is platform-wide, not isolated to a single subscription or payment method.
- Pause dunning emails — if subscriptions are failing due to a Recharge outage (not customer payment issues), halt any automated dunning or churn-prevention emails. Sending them during an outage will trigger unnecessary cancellations.
- Check renewal queue — identify which subscriptions were scheduled to renew during the outage window. These will need manual review after recovery.
- Freeze bulk actions — don't run bulk pauses, cancels, or skips during an outage. Failed bulk operations can leave subscriptions in inconsistent states.
Communication
- If the checkout widget is down, add a notice to your Shopify store (site announcement bar or popup): "Subscriptions are temporarily unavailable — check back shortly."
- For high-volume merchants, proactively contact VIP subscribers whose renewals were in the outage window before they see a failed payment notification.
- If you have a Slack or Discord community, post a brief update before customers start asking.
Recovery
- After Recharge recovers, identify all subscriptions that failed to renew during the outage window and trigger manual charges before the dunning sequence fires.
- Review your webhook logs for events that may have been lost during the outage — order fulfillment hooks may need to be re-triggered.
- Check that the Shopify checkout widget is loading correctly before removing any site notices.
Recharge Components and What Each Outage Looks Like
| Component | Impact when degraded |
|---|---|
| Billing engine | Scheduled renewals fail; recurring revenue stops |
| Checkout / Shopify integration | New subscribers can't complete checkout |
| Customer portal | Customers can't manage their subscriptions |
| API | Third-party integrations and automations break |
| Webhook delivery | Order events and subscription updates don't fire |
| Merchant dashboard | Can't view or manage subscriptions |
| Dunning / payment retry | Failed payment recovery sequences don't run |
Billing engine failures are highest-severity — they directly stop recurring revenue. Checkout failures block new acquisition. Both require immediate action.
Bring Recharge updates to your team
Follow reported Recharge status in Statusfield and choose which changes reach your configured alert destinations. Delivery depends on source updates, polling and successful processing. Check the catalog for supported components and the pricing page for channel availability.
Start your monitoring trial — view plans. Eligible first-time customers can start a free trial. Continued monitoring requires a paid plan.
Follow Recharge incidents with your team
Follow Recharge and your other vendors in one Statusfield workspace. Select supported components and route the updates your team needs. Eligible new accounts can start a free trial — no credit card required.
Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.
FAQ
Is Recharge down right now?
This article is a troubleshooting guide, not a live outage verdict. Check the Statusfield catalog and the official vendor status page for the latest reported status, affected components and observation times. Compare those reports with what your own application is experiencing.
How can I get alerts about Recharge incidents?
Follow reported Recharge status in Statusfield and choose which changes reach your configured alert destinations. Delivery depends on source updates, polling and successful processing. Check the catalog for supported components and the pricing page for channel availability.
Does an operational Recharge status mean my application is working?
No. A vendor status page describes reported service conditions. Your account, integration, network or application can still fail. Check your own public HTTPS endpoint and use logs or workflow tests to investigate the customer experience.
Browse the service catalog and plans and alert destinations.
Keep your vendors in view.
Choose from 7,000+ services, follow the components you use, and configure alerts for your team.
Try any paid plan for 30 days, no credit card required. Free trial for first-time customers.