Recurly Outage History

Recurly is up right now

Recurly had 13 outages in the last 2 years totaling 34h 34m of downtime — averaging 0.5 incidents per month.

There were 13 Recurly outages since April 19, 2026 totaling 34h 34m of downtime. Each is summarised below — incident details, duration, and resolution information.

Source: https://status.recurly.com

Minor July 23, 2026

[Recurly Subscription Management ] Exports & Analytics Delayed

Detected by Pingoru
Jul 23, 2026, 01:16 AM UTC
Resolved
Jul 23, 2026, 01:16 AM UTC
Duration
—
Affected: Reporting & Analytics
Timeline · 2 updates
  1. identified Jul 22, 2026, 09:23 PM UTC

    Status: Identified We have identified delays in exports and analytics within Recurly Subscription Management and are working towards a resolution. Affected components Reporting & Analytics (Degraded performance)

  2. resolved Jul 23, 2026, 01:16 AM UTC

    Status: Resolved The delays affecting exports and analytics within Recurly Subscription Management have been resolved. Affected components Reporting & Analytics (Operational)

Read the full incident report →

Minor July 9, 2026

[Recurly Commerce] Recurly Commerce elevated response times and error rates

Detected by Pingoru
Jul 09, 2026, 03:33 PM UTC
Resolved
Jul 09, 2026, 03:33 PM UTC
Duration
—
Affected: Commerce API
Timeline · 3 updates
  1. investigating Jul 09, 2026, 02:41 PM UTC

    Status: Investigating We are investigating elevated response times and error rates with Recurly Commerce Affected components Commerce API (Degraded performance)

  2. monitoring Jul 09, 2026, 03:18 PM UTC

    Status: Monitoring A fix has been implemented and we are monitoring the results. Affected components Commerce API (Degraded performance)

  3. resolved Jul 09, 2026, 03:33 PM UTC

    Status: Resolved All systems operational. Affected components Commerce API (Operational)

Read the full incident report →

Minor June 25, 2026

We are investigating reports of duplicated email delivery for Recurly Commerce

Detected by Pingoru
Jun 25, 2026, 08:57 PM UTC
Resolved
Jun 26, 2026, 12:51 AM UTC
Duration
3h 53m
Timeline · 4 updates
  1. investigating Jun 25, 2026, 08:57 PM UTC

    We are investigating reports of duplicated email delivery for Recurly Commerce

  2. identified Jun 25, 2026, 09:36 PM UTC

    The team has identified the issue and is working on a fix.

  3. monitoring Jun 26, 2026, 12:47 AM UTC

    We have implemented a fix for the duplicate email sends affecting Recurly Commerce and are monitoring the results

  4. resolved Jun 26, 2026, 12:51 AM UTC

Read the full incident report →

Minor June 3, 2026

[Recurly Subscription Management ] Test

Detected by Pingoru
Jun 03, 2026, 03:00 PM UTC
Resolved
Jun 03, 2026, 03:00 PM UTC
Duration
—
Affected: Subscription management API
Timeline · 3 updates
  1. investigating Jun 03, 2026, 02:46 PM UTC

    Status: Investigating This is only a test Affected components Subscription management API (Degraded performance)

  2. identified Jun 03, 2026, 02:47 PM UTC

    Status: Identified going through the statuspage workflow. Affected components Subscription management API (Degraded performance)

  3. resolved Jun 03, 2026, 03:00 PM UTC

    Status: Resolved all done Affected components Subscription management API (Operational)

Read the full incident report →

Minor June 2, 2026

Issues with Purchase Preview

Detected by Pingoru
Jun 02, 2026, 07:28 PM UTC
Resolved
Jun 02, 2026, 07:39 PM UTC
Duration
10m
Timeline · 3 updates
  1. identified Jun 02, 2026, 07:28 PM UTC

    We've Identified an issue with Preview API calls and our engineers are working on a resolution.

  2. monitoring Jun 02, 2026, 07:36 PM UTC

    A fix has been implemented and we are monitoring the results.

  3. resolved Jun 02, 2026, 07:39 PM UTC

Read the full incident report →

Minor May 18, 2026

We are investigating an outage for Recurly Commerce

Detected by Pingoru
May 18, 2026, 09:51 PM UTC
Resolved
May 18, 2026, 10:10 PM UTC
Duration
19m
Timeline · 3 updates
  1. investigating May 18, 2026, 09:51 PM UTC

  2. monitoring May 18, 2026, 10:03 PM UTC

    We are monitoring degraded performance for Recurly Commerce

  3. resolved May 18, 2026, 10:10 PM UTC

    Service has been restored for Recurly Commerce; we will continue to monitor for any issues

Read the full incident report →

Minor May 14, 2026

Admin UI showing a 500 error

Detected by Pingoru
May 14, 2026, 02:25 PM UTC
Resolved
May 14, 2026, 02:55 PM UTC
Duration
29m
Timeline · 2 updates
  1. investigating May 14, 2026, 02:25 PM UTC

    We are investigating reports of a 500 error on login. Please change /welcome in the URL to /accounts

  2. resolved May 14, 2026, 02:55 PM UTC

Read the full incident report →

Minor May 12, 2026

Intermittent payment failures on Stripe gateway

Detected by Pingoru
May 12, 2026, 12:47 PM UTC
Resolved
May 12, 2026, 01:55 PM UTC
Duration
1h 7m
Timeline · 4 updates
  1. investigating May 12, 2026, 12:47 PM UTC

    We are investigating intermittent payment failures on the Stripe payment gateway.

  2. identified May 12, 2026, 01:32 PM UTC

    The Recurly engineering team has identified the cause.

  3. monitoring May 12, 2026, 01:38 PM UTC

    A fix has been put in place, and the team is currently monitoring.

  4. resolved May 12, 2026, 01:55 PM UTC

    The issue has been resolved

Read the full incident report →

Minor May 6, 2026

Invoice Force Collection

Detected by Pingoru
May 06, 2026, 04:42 PM UTC
Resolved
May 06, 2026, 10:28 PM UTC
Duration
5h 46m
Timeline · 5 updates
  1. investigating May 06, 2026, 04:42 PM UTC

    We are currently investigating reports of invoices failing to be collected following a previous transaction decline. Our team is actively looking into this and will provide updates as our investigation progresses.

  2. identified May 06, 2026, 05:24 PM UTC

    The team has found the root cause of the issue and is working on a fix

  3. identified May 06, 2026, 08:50 PM UTC

    The team is implementing a fix and is currently completing validation before deploying to production. We will provide an update once it is live.

  4. monitoring May 06, 2026, 10:02 PM UTC

    The fix has been successfully deployed to production and our team is actively monitoring to ensure stability

  5. resolved May 06, 2026, 10:30 PM UTC

Read the full incident report →