Is Banked Down Right Now? Discover if there is an ongoing service outage.

We are currently experiencing a performance degradation and increased latency on our services. Investigations are ongoing and an update will be provided as soon as more information becomes available. There are known Issues across Google Cloud and Cloudflare services affecting us. We are working to mitigate the impact

We are continuing to investigate this issue.

We are investigating problems with scanning QR codes for hand off. All other bank hand off mechanism are not affected.

On June 10th, 2024, from 06:30 to 07:20 UTC, Banked experienced a partial outage in the Payments API and Checkout product in the UK/EU region. During the outage, approximately half of the payment creation and checkout attempts failed. This problem arose from a failure in one of the infrastructure components managed by our cloud provider. The service was restored after 50 minutes, and our system returned to normal. We are collaborating with our cloud service provider to prevent such issues in the future.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue.

We are still investigating, issues are caused by high latency in our Europe data center.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently investigating this issue.

The fix is now in place and all traffic is be back to normal.

A fix has been implemented by our downstream provider that should partially restore traffic. We are continuing to monitor.

Our third party provider has identified a fix and is rolling that out across all regions. The ETA is 1 hour. We will post an update once we have more information

We are currently in contact with the downstream provider, they have identified the issue and are actively working on a fix. The current impact to customers would be an error in the checkout when selecting a bank.

An issue has been identified with a downstream third party provider. We are in contact with the provider and will update as soon as we have more information.

This incident is now resolved.

A fix has been implemented by our downstream provider and we are continuing to monitor.

The third party provider has identified a fix and are working on rolling it out now. They estimate this will take one hour.

We are continuing to work with the downstream provider on this issue, and will update once we have more information. The current impact to customers would be an error in the checkout when attempting to select a bank.

The issue has been identified as an outage with a downstream third party provider. We are in contact with the provider and will update as soon as we have more information.

We are currently investigating an issue with EU payments in our checkout

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently investigating an issue affecting the ability for customers to complete checkout journeys

This issue has been resolved. Further details will be provided in a postmortem in due course.

A fix has been implemented and we are monitoring the results.

We are continuing to investigate this issue.

We are currently experiencing some issues with Webhooks. Payments processing remains unaffected. Investigations are ongoing and an update will be provided as soon as more information becomes available.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently experiencing a performance degradation to the API and Checkout service. Investigations are ongoing and an update will be provided as soon as more information becomes available.

On October 30th, 2023 between 11:18 -11:43 UTC, Banked experienced a partial outage in the payments API and checkout product in the UK/EU region. During the outage, about half of the attempts to create payments and checkout failed. This issue occurred due to a failure in a routine upgrade of a component in our infrastructure. Our on-call team responded immediately to the failure and stopped the upgrade to investigate with our cloud service provider. We are currently working with our cloud service provider to prevent similar issues from occurring in the future.

This incident has been resolved. Further details will be provided in the postmortem in due course.

We are still continuing to monitor the results following the earlier fix.

We are still continuing to monitor the results following the earlier fix.

We are still continuing to monitor the results following the earlier fix.

We are still continuing to monitor the results following the earlier fix.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

We are continuing to work on a fix for this issue.

The issue has been identified and a fix is being implemented.

We are continuing to investigate this issue.

We are currently experiencing a performance degradation to the payments and checkout service. Investigations are ongoing and an update will be provided as soon as more information becomes available.

On September 6th, 2023 between 9:05 -9:25 UTC, Banked experienced an outage in the payments API and checkout product. During the outage, attempts to create payments failed. This issue occurred due to a deployment of one of our services with incorrect configuration. Our on-call team responded immediately to the failure and rolled back the deployment of the service to restore the system to a healthy state. We are currently working on adding additional verifications to our services to prevent similar issues from occurring in the future.

This incident has been resolved. Further details will be provided in the postmortem in due course.

We are continuing to investigate this issue.

We are currently experiencing a performance degradation to the API and checkout service. Investigations are ongoing and an update will be provided as soon as more information becomes available.

