Recurly has been highly reliable recently: StatusBird's independent monitoring recorded 100.0% availability and zero major incidents over the last 90 days.
Numbers alone do not tell you whether to worry, so this post also covers what actually breaks when Recurly has problems and how to get warned early.
What is Recurly?
Recurly is a subscription billing and revenue management platform used by subscription businesses to handle recurring payments, plan management, dunning (failed payment retries), invoicing, and revenue reporting. It sits between the merchant's product and payment gateways like Stripe, Braintree, or Adyen, orchestrating when and how much each subscriber is charged. E-commerce and digital subscription companies use it for its billing flexibility, trial handling, and churn-reduction tooling.
Recurly uptime and outage history
| Metric (90 days, as of July 2026) | Value |
|---|---|
| Availability | 100.0% |
| Reliability grade | A+ |
| Major incidents | 0 |
| Total major-outage downtime | 0 minutes |
| Average incident duration | n/a |
| Most recent major incident | None in the last 90 days |
| Checks in window | 43,522 |
Among the 4 subscription billing services StatusBird monitors, Recurly ranks number 3 for 90-day availability. See the full ranking of subscription billing tools by reliability.
What happens to your store when Recurly goes down?
When Recurly goes down, new subscription signups fail because the hosted payment pages or Recurly.js checkout tokenization stop working, and scheduled renewal billing can be delayed. Webhooks that tell your systems about successful renewals, cancellations, and failed payments stop arriving, so downstream provisioning and fulfillment can drift out of sync with billing reality. Dunning retries pause as well. Existing subscriber access is usually unaffected in the short term; the immediate revenue hit is blocked new signups.
Typical symptoms during a Recurly outage:
- Checkout or signup forms using Recurly.js fail to tokenize cards
- Hosted payment and account management pages return errors
- Expected renewal invoices and charges do not appear on schedule
- Recurly webhooks stop arriving at your endpoints
- The Recurly admin console is slow or unreachable
If you are in the middle of an incident right now, see what to do when Recurly goes down for a step-by-step playbook.
Frequently asked questions
Renewals due today have not billed because Recurly is down. Is that revenue gone?
No. Recurly processes billing that was delayed by an incident once service is restored, so renewals typically bill late rather than never. Reconcile invoice counts against your subscriber base after recovery and raise any stragglers with Recurly support.
My app depends on Recurly webhooks. How do I recover the events I missed?
Recurly retries failed webhook deliveries automatically for a period, and you can also resend notifications from the admin console or reconcile by querying the API for recent transactions and subscription changes. After recovery, run a reconciliation pass rather than trusting that every retry landed.
How this data is measured
StatusBird checks Recurly's status every 2 minutes, around the clock, independently of the vendor. The availability figure counts major and critical outages only; minor degradation is excluded so numbers are not skewed by vendors that report small blips near-continuously. Grades run from A+ to F. See the live numbers on the Recurly reliability page and current status on the Recurly status page, or browse all 84 service grades.
Know before your customers do
StatusBird monitors Recurly and 83 other services online stores depend on, plus your own storefront, every 2 minutes. When something goes down you get an SMS, email, or Slack alert with plain-English context, usually before the official status page catches up. Start monitoring free, no card required for the free plan.