F5F Stay Refreshed Power Users Networks Packet loss jumped to 126% abruptly!

Packet loss jumped to 126% abruptly!

Packet loss jumped to 126% abruptly!

Pages (2): 1 2 Next
T
ThePenguGodmc
Junior Member
48
03-29-2016, 02:41 PM
#1
How bad is this...? http://imgur.com/a/bUmxbN6 Checked cables, reset router... No change. It's just odd because I never had this before today, it was always 0% packet loss so not sure if this is an error or what.
T
ThePenguGodmc
03-29-2016, 02:41 PM #1

How bad is this...? http://imgur.com/a/bUmxbN6 Checked cables, reset router... No change. It's just odd because I never had this before today, it was always 0% packet loss so not sure if this is an error or what.

A
AA_Fischer
Junior Member
4
04-04-2016, 06:16 AM
#2
Contact your internet service provider.
A
AA_Fischer
04-04-2016, 06:16 AM #2

Contact your internet service provider.

S
samsammie
Junior Member
9
04-04-2016, 08:32 AM
#3
It's okay if you feel confused—asking for more details is normal when dealing with a glitchy app.
S
samsammie
04-04-2016, 08:32 AM #3

It's okay if you feel confused—asking for more details is normal when dealing with a glitchy app.

T
TheBearForce
Junior Member
4
04-04-2016, 02:59 PM
#4
I just pinged Google... 30 packets sent, 0% loss So it *does* look like Ookla is f^ once again... Not the first time, just the first time it's showing me high packet loss, constantly... And you're almost right, because I did call my ISPs sometimes and they *will* tell you if there's a general issue at least usually so you know if it's an issue on their end most likely or not - but it can also be they'll say there's nothing, so yeah.
T
TheBearForce
04-04-2016, 02:59 PM #4

I just pinged Google... 30 packets sent, 0% loss So it *does* look like Ookla is f^ once again... Not the first time, just the first time it's showing me high packet loss, constantly... And you're almost right, because I did call my ISPs sometimes and they *will* tell you if there's a general issue at least usually so you know if it's an issue on their end most likely or not - but it can also be they'll say there's nothing, so yeah.

S
Streiyn
Posting Freak
768
04-04-2016, 08:08 PM
#5
Using speed tests on packetoss will consistently show packet loss. This behavior is part of how TCP functions and its algorithms operate. Try testing with sites like fast.com or others before drawing conclusions. No, simply reporting packet loss in a speed test app isn't the best approach. While they can identify issues, packet loss often has more nuanced causes.
S
Streiyn
04-04-2016, 08:08 PM #5

Using speed tests on packetoss will consistently show packet loss. This behavior is part of how TCP functions and its algorithms operate. Try testing with sites like fast.com or others before drawing conclusions. No, simply reporting packet loss in a speed test app isn't the best approach. While they can identify issues, packet loss often has more nuanced causes.

S
Sllendy
Junior Member
20
04-04-2016, 09:33 PM
#6
Several thousand tests on my app show different results (0%), but that's okay.
S
Sllendy
04-04-2016, 09:33 PM #6

Several thousand tests on my app show different results (0%), but that's okay.

F
FeuerLuke
Junior Member
14
04-05-2016, 06:31 AM
#7
It's near worthless to call them because unless it's an issue effecting everything and causing actual application problems and downloads to fail then either there is misreporting of packet loss in the application or the fault is not within the control of the ISP so would be pointless to ring them. You'll know when you have an actual problem with your connection because you'll have trouble using it at all, for anything. When that happens the problem is almost always between your house and the road side distribution. Internet is just a giant Jenga tower where every block is a different person/entity, only takes one of them to make the tower fall over. Oh and there is a Jenga tower per service/website so good luck trying to actually find root cause of issue when nobody has any real overall insight at all. Also that picture of yours shows negative packet loss which is clearly just a math error/bug. Negative loss is impossible and so is more than 100%, unless your network has found a way to create packets from nothing (magic maybe?).
F
FeuerLuke
04-05-2016, 06:31 AM #7

It's near worthless to call them because unless it's an issue effecting everything and causing actual application problems and downloads to fail then either there is misreporting of packet loss in the application or the fault is not within the control of the ISP so would be pointless to ring them. You'll know when you have an actual problem with your connection because you'll have trouble using it at all, for anything. When that happens the problem is almost always between your house and the road side distribution. Internet is just a giant Jenga tower where every block is a different person/entity, only takes one of them to make the tower fall over. Oh and there is a Jenga tower per service/website so good luck trying to actually find root cause of issue when nobody has any real overall insight at all. Also that picture of yours shows negative packet loss which is clearly just a math error/bug. Negative loss is impossible and so is more than 100%, unless your network has found a way to create packets from nothing (magic maybe?).

S
spikerdog89
Member
143
04-06-2016, 03:29 PM
#8
S
spikerdog89
04-06-2016, 03:29 PM #8

A
Amorphous_360
Member
65
04-07-2016, 12:49 AM
#9
I'd prefer Windows CMD or Linux Terminal for a more accurate view of packet loss than an online speed test. Try a ping, keep it running for 5 minutes, 15 minutes or longer if you're comfortable. Note any packet loss that appears. If the client shows minimal or no loss, Ookla's percentage will be significantly inaccurate—particularly since it would be a negative value above 100%. That doesn't make sense.
A
Amorphous_360
04-07-2016, 12:49 AM #9

I'd prefer Windows CMD or Linux Terminal for a more accurate view of packet loss than an online speed test. Try a ping, keep it running for 5 minutes, 15 minutes or longer if you're comfortable. Note any packet loss that appears. If the client shows minimal or no loss, Ookla's percentage will be significantly inaccurate—particularly since it would be a negative value above 100%. That doesn't make sense.

X
Xtun3r
Member
154
04-07-2016, 11:34 AM
#10
Sure, just to clarify, the negative sign confused me at first, but it seems like a server problem. I checked multiple test servers and still got no packet loss—30 pings in CMD worked fine. Likely everything is okay.
X
Xtun3r
04-07-2016, 11:34 AM #10

Sure, just to clarify, the negative sign confused me at first, but it seems like a server problem. I checked multiple test servers and still got no packet loss—30 pings in CMD worked fine. Likely everything is okay.

Pages (2): 1 2 Next