Back to the same old problems again!

asilva

Active Member
Joined
Mar 20, 2006
Messages
88
Reaction score
0
Location
Nelspruit
A few months ago, we were complaining of latency and speed degradation, and a few other things. Since three or four days ago, i am experiencing the same problem again, it feels like dejá vú. After we complained, things actualy improved , but it's back to the same as before, what's going on?

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

Reply from 64.233.187.99: bytes=32 time=2133ms TTL=240
Reply from 64.233.187.99: bytes=32 time=2318ms TTL=240
Reply from 64.233.187.99: bytes=32 time=2300ms TTL=240
Reply from 64.233.187.99: bytes=32 time=2540ms TTL=240

Ping statistics for 64.233.187.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2133ms, Maximum = 2540ms, Average = 2322ms


Pinging www.saix.co.za [196.25.1.200] with 32 bytes of data:

Reply from 196.25.1.200: bytes=32 time=263ms TTL=244
Reply from 196.25.1.200: bytes=32 time=122ms TTL=244
Reply from 196.25.1.200: bytes=32 time=121ms TTL=244
Reply from 196.25.1.200: bytes=32 time=233ms TTL=244

Ping statistics for 196.25.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 121ms, Maximum = 263ms, Average = 184ms


Tracing route to www.l.google.com [64.233.161.104]
over a maximum of 30 hops:

1 114 ms 359 ms 200 ms 66.18.87.50
2 220 ms 176 ms 160 ms 66.18.65.105
3 101 ms 295 ms 202 ms gige-0-0-102.rtr-core5-stp.infosat.net [66.18.65
.106]
4 102 ms 399 ms 179 ms 66.18.87.254
5 154 ms 221 ms 199 ms 168.209.18.61
6 139 ms 176 ms 181 ms core2b-rba-gi8-0-0.rtr.isnet.net [196.26.0.9]
7 381 ms 400 ms 478 ms 168.209.0.94
8 357 ms 419 ms 400 ms 168.209.244.7
9 * 383 ms 339 ms core1-0-2-0.lga.net.google.com [198.32.160.130]

10 359 ms 459 ms * 216.239.49.34
11 2215 ms 2223 ms 2177 ms 66.249.94.235
12 2236 ms 2303 ms 2479 ms 72.14.238.232
13 2218 ms 2159 ms 2179 ms 72.14.236.202
14 1919 ms 1958 ms 2000 ms 216.239.48.190
15 2180 ms 2660 ms 2119 ms 64.233.161.104


Tracing route to www.l.google.com [64.233.161.147]
over a maximum of 30 hops:

1 303 ms 199 ms 179 ms 66.18.87.50
2 172 ms 121 ms 137 ms 66.18.65.105
3 476 ms 660 ms 137 ms gige-0-0-102.rtr-core5-stp.infosat.net [66.18.65
.106]
4 156 ms 122 ms 176 ms 66.18.87.254
5 195 ms 239 ms 240 ms 168.209.18.61
6 139 ms 225 ms 274 ms core2b-rba-gi8-0-0.rtr.isnet.net [196.26.0.9]
7 412 ms 459 ms 519 ms 168.209.0.94
8 357 ms 480 ms 460 ms 168.209.244.7
9 456 ms 463 ms 397 ms core1-0-2-0.lga.net.google.com [198.32.160.130]

10 * 577 ms 439 ms 216.239.49.34
11 1759 ms 1816 ms 1780 ms 66.249.94.235
12 1739 ms 1880 ms 1933 ms 72.14.238.232
13 1903 ms 2035 ms 2021 ms 72.14.236.202
14 2101 ms 2015 ms 2101 ms 216.239.49.214
15 2199 ms 2212 ms 2160 ms 64.233.161.147


Tracing route to cnn.com [64.236.16.84]
over a maximum of 30 hops:

1 175 ms 181 ms 137 ms 66.18.87.50
2 433 ms 201 ms 401 ms 66.18.65.105
3 196 ms 200 ms 240 ms gige-0-0-102.rtr-core5-stp.infosat.net [66.18.65
.106]
4 99 ms 119 ms 98 ms 66.18.87.254
5 116 ms 200 ms 138 ms 168.209.18.61
6 177 ms 499 ms 398 ms core1b-rba-gi0-1.rtr.isnet.net [196.26.0.10]
7 197 ms 140 ms 137 ms core2b-rba-gi8-0-0.rtr.isnet.net [196.26.0.9]
8 417 ms 479 ms 477 ms 168.209.0.94
9 419 ms 599 ms 438 ms core1b-ny.nmszone.is.co.za [168.209.244.3]
10 554 ms 660 ms 499 ms POS1-2.IG2.NYC4.ALTER.NET [208.192.177.205]
11 423 ms 456 ms 398 ms 0.so-0-0-0.XL1.NYC4.ALTER.NET [152.63.22.14]
12 * * 567 ms 0.so-4-2-0.XL3.NYC4.ALTER.NET [152.63.20.209]
13 428 ms * 426 ms 0.ge-5-0-0.BR2.NYC4.ALTER.NET [152.63.3.114]
14 2145 ms 2304 ms 2213 ms 204.255.173.34
15 2559 ms 2539 ms 2480 ms bb2-nye-P0-0.atdn.net [66.185.151.50]
16 2377 ms 2738 ms 2438 ms bb2-vie-P12-0.atdn.net [66.185.152.201]
17 2619 ms 2499 ms 2458 ms bb2-atm-P3-0.atdn.net [66.185.152.33]
18 2396 ms 2420 ms 2380 ms pop1-atl-P5-0.atdn.net [66.185.136.35]
19 * * * Request timed out.
20 * * * Request timed out.
 
I really do think they have a problem, i was pinging google just now, seeing that high latency, when, all of a sudden the latency droped to 480ms, but, as it droped, the timeouts started, LOTS of it.

Reply from 64.233.167.99: bytes=32 time=375ms TTL=238
Request timed out.
Reply from 64.233.167.99: bytes=32 time=444ms TTL=238
Reply from 64.233.167.99: bytes=32 time=343ms TTL=238
Reply from 64.233.167.99: bytes=32 time=353ms TTL=238
Request timed out.
Reply from 64.233.167.99: bytes=32 time=484ms TTL=238
Request timed out.
Reply from 64.233.167.99: bytes=32 time=504ms TTL=238
Reply from 64.233.167.99: bytes=32 time=354ms TTL=238
Request timed out.
Reply from 64.233.167.99: bytes=32 time=634ms TTL=238
Reply from 64.233.167.99: bytes=32 time=343ms TTL=238
Request timed out.
Reply from 64.233.167.99: bytes=32 time=362ms TTL=238
Reply from 64.233.167.99: bytes=32 time=343ms TTL=238
Request timed out.
Reply from 64.233.167.99: bytes=32 time=464ms TTL=238

and it goes on and on and on...i wonder what's happening!?!?!!

cheers
 
Top
Sign up to the MyBroadband newsletter
X