Every business hits an outage eventually. A cable gets damaged, a carrier has a fault, hardware fails, someone unplugs the wrong thing. It’s not a question of if — it’s when.
So the real measure of an IT partner isn’t whether they can promise nothing will ever go wrong. Nobody can honestly promise that. The measure is what they do in the first ten minutes when it does. We know this one first-hand — we once caused an outage ourselves on a client site, and how we handled it mattered more than the mistake. (The full story is here →.)
Why the response matters more than the outage
When the internet goes down, the damage isn’t only technical — it’s trust. Staff can’t work, customers can’t get through, and everyone’s looking for answers. In that moment, silence is the worst possible response. A partner who goes quiet, gets defensive, or starts assigning blame turns a technical problem into a relationship problem.
A partner who communicates clearly and takes ownership does the opposite: they turn a bad day into proof that you picked the right people. The outage is forgotten in a month. How it was handled is remembered for years.
The first 10 minutes — what should happen
A good response in the opening minutes follows a simple pattern. None of it is about having the fix yet — it’s about control and communication.
Own it immediately
The first move is to acknowledge the problem before the client has to chase it. A partner who calls you and says “we’re aware, here’s what we know” — even with no solution yet — is a partner in control. Waiting to be asked, or hoping it resolves before anyone notices, is how trust erodes.
Escalate to the right people, in parallel
Most outages involve more than one party — an internet carrier, the building’s facilities team, a hardware vendor. A good partner gets the right people engaged at the same time, not one after another. Minutes matter, and working the problem in parallel is what shortens it.
Give one clear line of communication
Everyone affected needs the same three things: what’s happening, what’s being done, and when they’ll hear next. A single, honest status — repeated on a predictable cadence — keeps a room calm. Vague reassurance (“should be back soon”) does the opposite.
Contain and find workarounds
While the real fix is underway, a good partner looks for ways to keep people working — a backup connection, a mobile hotspot for critical staff, prioritising the systems that matter most. Even partial function buys goodwill and reduces the cost of the downtime.
When the fix takes longer than a coffee break
Not every outage is a ten-minute fix. Sometimes a repair needs a carrier technician, a part, or physical access to a comms riser — and it stretches across days rather than hours.
That’s where communication matters even more. A longer fix isn’t a failure in itself; going dark during it is. The partners you can rely on keep you updated at every step, set honest expectations about timing, and make sure the fix is done properly rather than patched and forgotten. On one of our own builds, a damaged fibre took several carrier visits across a few days to fully resolve — and the thing that kept three separate businesses onside was simply that nobody was ever left wondering what was happening.
The real test — what changes afterwards
The final mark of a good partner is what happens once the dust settles. A weak response ends with “it’s fixed, moving on.” A strong one ends with concrete changes so the same thing can’t happen again.
After our own incident, three things became standard on every job: physical protection at the exact point that failed, a redundancy conversation with every client before sign-off (so a single point of failure is a decision, not a surprise), and a written incident-response plan — who we call, in what order, and what we communicate. An outage you learn nothing from is a wasted one.
A real example — the outage we caused, owned and fixed
We put all of this to the test on a live client site — a multi-tenant network build in Sydney where we damaged the fibre during installation and took three businesses offline at once. We documented the whole thing, including exactly how we responded.
Questions worth asking your IT partner
You don’t need to wait for an outage to find out how yours will handle one. A few questions tell you a lot:
- Do you have a documented incident-response process — and can I see it?
- Who do you call, and in what order, when something breaks?
- What’s my redundancy or failover option if a single connection goes down?
- How, and how often, will you communicate with us during an outage?
- What do you change after an incident to stop it recurring?
If the answers are clear and specific, you’re in good hands. If they’re vague, that tells you how the real thing will go.
Talk to a partner who owns the hard days
We design and support networks for businesses across Sydney — and we’re upfront about how we handle the moments that go wrong, because that’s the part that actually matters.
