Back to News

Brawband’s Core Network Meltdown Left Scotland Offline All Day — The Network Resilience Lesson for UK SMEs

Brawband’s Core Network Meltdown Left Scotland Offline All Day — The Network Resilience Lesson for UK SMEs

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.

~Midnight
When the core-network fault began on 5 Aug 2026
4 areas
Inverness, Glasgow, Renfrewshire & Edinburgh hit
Full rebuild
Core equipment had to be rebuilt to restore service
1 circuit
All it takes to put a whole business offline

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.

Why a core-network failure is the outage you cannot fix yourself

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.

Around midnight, 5 Aug 2026 — The fault begins
Brawband’s broadband service starts failing in the small hours as a fault develops on its core network. With most customers asleep, the problem builds quietly overnight before anyone is in a position to report it.
Early morning — Reports multiply as people wake up
As households and businesses come online for the working day, they find no connection. Reports grow rapidly and span multiple locations at once — Inverness, Glasgow, Renfrewshire and Edinburgh — the tell-tale spread of a central rather than local fault.
Morning — The fault is traced to the core network
Brawband identifies the problem as sitting on its own core network. It becomes clear this is not a last-mile issue but a failure in the central equipment that carries every customer’s traffic.
Morning — A full rebuild is required
The provider tells customers the fix will need a full “rebuild of equipment”, described as “a significant piece of work which our technical engineers are treating with urgency”. This is not a reset; it is a reconstruction.
For several hours — No ETA at all
For a prolonged period Brawband is unable to give any estimated time to fix. Affected businesses have no way to plan around the outage — no signal on whether it will be minutes, hours or the rest of the day.
Midday — “Not by the end of the day”
A midday update warns customers the issue will not be resolved by the end of the day. For a business, that confirms a full working day lost to an outage entirely outside its control.
Throughout the day — Rivals on the same fibre stay up
Other ISPs delivering over the same CityFibre network in the same areas are not reporting equivalent outages, confirming the fault sits inside Brawband and HighNet’s own core rather than the shared CityFibre infrastructure.
Later on 5 Aug 2026 — Service restored after the rebuild
Once the core equipment rebuild is completed, connectivity returns. Customers are advised to power-cycle their routers to reconnect — the closing note on an outage that had lasted the best part of a working day.

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.

Single circuit, single provider
91%
No automatic failover configured
84%
VoIP phones on the same line as data
77%
Card payments dependent on one link
69%
No 4G/5G backup for critical services
62%
No tested business-continuity plan
54%
No named escalation route with the ISP
47%

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.

72%
Illustrative share of the business impact of a connectivity outage that stems from having a single, un-backed circuit — not from the provider fault itself, which resilient designs simply ride through

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.

Resilience gaps that turn a provider outage into a lost day
One circuit from one provider, with no second path High
No automatic failover — any switchover is manual High
VoIP phone system riding the only internet line High
Card payments dependent on that same single link High
No 4G/5G mobile backup for critical services Mid
Second line quietly reselling the same wholesale core Mid
No monitoring to alert staff the moment the line drops Mid
No documented escalation contact or fix-time expectation Low

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.

34
Typical SME connectivity-resilience readiness, out of 100

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.

Practical step you can take this week

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 Admin

Frequently asked questions

