New
#11
run in a backwards methodology
Start with tracert so open a cmd window and run
tracert www.google.com
The first entry in the sequnce will be your router so it should be low like in this example it is saying it is < 1ms which is fast.
1 <1 ms <1 ms <1 ms blayblah [yourRoutersIp]
2 xxx xxx xxx xxx xxx
3....
etc
You should see a hop or a few in the list that will say like your ISP's name this will be the ISP node/s that you are sending data through and if it is unreasonably high ms then you know its an ISP problem like anything over a few hundred ms is considered high 1000ms or 1 second is high etc.
if you have high round trip time like high ms after the ISP then that means the hop route to google.com after your ISP is slow.
seeing as you have internet connection then we would not expect to see anything out of the ordinary with tracert but it can still show some basic things when diagnosing connection issues.
This is not a true reflection of your upload speed but it is going to show you systematically that your connection to the internet is working as intended as it can show any potential for slow data.
Realistically though low upload speed will be from the ISP and one other area is to know if are on a CGnat based connection as this will affect things like speeds.
You will also want to make sure that your router has the most recent firmware update installed. You also want to be testing this between WiFi and Ethernet cable as WiFi introduces all sorts of problems for various reasons.
Outside of all this and you feel confident that your network is working as intended like your lan your router etc then you will basically just need to correspond with your ISP and state that you are not getting what you pay for.