When your suppliers go down: what small businesses should do
A simple plan for when a tool your business relies on goes offline during a security event like PHP2Shell: the first hour, first day and after.
By HackSpot team (Amethyst Apps) · · 4 min read

The short version: during a big security event like PHP2Shell, some suppliers take services offline while they update, as a precaution. That's often the responsible thing to do, but it can stop your business in its tracks. Have a simple plan: confirm what's happening, beware of scams, keep working another way, and ask the right questions. HackSpot can watch your suppliers' status pages and tell you in plain language when something changes.
Why suppliers go offline during a security event
The UK's National Cyber Security Centre (NCSC) advised organisations that can't apply the PHP2Shell fixes or temporary measures quickly to consider taking the system offline until it's fixed. So a supplier going quiet for a few hours may be following good advice, not hiding a disaster. An outage on its own doesn't mean your data has been stolen.
The NCSC also asked organisations to watch their own suppliers for updates, including products that bundle PHP. Many business tools are built on PHP, so for a small business the bigger risk may be the tools you rely on, not your own website.
A worked example: a letting agency
Imagine a small letting agency on a Monday morning. Its property software, tenant referencing service and online payment portal are all run by different suppliers. At 9am the property software won't load.
Here's a calm way through it. (This is an illustration, not a report about any real supplier.)
The first hour
- Confirm it's not just you. Check the supplier's status page or official social media. Ask a colleague to try from a different connection.
- Treat unexpected "log in again" messages as scams. Criminals send fake messages during outages. Go to the supplier's site by typing its address yourself, and call the number on your contract if in doubt.
- Switch to plan B. Phone viewings and maintenance requests in, keep notes on paper or a shared spreadsheet, and catch up later.
- Tell your team and your customers what to expect. A short, honest message ("our property system is temporarily unavailable; we're still reachable on the phone") prevents a flood of calls.
- Note the time and what you see. It helps later if you need to talk to the supplier, your insurer or a regulator.
The first day
- Ask the supplier four questions: what's affected, is our data safe, when will it be back, and is there anything we need to do?
- Export important data if you still can. If the service comes back in a limited way, download today's key information (for example upcoming viewings or rent due).
- Hold off on big decisions. Don't switch supplier or change passwords across the board on day one unless the supplier tells you to.
- Check your other suppliers. If one tool was affected, ask the others whether they've applied the PHP fixes. Our copy-and-paste email to your web host can be adapted for any supplier.
Afterwards
- Ask for a short write-up of what happened and whether any personal data was involved. If personal data was involved, you may have obligations of your own; the ICO publishes guidance on personal data breaches.
- Update your plan B. Write down what worked: who to call, which spreadsheet to use, where the phone numbers are.
- Keep a list of the tools you depend on, their status pages and their support numbers. That list is the single most useful thing to have on a bad morning.
How HackSpot helps
HackSpot's supplier watch keeps an eye on the status pages of the tools you choose, from property software and phone systems to payments and accounting, and reads public security alerts. When something changes, it emails you, in your language, with what's happening, whether the supplier has said anything, what to do now and a message you can send them. Serious alerts are checked by a person before they're sent, and they state facts only; we never say a supplier "has been hacked".
Questions people ask
Does a supplier outage mean my data was stolen?
Not necessarily. During PHP2Shell the NCSC advised taking systems offline if they can't be fixed quickly, so an outage can be a precaution. Ask the supplier directly.
Should I change my passwords if a supplier goes down?
Not automatically. Change a password if the supplier tells you to, if you've entered it on a suspicious page, or if you use the same password elsewhere.
What should I ask a supplier about PHP2Shell?
Whether their services use PHP, whether they've applied the 21 October 2026 fixes, whether your data is affected, and when any outage will end.
How do I find a supplier's status page?
Look for "status" in the footer of their website or help centre, or ask their support team. HackSpot's public status pages list the suppliers we watch.
Is this only for letting agents?
No. The same plan works for any small business that depends on online tools: clinics, salons, accountants, shops and trades.
More on PHP2Shell
- PHP2Shell: what small businesses need to do today
- Watch out for PHP2Shell phishing and fake patch offers
- A supplier is down: what to do (guide)
- PHP2Shell timeline: what happened and when