outages.live
Live
RRecurlyIncident · 2026-10-25 22:31 UTC

Degraded Metrics for Recurly Engage

ResolvedOfficial update

This issue is resolved, and the Performance dashboard is fully operational.

The latest update from Recurly.

State

Resolved

Started

7 d ago

2026-10-25 22:31 UTC

Lasted

21 h 38 min

until 2026-10-26 20:09 UTC

Worst impact

Degraded

Timeline

3 updates
22:3103:5509:2014:4420:09
DegradedUpdate postedTimes in UTC

Investigating

4 h 43 min 22%

Monitoring

16 h 55 min 78%

Updates

Times in UTC

As posted by Recurly

Resolved2026-10-26 20:09 UTC

This issue is resolved, and the Performance dashboard is fully operational.

Monitoring2026-10-26 03:14 UTC

Display of Engage prompt metrics is restored. We are monitoring the platform to ensure continued stability.

Investigating2026-10-25 22:31 UTC

Display of Engage prompt metrics are degraded. Metrics are still being collected.

Recurly in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

3

Days with an incident

4

Median duration

5 h 39 min

This incident

3.8× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

21 h 38 min
median 5 h 39 min
90 days agoToday

Other Recurly incidents

All incidents
R

Recurly·Snowflake on AWS and Azure shares may be unavailable.

Support will provide scripting to re-establish the data share and all grants. Please contact them directly.

Resolvedresolved 18 d ago
R

Recurly·Investigating issues with Recurly Subscription Management

All services are operational and caught up.

Resolvedresolved 75 d ago

Follow Recurly

Your coding agent knows when Recurly is down, and tells you when a failure is theirs, not yours. You can also get Recurly incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "recurly" and tell me if Recurly has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.cc/feed.xml?providers=recurly
Slack
/feed subscribe https://outages.cc/feed.xml?providers=recurly

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane