For the best part of a working day on 5 August 2026, thousands of homes and businesses across the central belt and Highlands of Scotland woke up, reached for the broadband and found nothing there. The cause was not a storm, a digger through a duct or a cyber-attack. It was a failure deep inside the core network of a single internet service provider — Inverness-based Brawband, which trades as HighNet and resells full-fibre connectivity over CityFibre’s network. Beginning at around midnight, a fault on Brawband’s own core equipment took its customers offline across Inverness, Glasgow, Renfrewshire and Edinburgh, and by the middle of the day the company was warning subscribers that the problem would not be fixed “by the end of the day”. Fixing it, Brawband said, would require nothing less than a full “rebuild of equipment” — “a significant piece of work which our technical engineers are treating with urgency”.
The incident, first reported by ISPreview and updated through the day, is a textbook illustration of a risk that most UK small and medium-sized businesses carry without ever naming it: total dependence on one provider, delivered down one circuit. When that provider’s core network fails — not the cable in the street, not the router on the wall, but the central switching and routing equipment that every one of its customers passes through — there is no self-service fix, no engineer visit that helps, and often no honest estimate of when service will return. You simply wait. For a household, a lost day of broadband is an inconvenience. For a business running VoIP phones, cloud applications, card payments and a hybrid workforce over that same single line, it is a lost day of trading. This article walks through what happened to Brawband’s customers, why a core-network failure is a different and more dangerous animal than an ordinary line fault, and what a UK SME should have in place so that one provider’s bad day never becomes your business’s.
What actually happened to Brawband
According to the account published by ISPreview on 5 August 2026, the trouble started in the small hours. From around midnight, Brawband’s broadband service began failing, and as customers woke and tried to get online the reports multiplied. This was not a handful of isolated faults in one town; the outage spanned a wide geographic spread of Scottish locations at once — Inverness in the Highlands, Glasgow and neighbouring Renfrewshire in the west, and Edinburgh in the east. A fault that surfaces in that many separate places simultaneously is the signature of a problem at the centre of a network rather than out at its edges, and that is exactly what it proved to be.
Brawband identified the cause as a fault on its core network — the central layer of switching and routing equipment through which every customer’s traffic flows on its way to and from the wider internet. Crucially, the company said the fix would not be a simple reset or a swapped card. It would require a full “rebuild of equipment”, which it described to customers as “a significant piece of work which our technical engineers are treating with urgency”. For several hours the provider was unable to give any estimated time to fix at all, and a midday update went further, cautioning customers that the issue would not be resolved by the end of the day. Service was eventually restored later on 5 August once the rebuild was completed, with customers advised to power-cycle their routers to reconnect.
One detail matters more than any other for understanding where the fault sat. Brawband resells full-fibre (FTTP) services delivered over CityFibre’s wholesale network, and other ISPs using that same CityFibre infrastructure in the same Scottish areas were not reporting equivalent outages at the time. That points clearly to the fault living specifically inside Brawband and HighNet’s own core network — the part of the chain the provider builds and operates itself — rather than in the shared physical fibre supplied by CityFibre. In other words, this was not a problem with the road; it was a problem with one haulier’s depot. Every business that had chosen that one haulier was grounded, while traffic on the same roads carried by others kept moving.
Most broadband problems a business hits are “last-mile” faults: a damaged cable, a dead router, a misconfigured line. They are frustrating, but they are local and usually fixable — a reboot, a replacement, an engineer visit. A core-network failure is a different category entirely. When the provider’s central equipment goes down, every single customer on that provider is offline at the same moment, and nothing on your premises can change that. You cannot reboot your way out of it, escalate your way past it or work around it, because the fault is in infrastructure you neither own nor can touch. Your only levers are the ones you put in place before the outage: a second circuit on a genuinely independent provider, automatic failover, and a mobile backup for the services that must never stop. Without them, your recovery time is entirely at the mercy of someone else’s engineering schedule — which, in Brawband’s case, meant “not by the end of the day”.
The timeline: from midnight fault to full rebuild
The value of the Brawband incident for any business planning its own resilience is in the sequence — how quickly a silent overnight fault became a full-day outage, and how long the affected businesses spent with no idea when they would be back. The chronology below is drawn from ISPreview’s reporting through 5 August 2026.
Why single-provider dependence is so common — and so risky
If a core-network outage is this damaging, why do so many businesses run on a single provider and a single circuit? The honest answer is that it is the path of least resistance. One line is cheaper, simpler to order, and works perfectly well — right up until the day it does not. The factors below are the ones we see, again and again, that leave a UK SME with no fallback when its one provider has a bad day. The bars are an indicative weighting of how often each contributes to a business being caught fully offline, based on the connectivity reviews Cloudswitched runs for clients.
Read the top three bars together and the exposure becomes obvious. A business on a single circuit, with no failover, running its phones over that same line, has stacked three dependencies on one point of failure. When Brawband’s core went down, a customer in that position lost their internet, their phone system and — if their card terminal rode the same link — their ability to take payment, all in the same instant. None of it could be restored from the premises. The fix for every one of those bars is not exotic or expensive: it is a second, independent path and the automation to switch to it without anyone lifting a finger.
How much of a business outage is really down to a single point of failure
It is tempting to treat a provider outage as an act of God — bad luck that could not have been foreseen or avoided. The reality is that the impact of an outage on a business is very largely a design choice made in advance. A provider’s core network will fail from time to time; that is a certainty across a long enough horizon. Whether that failure translates into a full day of lost trading, or into a two-second blip while traffic reroutes onto a second line, depends almost entirely on whether the business built in a fallback. The donut below is an illustrative reflection of how much of the business impact of a connectivity outage traces back to having a single, un-backed path rather than to the raw fact that a provider failed.
The point the donut makes is deliberately uncomfortable. The provider failure is the trigger, but the single point of failure is the reason the trigger matters. A business with a genuinely diverse second line and automatic failover experienced Brawband’s core rebuild as, at most, a brief reroute; a business without one experienced it as a lost day. Same event, wildly different outcome — and the difference was decided long before 5 August, at the point where someone chose whether to invest in a fallback.
Where SME connectivity resilience most often falls down
Across the connectivity reviews we carry out for UK SMEs, the same gaps recur. Individually each looks survivable; together they are the reason a provider outage becomes a business emergency. The grid below rates the ones that most often turn a single ISP’s bad day into your problem.
Notice the sixth row, because it is the trap that catches businesses which think they are already covered. Buying two broadband services does not guarantee resilience if both ultimately ride the same wholesale network or the same provider’s core. Two Brawband-style resellers sitting on the same CityFibre footprint, or two lines terminating in the same core equipment, share a single point of failure no matter how many invoices you receive. Genuine diversity means independent physical paths and independent core — ideally a second provider on a different underlying network, or a mobile link that touches none of the same infrastructure.
What connectivity resilience costs a UK SME
The obvious objection to a second line is cost. It is a fair challenge, and the answer is to weigh the monthly spend against the cost of a full day — or more — offline. The table below sets out indicative UK monthly figures for connectivity resilience by business size. They are planning ballparks to frame a conversation, not quotes; real pricing depends on your postcode, the networks available there, and how critical the workload is.
| Business size | Typical resilient setup | Indicative monthly cost | Cost of a full-day outage |
|---|---|---|---|
| Micro (1–9 staff) | Single FTTP plus 4G/5G automatic failover router | £60–£120 | Lost orders, dead phones, no card payments for a day |
| Small (10–49 staff) | Two lines on genuinely diverse providers, auto-failover | £150–£400 | A whole site unable to trade for the working day |
| Medium (50–249 staff) | Dual diverse fibre, SD-WAN, managed monitoring and SLA | £500–£1,500 | Multi-site disruption, SLA and contractual exposure |
| Multi-site/critical | Leased line plus diverse backup, guaranteed fix times | £1,500+ | Severe: revenue, compliance and customer-trust impact |
Set the monthly figures against the right-hand column and the arithmetic usually settles itself. For most trading businesses, one day without connectivity — no card payments, no email, no cloud applications, no VoIP phones — costs far more than a year of the resilience that would have prevented it. Brawband’s customers who happened to have a mobile backup or a second independent line barely noticed the outage; those who did not spent the day watching a status page and waiting for someone else’s engineers to finish a rebuild.
Reactive versus proactive connectivity management
The difference between a business that rides out an outage like Brawband’s and one that loses a day of trading is rarely the raw technology. It is the posture. Below is the contrast we see between the reactive default most SMEs live with and the proactive stance a managed network partner puts in place.
Reactive posture
What most SMEs do today
- One circuit from one provider, chosen on price alone
- Phones, data and card payments all on the same line
- No failover — an outage means everything stops at once
- The outage is discovered when staff cannot work
- Recovery time is entirely the provider’s to decide
- Escalation means joining the same queue as every consumer
Proactive posture
Where Cloudswitched takes you
- Two genuinely diverse providers on independent cores
- Critical services kept on a path that can never all fail together
- Automatic failover that reroutes in seconds, tested on a schedule
- Monitoring that alerts you the instant a line drops
- A documented continuity plan staff can follow on the day
- A named escalation path and pre-agreed fix-time expectations
Most of the proactive column is not about spending more on bandwidth. It is about design and discipline: a genuinely independent second path, automatic switchover, monitoring and a plan. Those are the controls that would have turned Brawband’s full-day outage into a non-event for a business — a brief reroute onto the backup while the primary provider rebuilt its core, with staff barely aware anything had happened.
In our experience the average unmanaged UK SME sits well below halfway on connectivity resilience: a single line, no automatic failover, phones and payments stacked on the same link, and no monitoring or continuity plan to fall back on. The gauge above reflects that typical starting point. The encouraging part is that most of the distance to a genuinely resilient posture is covered by design and process, not by heavy capital spend — a second independent path and automatic failover are within reach of a business of any size.
Ask one question and act on the answer: if our internet went down right now, what stops working, and what is our fallback? Walk it through service by service — email, cloud apps, the phone system, card payments, remote staff’s access — and note which ones die the moment the single line does. If the honest answer is “everything, and there is no fallback”, you have found your single point of failure. The immediate, low-cost fix is a 4G/5G failover router that keeps your most critical services alive automatically when the primary line drops; the fuller fix is a second, genuinely independent circuit. Either way, the time to arrange it is a quiet week — not the morning your provider announces a full core rebuild with no ETA.
The Brawband outage at a glance
| Detail | What happened |
|---|---|
| Provider | Brawband (trading as HighNet), based in Inverness |
| Underlying network | Resells full-fibre (FTTP) over CityFibre’s network |
| Date | 5 August 2026 |
| Start time | Around midnight; reports grew as customers woke up |
| Areas affected | Inverness, Glasgow, Renfrewshire and Edinburgh |
| Root location | Brawband’s own core network, not shared CityFibre infrastructure |
| How it was diagnosed | Other CityFibre-based ISPs in the same areas stayed up |
| Fix required | A full “rebuild of equipment” on the core network |
| Provider statement | “A significant piece of work which our technical engineers are treating with urgency” |
| ETA situation | No estimate for hours; midday update said not fixed by end of day |
| Duration | The best part of a working day |
| Resolution | Restored later on 5 August; customers told to power-cycle routers |
| Source | ISPreview, published and updated through 5 August 2026 |
How this connects to wider business-continuity risk
Connectivity failures rarely arrive in isolation, and the theme running through much of 2026 is the same: business continuity depends on eliminating single points of failure, wherever they sit. Our analysis of the botched full-fibre installation in Ilkeston made the point from the physical layer — an uncontrolled visit to install one line destroyed another — while the Azure West US outage of July 2026 made the identical argument from the cloud side, where a single region, like a single circuit, is a single point of failure. The security dimension is just as real: the UKGI data breach and the surge in AI-accelerated ransomware both show how a single unmanaged weakness becomes a whole-business event, much as the rise of rogue AI agents underlines why oversight of every dependency matters. Resilience is one discipline applied across the network, the cloud and the supply chain alike — not a product you buy once.
Find your single point of failure before your provider does
Cloudswitched designs, documents and manages resilient connectivity for UK SMEs — genuinely diverse lines on independent providers, automatic failover, mobile backup for the services that must never stop, and monitoring that catches a dropped line before your staff do.
Talk to us about Network AdminFrequently asked questions
Don’t let one provider’s bad day become your lost day
Brawband’s customers had no way to fix a core-network failure from their own premises — but the businesses among them with diverse lines and automatic failover barely noticed it. Cloudswitched’s Network Admin service finds your single points of failure and designs them out, so the next provider outage is something you read about rather than something that stops you trading.
Talk to us about Network Admin


