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 | 51 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 “Bacs Processing Issue Affecting Payments Scheduled for Collection on 2 October”. 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
Bacs Processing Issue Affecting Payments Scheduled for Collection on 2 October
minor resolved · started · resolved
4 updates
- investigating
We experienced an issue affecting a number of Bacs collection payments with a charge date of 2 October 2026, as well as some Bacs mandates. As a result, payments due for collection on 2 October will be collected from customers early next week. We are actively working to resolve the issue and are taking steps to ensure affected payments and mandates are processed as soon as possible. Under Bacs rules, merchants are not required to send an additional notification to payers, as a payment can be collected within three working days of the date given in the advance notice. However, merchants may wish to proactively notify customers. Some mandates that were due to be submitted for creation and/or cancellation on 2 October 2026 will also be delayed. We will contact affected merchants directly to confirm which payments and mandates are impacted and provide further information on expected processi
- monitoring
We’ve now resubmitted the Bacs collection payments and mandates due to be processed on 2 October 2026. Our engineering team are monitoring to identify any further issues. Payments that were due for collection on 2 October will now be collected on 5 October 2026. The same revised processing date applies to affected mandates that were due to be submitted for creation and/or cancellation on 2 October. We’ll continue to monitor processing, and we will contact all affected merchants tomorrow morning to provide an update.
- monitoring
We can now confirm that the issue has been resolved and all affected payments and mandates have been successfully resubmitted. Payments originally due for collection on 2 October 2026 will now be collected on 5 October 2026. Affected mandates will follow the same revised processing timeline. We will shortly contact all affected merchants directly to provide further details and clarify the impact of this issue. We apologise for the disruption and thank you for your patience and understanding.
- resolved
**We've resolved the issue affecting the delivery of a batch of Bacs payment submissions on 30 September.** Affected payments and mandates have been resubmitted and confirmed, with collection and processing dates moved to 5 October, which has now completed as planned. We're sorry for the disruption this caused and thank you for your patience while we worked through it.
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.