What is a “core network” and why did the Brawband fault take everyone offline at once?
A provider’s core network is the central layer of switching and routing equipment through which every customer’s traffic passes on its way to and from the wider internet. Unlike the “last mile” — the cable and router at each premises — the core is shared by all customers. When it fails, everyone on that provider goes offline simultaneously, which is exactly why Brawband’s fault surfaced across Inverness, Glasgow, Renfrewshire and Edinburgh at the same time. Because it is central infrastructure, nothing a customer does on their own premises can fix it; they can only wait for the provider’s engineers to repair or, in this case, rebuild it.
Brawband resells over CityFibre — so was this CityFibre’s fault?
No. Brawband delivers full-fibre services over CityFibre’s wholesale network, but the evidence points to the fault sitting in Brawband and HighNet’s own core rather than in the shared CityFibre infrastructure. The clue was that other ISPs using the same CityFibre network in the same Scottish areas were not reporting equivalent outages. If the shared fibre had been the problem, those providers would have been hit too. The failure was in the part of the chain Brawband builds and operates itself, which is why only its customers were affected.
Why couldn’t Brawband give an estimated fix time for so long?
Because the fault required a full “rebuild of equipment” rather than a simple reset or component swap. A rebuild of core network equipment is, in the company’s own words, “a significant piece of work”, and until engineers understand the full extent of the damage and the steps needed, any estimate would be a guess. That is why customers were left for several hours with no ETA, and why a midday update could only warn that the problem would not be resolved by the end of the day. Honest uncertainty from a provider is common in serious core failures — and it is precisely why a business should never depend on a fix time it cannot influence.
I already pay for two broadband lines — am I safe from this?
Not necessarily. Two lines only protect you if they are genuinely diverse — independent providers on independent core networks, ideally over different underlying infrastructure. If both of your lines ultimately resell the same wholesale network, or terminate in the same provider’s core equipment, they share a single point of failure and can go down together. The safest configurations pair a fixed line with a mobile (4G/5G) backup that touches none of the same infrastructure, or use two providers whose networks are known to be independent. A connectivity review can confirm whether your “two lines” are actually diverse or only diverse on the invoice.
What is automatic failover and how quickly does it switch?
Automatic failover is a router or SD-WAN configuration that detects when your primary line has stopped passing traffic and reroutes onto a backup connection without anyone intervening. A well-configured setup switches within seconds, so staff experience a brief blip rather than a dead line, and often keep working without realising anything happened. The key word is “automatic”: a manual failover that depends on someone noticing the outage, finding the backup and switching it over by hand will always be slower and is prone to being forgotten in the panic of a live outage. Failover should also be tested on a schedule, because an untested backup is only a hope, not a plan.
We use VoIP phones — what happens to them in an outage like this?
If your VoIP phone system runs over the same single internet line as your data, it dies the moment that line does — which for Brawband’s customers meant losing their phones for the best part of a working day alongside everything else. This is one of the most common and most damaging single points of failure we see, because a business that cannot answer its phones is often invisible to its customers. The fix is to make sure the phone system can fail over to a second path — a diverse line or a mobile backup — and to configure the VoIP platform to divert calls to mobiles automatically if the site connection is lost entirely.
How much does it actually cost to add resilience?
Far less than most owners expect, and far less than an outage. At the smallest end, a 4G/5G automatic failover router that keeps your critical services alive can sit within a £60–£120 monthly connectivity budget. A small business running two genuinely diverse lines with auto-failover is typically in the £150–£400 range, and larger or multi-site operations that want SD-WAN, managed monitoring and an SLA move into £500–£1,500 and above. These are planning ballparks rather than quotes, but the comparison that matters is against the cost of a full day — or several — unable to trade, which for most businesses dwarfs a year of the resilience that would have prevented it.
Is a mobile (4G/5G) backup really good enough for a business?
For keeping critical services alive through an outage, yes — and it is often the fastest, cheapest resilience win available. A 4G/5G backup uses a completely separate network from your fixed fibre, so a fault in your ISP’s core, or even in the fixed infrastructure at your postcode, does not affect it. It may not match full-fibre for raw speed, but it is more than enough to keep card payments, VoIP phones, email and cloud access working while the primary line is down. For many micro and small businesses, a mobile failover router is the single highest-value step they can take, and it can be in place within days rather than the weeks a second fixed line can take to provision.
How would a managed network admin service have changed the outcome?
A managed network admin service changes the outcome before the outage ever happens. It starts by mapping your connectivity to find the single points of failure — the shared line, the stacked services, the missing failover — and then designs them out with a genuinely diverse second path and automatic switchover. It adds monitoring so a dropped line raises an alert immediately, a documented continuity plan staff can follow on the day, and a named escalation route with the provider rather than the consumer support queue. Had Brawband’s affected businesses had that in place, the core rebuild would have been someone else’s problem to fix while their traffic quietly ran on the backup.
What is the first thing I should do after reading this?
Establish, honestly, what breaks if your internet stops right now. List your critical services — email, cloud applications, the phone system, card payments, remote staff access — and mark which ones depend on your single line with no fallback. That list is your risk register, and the items with no fallback are your single points of failure. From there the priorities usually order themselves: an automatic mobile backup for the most critical services first, then a genuinely diverse second line, then monitoring and a tested continuity plan. If you would rather not work through it alone, a connectivity review will do it with you and turn the findings into a concrete, costed plan.

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
Tags:Network AdminConnectivityIT SupportVirtual CIO
CloudSwitched

London-based managed IT services provider offering support, cloud solutions and cybersecurity for SMEs.

CloudSwitched Service

Network Admin Services

Server administration, infrastructure ops and proactive network management for UK businesses

Learn More

Technology Stack

Powered by industry-leading technologies including SolarWinds, Cloudflare, BitDefender, AWS, Microsoft Azure, and Cisco Meraki to deliver secure, scalable, and reliable IT solutions.

SolarWinds
Cloudflare
BitDefender
AWS
Hono
Opus
Office 365
Microsoft
Cisco Meraki
Microsoft Azure

Latest Articles

17
  • Google Ads & PPC

How to Measure Google Ads ROI and ROAS

17 May, 2026

Read more
11
  • Network Admin

Server Health Check Checklist for UK Businesses

11 Apr, 2026

Read more
11
  • IT Office Moves

Server Room Setup for Your New Office: A Planning Guide

11 Mar, 2026

Read more

Enquiry Received!

Thank you for getting in touch. A member of our team will review your enquiry and get back to you within 24 hours.