On July 28th, 2023 between 9:38 -10:35 UTC, Banked experienced an outage in the payments API and checkout product. During the outage, most attempts to create payments failed. This issue occurred during a platform upgrade to our clusters that caused a failure in one of our core components. Our on-call team responded immediately to the failure and started a recovery process to return the system to healthy state. We have already begun and are continuing to work on improving our infrastructure components and their resilience.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are continuing to work on a fix for this issue.

The issue has been identified and a fix is being implemented.

We are currently experiencing a performance degradation to the API and checkout service. Investigations are ongoing and an update will be provided as soon as more information becomes available.

On June 14th, 2023 between 17:54-18:55 UTC, Banked experienced an outage in the payments API and checkout product. During the outage, most attempts to create payments failed. This issue occurred during a patch upgrade to our infrastructure that caused a failure in our streaming component. Our on-call team responded immediately to the failure and started a recovery process to return the system to healthy state. Moving forward, we are working to improve the resilience of our components and their self-healing abilities.

The issue affecting the API and checkout service has been fully resolved. We have confirmed, following a period of monitoring, that the service has returned to normal processing and no further degradation has been observed. Further details will be provided in the postmortem in due course.

A fix has ben deployed and the intermittent failures have stopped. We will continue to monitor the situation and update once the situation has resolved.

We're continuing to investigate intermittent issues with payment creation and completion the team is investigating and deploying a fix. We will update next by 20:00.

We're continuing to investigate intermittent issues with payment creation and completion the team is investigating and deploying a fix. We will update next by 19:45.

A fix has been implemented and we are starting to accept payments again and payments are completing. The Incident response team are continuing to monitor the situation.

We have isolated the issue on the API and checkout service; which is calls to create payments to fail and checkouts to complete. Our Incident Response team is actively working to resolve this as high priority. We will post an update at 19:30 UTC unless there is further information to share before this time.

We are currently experiencing a performance degradation to the API and hosted checkout service. Investigations are ongoing and an update will be provided as soon as more information becomes available.

On June 2nd, 2023 at 11:36 UTC, Banked experienced an issue with status updates of payments. The issue was resolved within 45 minutes, at 12:21 UTC on June 2nd. During this time, successful payments remained in pending status, and merchants did not receive success webhooks until the issue was resolved. This issue occurred due to an unexpected failure of an application to receive events during routine maintenance of an infrastructure component. After being alerted, our on-call team initiated a manual recovery procedure to recover the affected application. Moving forward, we are working to improve the resilience of our applications and their self-healing abilities.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

The issue has been identified and a fix is being implemented.

We are currently experiencing a performance degradation in the checkout service. Payment are processed but status updates are not being sent to customers. Investigations are ongoing and an update will be provided as soon as more information becomes available.

For a period of less than three minutes Banked's API returned unexpected errors during the creation and update of payments. This was caused by an unexpected temporary network issue that occurred during the routine upgrade of an internal service. This issue was quickly resolved and operations have returned to normal.

We performed a rollback of this change and deployed a fix. We have tested this fix with our Android SDK.

A fix for this issue has been identified and the team are in the process of deploying the fix. We will continue to monitor the impacted SDK's and provide further updates.

We are continuing to work on a fix for this issue.

Our Android SDK is experiencing issues fetching images which is preventing payments

This incident has been resolved.

We are continuing to monitor for any further issues.

A fix has been implemented and we are monitoring the results.

We have identified a fix which has been deployed, we are now running as normal. We will be continuing to monitor this with further details provided in due course.

Checkouts for the Android SDK are failing due to an issue contacting the backend API for payment sessions.

Today between 11.39 and 12:15 UTC we had delays in payment status notifications to customers. This has been fully resolved and all notifications sent by 12:51 Further details will be provided in the postmortem in due course.

On February 9th, Banked observed a major outage on the checkout service between 17:09 to 18:26 UTC. During this time, checkout session could not be created or completed for customers using our embedded and hosted checkout. This was due to a faulty configuration applied to one of our components After Identifying the faulty configuration, our on-call team reverted the change and restored the system to normal operation. We have taken immediate action to add additional quality gates and checks to ensure this or similar issues do not happen again.

The issue affecting checkout service has been fully resolved. We have confirmed, following a period of monitoring, that the service has returned to normal processing and no further degradation has been observed. Further details will be provided in the postmortem in due course.

