Blue cloud icon on grey background

If Microsoft Can Go Down, Can VASPs Trust Smaller SaaS Providers?

16 Nov, 2026

The global Microsoft outage of 12–13 November 2026 disrupted businesses worldwide, leaving users unable to access essential services such as Outlook and parts of Teams. More than 12 hours after the disruption began, Microsoft was still struggling to restore normal operations.

The incident affected businesses, financial institutions, government departments and public services across numerous countries.

Microsoft operates one of the world's largest technology infrastructures, supported by extensive engineering resources, sophisticated monitoring systems and significant investments in redundancy and disaster recovery.

Yet even Microsoft could not prevent a major service disruption.

If a technology giant like Microsoft struggles to keep its SaaS services running, how much confidence should businesses place in smaller providers operating critical applications?

For VASPs, this question is particularly important when choosing a Travel Rule compliance solution. An outage affecting a critical compliance provider can prevent transactions from being processed, directly disrupting business operations.

The Microsoft incident exposes two fundamental risks of centralised SaaS: the challenge of scaling infrastructure for an entire customer base and the consequences of relying on a shared service that can fail.


The Scalability Challenge of SaaS

In a Software-as-a-Service (SaaS) model, the provider operates the infrastructure supporting its customers.

This means the application must have sufficient processing capacity to handle the combined workload of every organisation relying on it.

As more customers join the service and transaction volumes increase, the infrastructure must scale accordingly. A problem affecting shared resources can quickly spread across the customer base.

The Microsoft outage illustrates this challenge. As servers became unavailable, the remaining infrastructure came under increasing pressure. Microsoft reported that an overwhelmed process was contributing to capacity loss, making recovery more difficult.

Despite its considerable infrastructure resources, Microsoft struggled to restore service.

For smaller SaaS providers, the challenge is no less significant. They must ensure their infrastructure can continuously support the growing demands of all their customers, including during unexpected failures and periods of increased activity.

In the digital asset industry, where transaction processing is time-sensitive, an inability to scale or maintain sufficient capacity can have immediate operational consequences.

And scalability is only half the problem.


When a SaaS Provider Goes Down, Its Customers Go Down With It

The greatest risk of centralised SaaS is the dependency it creates.

When multiple organisations rely on the same application infrastructure, a failure can affect all of them simultaneously.

This is particularly concerning for Travel Rule compliance.

VASPs rely on Travel Rule solutions to collect and exchange the required information associated with virtual asset transfers. When a centrally hosted compliance application becomes unavailable, the VASPs depending on it can lose the ability to complete essential compliance processes.

The consequences can include delayed withdrawals and deposits, interrupted transaction processing, dissatisfied customers, lost business and reputational damage.

More importantly, affected VASPs cannot resolve the problem themselves.

They must wait for their SaaS provider to identify the issue, restore the infrastructure and bring the service back online.

Whether the disruption lasts minutes or hours, the affected businesses remain dependent on a third party to resume operations.

The Microsoft incident demonstrates how serious this dependency can become. When a centralised provider experiences a major failure, the consequences extend far beyond its own organisation.

For VASPs, relying on a single SaaS provider introduces a central point of failure into an essential business process.


On-premises: Distributed Scalability and Independent Operations

An on-premises Travel Rule solution takes a fundamentally different approach.

Rather than depending on a centrally hosted application shared across an entire customer base, each VASP operates its own independent instance of the software.

This creates two important advantages.


Each VASP Scales Independently

With SaaS, the provider must maintain enough application capacity to handle the combined processing requirements of all its customers.

With on-premises software, each VASP only needs to provision sufficient resources for its own transaction volumes.

A VASP processing millions of transactions can allocate the capacity it requires without affecting the resources available to another VASP processing a much smaller volume.

As more VASPs join the ecosystem, processing capacity is distributed across additional independent deployments.

Instead of forcing one provider to scale for the entire ecosystem, the ecosystem scales through its participants.

This removes the central application bottleneck and prevents the workload of one VASP from consuming the application resources of another.


One Outage Does Not Take Down the Entire Ecosystem

The second advantage is operational independence.

With SaaS, an outage affecting shared application infrastructure can disrupt every VASP relying on that service.

With on-premises deployment, each VASP operates its own application instance.

If one instance experiences an outage, the remaining instances continue operating independently.

The affected VASP may need to restore its own application, and transactions involving that VASP may be delayed. However, the failure does not automatically interrupt compliance operations for every other participant.

Crucially, VASPs are not dependent on the software provider restoring a centralised application before they can resume their own operations.

An individual outage remains an individual outage, rather than becoming a problem for the entire ecosystem.

This is a fundamental architectural advantage for businesses that cannot afford to have essential compliance operations interrupted by failures beyond their control.


Why 21 Analytics Takes a Different Approach

21 Analytics developed 21 Travel Rule around the principle that VASPs should remain in control of their critical compliance infrastructure.

Unlike centrally hosted SaaS solutions, 21 Travel Rule is deployed on-premises, with each VASP operating its own independent application instance.

21 Analytics does not host the application or access customer data.

This architecture means each VASP can scale its deployment according to its own processing requirements without depending on the capacity of a shared SaaS application.

It also ensures that an outage affecting one deployment does not automatically disrupt the operations of other VASPs using 21 Travel Rule.

VASPs retain operational independence instead of relying on 21 Analytics to maintain and restore a centralised service for the entire customer base.

The objective is not merely to provide Travel Rule functionality. It is to ensure that the architecture supporting compliance does not introduce an unnecessary central point of failure.


Decentralisation Should Extend to Business Operations

The Microsoft outage is a reminder that even the world's largest technology companies cannot guarantee uninterrupted SaaS availability.

If Microsoft, with its extensive infrastructure and engineering resources, can struggle to maintain and restore its services, VASPs should carefully consider the risks of relying on smaller SaaS providers for business-critical operations.

The issue goes beyond a provider's reputation, resources or service-level agreement. It is about the consequences of centralising essential processes.

A SaaS provider must scale its application infrastructure for its entire customer base. When that shared infrastructure fails, all dependent customers can be affected, with recovery outside their control.

An on-premises architecture distributes processing capacity and isolates failures across independently operated instances.

For an industry built around decentralisation, this distinction should matter.

Critical compliance infrastructure should not introduce the very centralisation risks that the digital asset industry was designed to avoid.

A VASP should not have to stop processing transactions simply because its software provider has gone offline.

With 21 Travel Rule, VASPs retain control over their compliance operations without depending on a centrally hosted SaaS application.

Learn more about 21 Analytics' on-premises Travel Rule solution.

Request a Demo
Info Circle Outlined Icon

Disclaimer

This material is provided for educational and informational purposes only and is not intended to be a substitute for professional advice or detailed research.

Written by:
Filip Gospodinov
Having spent more than two-thirds of his nine-year career as a software engineer with companies in finance and blockchain technology, Filip is a true veteran in the field. With a Master’s in Electrical Engineering from ETH Zurich, he focuses on the blockchain’s protocol level. His numerous contributions include libbitcoin, Bitcoin Core, Electrum and many more.
21 Analytics offers Software Solutions for Virtual Asset Service Providers.
Poststrasse 22, Zug, Switzerland     |     info@21analytics.co
X
Trust Graphic

New: TRUST Network

Transact with Coinbase, Kraken, Gemini and others.