Maintenance
Part of Business internet: 4 differences from home service and 7 questions to ask
Business Internet Troubleshooting: A Short Method
Business internet troubleshooting uses narrowing questions, a wired speed-test baseline, a cellular check, and a fault log for test results and router logs.
Business internet troubleshooting starts with evidence, not a guess. "The internet is slow" is not a fault report. It is a symptom that could mean twelve different things, and the reason support calls go badly is that both sides start from the symptom and guess.
This page is organized by symptom. Each one has a set of questions that narrow it, and a test that usually settles it. The method behind all of it, and the records that make it possible, are in setup and troubleshooting.
Make a baseline and fault log
While the connection is working, connect a computer by Ethernet and run Speedtest by Ookla. Record the date and time, test location and device, and the reported download, upload, and ping or latency results; save a screenshot or copy the results into a spreadsheet or support log. When a fault appears, repeat the test from the same wired setup at the same time of day.
Copy these fields into a new entry for each incident:
- Start and end time; affected people, devices, and services; and whether the issue affected wired or wireless users.
- What failed and in which direction, such as slow uploads, dropped connections, or inbound calls.
- Wired test results, any cellular comparison, router-log events, actions taken, and whether service recovered.
To find drop records, sign in to the router’s admin interface and look for a System or Event log and an Internet or WAN status or connection log. Labels vary by model; note upstream reset times and save relevant log details before rebooting or resetting the router.
What to take away
- Every symptom narrows fast with three questionswho is affected, when, and in which direction.
- A test from a mobile on cellular separates "our connection" from "the thing we are trying to reach" in thirty seconds.
- The symptoms that come and go are the ones to write down, because they are only solvable as a pattern.
"It is slow"
Who? One person: their device or their wireless. Everyone: the router, the line, or something using all of it.
What saturates upload
- Offsite backups running during the day
- File synchronisation on many machines
- Cloud camera systems
- One machine uploading something enormous
When?
Which direction?
It is slow
- Offsite backups running during the day.
- File synchronisation on many machines at once.
- Cloud camera systems.
- One machine uploading something enormous.
Test. From a wired machine, run Speedtest by Ookla at the same time of day and compare the download, upload, and ping results with the saved baseline. If the results match, look for demand or a local issue; if they are consistently different, record the readings as evidence for a fault report. Compare any shortfall with the performance commitment in your service agreement; an overview of business-grade service commitments is in business internet.
"It keeps dropping"
The word "drop" hides two different events. A wireless disconnection, where
Wireless drop or line drop
Router log shows upstream resetting?
line or router fault
problem inside the building
It keeps dropping
- Look at the router's log for the times of the drops. If the router shows the upstream connection resetting, it is the line or the router. If it shows nothing, it is inside the building.
- Note whether the drops cluster at particular times or follow particular activity, such as heavy rain, the lift running, or the kettle going on in a cabinet that shares its socket.
- Check whether wired machines are affected when wireless users complain.
Intermittent line faults are the hardest to get fixed because the provider tests the line when it is working. A list of drop times from the router log, over a week, is what turns "it keeps dropping" into a fault they can find.
"Calls are bad but the web is fine"
The connection is up; the path may not be good enough for voice. Delay variation and loss affect calls long before browsing, and a large upload can starve calls unless the router prioritizes them; this is often a network configuration problem. For each bad-call report, record the call time, incoming or outgoing direction, and whether audio is delayed, one-way, or dropped; ask your VoIP provider to review its call-quality diagnostics. The FCC's Broadband Speed Guide explains why a speed-test figure alone is not the property a call depends on; more configuration checks are in VoIP systems.
"Nobody can reach us from outside"
Things that must accept inbound connections, such as remote access, an
Inbound access checks
- Has the public address changed?
- Is emergency calling affected?
- Does the service give a public address?
- Has the forwarding rule survived an update?
- Has the address changed? A service without a fixed address can change it at any restart, and anything configured against the old one stops.
- Is emergency calling affected? If the phones run over this connection, the address passed with such a call is a record your provider holds, as the FCC's guide to VoIP and 911 service explains. Confirm it rather than testing it.
- Does the service give you a public address at all? Some, particularly cellular ones, do not, and the fix is a plan option or a design change. Shared addressing on cellular services is covered in 5G business internet.
- Has the router's forwarding rule survived a firmware update or a factory reset? These get lost more often than they get changed.
Test. From a mobile on cellular, try to reach the thing. If it works from inside the building but not from the mobile, the problem is in the address or the router, not the service you are trying to reach.
"One site or service is unreachable, everything else works"
The connection is fine. The path to that one destination is not, or the
One destination unreachable
Fails from mobile on cellular?
it is them
path or name resolution
One site or service is unreachable
- Try it from a mobile on cellular. If it fails there too, it is them.
- Try it by address rather than by name, if you know how. If that works, the problem is name resolution, and changing which resolver the router uses is a legitimate fix.
- Ask whether that organization has recently restricted where they accept connections from. If your address changed lately, you may have fallen off a list.
"It works on a cable but not on wireless"
Then it is not the internet, and the provider cannot help. The issue is likely coverage, wireless congestion, interference, or an access point needing attention.
If a wired machine beside the struggling laptop is fine, treat it as a building problem.
"It came back on its own"
The most important symptom on the page, because it will happen again.
Log a self-healing fault
- Time it stopped
- Time it returned
- Who was affected
- What the router log shows
A fault that resolves itself three times without being logged is a fault that will resolve itself a fourth time at the worst possible moment.
Common questions
Should I call the provider straight away?
Call once you know whether it affects everyone, whether it affects everything, and what their box's lights are doing. Those three facts are what the first five minutes of the call would otherwise be spent finding.
The provider says it is my equipment. How do I know?
Plug a single known-good laptop directly into the provider's box, bypassing your router, and repeat the test. If the problem vanishes, it was yours. If it persists, it is theirs, and you can say so with evidence.
Can a second connection stop most of this?
It stops the outage kind. It does not stop the slow-at-four-o'clock kind or the wireless kind, which are inside the building. A radio second path such as fixed wireless is the common choice for the outage kind.
How do I stop the same fault recurring?
Log it, find the pattern behind it, and fix that. Restarting things fixes the symptom and preserves the cause.
