Telkom Internet Capped/Uncapped User Feedback (Pt2)

I challenge you to call Telkom and ask for the person in question to verify for yourself. Do you accept?

Please, you trying to bait me into calling the helpdesk and hanging on for 45min to ask for some mythical Telkom helpdesk agent nxa.

Challenge accepted, name please sir.

BTW, did you ever try the nzb challenge?
 
Please, you trying to bait me into calling the helpdesk and hanging on for 45min to ask for some mythical Telkom helpdesk agent nxa.

Challenge accepted, name please sir.

BTW, did you ever try the nzb challenge?
edward madigage

I'm downloading overnight as recommended, so that isn't so much an issue unless the speeds are pathetic.The account will get throttled if the maximum is too high in the daytime, NZB or not.

We must be on our guard for further measures by Telkom to impose more restrictions. In the past, the torrent stoppage was done prior to any announcement, so there is a pattern of doing this and then confirming later.
 
edward madigage

12/8

I'm downloading overnight as recommended, so that isn't so much an issue unless the speeds are pathetic.The account will get throttled if the maximum is too high in the daytime, NZB or not.

We must be on our guard for further measures by Telkom to impose more restrictions. In the past, the torrent stoppage was done prior to any announcement, so there is a pattern of doing this and then confirming later.

Regardless, the challenge was 3 fold. 1> Setup a trial sunny account and test nzb's during the day
2> Try to work around your ISP and not the other way around.
3> Show us some proof your a Ti customer.
You dodge well but not enough I'm afraid.

"We must be on our guard for further measures by Telkom to impose more restrictions. In the past, the torrent stoppage was done prior to any announcement, so there is a pattern of doing this and then confirming later."

Statements like the above convince me that your a troll. Please click my link below, read up and I'm sure your trolling will improve ;)
http://www.wikihow.com/Be-a-Troll

I'm on hold for Telkom helpdesk as I type... this better not be a waste of my time...
 
Something is not right at the moment:

Tracing route to wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms home.gateway [10.0.0.2]
2 10 ms 10 ms 8 ms ti-224-80-01.telkomadsl.co.za [105.224.80.1]
3 184 ms 182 ms 177 ms ti-226-0-22.telkomadsl.co.za [105.226.0.22]
4 186 ms 188 ms 192 ms ti-226-0-57.telkomadsl.co.za [105.226.0.57]
5 12 ms 10 ms 10 ms 165.165.214.213
6 11 ms 13 ms 13 ms wbs-ip-hsll-1-gig-7-0-0.telkom-ipnet.co.za [196.
43.52.66]
7 10 ms 10 ms 11 ms wbs-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [
196.25.37.2]
8 12 ms 12 ms 11 ms wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]


Trace complete.

Tracing route to 197-80-200-233.jhb.mweb.co.za [197.80.200.233]
over a maximum of 30 hops:

1 <1 ms 1 ms <1 ms home.gateway [10.0.0.2]
2 8 ms 9 ms 8 ms ti-224-80-01.telkomadsl.co.za [105.224.80.1]
3 197 ms 203 ms 200 ms ti-226-0-22.telkomadsl.co.za [105.226.0.22]
4 204 ms 208 ms 210 ms ti-226-0-57.telkomadsl.co.za [105.226.0.57]
5 11 ms 11 ms 13 ms 165.165.214.213
6 192 ms 186 ms 184 ms 196.43.11.218
7 156 ms 153 ms 153 ms 196.43.25.206
8 171 ms 167 ms 169 ms gigabitethernet1-1-1.cpt-pr-1.mweb.co.za [197.84
.4.22]
9 200 ms 198 ms 200 ms tengig-0-7-0-3-cpt-p-2.mweb.co.za [197.84.7.2]
10 201 ms 203 ms 204 ms tengig-0-7-0-1-vic-p-1.mweb.co.za [197.84.4.47]

