So what is Spanning Tree Protocol?

Spanning Tree Protocol, usually shortened to STP, is the system that keeps the network of switches inside a building from forming loops. A loop is simply more than one path between the same two points, and on a local network a loop is surprisingly dangerous.

It was invented by Radia Perlman back in 1985 and later written into an international standard, and the basic job hasn’t changed since: let a network have backup links for resilience, while making sure those backups never quietly form a loop that brings everything down.

You can think of it as a referee for your cabling. It looks at every possible path through the network, picks a sensible set that reaches everywhere without doubling back, and benches the rest until they’re needed.

Why a loop is so dangerous

Inside an office, switches move traffic around by flooding certain messages to every port until they learn where everything lives. If there are two paths between two switches, those messages can go round and round the loop, forever, multiplying as they go.

Within seconds you get what’s called a broadcast storm: the network fills with the same traffic echoing endlessly, the switches are overwhelmed, and real traffic can’t get through. To everyone in the building it looks like the whole network has simply died, all at once.

The cruel irony is that loops are usually created with the best of intentions. You add a second cable between two switches so there’s a backup if one fails. Without something watching over it, that act of caution is exactly what creates the loop.

How STP keeps the peace

STP’s solution is rather elegant. All the switches talk to each other and elect one of them as the reference point, the root. Each switch then works out its best path back to that root and quietly switches off any other path that would create a loop. The blocked links aren’t gone; they’re held in reserve.

The clever part is what happens when something fails. If the main link a switch was using goes down, STP notices, recalculates, and brings one of those reserved backup links into service. You get the resilience of having spare cabling without the danger of a loop. The wider internet runs on the same idea one level up, healing around failures out on the backbone. You plug in two paths for safety, and STP makes sure only one of them is ever live at a time.

Why this matters if you run a business

Like a lot of networking, STP is something you’ll never touch directly. Your switches handle it, and a well-built network has it working sensibly from day one. But it’s worth understanding for two opposite reasons.

The first is resilience. STP is the mechanism that lets a network have backup links at all. A properly designed network can lose a cable or a switch and keep running, because a spare path quietly takes over. That only works if the network was built with redundancy in mind, rather than as an afterthought.

The second is fragility. When STP is missing, misconfigured, or running on cheap unmanaged switches that don’t support it, a single careless loop can take everything down.

The hospital that went back to paper

The classic cautionary tale is Beth Israel Deaconess Medical Center in Boston. In November 2002 a single application began looping data across a network built almost entirely on simple switches that leaned heavily on spanning tree. The result was a network meltdown that came and went for the best part of four days. Staff fell back to paper records, lab results that normally took 45 minutes took five hours, and the emergency department had to divert patients. The network ended up being rebuilt from the ground up.

The everyday version

Most loops are far less dramatic. The common one is mundane: someone tidies a cupboard and plugs both ends of a spare cable into the same switch, or daisy-chains a little desk switch back into the wall. On a network with STP doing its job, that mistake is spotted and the offending path is blocked before anyone notices. On a network without it, the office goes dark until someone physically finds the cable.

You add a second cable for safety, and on a network without spanning tree, that very act of caution is what takes the whole office down.

The practical takeaway

You don’t need to learn spanning tree. You need a network that was set up by someone who has. In practice that comes down to a few things:

• Use proper managed switches. The cheapest unmanaged kind often don’t run spanning tree at all, which is precisely how an accidental loop turns into an outage.
• Design in redundancy on purpose. Backup links only help if the network was built to use them, with spanning tree configured to match, not bolted on later and hoped for.
• Switch on the modern safeguards. Newer versions and features, with names like RSTP, BPDU Guard and loop protection, make the network recover faster and stop a stray cable causing chaos. A good setup turns them on, and turns off the insecure ones, like automatic trunking.
• Keep an eye on it. Knowing that a backup link has taken over, or that something has started looping, before it spirals is the difference between a non-event and a very bad afternoon.

The short version

Spanning Tree Protocol is the referee that lets your network have backup cabling without those backups forming a loop that takes everything down. You’ll never configure it, but whether it’s set up properly is the difference between a spare link that quietly saves you and a single loose cable that floors the whole office.

The bottom line

