It seems currently (22:25 14/10/07) there is an improvement; however there is little network traffic at present.
The only IP that is still reporting packet loss is 96.30.31.120 (www.iburst.co.za) at hop 7 packet loss occurs after IP 66.8.42.22 and before IP 196.30.31.102.
Cape sites reflect: 65 ms ave.
Joburg sites reflect: 87 ms ave.
Intl. sites reflect: 405 ms ave.
216.239.38.10
216.239.38.10
Location:United States
Packets Sent:34
Packets Received:25
Packets Lost:9(26% loss)
Response time Minimum:415ms
Response time Maximum:738ms
Response time Average:361ms
smtp.saix.net
196.25.240.94
Location:South Africa
Packets Sent:66
Packets Received:61
Packets Lost:5(7% loss)
Response time Minimum:89ms
Response time Maximum:415ms
Response time Average:185ms
Yup... end of the month salty crax again... Ive wasted so much bandwidth this month
I had a lot of PC's on my network at my house over the holidays. And 3 PC's permanently in the house using the connection, other than that I download quite a bit of music and software.
But I am quite surprised at being capped this early, I'm not really sure where all the bandwidth went :/
smtp.saix.net
196.25.240.94
Location:South Africa
Packets Sent:7987
Packets Received:7052
Packets Lost:935(11% loss)
Response time Minimum:67ms
Response time Maximum:966ms
Response time Average:191ms
Its getting worse.
Ed, might I suggest hiring Network Engineers that actually know how to look after a network? This amazing, its the 15th of the month and therefore everything goes bad thing is getting a little lame. Also, could someone look into the Blairgowrie (not sure if I spelt that right) tower. Its dropping me every couple of minutes.
Most of the loss is occurring on the UUNET/Verizon Network, download http://www.visualroute.com/lite.html then you can pinpoint who is supposed to be accountable...
Looks like it is again with the upstream provider, and we have escalated to them. We await feedback. As soon as I have heard something I will post again.
I would be interested to know if there are any others that are experienncing the same problem.
Every Friday is the same thing. I try to play WoW, with so many random disconnects. Useless... 2am in the evening is a ball to play. But I like my sleep.
Reply from 196.25.240.94: bytes=18 (sent 1) time=64ms TTL=119
Reply from 196.25.240.94: bytes=18 (sent 1) time=61ms TTL=119
Reply from 196.25.240.94: bytes=18 (sent 1) time=73ms TTL=119
Reply from 196.25.240.94: bytes=18 (sent 1) time=63ms TTL=119
Reply from 196.25.240.94: bytes=18 (sent 1) time=63ms TTL=119
Reply from 196.25.240.94: bytes=18 (sent 1) time=63ms TTL=119
Reply from 196.25.240.94: bytes=18 (sent 1) time=63ms TTL=119
Reply from 196.25.240.94: bytes=18 (sent 1) time=63ms TTL=119
Reply from 196.25.240.94: bytes=18 (sent 1) time=84ms TTL=119
Reply from 196.25.240.94: bytes=18 (sent 1) time=63ms TTL=119
Reply from 196.25.240.94: bytes=18 (sent 1) time=63ms TTL=119
Ping statistics for 196.25.240.94:
Packets: Sent = 11, Received = 11, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 61ms, Maximum = 84ms, Average = 65ms
Ping statistics for 196.25.240.94:
Packets: Sent = 19, Received = 19, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 55ms, Maximum = 139ms, Average = 86ms
During office hours the figures more than double up, with packet loss.