Is Recurly Down?

No — Recurly is up

Reachable from all 8 checked regions

Average response time: 473ms

Last checked 3 hours ago · checks run every 6 hours

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

Recurly uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

717ms

Avg response, 30 days

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

30-day history

65-day clean streak

Sep 12 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.

ams

420ms

DNS 20ms TCP 5ms TLS 9ms TTFB 414ms

arn

202ms

DNS 33ms TCP 6ms TLS 21ms TTFB 192ms

cdg

244ms

DNS 114ms TCP 2ms TLS 9ms TTFB 232ms

ord

189ms

DNS 52ms TCP 20ms TLS 24ms TTFB 165ms

sin

1089ms

DNS 150ms TCP 2ms TLS 5ms TTFB 1083ms

sjc

377ms

DNS 237ms TCP 9ms TLS 19ms TTFB 366ms

syd

1056ms

DNS 141ms TCP 1ms TLS 117ms TTFB 1054ms

yyz

211ms

DNS 120ms TCP 2ms TLS 27ms TTFB 204ms

What Recurly does

Recurly runs subscription billing for businesses that charge on a recurring basis. It handles plans, trials, proration, dunning for failed cards, invoicing and revenue recognition, and connects to payment gateways rather than processing cards itself. Companies build signup and upgrade flows against its API, so a Recurly fault shows up at the point a customer tries to subscribe or change plan.

What an outage looks like

Recurly's status page separates Subscription Management, Recurly Commerce, Recurly Engage and Revenue Recognition. During an incident, new subscriptions and plan changes fail at checkout, the admin interface may be unreachable, and scheduled renewal runs can be delayed. Because Recurly sits between your app and a payment gateway, a card can be perfectly valid while the subscription it belongs to cannot be created.

What to do about it

Check status.recurly.com and note which of the four components is affected, since Revenue Recognition failing has no customer-facing impact while Subscription Management failing stops signups. Recurly retries failed renewal charges through its dunning process, so a renewal missed during an outage is normally attempted again rather than abandoned. Avoid manually re-charging customers until the incident is closed.

Is it down for everyone, or just you?

If this page says Recurly 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

Recurly outage FAQ

Will my customers be charged twice if Recurly has an outage?

Double charges usually come from manual retries rather than from the outage itself. Recurly handles failed renewals through dunning, which retries on a schedule, so a charge that failed during an incident is normally attempted again automatically. Re-running a billing job by hand while the incident is open is the main way duplicates happen. Check the invoice record before intervening.

Do renewals stop during a Recurly outage?

They can be delayed rather than skipped. Subscription Management is the component covering renewals, and when it is affected scheduled billing runs may not execute on time. Recurly picks them up afterwards. The practical impact is that revenue lands late and customers on the edge of a dunning cycle may see access lapse briefly before the retry succeeds.

Can customers still use my product when Recurly is down?

That depends on how your app checks entitlement. If it calls Recurly's API on each request to confirm a subscription, an outage will lock users out. If it caches subscription state locally, they keep working. This is the single most useful thing to know before an incident, and testing it beforehand beats discovering the answer mid-outage.

Is Recurly the same as a payment processor?

No. Recurly manages the subscription, the plan and the invoice, then passes the actual card transaction to a payment gateway. That is why a Recurly outage and a gateway outage look different: with Recurly affected, checkout can fail before a card is charged at all; with the gateway affected, the subscription exists but the payment does not go through. The status pages to check are different too.

How we measure this

We request Recurly'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 Recurly 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 Recurly 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