It Wasn't the Internet. Not Yet, Anyway.

It started with lightning.

A strike hit the house, and the home network never really came back right afterward. Devices dropped off. The internet felt slow and unreliable. By the time we got the call, the homeowner had reached the conclusion most people reach: "It's Cox. The internet is terrible, and I'm done with them."

He might be right. Cox may well be part of the problem. But when we arrived, the house couldn't tell us either way. Blaming the internet provider only works if everything on your side of the modem is healthy, and nobody had checked.

So we did it in order.

Step 1: Get eyes on the network

To his credit, the homeowner had the right idea. In a house of more than 6,500 square feet, one router in a closet was never going to cover it, so he'd bought good equipment: six TP-Link Omada Wi-Fi 7 access points. He just didn't go far enough. What he didn't have was anything that could show what was happening between those access points. They hung off a basic unmanaged switch, which passes traffic but reports nothing.

We replaced it with an Omada Access Pro PoE switch and added it to the same Omada cloud site as the access points. For the first time, the whole network (switch, access points, and every connected device) was visible in one place.

Step 2: Find what was missing

That visibility showed the real problem quickly. Only five devices were connected.

The Wi-Fi had been set up with the newest security and Wi-Fi 7 features switched on: WPA3-only security and multi-link operation. They look great on a spec sheet. But garage door openers, thermostats, irrigation controllers, and plenty of other smart home devices are built on older Wi-Fi chips, and they simply can't join a network set up that way. They weren't dropping off. They were never getting on.

We moved the network to WPA/WPA2 security, which newer phones and laptops still handle well, and turned off the settings the older devices couldn't use. We kept the network name and password exactly as they were, so nothing in the house had to be set up again.

Connected devices went from 5 to 33. Then we checked signal strength across the house to make sure every device had a solid, reliable connection, not just a connection.

Step 3: Name everything

Most home networks are a list of devices nobody can identify: a MAC address, maybe a manufacturer, no name. You can't troubleshoot what you can't identify.

We traced every device on the network, wired and wireless, looked up who made it, matched it to what it actually is and where it lives in the house, and labeled it in the Omada controller. A garage door opener is now labeled as that garage door opener, not a string of hex.

Step 4: Write it down somewhere the homeowner can find it

All of it went into a private network record for the home: the gateway, the switch, each access point, the Wi-Fi settings, every labeled device, and recommended next steps. Only the homeowner can open it. He signs in with his email address and a one-time code.

The passwords are on that page too, which needs a word of explanation, because it's the part people ask about.

The passwords aren't actually stored on the page. They live in an encrypted Bitwarden vault. When the homeowner presses Reveal, the page confirms it's really him, fetches that one password from the vault right then, and shows it. After two minutes it hides again. The Wi-Fi password also comes with a QR code his phone camera can scan to join, which is handy when guests visit.

Nothing sits in the page, and nothing is saved along the way. If someone took a screenshot of the page yesterday, they'd have a list of masked fields.

Step 5: Now watch the internet line

With the inside of the house healthy, the original question is fair again: is it Cox?

We don't guess at that. We measure it. Every two minutes, a server in Dallas checks the connection on the outside of his Cox gateway and records how fast it answers (latency), how steady that response is (jitter), and whether anything gets lost along the way (packet loss). Every outage is logged with a start and end time.

The homeowner has a live page showing all of it. (Here's a page like this for our founder's own internet connection, where it tracks Cox alongside a Starlink backup line.) Over the coming weeks that data becomes a baseline. If Cox is the problem, he'll have dated, timestamped evidence to put in front of them. If it isn't, he saves himself a provider switch that wouldn't have fixed anything.

What comes next

This phase was about getting the house back to healthy and making it visible. We've also laid out recommendations for a next phase, built with the future in mind: equipment that can carry faster internet plans as they arrive, and a second internet connection with automatic failover, so if the main line ever goes down, the house switches over on its own. None of that is urgent today. It's there for when he decides he needs it.

The takeaway

When the internet feels bad, the provider is the easiest thing to blame, and sometimes it's the right answer. But it's rarely the first thing to check. Work from the inside out: see the network, get every device connected properly, write it all down, and then measure the line. Whatever the answer turns out to be, you'll actually know it.

If your home network feels unreliable and you're not sure where the problem is, get in touch. We'll start with the part you can't see.