Spanning Tree is one of those quietly brilliant pieces of plumbing that has been holding networks together since the 1980s. When it’s set up well you never think about it: links fail, backups take over, and nobody notices. When it’s missing or done badly, an ordinary mistake can take down everything at once.

The lesson for a business isn’t to understand the protocol. It’s to make sure the network underneath you was built properly, with real redundancy, sensible switches and the modern safeguards switched on, so that a single cable never gets to decide how your team’s afternoon goes.

If you’d like someone to take an honest look at how resilient your network actually is, that’s exactly the kind of thing we enjoy getting stuck into.

The post Spanning Tree Protocol (STP) Explained appeared first on Orbit Computer Solutions.

So what is BGP?

BGP stands for Border Gateway Protocol. In plain terms, it’s the standardised system the internet uses to exchange routing and reachability information between large networks. That’s the textbook definition, and it really is the heart of it, so let’s unpack it.

The internet isn’t a single network. It’s tens of thousands of separate networks stitched together: internet service providers, cloud platforms, mobile carriers, universities and big companies. Each of these is called an autonomous system, and each has its own number, an ASN, a little like a telephone area code.

BGP is the common language those networks use to talk to one another. Each one announces, in effect, “here are the ranges of internet addresses I can deliver traffic to,” and BGP gathers up all of those announcements so that any network can work out a path to any other. Without it, the separate pieces of the internet would have no agreed way to find each other.

The internet’s road signs

A helpful way to picture BGP is as the road signs and sorting office of the internet, rather than the vehicles or the roads themselves.

BGP doesn’t carry your data. It works out the route that data should take. Every network advertises which destinations it can reach and which neighbours it connects to. Routers then compare the available paths and choose the one that looks best, usually the one that crosses the fewest networks to get there.

Because every route carries a record of the networks it passes through, the system can avoid sending traffic round in circles, and each network gets to apply its own preferences about which way to send things. It’s updating constantly, too. If a link goes down somewhere, BGP notices that a route has disappeared and the rest of the internet quietly reroutes around the gap, often before anyone notices.

Why this matters if you run a business

You’ll almost certainly never configure BGP yourself. That job sits with your internet provider and your hosting or cloud platforms. But BGP underpins nearly everything your business relies on online: your website being reachable, your email arriving, your cloud software loading, your card payments going through.

The reason it’s worth knowing the name is that when BGP goes wrong, it tends to go wrong in a big, visible way. A few well-known examples make the point.

The day Facebook vanished

In October 2021, Facebook, Instagram and WhatsApp disappeared from the internet for around six hours. Nothing had been hacked. A faulty internal change withdrew the BGP routes that told the rest of the world where to find Facebook’s systems. The servers were still running; the directions to them had simply been erased, and for a while billions of people couldn’t load the sites at all. It rhymes with the internet’s address-book failures, where the names stop resolving instead.

Traffic sent the wrong way

Because networks largely take each other’s BGP announcements on trust, it’s possible for one to claim, by mistake or on purpose, that it can reach addresses it has no business handling. The result is a route leak or a BGP hijack: traffic meant for one place gets pulled somewhere else, causing outages or, in the worst case, giving someone the chance to snoop on it. It has happened to banks, payment networks and large online services.

The “512k day”

Back in 2014, the global list of internet routes grew past a limit that a lot of older routers had been set up to hold, around 512,000 entries. Hardware around the world started misbehaving on the same day, and chunks of the internet slowed or dropped out. It was a useful reminder that even the internet’s plumbing has finite limits that have to be managed.

BGP is one of those foundations you only ever meet on the day it fails. The rest of the time, it works silently, which is exactly why so few people have heard of it.

The practical takeaway: stay reachable

For most small and growing businesses, the lesson isn’t to go and learn BGP. It’s to make sure your business isn’t sitting on a single weak link. A few sensible habits cover most of it:

• Choose well-connected providers. Good hosting and cloud platforms reach the internet through several networks at once, so if one path has a bad day your services stay reachable through another. That’s the resilient version of what BGP makes possible.
• Have a fallback for your own connection. A second line or a mobile failover means one provider’s outage doesn’t take your whole office offline with it.
• Keep an eye on your systems. Monitoring that tells you something has become unreachable, ideally before your customers find out, turns a quiet crisis into a quick phone call.

