• +1 (602) 922-5990
  • This email address is being protected from spambots. You need JavaScript enabled to view it.
  • Mon - Fri 8:00a - 5:00p AZ
IT executive with a glowing tablet in a darkened data center aisle with amber warning lights, facing a doorway of warm daylight, with the article title When a Critical Provider Cannot Recover and icons for stressed exit, data, substitution, in-house options, workarounds, testing, and decisions.

Most third-party contingency planning rests on a quiet assumption: the provider will come back. Business continuity plans describe how to operate while a supplier restores its service. Contracts specify recovery time objectives. Exercises rehearse the hours or days until normal operations resume. That assumption is usually right. But sometimes it is not.

Providers can become insolvent. They can be acquired and decide to discontinue a product. They can suffer a destructive cyberattack from which certain systems cannot be restored. They can be subject to sanctions, legal action, or regulatory intervention that stops them from serving you. They can simply withdraw from a market. In these situations, waiting for recovery is not a strategy. The organization needs a way to keep its critical services running without that provider, possibly for a long time, possibly permanently.

This article explains how to prepare for the case where a critical provider cannot recover, and how to build alternatives that work before they are needed.

Subcategories