- Level
- confirmed
- Worst impact
- Partial outage
- Down Index
- 40of 100
What to do
Check whether your product depends on Recurly. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2h 41m it lasted.
Anything that failed between 2026-10-15 04:34 UTC and 2026-10-15 07:15 UTC may need a replay.Subscribe to Recurly's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=recurly works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Recurly 3
- identified
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.
provider
- identified
Please contact support for assistance in re-establishing a datashare.
provider
- resolved
Support will provide scripting to re-establish the data share and all grants. Please contact them directly.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-4326b2a667
Is Recurly still down?
No, this incident was resolved 2026-10-15 07:15 UTC. For Recurly's live state, see https://down.guide/recurly.
How long did it last?
2h 41m, from 2026-10-15 04:34 UTC to 2026-10-15 07:15 UTC, by the times Recurly posted.
What caused it?
Recurly hasn't published a root cause. If it does, it shows here.
Where does this come from?
Recurly's official status page, https://status.recurly.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.