We have idenitifed an issue with the checkout, a fix has been deployed and we are continuing to monitor

We have noticed errors occuring in the checkout, we are currently investigating

> On January 26th, we observed a major outage on our payment api and checkout service between 11:06 - 12:16 UTC. During this time, calls to create payment sessions failed and users were unable to complete checkout. > > This was due to the degradation of an internal service. The service gradually self healed while our incident response team was monitoring and investigating the scenario that lead to this incident. > > Additional mitigation measures has been identified and deployed to ensure our system’s resilience to such scenarios.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

Calls to create payments and complete checkouts are currently failing. We believe this is due to a third party vendor issue, but are continuing to investigate.

This incident has been resolved.

The issue has been identified and a fix is being implemented.

Currently investigating, this is an internal issue and a fix has been identified

This incident has been resolved.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

Banked's products are functioning as normal, despite underlying challenges with our cloud provider. We will continue to monitor the situation and update here if anything changes.

We're been made aware of an incident with our underlying cloud provider (Google Cloud), this issue is effecting many of their customers. We're seeing elevated levels of internal errors for some of our products, but our products are functioning as expected. We're investigating and will update as we discover more information

Access to Banked's services has returned to normal, and Cloudflare have resolved their network issue. We will continue to monitor the situation.

We've identified issues with accessing Banked services that are deployed behind Cloudflare, our CDN provider. Cloudflare are currently experiencing an incident with degraded access and performance, which means requests into their infrastructure are timing out or failing. Cloudflare have deployed a fix and normal access should resume shortly. We are monitoring the issue and will update this incident when we have new information

This incident has been resolved by GitHub.

