Telkom must be changing the network!

daysleeper

Senior Member
Joined
Mar 16, 2005
Messages
677
Reaction score
1
Location
Gordon's Bay
usually my pings were about 38ms, today they are half of that! maybe telkom upgraded the dslam.



C:\>ping saix.net

Pinging saix.net [196.25.1.200] with 32 bytes of data:

Reply from 196.25.1.200: bytes=32 time=15ms TTL=251
Reply from 196.25.1.200: bytes=32 time=16ms TTL=251
Reply from 196.25.1.200: bytes=32 time=15ms TTL=251
Reply from 196.25.1.200: bytes=32 time=15ms TTL=251

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

C:\>



first they drop my speed, then they lower my latency, what is next a decrease in the rental?

:rolleyes:
 
Pinging siax.net [200.155.15.24] with 32 bytes of data:

Reply from 200.155.15.24: bytes=32 time=487ms TTL=111
Reply from 200.155.15.24: bytes=32 time=489ms TTL=111
Reply from 200.155.15.24: bytes=32 time=490ms TTL=111
Reply from 200.155.15.24: bytes=32 time=488ms TTL=111

Hmmm, wonder wtf is happening on my side, the IP's don't even match
 
James said:
Pinging siax.net [200.155.15.24] with 32 bytes of data:

Reply from 200.155.15.24: bytes=32 time=487ms TTL=111
Reply from 200.155.15.24: bytes=32 time=489ms TTL=111
Reply from 200.155.15.24: bytes=32 time=490ms TTL=111
Reply from 200.155.15.24: bytes=32 time=488ms TTL=111

Hmmm, wonder wtf is happening on my side, the IP's don't even match

Typo! SAIX :D
 
.geek said:
Typo! SAIX :D

thought something was a bit wierd cause I ran a tracert straight after and it was fine... Whoops!

Pinging saix.net [196.25.1.200] with 32 bytes of data:

Reply from 196.25.1.200: bytes=32 time=33ms TTL=248
Reply from 196.25.1.200: bytes=32 time=34ms TTL=248
Reply from 196.25.1.200: bytes=32 time=33ms TTL=248
Reply from 196.25.1.200: bytes=32 time=33ms TTL=248

much better
 
Reply from 64.233.167.99: bytes=32 time=195ms TTL=239
Reply from 64.233.167.99: bytes=32 time=208ms TTL=239
Reply from 64.233.167.99: bytes=32 time=195ms TTL=239
Reply from 64.233.167.99: bytes=32 time=195ms TTL=239

Ping statistics for 64.233.167.99:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 195ms, Maximum = 208ms, Average = 198ms

C:\>
 
Your line speed is approximately 109.6 Kbps or 13.4 kBytes/sec
( Where kb = kilobits and kB = kiloBytes )

high speed stuff!
 
:(

Pinging saix.net [196.25.1.200] with 32 bytes of data:

Reply from 196.25.1.200: bytes=32 time=647ms TTL=250
Request timed out.
Reply from 196.25.1.200: bytes=32 time=857ms TTL=250
Reply from 196.25.1.200: bytes=32 time=678ms TTL=250

Ping statistics for 196.25.1.200:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 647ms, Maximum = 857ms, Average = 727ms
 
Pinging saix.net [196.25.1.200] with 32 bytes of data:

Reply from 196.25.1.200: bytes=32 time=649ms TTL=241
Reply from 196.25.1.200: bytes=32 time=750ms TTL=241
Reply from 196.25.1.200: bytes=32 time=915ms TTL=241
Reply from 196.25.1.200: bytes=32 time=888ms TTL=241

Ping statistics for 196.25.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 649ms, Maximum = 915ms, Average = 800ms
 
Pinging SAIX.NET [196.25.1.200] with 32 bytes of data:

Reply from 196.25.1.200: bytes=32 time=12ms TTL=248
Reply from 196.25.1.200: bytes=32 time=12ms TTL=248
Reply from 196.25.1.200: bytes=32 time=12ms TTL=248
Reply from 196.25.1.200: bytes=32 time=13ms TTL=248

Ping statistics for 196.25.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 13ms, Average = 12ms
 
PING saix.net (196.25.1.200): 56 data bytes
64 bytes from 196.25.1.200: icmp_seq=0 ttl=250 time=15.961 ms
64 bytes from 196.25.1.200: icmp_seq=1 ttl=250 time=12.411 ms
64 bytes from 196.25.1.200: icmp_seq=2 ttl=250 time=13.826 ms

--- saix.net ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/stddev = 12.411/14.066/15.961/1.459 ms
 
Vodacom GPRS :D

Pinging saix.net [196.25.1.200] with 32 bytes of data

Reply from 196.25.1.200: bytes=32 time=599ms TTL=247
Reply from 196.25.1.200: bytes=32 time=811ms TTL=247
Reply from 196.25.1.200: bytes=32 time=548ms TTL=247
Reply from 196.25.1.200: bytes=32 time=817ms TTL=247

Ping statistics for 196.25.1.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% los
Approximate round trip times in milli-seconds:
Minimum = 548ms, Maximum = 817ms, Average = 693ms
 
Pinging saix.net [196.25.1.200] with 32 bytes of data:

Reply from 196.25.1.200: bytes=32 time=16ms TTL=250
Reply from 196.25.1.200: bytes=32 time=20ms TTL=250
Reply from 196.25.1.200: bytes=32 time=19ms TTL=250
Reply from 196.25.1.200: bytes=32 time=19ms TTL=250

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

:cool: Seems good to me ....
 
ADSL-192k

ping saix.net

Pinging saix.net [196.25.1.200] with 32 bytes of data:

Reply from 196.25.1.200: bytes=32 time=22ms TTL=249
Reply from 196.25.1.200: bytes=32 time=24ms TTL=249
Reply from 196.25.1.200: bytes=32 time=21ms TTL=249
Reply from 196.25.1.200: bytes=32 time=23ms TTL=249

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

Local seems fine.
 
Iburst if anyones interested.. but we are sucking with local pings atm.

Pinging saix.net [196.25.1.200] with 32 bytes of data:

Reply from 196.25.1.200: bytes=32 time=165ms TTL=244
Reply from 196.25.1.200: bytes=32 time=154ms TTL=244
Reply from 196.25.1.200: bytes=32 time=212ms TTL=244
Reply from 196.25.1.200: bytes=32 time=147ms 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 = 147ms, Maximum = 212ms, Average = 169ms

And myadsl just for fun.. usually much better, around 60-90 with some spikes.

Pinging www.mybroadband.co.za [196.7.147.165] with 32 bytes of data:

Reply from 196.7.147.165: bytes=32 time=123ms TTL=249
Reply from 196.7.147.165: bytes=32 time=132ms TTL=249
Reply from 196.7.147.165: bytes=32 time=82ms TTL=249
Reply from 196.7.147.165: bytes=32 time=142ms TTL=249

Ping statistics for 196.7.147.165:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 82ms, Maximum = 142ms, Average = 119ms
 
ok i dont have all pings and what eva
but i just logged into WOW and ive neva had a better response time
there r moments of lag but between that its swt:D

TBH i just thought the exact name of this thread bout 10min ago when i noticed a difference
OMG could this be 10 points for telkom :O
 
Pretty smooth playing in WoW...just remember ...it's the first of the month...so they not playing with ports/shaping as much as they do later on. I'm sure to eat my words by the 26th,
 
Mmm wasn't it the case that some CT->CT traffic went via JHB? Possible that it's now routed directly?
 
Top
Sign up to the MyBroadband newsletter
X