South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Reply from 196.38.180.26: bytes=32 time=604ms TTL=51
Reply from 196.38.180.26: bytes=32 time=600ms TTL=51
Reply from 196.38.180.26: bytes=32 time=611ms TTL=51
Reply from 196.38.180.26: bytes=32 time=663ms TTL=51
Reply from 196.38.180.26: bytes=32 time=752ms TTL=51
Reply from 196.38.180.26: bytes=32 time=631ms TTL=51
Reply from 196.38.180.26: bytes=32 time=447ms TTL=55
Reply from 196.38.180.26: bytes=32 time=492ms TTL=55
Reply from 196.38.180.26: bytes=32 time=623ms TTL=55
Reply from 196.38.180.26: bytes=32 time=731ms TTL=55
Reply from 196.38.180.26: bytes=32 time=704ms TTL=55
Reply from 196.38.180.26: bytes=32 time=718ms TTL=55
Telkom managed to fix my line. There is some problem they definitely know about but don't want to fix.
Other - La Lucia - UN01LAI003C - Down - Telkom Technician investigating
Ref: NN0013315Category Planned Work Type: Fault Condition Status: New
TimeDown: Mon, 20 May 2013 05:14:00 +0200 ETTR: 5 Hours
Areas affected: DSLAM Affected: RST1 - NLMD(F18A1)
Progress:
So your pings are fine now mr feesh?
did nothing. Just random, so hopefully it is your turn soon, have you considered getting another line?So how did u get them to fix yours?
Hmm, i'm also 572. So cancel and get a new line? Probably a good idea but who knows how long that will take. Also how long has yours been ok?