PurSpyk!!
Expert Member
Guys not to be a DOOM sayer but the 18th is a holiday??? wont this affect the install??? some feedback??
I mentioned this the day they announced the new date, supposedly they work on holidays too.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Guys not to be a DOOM sayer but the 18th is a holiday??? wont this affect the install??? some feedback??
Hasn't been a good year for internet ><
Tried your app, but doesn't seem to like me.
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)
Bad parameter *.
2014-04-14 21:44:59,14
EDIT: "80 was unexpected at this time." appears on the screen after "Press any key to continue..."
Haha, okay. Ill have a look at why that is! Are you by any chance running a firewall?
Z
Just the usual windows firewall.. tried disabling it but no luck.
.exe doesn't create any text files, but the zipped version does.. although just had what I pasted in my previous message in it.
Maybe my net is on another level of screwed..
Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert)
Pinging 105.236.11.193 with 32 bytes of data:
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=14ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=12ms TTL=254
Reply from 105.236.11.193: bytes=32 time=13ms TTL=254
Reply from 105.236.11.193: bytes=32 time=89ms TTL=254
Reply from 105.236.11.193: bytes=32 time=49ms TTL=254
Reply from 105.236.11.193: bytes=32 time=47ms TTL=254
Reply from 105.236.11.193: bytes=32 time=39ms TTL=254
Reply from 105.236.11.193: bytes=32 time=92ms TTL=254
Reply from 105.236.11.193: bytes=32 time=114ms TTL=254
Reply from 105.236.11.193: bytes=32 time=112ms TTL=254
Reply from 105.236.11.193: bytes=32 time=117ms TTL=254
Reply from 105.236.11.193: bytes=32 time=111ms TTL=254
Reply from 105.236.11.193: bytes=32 time=57ms TTL=254
Reply from 105.236.11.193: bytes=32 time=119ms TTL=254
Reply from 105.236.11.193: bytes=32 time=114ms TTL=254
Reply from 105.236.11.193: bytes=32 time=147ms TTL=254
Reply from 105.236.11.193: bytes=32 time=182ms TTL=254
Reply from 105.236.11.193: bytes=32 time=173ms TTL=254
Reply from 105.236.11.193: bytes=32 time=98ms TTL=254
Reply from 105.236.11.193: bytes=32 time=66ms TTL=254
Reply from 105.236.11.193: bytes=32 time=79ms TTL=254
Reply from 105.236.11.193: bytes=32 time=139ms TTL=254
Reply from 105.236.11.193: bytes=32 time=85ms TTL=254
Ping statistics for 105.236.11.193:
Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 12ms, Maximum = 182ms, Average = 71ms
2014/04/14 22:42:54.37
Line has been dodgy for the last 3 days. And no, this is not over Wifi, it is via the cable (which was replaced last month as a fault finding measure, and it is not anything else but a crap line, yet again....)
Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 71ms
Your maximum ping was 182ms
Looking at your average ping, your line seems to be a bit dodgy :/ This may account for any slow speeds you may be experiencing. However, it could just be related to a high-latency home network (ie... Wi-Fi). If you feel the need, please post the results (at the end of the program) into the forum for advice
Detailed Report
Code:Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) Pinging 105.236.11.193 with 32 bytes of data: Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=12ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=12ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=14ms TTL=254 Reply from 105.236.11.193: bytes=32 time=12ms TTL=254 Reply from 105.236.11.193: bytes=32 time=12ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=89ms TTL=254 Reply from 105.236.11.193: bytes=32 time=49ms TTL=254 Reply from 105.236.11.193: bytes=32 time=47ms TTL=254 Reply from 105.236.11.193: bytes=32 time=39ms TTL=254 Reply from 105.236.11.193: bytes=32 time=92ms TTL=254 Reply from 105.236.11.193: bytes=32 time=114ms TTL=254 Reply from 105.236.11.193: bytes=32 time=112ms TTL=254 Reply from 105.236.11.193: bytes=32 time=117ms TTL=254 Reply from 105.236.11.193: bytes=32 time=111ms TTL=254 Reply from 105.236.11.193: bytes=32 time=57ms TTL=254 Reply from 105.236.11.193: bytes=32 time=119ms TTL=254 Reply from 105.236.11.193: bytes=32 time=114ms TTL=254 Reply from 105.236.11.193: bytes=32 time=147ms TTL=254 Reply from 105.236.11.193: bytes=32 time=182ms TTL=254 Reply from 105.236.11.193: bytes=32 time=173ms TTL=254 Reply from 105.236.11.193: bytes=32 time=98ms TTL=254 Reply from 105.236.11.193: bytes=32 time=66ms TTL=254 Reply from 105.236.11.193: bytes=32 time=79ms TTL=254 Reply from 105.236.11.193: bytes=32 time=139ms TTL=254 Reply from 105.236.11.193: bytes=32 time=85ms TTL=254 Ping statistics for 105.236.11.193: Packets: Sent = 30, Received = 30, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 12ms, Maximum = 182ms, Average = 71ms 2014/04/14 22:42:54.37
Certain changes are immediate others are at the beginning of the month.
Upgrades are usually instantly, but downgrades I think only effective at the start of the new month.

