When a Technology Supplier Gets Into Trouble, What Happens to Your Business?

A business can buy a reliable service and still become too dependent on the organisation providing it. Supplier financial distress, acquisition, service withdrawal or a change in contract terms can expose that dependency. The aim is not to predict every failure. It is to avoid discovering, during a disruption, that nobody in your business can access its own domain, data or critical applications.

What Getty Images actually announced

In its statement dated 21 October 2026, Getty Images announced voluntary Chapter 11 proceedings for certain US entities as part of an agreed financial restructuring. It said it would continue operating normally and anticipated no impact on customers or other operational stakeholders. It expected completion by year end, subject to approvals; an expectation is not a completed outcome.

Chapter 11 is a US restructuring process, not synonymous with ceasing to trade. The announcement discusses its capital structure and non-operating liabilities. It does not establish that AI alone caused the difficulties, that customers lost data or that services stopped. Those claims should not be inferred. The wider lesson is about maintaining options when a supplier's circumstances change.

Map the dependencies behind a working day

List cloud hosting, Microsoft 365 and other SaaS, domain registration, DNS hosting, backup providers, CRM systems, website platforms and specialist business software. For each, identify the business process it supports, the data it holds, who administers it and how long the business could tolerate losing access.

Trace dependencies between services. A recovery plan stored only inside an unavailable cloud account is difficult to use. An alternative website host is little help if nobody can change DNS. A backup service may depend on the same account, payment arrangement or supplier relationship as the production system. Identify these shared failure points before choosing a recovery approach.

What could change if a supplier fails?

Possible consequences include service interruption, restricted data access, reduced technical support or difficulty obtaining licence renewals. Contracts may limit termination, export assistance or continued use of software. A specialist application may export records but not the workflow rules, attachments or configuration needed to operate elsewhere.

These are planning scenarios, not claims about Getty or any specific provider. Read your actual agreement and obtain appropriate legal advice where necessary. Operational preparation and contractual rights are related but different: a right to retrieve data does not guarantee a fast, usable migration if the export has never been tested.

Retain appropriate control over business technology

Check that domains are registered to the correct organisation and that your business can reach the registrar and DNS account. Keep verified ownership records, renewal responsibilities and recovery contacts. Where a provider manages these services, document how authorised access can be obtained without depending on one person's availability.

For cloud systems, retain appropriate customer administrative access with MFA, secure credential storage and a tested recovery route. Do not respond by giving every employee administrator rights. Establish a small number of accountable owners and a controlled emergency-access procedure. Confirm what a reseller or support provider can change and how that relationship can be ended.

Test the exit, not just the export button

Obtain a representative data export and inspect it in an isolated environment. Can you read the records, match attachments, preserve necessary history and reconstruct important relationships? Check formats, export charges, rate limits and the time needed to retrieve the full dataset. A spreadsheet containing customer names is not a complete replacement for a CRM.

Identify realistic alternative suppliers and the prerequisites for migration: licences, compatible formats, technical skills, identity changes, DNS access and staff training. Set recovery time and acceptable data-loss objectives with business owners. Document manual workarounds for essential tasks while systems are being restored or moved.

Independent backups can reduce dependency, but independence must be demonstrated. Review where copies sit, who controls deletion and encryption keys, whether access survives loss of the primary account and what can actually be restored. Periodic recovery tests should produce usable files or services, not just a screenshot of a successful backup job.

Keep a concise supplier continuity record

• The supplier, contract owner, critical service and business impact.
• Renewal, termination, licensing and export conditions, with professional review where needed.
• Administrative access, domain ownership, credential recovery and escalation contacts.
• The last successful export or restore test, its limitations and observed recovery time.
• A fallback supplier or workaround, migration dependencies and next review date.

Review this after material contract, ownership or service changes, not only at renewal. Avoid unnecessary duplication of sensitive credentials in the continuity document; reference controlled storage and access procedures instead. Keep an appropriately protected copy of the plan accessible during the outage it describes.

Where independent assurance adds value

Our existing supplier security assurance article considers who can access systems and data. Exit planning asks a different question: can the business continue if the relationship or service changes? An independent IT review can compare the contract, ownership records, backups and observed recovery results within an agreed scope.

Explore the IT Road for selectable responsibilities, including backup and assurance. The objective is not to assume every supplier is about to disappear. It is to retain enough control, information and tested alternatives that a supplier's difficulties do not leave your business helpless.

Primary source

Getty Images restructuring announcement. Checked 2 November 2026. This article reports the announced process, not a completed restructuring or demonstrated customer disruption.