Go Cardless outage history

Status: Resolved The issue has been resolved. We apologise for any inconvenience caused. Affected components GoCardless for Xero (GC4X) (Operational)

Status: Resolved The resending of emails affected by the recent service disruption has now completed. We apologise for any inconvenience caused.

Status: Resolved All SEPA Instant payouts have been processing correctly. The issue is confirmed to be resolved. Affected components Payouts (Operational)

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.

We are currently investigating reports of discrepancies in the amounts displayed on the GoCardless dashboard homepage. Our engineering team is actively working to identify the root cause and implement a fix. We understand the importance of accurate reporting and appreciate your patience while we resolve this issue. We will provide a further update shortly.

The issue affecting the amounts displayed on the GoCardless dashboard homepage has now been resolved. Our engineering team identified the root cause of the discrepancy and implemented a fix. All displayed amounts are now accurate, and the dashboard is functioning as expected. We will continue to monitor the system closely to ensure ongoing stability.

We’ve monitored for a while and can confirm that the issue with amounts displayed on the GoCardless dashboard homepage has been fully resolved and is now working as expected.

We are currently investigating an incident that has resulted in an increased number of Direct Debit collection failures for some New Zealand customers on 24th February. We are working with our banking partner and will provide further updates as soon as more information becomes available.

We are continuing to investigate the incident that has resulted in an increased number of Direct Debit collection failures for some New Zealand customers. In addition to payments scheduled for 24th February, we have identified that some payments scheduled for 25th February are also impacted and there may be delays to processing these payments. We are actively working with our banking partner to resolve this as quickly as possible. We will provide further updates as more information becomes available. We will soon reach out to all affected merchants.

The previously reported issue affecting some Direct Debit collections for New Zealand customers has now been fully resolved. We have contacted all impacted merchants and continued monitoring confirms that payment processing is operating as expected. Thank you for your patience.

We are currently investigating an issue affecting the GoCardless Dashboard, where some users are encountering a blank screen. We have also received reports of API disruption. Our team is actively working to identify the root cause and will provide a further update as soon as more information becomes available.

We’ve identified the root cause and implemented a fix. Access to the GoCardless dashboard and APIs are recovering at the moment. We’ll continue to monitor the system to ensure everything remains stable.

We have confirmed that our fix has resolved the issue and that users can access the GoCardless Dashboard as normal. We apologise for any inconvenience caused.

We have identified an issue affecting direct debit mandates for customers holding accounts with **Société Générale** and **Boursorama/BoursoBank** whereby collections for impacted payers have failed and the mandates cancelled. We are working closely with our partner bank to identify the root cause and assess the full impact. We will provide a further update as soon as more information becomes available.

We have identified the root cause, and the issue has now been resolved. We are currently conducting a detailed impact analysis to determine the full scope of affected mandates and collections. We will be back with another update shortly.

Following our detailed impact analysis, we have identified the affected mandates and are currently working on the feasibility of reinstating all impacted direct debit mandates. We expect this process to be completed by tomorrow. We will provide a further update tomorrow.

Following our detailed impact analysis, we identified the affected mandates and assessed the feasibility of reinstating all impacted direct debit mandates. We have now successfully reinstated all impacted mandates, and these existing mandates are active again (except the ones cancelled by the merchants). As next steps, we will first reach out directly to all affected merchants, after which we will contact the impacted payers to clarify the situation. We will continue to provide updates as needed.

We have now contacted all affected parties, and have resolved this incident.

We are investigating an issue related to our dashboard, in particular, reports of seeing a blank screen. In most cases, clearing the cache is able to resolve the issue. We will provide another update shortly once we have identified the cause.

We are continuing to investigate the issue affecting the dashboard, including reports of users seeing a blank screen. Our team is actively working to identify the root cause. In the meantime, clearing your browser cache may help resolve the issue for some users. We appreciate your patience and will provide a further update as soon as more information becomes available.

We’ve identified the root cause and implemented a fix. Access to the GoCardless dashboard should now be fully restored. We’ll continue to monitor the system to ensure everything remains stable.

We have confirmed that our fix has resolved the issue and that users can access the GoCardless Dashboard as normal. We apologise for any inconvenience caused.

We experienced an issue with payouts that has now been resolved. Payouts for SEPA, BECS New Zealand, PAD Canada, and Betalingsservice Denmark were delayed by approximately 40-50 minutes compared to the usual processing time. Apologies for any inconvenience caused.

We can now confirm that the issue has been fully resolved. All affected payouts have processed successfully and should be delivered to merchants with only a minor delay. We apologise for any inconvenience this may have caused.

We are experiencing a slight delay to AUD payout processing this morning, funds may arrive up to five hours later than normal. We will provide further updates when payouts have been processed.

We have confirmed that this issue has been resolved and payments have now been successfully executed. We apologise for any inconvenience caused.

Around 8:50 to 9:11 UTC our Dashboard and API were temporarily unavailable due to a Cloudflare outage. Cloudflare seems to have resolved the issue, we're monitoring the situation.

We have confirmed that there are no further service disruptions.