document internet connection problem
How to document an Internet problem for your provider
Support cannot do much with “Internet is slow.” Dates, consistent conditions, repeated results and precise symptoms are far more useful. The goal is not absolute proof, but a record that another technician can verify.
Describe the symptom before the number
State the affected activity, frequency, devices and times. Separate outages, low throughput, high latency and instability, and note which tests remain normal.
Collect comparable measurements
Create a wired reference and document Wi-Fi separately. Keep the server, time, VPN state, subscribed speed, equipment and competing traffic, including failed measurements rather than only the best result.
What the provider can still verify
The provider can inspect optical levels, access errors, synchronization, incidents and line configuration that FiberPulse cannot see. It may require its own official protocol before service or compensation.
Why local history matters
FiberPulse measures directly to the selected M-Lab server and stores the exact context locally. A provider cannot rewrite that local history, but routing and traffic treatment can still influence measurements, which is why the report remains indicative.
Frequently asked questions
Does a speed report force the provider to act?
Not automatically. It makes diagnosis easier, while the contract, regulation and official process determine the next steps.
Does FiberPulse replace the provider’s test?
No. It offers an independent structured observation that should be completed through the competent official procedure.