11 38 ms 39 ms 39 ms tengig-0-0-0-0-101-vic-pe-1.mweb.co.za [197.80.7
.9]
12 208 ms 205 ms 203 ms tengig0-0-0-0.mca-pe-1.mweb.co.za [197.80.4.37]

13 202 ms 206 ms 206 ms 197-80-96-30.jhb.mweb.co.za [197.80.96.30]
14 210 ms 211 ms 216 ms OPTI-JHB-VP-Hosting.optinet.net [197.80.206.6]
15 38 ms 37 ms 37 ms 197-80-215-18.jhb.mweb.co.za [197.80.215.18]
16 220 ms 219 ms 216 ms 197-80-200-233.jhb.mweb.co.za [197.80.200.233]

Trace complete.

Tracing route to 197-80-200-232.jhb.mweb.co.za [197.80.200.232]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms home.gateway [10.0.0.2]
2 9 ms 10 ms 8 ms ti-224-80-01.telkomadsl.co.za [105.224.80.1]
3 179 ms 175 ms 175 ms ti-226-0-22.telkomadsl.co.za [105.226.0.22]
4 180 ms 182 ms 183 ms ti-226-0-57.telkomadsl.co.za [105.226.0.57]
5 11 ms 11 ms 12 ms 165.165.214.213
6 175 ms 177 ms 180 ms 196.43.11.218
7 165 ms 167 ms 171 ms 196.43.25.206
8 469 ms 190 ms 189 ms gigabitethernet1-1-1.cpt-pr-1.mweb.co.za [197.84
.4.22]
9 37 ms 34 ms 39 ms tengig-0-0-0-1-cpt-p-1.mweb.co.za [197.84.7.1]
10 200 ms 201 ms 197 ms tengig-0-0-0-0-vic-p-2.mweb.co.za [197.84.4.35]

11 35 ms 34 ms 35 ms tengig-0-0-0-0-102-vic-pe-1.mweb.co.za [197.80.7
.41]
12 204 ms 207 ms 207 ms tengig0-0-0-0.mca-pe-1.mweb.co.za [197.80.4.37]

13 216 ms 217 ms 220 ms 197-80-96-30.jhb.mweb.co.za [197.80.96.30]
14 215 ms 216 ms 213 ms OPTI-JHB-VP-Hosting.optinet.net [197.80.206.6]
15 33 ms 47 ms 33 ms 197-80-215-18.jhb.mweb.co.za [197.80.215.18]
16 32 ms 34 ms 32 ms 197-80-200-232.jhb.mweb.co.za [197.80.200.232]

Trace complete.
 
Something is not right at the moment:

We had a ticket open with the vendor who supplied the IPC router, for it not load-balancing correctly, since yesterday, escalated as high as it can be for an issue that isn't a complete outage since this morning, with no resolution as yet.

Since there has been no resolution to load balancing problem, and we won't be able to get a workaround in place tonight, we will be preventing the congestion at the router by implementing changes on the traffic management side immediately. This will likely result in slightly worse internet until 20h00 or so, and we won't be able to use anywhere near our full IPC capacity in the Cape Town site, so the experience will still be worse than last week, but hopefully not as bad as last night.
 
Not a good night for TI. Please hurry with that FTTH cable company outside my gate...
 
Telkom Internet is tonight useless and pathetic

C:\Users\C>ping www.bbc.co.uk

Pinging www.bbc.net.uk [212.58.244.67] with 32 bytes of data:
Reply from 212.58.244.67: bytes=32 time=428ms TTL=48
Reply from 212.58.244.67: bytes=32 time=425ms TTL=48
Reply from 212.58.244.67: bytes=32 time=417ms TTL=48
Reply from 212.58.244.67: bytes=32 time=419ms TTL=48

Ping statistics for 212.58.244.67:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 417ms, Maximum = 428ms, Average = 422ms
 
Gaming was rubbish until after 10 when it improved by roughly 20%
Now nobody is playing.
 
So is everyone getting more or less full line speeds during midnight surfer times?
 
Top
Sign up to the MyBroadband newsletter
X