A visitor to a major brand’s website might reasonably assume that the scripts running behind the page are safe.
But that assumption was put to the test on November 16, when malicious code delivered through Optimizely’s Web Experimentation platform reached visitors to sites linked to 178 organizations, including Salesforce, Zoom, GitLab, the BBC, CNN and HSBC.
According to security researcher Scott Helme, attackers inserted malicious code into the Project JavaScript field within customer projects.
The code was designed to steal payment card details, replace cryptocurrency wallet addresses, harvest browser data and deliver iOS exploit kits. The incident offers a clear indication of how a vulnerability in one technology provider can expose customers across an extensive network of businesses. Helme warned in a post on X:
The Optimizely incident was a near miss, and far too close for comfort. We need to do better.
And yet the incident is one of a series of technology disruptions and security incidents affecting major providers and their customers. A global Microsoft 365 outage, problems with AWS authentication affecting Amazon Connect, a nationwide FAA ground stop and transaction delays at JPMorgan Chase all demonstrated the consequences of technology failures.
The security picture became more concerning on November 19, when a ransomware group leaked customer data associated with Visa, Mastercard and JPMorgan Chase following attacks on third-party service providers. The disclosures came just two days after Visa published research warning that AI-enabled fraud and attacks targeting third parties are increasing worldwide.
The pressing question for customer experience leaders is how much control businesses really have over the technology and suppliers their customers depend on.
When One Provider’s Failure Affects the Wider Customer Experience
The Microsoft 365 outage on November 12-13 demonstrated how quickly a problem within a major technology provider can disrupt everyday business operations.
The incident affected Dynamics Contact Center 365, Outlook, Exchange Online and other Microsoft 365 services, including elements of Teams and Copilot. Microsoft’s preliminary post-incident report, published on November 16, attributed the disruption to a combination of factors, including a software defect introduced in July, increased traffic following a change to Teams infrastructure and reduced server capacity.
The consequences for enterprises extended beyond employees temporarily losing access to email. Customer enquiries, service updates, internal escalations and communications with suppliers can all depend on the same platforms. When those channels become unavailable, service teams may struggle to respond, even when their own customer-facing systems remain operational.
At Phantasialand, a theme park in Brühl, Germany, the outage reportedly prevented a hotel’s pool safety system from delivering an automated warning to staff. A fault in the pool’s chlorine dosing system had caused levels to rise dangerously, but the alert was sent by email and did not arrive while Outlook was disrupted. The local fire department reported that “emergency medical services evaluated a total of 15 individuals,” of which five were taken to hospital for further treatment.
It was a clear illustration of how dependence on a single communications channel can turn a technical outage into a physical safety risk, with direct consequences for customers.
The risks also extend to the infrastructure supporting contact center operations.
On November 15, Amazon Web Services (AWS) reported authentication and connectivity problems in its US-East-1 region, affecting customers using IAM Identity Center to access the AWS console and other services. Amazon Connect was among the affected services, alongside Kiro and several other AWS products.
The issue lasted from 3:05am to 6:10am PT, with AWS reporting that it had mitigated the authentication problems by 5:20am. Some connectivity problems affecting Network Load Balancers continued until 6:21am.
For businesses using Amazon Connect, the incident illustrates how a problem with an underlying authentication service can affect access to the technology supporting customer conversations. Even when a contact center platform itself is functioning, customers and agents may struggle to reach it if the infrastructure responsible for authentication becomes unavailable.
The incident also raises questions about how contact center operators prepare for failures in services that sit beneath their primary CX platforms. Having alternative customer communication channels is useful, but businesses also need to understand which dependencies could prevent employees from accessing those alternatives or the tools needed to manage them.
A separate infrastructure failure affecting the U.S. aviation system demonstrated how the consequences of technology disruption can extend well beyond individual businesses. On November 13, the Federal Aviation Administration (FAA) issued a nationwide ground stop that lasted almost five hours, after telecoms problems affected the stability of communications and radar systems used by air traffic control.
The FAA said its legacy equipment became unstable when data flooded its FAA Telecommunications Infrastructure network, generating approximately 1,000 connection attempts every four to five seconds. The disruption followed routine router replacement work at a remote facility. The agency subsequently disabled the functionality of the originating Juniper routers and paused further installations while it investigated.
The incident indicates how a failure within a critical telecommunications network can affect thousands of customer journeys, even when the airlines themselves have no underlying technology problem. It also highlights the importance of contingency planning across interconnected infrastructure providers.
The disruption to JPMorgan Chase services on November 16 offered another example of a technical failure with consequences beyond the organization experiencing it. The bank stated in a post on X that it was "a temporary issue related to a software bug in on-premise hardware systems – there is no evidence this is cyber-related," adding:
"Where we were party to a transaction involving other banks, those banks may have been impacted, but this is not a systemic issue."
US Bank also warned that transactions involving other financial institutions could be delayed, despite its own systems remaining operational.
For customers, the distinction between a bank’s own systems and a problem at another institution may be largely irrelevant. A delayed transfer can still mean a missed payment or uncertainty about whether money has reached its destination.
Visa, Mastercard and JPMorgan Customers Caught Up in Third-Party Data Leak
The risks extend beyond accidental technology failures. Third-party suppliers are increasingly attractive targets for attackers looking for access to multiple organizations through a single intrusion.
Visa warned in its Fall 2026 Biannual Threats Report that AI is helping criminals execute familiar fraud techniques faster, with greater precision and across more markets. The research, covering threat activity between January and June 2026, found that incidents involving third-party agents increased 62 percent compared with the previous six-month period. These providers were linked to approximately 56 percent of compromised payment credentials identified during the reporting period. The timing of the report proved to be particularly significant.
Just two days after Visa warned of the growing risks associated with third-party attacks, the payment provider confirmed that it had been affected by one.
On November 19, The Wall Street Journal reported that a ransomware group called n0n had leaked data belonging to thousands of customers of Visa, Mastercard and JPMorgan Chase. The companies said attackers had targeted third-party service providers rather than their own systems.

