Seeing the problem before the subscriber calls

"Slow" is not a diagnosis

A subscriber reports a symptom. The provider has to convert it into a cause, usually over the phone, usually with someone who cannot be expected to describe their own network.

The causes are a short list and they need entirely different responses: the upstream line, the wireless environment inside the premises, a second router creating a double-NAT situation, or one device consuming everything. Guessing wrong costs either a truck roll or a repeat call.

Diagnosis belongs where the evidence is

All four of those causes are visible from the gateway and from almost nowhere else. It is the one point that sees the upstream line, the local wireless, and every device behind it at the same time.

Moving diagnosis there changes the shape of support: the question stops being "what is wrong?" and becomes "which of these known conditions is present?"

What that is worth

• Fewer truck rolls for conditions that were never on the provider's side.
• Calls that start with a cause instead of an interrogation.
• Conditions that can be spotted before the subscriber notices them.

EWUS Network is built for this shape of support. On what is live today versus what is still specification, the site says so plainly rather than presenting the whole picture as shipped: the diagnostic capabilities are described as designed behaviour and marked as such where a built-or-roadmap ruling is still outstanding.