Packet loss


#21

That’s mine Chilli, the time is so high because my net has always been stuffed with a capital S. Mine is based on a congestion issue, every night around the same times, my latency goes mad. The above ping test was done with no other PC using the net, nothing running in the background to effect my net such as uTorrent, it’s purely out of my control.

Here’s what it looks like now that most people are probably heading off to bed, you can immediately spot the improvement.

C:UsersADAM_MAIN>ping 192.231.203.132 -n 15

Pinging 192.231.203.132 with 32 bytes of data:
Reply from 192.231.203.132: bytes=32 time=18ms TTL=61
Reply from 192.231.203.132: bytes=32 time=19ms TTL=61
Reply from 192.231.203.132: bytes=32 time=20ms TTL=61
Reply from 192.231.203.132: bytes=32 time=19ms TTL=61
Reply from 192.231.203.132: bytes=32 time=45ms TTL=61
Reply from 192.231.203.132: bytes=32 time=20ms TTL=61
Reply from 192.231.203.132: bytes=32 time=20ms TTL=61
Reply from 192.231.203.132: bytes=32 time=19ms TTL=61
Reply from 192.231.203.132: bytes=32 time=23ms TTL=61
Reply from 192.231.203.132: bytes=32 time=23ms TTL=61
Reply from 192.231.203.132: bytes=32 time=21ms TTL=61
Reply from 192.231.203.132: bytes=32 time=19ms TTL=61
Reply from 192.231.203.132: bytes=32 time=25ms TTL=61
Reply from 192.231.203.132: bytes=32 time=20ms TTL=61
Reply from 192.231.203.132: bytes=32 time=19ms TTL=61

Ping statistics for 192.231.203.132:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 45ms, Average = 22ms

C:UsersADAM_MAIN>
That’s still not perfect either mind you, come midnight - early hours of the morning, I get a consistent ping of around 20ms with a ~1ms variance.

Some nights I get really bad packet loss, as in it drops every 3rd or 4th packet with consistency.


#22

i get 22-24ms, average of 23. D:


#23

That sounds bang on, iinsom.


#24

Just like clockwork, every night the later it gets, the better my latency becomes.

C:UsersADAM>ping 192.231.203.132 -n 15

Pinging 192.231.203.132 with 32 bytes of data:
Reply from 192.231.203.132: bytes=32 time=18ms TTL=61
Reply from 192.231.203.132: bytes=32 time=19ms TTL=61
Reply from 192.231.203.132: bytes=32 time=18ms TTL=61
Reply from 192.231.203.132: bytes=32 time=19ms TTL=61
Reply from 192.231.203.132: bytes=32 time=18ms TTL=61
Reply from 192.231.203.132: bytes=32 time=18ms TTL=61
Reply from 192.231.203.132: bytes=32 time=19ms TTL=61
Reply from 192.231.203.132: bytes=32 time=18ms TTL=61
Reply from 192.231.203.132: bytes=32 time=19ms TTL=61
Reply from 192.231.203.132: bytes=32 time=18ms TTL=61
Reply from 192.231.203.132: bytes=32 time=20ms TTL=61
Reply from 192.231.203.132: bytes=32 time=19ms TTL=61
Reply from 192.231.203.132: bytes=32 time=18ms TTL=61
Reply from 192.231.203.132: bytes=32 time=19ms TTL=61
Reply from 192.231.203.132: bytes=32 time=19ms TTL=61

Ping statistics for 192.231.203.132:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 20ms, Average = 18ms

C:UsersADAM>


#25

thats what mine was doing. Who is your ISP.

Congestion shouldnt be that fuked up surely.


#26

My ISP is Internode but I had the same problem with Telstra. What your seeing is congestion to the extreme, I basically think that they didn’t anticipate for the amount of people that would be getting ADSL in my neighbourhood when they upgraded the exchange for ADSL.

The thing is, Telstra is the wholesaler for ADSL here, so every ISP is paying rental fees to Telstra in order to use their lines. So it is Telstra that are obligated to fix this problem for me, but they are just very slow getting it done. It doesn’t matter which ADSL ISP I go with, I’ll have the same problem. They’ve accepted that their is a problem which is a start I guess.

I’m not sure whether this applies to ADSL 2 though as the ISP is allowed to use their own hardware in the exchange unlike regular ADSL which is limited to Telstra only. This is what I was told anyway.


#27

yer i expect the same thing is happening to me but im not gonna continue to pay for a bullshit service.


#28

Let me know how you go, they’ll throw excuse after excuse at you. Apparently Telstra do not care about your latency unless it is affecting your download speeds. That is the only way I got them to notice my issue because it was starting to affect me in that way. Packet loss is another great excuse to get them to notice your issue. They are too dumb to realise that low latency is in many ways more important for many people than line speed.

The only reason I don’t have too much of a problem with it is because I still manage to download my 40GB limit every month, means I miss out on a bit of gaming but the problem has been identified and now all I can really do is keep asking them for progress.