Recurly reported "Snowflake on AWS and Azure shares may be unavailable." on its status page at 2026-10-15 04:34 UTC.

Recurly did not name the affected components. The updates on this page have the details.

When did the incident start and end?

It started at 2026-10-15 04:34 UTC and ended at 2026-10-15 07:15 UTC. It lasted 2 h 41 min.

How do I get alerts for Recurly?

Subscribe to the Recurly live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Recurly. outages.live reads it every few minutes and keeps every update.

RRecurlyIncident · 2026-10-15 04:34 UTC

Snowflake on AWS and Azure shares may be unavailable.

ResolvedOfficial update

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

The latest update from Recurly.

State

Resolved

Started

18 d ago

2026-10-15 04:34 UTC

Lasted

2 h 41 min

until 2026-10-15 07:15 UTC

Worst impact

Partial outage

Timeline

3 updates

04:3405:1405:5406:3407:15

Partial outageUpdate postedTimes in UTC

Identified

2 h 41 min 100%

Updates

Times in UTC

As posted by Recurly

Resolved2026-10-15 07:15 UTC

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

Identified2026-10-15 07:14 UTC

Please contact support for assistance in re-establishing a datashare.

Identified2026-10-15 04:34 UTC

We are aware that some Snowflake data shares on AWS and Azure are in an inconsistent state, with permissions affected following a recent release. We are actively investigating the scope of the issue. Merchants whose shares are affected may be unable to access or query them until permissions are restored. If you are affected, please contact Support for guidance.

Recurly in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

5 h 39 min

This incident

53% shorter than 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

Recurly·Degraded Metrics for Recurly Engage

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

Resolvedresolved 6 d ago

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