Cause and consequence are different
A service can fail without an attack, and an attack can occur without public-facing disruption.
Public systems and disruption
Digital outages and service disruption
A digital outage means a service or system is unavailable or impaired. It may result from a technical failure, supplier problem, operational error, physical event or cyberattack. The outage alone does not confirm the cause.
Page T-013Guidance pageReviewed 29 August 2026
Key Guidance
Check the service through a route you already trust and wait for confirmed information about the cause. Treat unexpected workarounds, priority access, refunds and alternative payment instructions as separate claims that require independent confirmation.
Start with Key Guidance for the short answer. Then read the sections that match what happened and what you need to do.
Understand the issue
Why this matters to you
Outages can affect healthcare, emergency services, transport, utilities, communications, payments and ordinary online accounts. The public often needs an immediate alternative before the cause is known.
Essential services magnify the impact
Delays in health, emergency, transport or payment systems can create urgent real-world needs beyond the technology itself.
Suppliers connect many organisations
One software, network or service-provider problem can affect many otherwise unrelated organisations at the same time.
Confusion creates an opening
Scammers can offer false assistance, alternative payment routes or fabricated explanations while normal channels are difficult to reach.
Consequences and movement
What may happen next
Separate what is unavailable, what the organisation has confirmed and what action is genuinely necessary. Avoid filling an information gap with the most dramatic explanation.
A temporary route is published
Use it only when you found it through the organisation’s confirmed website, app, status page or other known channel.
A cyber incident is confirmed
The outage then also becomes a cyberattack question, but data exposure still requires separate confirmation.
A breach is confirmed
Follow the organisation’s data notice and match action to the information involved rather than assuming every customer faces the same risk.
Service returns before answers arrive
Recovery of operations does not settle questions about cause, data, responsibility or later scam contact.
Practical response
What you should do
Your priorities are continuity and route safety. You do not need to diagnose the failure to avoid an unsafe workaround.
- Check the established status routeOpen the service’s known app, website or status page yourself. Use official emergency or continuity information for essential services.
- Confirm alternatives independentlyVerify any new account, number, payment method, collection point or support channel before using it.
- Do not repeat failed payments blindlyCheck the account or transaction history before trying again so an apparent failure does not become a duplicate payment.
- Keep necessary recordsSave booking references, failed transaction evidence, official updates and any unexpected contact that refers to the disruption.
- Use urgent offline routes when providedFor health, safety or essential-service needs, follow verified emergency arrangements rather than waiting for ordinary digital channels.
- Reassess when facts changeUpdate your response if the organisation later confirms data exposure, account risk or a specific customer action.
Look more closely
An outage can make an unsafe workaround seem necessary
When the normal service is unavailable, an alternative can feel urgent and reasonable. Separate the genuine disruption from the identity and destination offered by anyone claiming to provide a solution.
The outage, failed payment or public warning creates attention.
Urgent access, continuity, fear of loss or promised priority makes action attractive.
The contact appears to be the provider, technical support, emergency assistance or an authority.
A new number, link, account or payment route is presented as the only available solution.
The alternative may collect payments, sign-in details, personal data or remote access.
Selected history
Historical cases and lasting lessons
WannaCry disruption
The WannaCry cyberattack affected organisations internationally and disrupted NHS services as well as computer systems.
Lasting lesson: A cyberattack can create serious operational harm, but the public response still depends on confirmed service and data effects.
Supplier and platform outages
Failures in shared software, cloud, telecommunications and payment infrastructure can affect many services without those organisations being attacked individually.
Lasting lesson: Simultaneous disruption is evidence of dependency, not by itself evidence of a coordinated cyberattack.
Transferable understanding
Patterns over time
Outage is an observed condition
It describes availability, not the technical or criminal cause.
Workarounds carry concentrated risk
Normal checks may be weakened precisely when an unfamiliar alternative is most tempting.
Essential services require proportionate language
Clear action and confirmed operational facts matter more than speculative labels.
Publicly reported incident data is incomplete
Sector summaries can reveal patterns while still underrepresenting events that were not publicly disclosed.
Plain-language answers
Common questions
Does an outage mean the service was hacked?
No. Technical, operational, supplier, physical and cyber causes are all possible. Wait for reliable confirmation.
Does a cyberattack mean my data was stolen?
No. Data exposure is a separate fact that the organisation or investigators need to confirm.
How can I trust a temporary payment route?
Find and confirm it through a confirmed official channel. Do not use a route supplied only in an unexpected message or call.
Should I keep retrying a failed payment?
Check transaction history first. A delayed confirmation can otherwise lead to duplicate payments.
Use verified continuity and support routes
Follow the affected service’s official status and emergency arrangements. Contact the relevant provider for duplicate payments or access problems, and report unexpected outage-themed approaches separately.
Scamology Insights
Recognise when disruption is being used to redirect you
These apps, tools, books and courses can help you separate a real service problem from a false solution. They show where checking through contact details you found yourself restores control. Links are intentionally withheld in this production version.
Continue understanding
Explore related guidance
Evidence and currency