CHYP.ai · ORBIT // Cloudy_Day Security Suite

Payments

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 vs. reality: Vendor status and outside signals roughly agree
The four clocks
ClockStartedRunning
Vendor clock when the vendor's open incident started78 days
Crowd clock when user reports began rising above normalnot seenn/a
Network clock when routing anomaly data first flagged itnot seenn/a
ORBIT clock when our checker first recorded the changenot seenn/a

Evidence

  • Official page: Operational (“All Systems Operational”). evidence confidence: high
  • Vendor stage: resolved on “AUDDIS-I errors affecting transferred mandates”. 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

AUDDIS-I errors affecting transferred mandates

none resolved · started · resolved

3 updates

  1. investigating

    We are receiving reports that some mandates transferred from one bank to another are being cancelled with an AUDDIS-I error. The issue appears to be affecting multiple banks, with the majority of reported cases currently involving Nationwide Bank, as well as HSBC, NatWest, Barclays, and others. Our team is actively working with our banking partners to investigate the issue and identify the root cause. We are continuing to monitor the situation closely and will provide another update as soon as we have more information.

  2. monitoring

    Following our investigation with our banking partner, we identified the root cause of the issue. The payer’s bank has since implemented a fix, and the issue is now resolved. However, further investigation has revealed that the information previously shared via email with the affected merchants is no longer accurate. We will therefore contact all affected merchants again to clarify the situation, provide the correct information, and explain the next steps. We apologise for any inconvenience caused and appreciate your continued patience and understanding.

  3. resolved

    We have contacted all affected merchants directly with further details on the failed mandates. We apologise for the disruption caused and thank you for your patience and understanding.

Official incident page ↗

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.

Where to next