We are aware of an issue with Github Packages (https://www.githubstatus.com/). Our Android SDK uses Github Packages for distribution, so attempts to install the Android SDK in development environments may fail. Production Android apps will not be affected, and our SDK will continue functioning as expected.

All services have returned to normal.

The upstream issue with our public cloud provider appears to be resolved and services have returned to normal operation.

We believe the incident is caused by an upstream issue with our public cloud provider Google Cloud. We are monitoring the situation and investigating mitigations we can put in place. We keep this page updated as soon as we know more.

We have been alerted to some customers having trouble accessing Banked's services, we area currently investigating and will update here as soon as we know more.

This incident has been resolved.

We have been notified of an outage of Lloyds Banking Group APIs.

We have not seen any payments fail due to this issue recently.

We are continuing to investigate this issue.

Lloyds payment authorisation is not available on the following Android devices: Huawei Kirin 980 OnePlus040619A Google Pixel 2 XL Google Pixel 3 Samsung A90 Moto G6 Huawei P20. This issue is being investigated by Lloyds.

NatWest have restored the functionality, and all Open Banking APIs are now working as expected.

An ongoing issue is affecting AIS and PIS calls to all Natwest brands.

The incident has been resolved.

Our upstream providers have implemented a fix for this issue and Banked's services have resumed their normal function. We are monitoring the situation.

We're continuing to investigate the issue. Banked appears to have been affected by a large-scale internet-wide outage.

We are currently experiencing issues with our hosted checkout (and several other domains) that are being serviced through Cloudflare. We are investigating the root cause but it looks to be a widescale incident at Cloudflare, our upstream service provider and is affecting many internet properties outside of Banked.

This incident has been resolved.

We’ve identified the root cause of this issue as being related to an upstream issue with our service provider in Google Cloud. For a short period of time (<1 minute) our Hosted Checkout responded with a 500 ‘Internal Error’ for a small subset of requests. This issue appears to have stabilised with our provider. We continue to monitor the situation.

Our monitoring stack has alerted us to some intermittent 500 errors being generated on our Hosted Checkout. We’re investigating and will update when we have more information.

The incident with our upstream provider, Github Packages, has been resoloved

We use Github Packages to distribute our Android SDK and it's currently experiencing issues. This may cause issues with accessing our Android SDK in your development or CI environments. It will not affect any live Android deployments. We expect this issue to be resolved quickly and you can track the ongoing issue here: https://www.githubstatus.com/incidents/76nv9h8pmkv4

This incident has been resolved.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

We are continuing to investigate this issue.

We have not logged any errors when creating Payment Consents for NatWest and Ulster Bank, and are waiting for confirmation from NatWest Group on whether the issue is resolved.

NatWest Group is experiencing intermittent failures on Payment Consent journeys for NatWest and Ulster Bank ROI. These are affecting a small percentage of journeys. We are monitoring the situation.

This issue has been resolved by Natwest. All banks are back to being operational.

We received information that Natwest are experiencing a partial outage that is affecting the Payment Initiation Service (PIS) and Account Information Services (AIS) APIs for Natwest, Bankline, Ulster Bank and RBS. This means that transaction initiation as well as transaction information retrieval capabilities may be affected. We are awaiting further information from Natwest, and are monitoring this issue internally.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

We are experiencing issues with Natwest Bankline Account Information Services (AIS) API returning unexpected errors. This means we are not able to retrieve transaction information from Natwest Bankline accounts. Other services, including the ability to authorise payments and initiate batch payments, are fully operational.

Natwest are experiencing a partial outage that is affecting the Payment Initiation Service (PIS) and Account Information Services (AIS) APIs. This means that transaction initiation as well as transaction information retrieval capabilities may be affected. We are awaiting further information from Natwest, and are monitoring this issue internally.

The issue has been resolved and downloads of Banked's Android SDK binaries should now function as expected.

We are experiencing issues with the availability of our Android SDK binaries, due to a problem with our package hosting provider. The packages are still available for manual download and inclusion (https://github.com/banked/banked-android-sdk/packages/281330). This does not affect the functionality of the Android SDK in any deployed environment, but only it's availability when installing dependencies in a development, build or CI environment.

Lloyds API has had a breaking change implemented, which means Banked payments could not be authorized via Lloyds. This issue was resolved by Banked at 12:30pm UTC on 17th of March.

We've validated the fix deployed by Lloyds bank and reenabled it in our checkout.

A fix has been deployed by Lloyds bank to address this issue, we're testing their fix and will reenable Lloyds in our checkout's when we've validated it.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

Lloyds bank is currently experiencing issues processing all domestic Open Banking payments, we're in contact with their team and will update the incident when we have more information, or when a fix has been deployed

This incident has been resolved.

We are continuing to investigate this issue.

We are currently investigating this issue.

A fix has been implemented and we're seeing Mockbank returning to normal operation. We apologise for any inconvenience.

We're currently experiencing issues with our internal test bank (Mockbank) we're investigating and will update when we have more information.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

All service are now restored

We are currently investigating this issue.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We've identified the root cause and a fix will be deployed within the next few minutes.

We're seeing errors occurring when merchants are attempting to log into the Banked console. We're investigating the root cause and will update this incident when we have more information

This incident has been resolved.

We are continuing to investigate this issue.

We are continuing to investigate this issue.

One of our upstream bank providers, Revolut, is producing errors after customer payments complete. We're monitoring the situation and will update when Revolut resolves the issue.

We use Cloudflare for DNS, SSL origination, DDoS/DOS protection and hosting for some of our single page applications, as such our services were affected by the major incident that occurred with Cloudflare on the 17th of July 2020. More information can be found about this incident here: https://www.cloudflarestatus.com/incidents/b888fyhbygb8 Like many other services on the web we saw instability in Cloudflare's DNS resolution for our services for a period of 55 minutes, from 22:14 until 23:09, at that point all Banked's services returned to normal operation. We are taking steps to minimise any such DNS issue in the future.

This incident has been resolved.

We are continuing to investigate this issue.

We are currently investigating this issue.

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

HSBC outage now resolved.

We are currently investigating this issue.

This incident has been resolved.

RBSG are aware of an issue impacting our app to app journey, where a PSU tries to re-consent their accounts. The PSU can select their accounts, but the re-direct then fails with a Page Expired error

This incident has been resolved.

We are currently investigating this issue.

This incident has been resolved.

Revolut current checkout api is experiencing problems

This incident has been resolved.

We are continuing to monitor for any further issues.

We are continuing to monitor for any further issues.

We've seen increased error rates from Barclays API infrastructure which is causing payments from customers to fail. We've informed them of the issue and they're investigating and mitigating. We've temporarily disabled payments from Barclays accounts.