Fiber slow because of bad cable?

[cmb6062]

Lately our internet has been really bad, it was good for a while and then suddenly it got really bad, my dad thinks it is the wire, and when we wiggle a little bit or but it in and out we may get the normal speeds or the bad, but now we cant get the good, only bad, upload speed is almost where it is suppose to be, but download, far from it. We have had this problem before but it got fixed when we called our providers and they said it was something wrong with the wire, the next day it was suddenly fixed without them checking it out. we pay for 50 download and 20 upload.

 

Anyone got an idea how to fix this?

 

Nothing was being downloaded or uploaded during this speed test, its the same with all computers and phones in the house

Did another test, and got 24mb upload, its getting weirder

 

[amp88]

My first thought is that this could be caused by a significant amount of packet loss, which would be possible with a bad cable. There are a couple of ways to check for packet loss, but probably the easiest (assuming you're on Windows) is to run the following from command prompt:

ping -n 25 www.google.com

This will attempt to send 25 ping requests to www.google.com. Please report the results from the run. For example:

C:\Users\Gus>ping -n 25 www.google.comPinging www.google.com [216.58.211.164] with 32 bytes of data:Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=28ms TTL=51Reply from 216.58.211.164: bytes=32 time=28ms TTL=51Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=28ms TTL=51Reply from 216.58.211.164: bytes=32 time=28ms TTL=51Reply from 216.58.211.164: bytes=32 time=28ms TTL=51Reply from 216.58.211.164: bytes=32 time=29ms TTL=51Reply from 216.58.211.164: bytes=32 time=28ms TTL=51Reply from 216.58.211.164: bytes=32 time=28ms TTL=51Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=28ms TTL=51Reply from 216.58.211.164: bytes=32 time=28ms TTL=51Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=28ms TTL=51Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=28ms TTL=51Ping statistics for 216.58.211.164:    Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:    Minimum = 27ms, Maximum = 29ms, Average = 27ms

To copy from command prompt, right click and hit 'Mark', then drag-select the relevant text and hit your Enter key, and it should be copied to clipboard. When you reply, please use the 'CODE' tags (by clicking on the 'Code' icon in the editor, which looks like two angle-brackets: <>).

[legopc]

Maybe you should try contacting your isp with questions related to your isp.

[Ssoele]

You should blur out your IP better

[cmb6062]

My first thought is that this could be caused by a significant amount of packet loss, which would be possible with a bad cable. There are a couple of ways to check for packet loss, but probably the easiest (assuming you're on Windows) is to run the following from command prompt:

ping -n 25 www.google.com

This will attempt to send 25 ping requests to www.google.com. Please report the results from the run. For example:

C:\Users\Gus>ping -n 25 www.google.comPinging www.google.com [216.58.211.164] with 32 bytes of data:Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=28ms TTL=51Reply from 216.58.211.164: bytes=32 time=28ms TTL=51Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=28ms TTL=51Reply from 216.58.211.164: bytes=32 time=28ms TTL=51Reply from 216.58.211.164: bytes=32 time=28ms TTL=51Reply from 216.58.211.164: bytes=32 time=29ms TTL=51Reply from 216.58.211.164: bytes=32 time=28ms TTL=51Reply from 216.58.211.164: bytes=32 time=28ms TTL=51Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=28ms TTL=51Reply from 216.58.211.164: bytes=32 time=28ms TTL=51Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=28ms TTL=51Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=27ms TTL=51Reply from 216.58.211.164: bytes=32 time=28ms TTL=51Ping statistics for 216.58.211.164:    Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),Approximate round trip times in milli-seconds:    Minimum = 27ms, Maximum = 29ms, Average = 27ms

To copy from command prompt, right click and hit 'Mark', then drag-select the relevant text and hit your Enter key, and it should be copied to clipboard. When you reply, please use the 'CODE' tags (by clicking on the 'Code' icon in the editor, which looks like two angle-brackets: <>).

Pinging www.google.com [216.58.209.100] with 32 bytes of data:

Reply from 216.58.209.100: bytes=32 time=23ms TTL=51

Reply from 216.58.209.100: bytes=32 time=23ms TTL=51

Reply from 216.58.209.100: bytes=32 time=23ms TTL=51

Reply from 216.58.209.100: bytes=32 time=23ms TTL=51

Reply from 216.58.209.100: bytes=32 time=21ms TTL=51

Reply from 216.58.209.100: bytes=32 time=28ms TTL=51

Reply from 216.58.209.100: bytes=32 time=22ms TTL=51

Request timed out.

Reply from 216.58.209.100: bytes=32 time=23ms TTL=51

Reply from 216.58.209.100: bytes=32 time=22ms TTL=51

Reply from 216.58.209.100: bytes=32 time=23ms TTL=51

Reply from 216.58.209.100: bytes=32 time=23ms TTL=51

Reply from 216.58.209.100: bytes=32 time=23ms TTL=51

Reply from 216.58.209.100: bytes=32 time=24ms TTL=51

Reply from 216.58.209.100: bytes=32 time=23ms TTL=51

Reply from 216.58.209.100: bytes=32 time=23ms TTL=51

Reply from 216.58.209.100: bytes=32 time=22ms TTL=51

Reply from 216.58.209.100: bytes=32 time=24ms TTL=51

Reply from 216.58.209.100: bytes=32 time=23ms TTL=51

Reply from 216.58.209.100: bytes=32 time=23ms TTL=51

Reply from 216.58.209.100: bytes=32 time=23ms TTL=51

Reply from 216.58.209.100: bytes=32 time=22ms TTL=51

Reply from 216.58.209.100: bytes=32 time=22ms TTL=51

Reply from 216.58.209.100: bytes=32 time=23ms TTL=51

Reply from 216.58.209.100: bytes=32 time=23ms TTL=51

 

Ping statistics for 216.58.209.100:

    Packets: Sent = 25, Received = 24, Lost = 1 (4% loss),

Approximate round trip times in milli-seconds:

    Minimum = 21ms, Maximum = 28ms, Average = 23ms

[amp88]

Ping statistics for 216.58.209.100:

    Packets: Sent = 25, Received = 24, Lost = 1 (4% loss),

Approximate round trip times in milli-seconds:

    Minimum = 21ms, Maximum = 28ms, Average = 23ms

 

 

Apart from the 1 lost packet that looks quite good (relatively consistent and low ping). It might be worth running this command a few more times at different times of the day, to get an idea if there's a lot of variation (e.g. due to peak/off-peak hours and utilisation in your ISP's network).

 

It might be possible for you to request a visit from a technician from the ISP or telecommunications provider to assess the situation. Depending on their policies and the results of the visit you may have to pay for that, though...so it's something to look into.

[JustinBieber]

Your being limited.

 

Contact ISP.