35 recorded Go Cardless incidents since September 2025, with official updates, affected components, duration and resolution information.
Status: Resolved Following a period of monitoring, we can confirm that the issue has been fully resolved and SSO access to the GoCardless dashboard is working as expected. Thank you for your patience, and we apologise for any inconvenience caused.
Status: Resolved We have completed resending the emails to Yahoo and AOL addresses that were affected by the delivery issue between October 1 and October 8. All affected users were notified on October 13. Thank you for your patience.
Status: 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. Affected components Submissions (Degraded performance)
Status: 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. Affected components Submissions (Operational)
Status: 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. Affected components Reporting (Operational)
Status: 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.
Status: Resolved We’ve now confirmed that the issue has been fully resolved. All affected merchants have been contacted directly to explain the situation. We apologise for the issue and thank you for your patience and understanding. Affected components Submissions (Operational) Payouts (Operational)
Status: Resolved All affected GBP payouts have now been processed. We apologise for the disruption and thank you for your patience. Affected components Payouts (Operational)
We've identified an issue where the homepage of GoCardless for Xero shows an error. The issue is only affecting the display of the homepage. As a workaround, you can access GoCardless for Xero at this url: [xero.gocardless.com/merchant/invoices](http://xero.gocardless.com/merchant/invoices "xero.gocardless.com/merchant/invoices") Our engineering team is actively working to resolve the issue.
The issue has been resolved. We apologise for any inconvenience caused.
We would like to inform you that we are currently experiencing email delivery failures affecting Microsoft mailboxes, including Outlook, Hotmail, Live, and MSN (and their regional extensions). We are in contact with Microsoft regarding this issue, however they have not yet provided an estimated resolution time. We will continue to monitor the situation and share updates as soon as they become available.
Email deliverability to Microsoft mailboxes (Outlook, Hotmail, Live, MSN, etc.) has been restored. We are actively monitoring the service to ensure continued stability
We have begun resending the emails that failed to deliver during the recent service disruption. To help you easily identify these messages, **(Delayed Delivery)** has been added to the beginning of the subject line.
The resending of emails affected by the recent service disruption has now completed. We apologise for any inconvenience caused.
Due to an issue with a 3rd party provider we have temporarily paused SEPA Instant Payouts at 9:14 BST today. Other payout types are not affected. We will resume SEPA Instant payouts as soon as we've received a confirmation that the issue has been resolved. If the issue persists we will contact affected customers with an update before 17:00 BST
SEPA Instant Payouts remain paused due to a third party issue. Emergency maintenance has been scheduled by our banking partners over night, and we expect to resume payouts tomorrow. All affected parties have been contacted directly. We will provide further updates when the third party issue has been resolved. Apologies for any inconvenience.
The issue has been confirmed as resolved. We have resumed SEPA Instant payouts and all pending payouts should soon reach the recipient bank accounts. We will continue to monitor for errors until the end of day.
All SEPA Instant payouts have been processing correctly. The issue is confirmed to be resolved.
We identified an issue affecting a small number of merchants, where queries to the Events API returned no events for payments, payment_actions, or customers created after 29 April. This also impacted the dashboard view for these resources. The issue has now been resolved, and we are continuing to monitor the situation.
We’ve continued monitoring following the earlier Events API issue, and all systems are operating as expected.
Status: Complete Maintenance has completed Affected components Live (Under maintenance)
We have identified an intermittent issue with processing Instant Bank Payments and Variable Recurring Payments. Our Engineers have identified the issue and are working on resolving it. We will get back to you shortly with an update.
Our team have now resolved the issue, and Instant Bank Payments and Variable Recurring Payments are working as expected. We will continue to monitor closely to ensure stability.
We have confirmed that Instant Bank Payments and Variable Recurring Payments are now functioning as expected. We apologise for any inconvenience this may have caused.
We recently experienced an issue with SEPA Instant Payouts due to a problem with our banking partner. The issue has been resolved, and we’re working closely with them to restore normal service. Payouts scheduled for this afternoon may be slightly delayed and are expected to arrive at merchants 60–90 minutes later than usual.
We can now confirm that all SEPA Instant payouts for April 14th have been processed and received. We apologise for any inconvenience caused.
``` We'd like to inform you that some webhooks that should have been sent today between 9:40 and 9:55 BST, were sent out at 11:30 BST. We apologise for any inconvenience caused. ```
We are currently experiencing an issue affecting the export functionality on the Payments page. Our team is actively investigating the root cause of this issue and working on a resolution. We will provide an update as soon as more information becomes available or the issue is resolved.
The issue affecting the export functionality on the Payments page has now been resolved. Our team has identified and fixed the root cause of the problem. Exports are working as expected, both with and without filters applied. We appreciate your patience while we worked on resolving this issue, and we apologize for any inconvenience caused.
We'd like to inform you that GoCardless API for Payout items is not returning the expected result. Other API functionality is not affected. Our engineers are reverting the change that caused the issue and will update you as soon as it's completed.
The revert was successful, Payout items are now correctly reflected in our API. We apologise for any inconvenience caused.
We would like to inform you that from 12:01-12:03 UTC our API and Payment pages were unavailable. We apologise for any inconvenience caused, our engineers are actively investigating the root cause of this disruption.
We’re currently experiencing an intermittent issue affecting access to the GoCardless dashboard for a few merchants. The root cause has been identified, and we are in the process of implementing a fix. We will provide a further update once the issue has been resolved.
The issue affecting access to the GoCardless dashboard for a small number of merchants has now been resolved. Our team has implemented a fix, and we can confirm that access to the dashboard has been restored. Thank you for your patience while we worked to resolve this issue.