A word on security

BGP was designed decades ago, in a more trusting era, and it largely assumes networks are telling the truth about which addresses they can reach. That assumption is exactly what makes hijacks possible.

The wider industry has been steadily fixing this with measures that let networks verify whether a route really is coming from its rightful owner. You don’t need to implement any of that yourself. It’s simply one more reason to choose infrastructure providers who take it seriously, and to treat the security of your connectivity as part of the picture rather than an afterthought.

The short version

BGP is the set of directions that lets the internet’s thousands of separate networks find one another, so your data reaches the right place. You’ll never touch it. But the providers you build on either look after it well, with good connections and sensible security, or they don’t, and that difference tends to show up on the day something breaks.

The bottom line

Almost all of the time, BGP works flawlessly and invisibly. When it does break it’s dramatic, and it’s usually entirely out of your hands. What is in your hands is what you choose to build on. Solid, well-connected hosting, a connection with a fallback, and a bit of monitoring all mean the rare bad day out on the wider internet is far less likely to become a bad day for your customers.

If you’d like a straightforward look at how resilient your connectivity and hosting actually are, with no jargon and no pressure, that’s exactly the kind of conversation we enjoy having.

The post So what is BGP? Border Gateway Protocol Explained (2026) appeared first on Orbit Computer Solutions.

The internet’s address book

Computers do not find each other by name. They find each other by number, an IP address, a string like 172.217.16.196 that means nothing to a person and everything to a machine. DNS is the system that translates between the two, turning the orbit-computer-solutions.com you type into the numbered address your browser actually connects to. It is, in the well-worn phrase, the address book of the internet.

The lookup itself is a short relay race that runs behind the scenes:

1. Your device asks a resolver, usually run by your internet provider (one it was handed automatically when it joined the network), “where do I find this name?”
2. If the resolver does not already know, it works up the chain, asking the servers responsible for that domain.
3. The answer, an IP address, comes back, and gets remembered for a while so the next lookup is instant.
4. Your browser connects to that address, and the page loads.

All of that finishes in the blink before a page appears, millions of times a second, all over the world.

The day the address book went down

The best way to appreciate DNS is to watch what happens when it fails. On 21 October 2016, a company called Dyn, which ran the DNS for a large slice of the web, was hit by a huge attack. The websites themselves were perfectly fine. Their servers were running and their data was intact. But with Dyn’s DNS knocked offline, the rest of the internet could no longer look up where they were. For much of a day, Twitter, Spotify, Reddit, Netflix and dozens of others were unreachable for millions of people, not because they were down, but because nobody could find them.

That is the strange power of DNS. It does not store your website or your email. It only holds the directions to them. Lose the directions, and everything else may as well not exist. It is the same fragility behind the internet’s great routing outages, where the paths between networks vanish rather than the names.

Why it matters for your business

You depend on DNS far more than you might think, and usually through a handful of records most business owners have never seen. One record points the world at your website. Another, the MX record, tells the world where to deliver your email. Others quietly vouch that your email is genuine and help it land in inboxes instead of spam folders. Set out in the standards back in the 1980s and barely changed since, these records are the foundation almost everything else sits on.

Which is exactly why DNS mistakes hurt so much. A single mistyped record can send your email into a black hole. A lapsed domain can take your entire online presence offline overnight. A change made carelessly can take hours to ripple out across the world’s resolvers, a delay known as propagation, during which some visitors see the new version and some the old. None of these are exotic failures. They are ordinary slips, and they are common precisely because DNS is so easy to ignore until it bites.

Looking after it

For a business, DNS is not something to manage day to day. It is something to get right once and then leave well alone, in the hands of someone who treats it with care. In practice that comes down to a few quiet habits: never letting the domain registration lapse, knowing exactly who controls your DNS records, changing them deliberately rather than in a rush, and using a dependable DNS provider rather than whatever came bundled years ago. It is also worth checking it does not quietly slip out of the tunnel when your team is on a VPN.

It is unglamorous, and that is rather the point. Good DNS is invisible. The only time you are likely to think about it is the day something goes wrong, and the entire aim is to make sure that day never arrives.

The post DNS Explained: the internet’s address book, and the day it failed appeared first on Orbit Computer Solutions.