Investigating issues with Recurly Subscription Management
All services are operational and caught up.
The latest update from Recurly.
State
Resolved
Started
75 d ago
2026-08-18 13:49 UTC
Lasted
5 h 39 min
until 2026-08-18 19:28 UTC
Worst impact
Degraded
Timeline
7 updatesInvestigating
1 h 25 min 25%
Identified
1 h 42 min 30%
Monitoring
2 h 33 min 45%
Updates
Times in UTCAs posted by Recurly
All services are operational and caught up.
Issues impacting availability have been resolved. Some users may still experience delays in reporting and analytics.
The team has identified the issue and is continuing remediating it
We're expanding the impacted components based on investigation
The team is investigating further into the 500s
Our engineers have identified the issue and are actively remediating it.
We are investigating elevated 500 errors with Recurly Subscription Management.
Recurly in the last 90 days
Full historyIncidents in 90 days
3
Days with an incident
4
Median duration
5 h 39 min
This incident
About the median
Other Recurly incidents
All incidentsRecurly·Degraded Metrics for Recurly Engage
This issue is resolved, and the Performance dashboard is fully operational.
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.
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.
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.
https://outages.cc/feed.xml?providers=recurly/feed subscribe https://outages.cc/feed.xml?providers=recurlyFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane