On Nov. 4, 2026, Leaseweb published survey numbers that should make any ops lead uncomfortable: among the C-suite leaders it polled, nearly nine in ten said they could not move business-critical workloads off their largest cloud or infrastructure provider within three weeks. That is a different problem from getting through a bad day in one region. Outage response is about restoring service within agreed time and data-loss limits, sometimes by failing over inside the same provider and sometimes outside it. A cloud provider exit plan is about replacing your dependencies on that provider altogether. Mix up those two clocks and you end up running the wrong drill.
What the Survey Actually Measured
Start with the publisher and the sample, not the headline. In its Digital Independence Survey 2026 press release, Leaseweb, an IaaS and cloud provider with a commercial interest in alternatives to hyperscale lock-in, reported that 89% of respondents could not migrate business-critical workloads away from their largest cloud or infrastructure provider within three weeks. Only 11% said they could make that move in that window. More than half (55%) said it would take longer than three months or was not currently possible.
The same release says 76% reported complete or high control over their ability to move data to another provider or environment. Leaseweb presents that next to the migration figure as a gap. I read it as two different tasks. Copying data out is one job. Moving a whole workload means rebuilding the compute, identity, networking, managed services, deployment pipelines, and monitoring around that data. A team can be confident about the first and still realistic about how long the second takes.
Censuswide ran the fieldwork for Leaseweb among 800 C-suite leaders at organizations with 500 to 5,000 employees, 200 each in the UK, US, Germany, and the Netherlands, between Sept. 22 and 30, 2026. The release summarizes the findings but does not publish the questionnaire wording. Read “most companies” as most of this vendor-sponsored, self-reported sample of organizations in four countries, estimating how long an exit would take. It is not a census of every cloud customer.
The October 2025 Outages Illustrate a Different Problem
Provider exit is a planned migration measured in weeks or months. Incident recovery is measured against your recovery time objective (RTO), meaning how long until the service is usable again, and your recovery point objective (RPO), meaning how much data loss you can accept. Bringing DynamoDB clients back in us-east-1 tells you nothing about whether you could re-platform the estate onto another vendor by Friday.
Amazon’s own summary of the Amazon DynamoDB service disruption in Northern Virginia (us-east-1) says impact began at 2:48 AM EDT on Oct. 20, 2025. AWS says the broader event ended at 5:20 PM EDT that day. In between there were separate periods of DynamoDB API errors, Network Load Balancer connection errors, and EC2 launch and connectivity problems. AWS attributes the DynamoDB portion to a latent defect in automated DNS management that caused endpoint resolution failures. That postmortem is about dependencies inside a single region: DNS, control planes, and shared building blocks. It is not a case study in leaving a provider.
Customers also published their own accounts. Coinbase’s retrospective says it saw severe disruption from the us-east-1 outage on Oct. 20, 2025. Customer impact ranged from login failures to being unable to trade, with about 3 hours 17 minutes of degraded performance for users. Engineers were paged at 3:08 AM EDT, and Coinbase says all services were restored at 6:45 PM EDT after AWS fixed the systems it depends on. Coinbase also notes it could not reach AWS Support because the Support Console was offline. That is incident response and dependency triage during a provider outage, not a three-week migration to someone else.
Microsoft’s Azure Networking team offers another recovery example from the edge side. Its December 2025 post on Azure Front Door lessons from the October outages covers customer-impacting incidents on Oct. 9 and Oct. 29, 2025, both caused by incompatible configuration metadata spreading through the global edge. The fixes Microsoft describes are configuration safety, tenant isolation, and faster automated recovery, including a proposed practical recovery target of about ten minutes for Front Door—not a guarantee or proof of achieved recovery times. That is RTO work, not advice to move off Azure this quarter.
What a Cloud Provider Exit Plan Drill Should Actually Test
The rest of this post is my own analysis as an operator. I’m not claiming Leaseweb’s 89% applies to your shop, and I’m not claiming lock-in caused any of those October outages.
- Write both clocks down. For each critical user journey, record the RTO and RPO next to an honest estimate of how long a provider exit would take. If the exit column is blank or says “call the vendor,” you have found a documentation gap.
- Inventory the sticky parts first. That means data gravity (object stores, databases, logs), identity (IAM roles, workload identity, SSO apps), DNS and TLS (registrars, certificate automation, traffic managers), and managed services with no clean equivalent elsewhere (queues, ML endpoints, proprietary APIs). Exit drills tend to fail on that glue, not on the VM list.
- Keep recovery tests and exit tests separate. Failing over to another region or another account with the same provider exercises RTO and RPO. It does not test an exit, because you are still on the same provider’s identity, control plane, and managed services. Imagine a tabletop where the team announces “we cut over to another provider by Monday” without export paths, IAM remapping, or named DNS cutover owners. That exercise is fiction, and the gaps it skips are your real findings.
- Run a bounded exit drill on one workload. In a hypothetical drill, you pick a non-critical service and time a restore onto a different provider or an independently operated on-premises environment. Moving to a different account or region does not count here. Write down what breaks: secrets, service endpoints, observability agents, payment webhooks. That stopwatch reading feeds your exit estimate. It does not prove you could move your most critical systems in three weeks.
- Budget for people and change windows. Leaseweb’s sample already says full workload migration is slow, even among leaders who feel confident about moving data. Your real constraint may be contract terms, data-residency rules, or the one engineer who understands the Terraform state.
Use the survey as a reason to write the exit estimate down. Use the October postmortems as a reason to harden the recovery dependencies inside the provider you already pay. Keep those two drills on separate checklists, so the next outage doesn’t get answered with a three-month migration plan.

Leave a Reply