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 started9 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 “BECS NZ Payouts Delayed – November 13, 2026”. 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

BECS NZ Payouts Delayed – November 13, 2026

minor resolved · started · resolved

2 updates

  1. investigating

    We are currently experiencing an issue affecting a number of BECS NZ payouts scheduled for November 13, 2026. As a result, these payouts are delayed by a few hours. Our team is actively working to resolve the issue and ensure all affected payouts are processed as soon as possible. We will provide a further update as soon as more information becomes available. We sincerely apologise for any inconvenience caused and appreciate your patience.

  2. resolved

    The issue affecting BECS NZ payouts scheduled for November 13, 2026 has been resolved, and the affected payouts have now been submitted to the bank. Because of the interruption with our sponsor bank, these payouts were submitted later than usual, so they may arrive in your bank account later than expected. We sincerely apologise for the inconvenience and appreciate your patience.

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