Operational GoCardless status
gocardless.com · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
No sign of a widespread GoCardless problem right now; every source we read is quiet.
confidence: medium Vendor: operational · users: normal · routing: no data.
- Vendor status page Operational · 1 open incident
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) no mapped dependencies
- CISA KEV (context) no recent entries for this vendor
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 58 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “Intermittent ARUDD-8 failures for Nationwide Bank”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
What we don't know: what is happening inside GoCardless' own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.
Who depends on whom
We don't map other services that depend on GoCardless. Dependency chains are where single points of failure hide.
Identity & trust lens
When GoCardless has trouble, people see failed logins, MFA prompts that don't arrive and sessions that drop. That's when phishing pages and “verify your account” texts show up. Only sign in through the official app or site, and don't re-enter credentials from a link someone sends you.
For users
Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on GoCardless, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
Any new vendor incident, a jump in user reports above baseline, or trouble at the providers GoCardless may depend on.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with GoCardless. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Intermittent ARUDD-8 failures for Nationwide Bank
minor resolved · started · resolved
4 updates
- investigating
We are aware of an issue affecting a small percentage of Direct Debit payments to Nationwide, which are failing intermittently each day with the code ARUDD-8. We are investigating the issue with our banking partner and will provide an update as soon as we have more information.
- investigating
Upon further investigation, we have identified that payments to Nationwide accounts that initially fail with ARUDD-8 are succeeding when retried. **Action for merchants:** We recommend retrying any Nationwide payments that have failed with ARUDD-8. We are continuing to monitor the situation and will provide a further update as more information becomes available.
- monitoring
We are seeing a reduction in the number of payments to Nationwide failing with ARUDD-8, and retries are continuing to successfully go through. We are in contact with our partner bank to monitor the fix that Nationwide is implementing. **Action for merchants:** We continue to recommend retrying any Nationwide payments that have failed with ARUDD-8.
- resolved
We can confirm that we no longer see payments to Nationwide failing with ARUDD-8, and we have not observed any further intermittent failures. Payments are now processing successfully. We sincerely apologise for any inconvenience this issue may have caused. **Action for merchants:** Any payments that previously failed with ARUDD-8 can be retried, and retries are processing successfully. Thank you for your patience and understanding.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.