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 | 61 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 “Delayed BACS reports”. 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
Delayed BACS reports
major resolved · started · resolved
5 updates
- investigating
We are investigating delayed BACS failure reports. This means that returned-payment information is not yet available in the dashboard or scheduled reports. We are working with the relevant provider to restore report delivery and will provide an update as soon as we have more information. We apologise for any inconvenience and appreciate your patience.
- identified
The issue has been identified and is affecting the Bacs scheme more broadly. The relevant parties are actively implementing technical fixes, and work is progressing to restore normal service as soon as possible. We are closely monitoring the situation and will provide further updates as they become available.
- identified
We have seen BACS failure reports begin to flow again and are working with our provider to reconcile report completeness and ensure all delayed reports are processed. Some returned-payment information may remain delayed in the dashboard and scheduled reports while this work continues. We will provide a further update once reconciliation is complete.
- identified
On Monday 21st September we received delayed reports for failed payments, mandate cancellations and other BACS reports. We have confirmed internally that all reports received were processed before midnight yesterday and all relevant payment and mandate statuses were updated and accurate when viewed today. Statuses will be visible in the dashboard and scheduled reports as usual, and expected API events have been sent. We have identified a very limited number of customers where we did not receive failure reports yesterday. We are working with our provider to receive these missing reports and will contact each affected merchant directly with more information. BACS report delivery has returned to normal resumed so no further impact is expected. We will provide a further update once this work is complete.
- resolved
We can confirm that the issue affecting reports for failed payments, mandates, cancellations, and other BACS reports has now been resolved. We have contacted the affected merchants directly with further details. We apologise for any inconvenience this may have caused.
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.