Spoke too soon, speed crap again. 8mb Business Uncapped .
Last Result:
Download Speed: 2014 kbps (251.8 KB/sec transfer rate)
Upload Speed: 859 kbps (107.4 KB/sec transfer rate)
Latency: 17 ms
Monday, 14 April 2014 19:44
Wow Guys, if you ever want an example of intermittent line issues:
Sigh... this usually fixes itself in an hour.
Z
So basically I am screwed until Telkom decides to do something...My problem is that it was running fine two months ago and now all of a sudden my noise margin has become really bad :/
Line has been dodgy for the last 3 days. And no, this is not over Wifi, it is via the cable (which was replaced last month as a fault finding measure, and it is not anything else but a crap line, yet again....)
Zertop's "Is it my Line" Results
Basic Report:
Your average ping was 71ms
Your maximum ping was 182ms
Looking at your average ping, your line seems to be a bit dodgy :/ This may account for any slow speeds you may be experiencing. However, it could just be related to a high-latency home network (ie... Wi-Fi). If you feel the need, please post the results (at the end of the program) into the forum for advice
Detailed Report
Code:Ping results for last hop before account switches to ISP's hardware (Hop 2 on Tracert) Pinging 105.236.11.193 with 32 bytes of data: Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=12ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=12ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=14ms TTL=254 Reply from 105.236.11.193: bytes=32 time=12ms TTL=254 Reply from 105.236.11.193: bytes=32 time=12ms TTL=254 Reply from 105.236.11.193: bytes=32 time=13ms TTL=254 Reply from 105.236.11.193: bytes=32 time=89ms TTL=254 Reply from 105.236.11.193: bytes=32 time=49ms TTL=254 Reply from 105.236.11.193: bytes=32 time=47ms TTL=254 Reply from 105.236.11.193: bytes=32 time=39ms TTL=254 Reply from 105.236.11.193: bytes=32 time=92ms TTL=254 Reply from 105.236.11.193: bytes=32 time=114ms TTL=254 Reply from 105.236.11.193: bytes=32 time=112ms TTL=254 Reply from 105.236.11.193: bytes=32 time=117ms TTL=254 Reply from 105.236.11.193: bytes=32 time=111ms TTL=254 Reply from 105.236.11.193: bytes=32 time=57ms TTL=254 Reply from 105.236.11.193: bytes=32 time=119ms TTL=254 Reply from 105.236.11.193: bytes=32 time=114ms TTL=254 Reply from 105.236.11.193: bytes=32 time=147ms TTL=254 Reply from 105.236.11.193: bytes=32 time=182ms TTL=254 Reply from 105.236.11.193: bytes=32 time=173ms TTL=254 Reply from 105.236.11.193: bytes=32 time=98ms TTL=254 Reply from 105.236.11.193: bytes=32 time=66ms TTL=254 Reply from 105.236.11.193: bytes=32 time=79ms TTL=254 Reply from 105.236.11.193: bytes=32 time=139ms TTL=254 Reply from 105.236.11.193: bytes=32 time=85ms TTL=254 Ping statistics for 105.236.11.193: Packets: Sent = 30, Received = 30, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 12ms, Maximum = 182ms, Average = 71ms 2014/04/14 22:42:54.37
Guys not to be a DOOM sayer but the 18th is a holiday??? wont this affect the install??? some feedback??
I don't think it's an impossibility - Telkom have made people available on Public Holdays before during outages and maintenance. I think it could be a valid date. At the level we're talking about management-wise, I don't think those dates are given out lightly (I hope so).
This does not sound so confident anymore? I have a feeling the ipc issues will remain.
The noise margin could be determined by several factors - POTS filters are the first place to look, but there could be induced noise on the line from Electromagnetic interference from electric fences or appliances on the same power circuit as the router, etc. Sometimes it can be pretty hard to pin down.
Are you logging faults with Telkom (either directly or through us)?