Sorry to ask this here, but is anyone else having issues with the TI tracker? Every time I put in my username and password I get thrown an error and told to email them with the date and time. I got some read marker on the email but no replies, or it working.
Guess the only thing to do is keep emailing them when ever I get the error. (Fill their inbox I say :twisted: )
Hey Friends,
Network Notice:
Dear IS Client
Emergency Telkom SA Upstream Service Provider Change Notification.
AFFECTED SERVICE:
- International Access, International ADSL (Major, No Connectivity)
- International MPLS VPN (Minor increased latency/packet loss)
LOCATION: National (international traffic)
START DATE: Fri Apr 05 2013 2:00 (SAST)
END DATE: Fri Apr 05 2013 8:00 (SAST)
EXPECTED DURATION: Up to 6 hours
IMPACT:
- International Access, International ADSL (Major, No Connectivity)
- International MPLS VPN (Minor increased latency/packet loss)
REASON FOR CHANGE: International Upstream Service Provider submarine cable repairs (Mediterranean sea)
I switched to Telkom's 4MB uncapped service a month ago, and am very happy. As my line syncs at 10Mbps, I'd like to upgrade to the 10MB uncapped service, so I tried to do it by 'ordering' it via the website (I REALLY want to avoid the call-centre if at all possible - while the product performs well, the same cannot be said for the call-centre) but I get the following error when clicking the ORDER button found at http://www.do.co.za/broadband/offerings/telkom-internet-plans/uncapped/do-uncapped-up-to-10mbps/:
500 Internal Server Error
Servlet error: An exception occurred. The current application deployment descriptors do not allow for including it in this response. Please consult the application log for details.
Sorry to ask this here, but is anyone else having issues with the TI tracker? Every time I put in my username and password I get thrown an error and told to email them with the date and time. I got some read marker on the email but no replies, or it working.
Guess the only thing to do is keep emailing them when ever I get the error. (Fill their inbox I say :twisted: )
Not sure what's up atm. International browsing and NNTP @ 40 KB/s. Youtube @ 1020kbps?!?
International speed test:
Test conducted on Wed Apr 3 22:16:53 2013
Download Speed: 8135 kbps (1016.9 KB/sec transfer rate)
Upload Speed: 809 kbps (101.1 KB/sec transfer rate)
Latency: 233 ms
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\>tracert capetown.spdtst.saix.net
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 Billion.810VNTX [10.0.0.2]
2 16 ms 13 ms 36 ms 224-140-1.dsl.subscriber.telkomsa.net [105.224.1
40.1]
3 19 ms 20 ms 22 ms 226-0-6.dsl.subscriber.telkomsa.net [105.226.0.6
]
4 21 ms 18 ms 18 ms 226-0-13.dsl.subscriber.telkomsa.net [105.226.0.
13]
5 27 ms 26 ms 26 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 30 ms 33 ms 27 ms 196.43.39.78
7 27 ms 26 ms 26 ms wbs-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [
196.25.37.2]
8 27 ms 27 ms 43 ms wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]
Trace complete.
C:\>tracert capetown.spdtst.saix.net
Tracing route to wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]
over a maximum of 30 hops:
1 11 ms <1 ms <1 ms Billion.810VNTX [10.0.0.2]
2 36 ms 9 ms 8 ms 224-140-1.dsl.subscriber.telkomsa.net [105.224.1
40.1]
3 21 ms 22 ms 18 ms 226-0-6.dsl.subscriber.telkomsa.net [105.226.0.6
]
4 18 ms 18 ms 19 ms 226-0-13.dsl.subscriber.telkomsa.net [105.226.0.
13]
5 22 ms 20 ms 23 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 37 ms 33 ms 44 ms 196.43.39.78
7 27 ms 31 ms 27 ms wbs-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [
196.25.37.2]
8 31 ms 30 ms 29 ms wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]
Trace complete.
C:\>tracert capetown.spdtst.saix.net
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 Billion.810VNTX [10.0.0.2]
2 14 ms 13 ms 20 ms 224-140-1.dsl.subscriber.telkomsa.net [105.224.1
40.1]
3 22 ms 24 ms 19 ms 226-0-6.dsl.subscriber.telkomsa.net [105.226.0.6
]
4 20 ms 20 ms 18 ms 226-0-13.dsl.subscriber.telkomsa.net [105.226.0.
13]
5 36 ms 20 ms 19 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 40 ms 34 ms 43 ms 196.43.39.78
7 36 ms 36 ms 33 ms wbs-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [
196.25.37.2]
8 27 ms 27 ms 29 ms wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]
Trace complete.
C:\>tracert capetown.spdtst.saix.net
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 Billion.810VNTX [10.0.0.2]
2 16 ms 13 ms 13 ms 224-140-1.dsl.subscriber.telkomsa.net [105.224.1
40.1]
3 19 ms 18 ms 18 ms 226-0-6.dsl.subscriber.telkomsa.net [105.226.0.6
]
4 19 ms 19 ms 19 ms 226-0-13.dsl.subscriber.telkomsa.net [105.226.0.
13]
5 33 ms 19 ms 18 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 34 ms 28 ms 26 ms 196.43.39.78
7 36 ms 31 ms 32 ms wbs-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [
196.25.37.2]
8 27 ms 27 ms 28 ms wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]
Trace complete.
C:\>tracert capetown.spdtst.saix.net
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 Billion.810VNTX [10.0.0.2]
2 8 ms 15 ms 13 ms 224-140-1.dsl.subscriber.telkomsa.net [105.224.1
40.1]
3 18 ms 18 ms 20 ms 226-0-6.dsl.subscriber.telkomsa.net [105.226.0.6
]
4 31 ms 33 ms 18 ms 226-0-13.dsl.subscriber.telkomsa.net [105.226.0.
13]
5 28 ms 28 ms 18 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 26 ms 33 ms 26 ms 196.43.39.78
7 27 ms 33 ms 29 ms wbs-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [
196.25.37.2]
8 30 ms 27 ms 31 ms wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]
Trace complete.
C:\>tracert capetown.spdtst.saix.net
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 Billion.810VNTX [10.0.0.2]
2 9 ms 8 ms 8 ms 224-140-1.dsl.subscriber.telkomsa.net [105.224.1
40.1]
3 19 ms 23 ms 23 ms 226-0-6.dsl.subscriber.telkomsa.net [105.226.0.6
]
4 18 ms 18 ms 18 ms 226-0-13.dsl.subscriber.telkomsa.net [105.226.0.
13]
5 19 ms 18 ms 18 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 26 ms 26 ms 26 ms 196.43.39.78
7 27 ms 31 ms 28 ms wbs-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [
196.25.37.2]
8 34 ms 33 ms 28 ms wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]
Trace complete.
C:\>tracert capetown.spdtst.saix.net
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 Billion.810VNTX [10.0.0.2]
2 13 ms 12 ms 17 ms 224-140-1.dsl.subscriber.telkomsa.net [105.224.1
40.1]
3 18 ms 19 ms 18 ms 226-0-6.dsl.subscriber.telkomsa.net [105.226.0.6
]
4 35 ms 27 ms 18 ms 226-0-13.dsl.subscriber.telkomsa.net [105.226.0.
13]
5 25 ms 27 ms 19 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 35 ms 32 ms 27 ms 196.43.39.78
7 30 ms 31 ms 27 ms wbs-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [
196.25.37.2]
8 32 ms 27 ms 27 ms wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]
Trace complete.
C:\>tracert capetown.spdtst.saix.net
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 Billion.810VNTX [10.0.0.2]
2 10 ms 10 ms 9 ms 224-140-1.dsl.subscriber.telkomsa.net [105.224.1
40.1]
3 24 ms 18 ms 18 ms 226-0-6.dsl.subscriber.telkomsa.net [105.226.0.6
]
4 19 ms 23 ms 23 ms 226-0-13.dsl.subscriber.telkomsa.net [105.226.0.
13]
5 39 ms 28 ms 19 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 113 ms 31 ms 27 ms 196.43.39.78
7 27 ms 26 ms 27 ms wbs-ip-cat-1-fwsm-speedtest.telkom-ipnet.co.za [
196.25.37.2]
8 31 ms 29 ms 27 ms wbs-ip-dlr-1-1.telkom-ipnet.co.za [196.25.37.14]
Trace complete.
C:\>tracert 8.8.8.8
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Billion.810VNTX [10.0.0.2]
2 13 ms 40 ms 19 ms 224-140-1.dsl.subscriber.telkomsa.net [105.224.1
40.1]
3 31 ms 25 ms 26 ms 226-0-6.dsl.subscriber.telkomsa.net [105.226.0.6
]
4 26 ms 26 ms 26 ms 226-0-13.dsl.subscriber.telkomsa.net [105.226.0.
13]
5 48 ms 26 ms 30 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 172 ms 172 ms 181 ms lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.
43.9.46]
7 184 ms 177 ms 179 ms 196.25.191.146
8 * * 171 ms 209.85.240.61
9 185 ms 178 ms 183 ms 209.85.253.94
10 180 ms 181 ms 190 ms 209.85.243.33
11 198 ms 187 ms 190 ms 216.239.49.28
12 * * * Request timed out.
13 179 ms 183 ms 183 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.
C:\>tracert 8.8.8.8
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Billion.810VNTX [10.0.0.2]
2 14 ms 17 ms 15 ms 224-140-1.dsl.subscriber.telkomsa.net [105.224.1
40.1]
3 150 ms 73 ms 36 ms 226-0-6.dsl.subscriber.telkomsa.net [105.226.0.6
]
4 85 ms 25 ms 25 ms 226-0-13.dsl.subscriber.telkomsa.net [105.226.0.
13]
5 27 ms 27 ms 35 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 170 ms 176 ms 170 ms lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.
43.9.46]
7 186 ms 178 ms 183 ms 196.25.191.146
8 * 185 ms 172 ms 209.85.240.61
9 182 ms 179 ms 178 ms 209.85.253.94
10 177 ms 176 ms 177 ms 209.85.243.33
11 211 ms 187 ms 187 ms 216.239.49.28
12 * * * Request timed out.
13 183 ms 180 ms 179 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.
C:\>tracert 8.8.8.8
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Billion.810VNTX [10.0.0.2]
2 8 ms 8 ms 9 ms 224-140-1.dsl.subscriber.telkomsa.net [105.224.1
40.1]
3 26 ms 25 ms 25 ms 226-0-6.dsl.subscriber.telkomsa.net [105.226.0.6
]
4 26 ms 26 ms 30 ms 226-0-13.dsl.subscriber.telkomsa.net [105.226.0.
13]
5 26 ms 25 ms 26 ms wblv-ip-hsll-1-wan.telkom-ipnet.co.za [196.25.39
.45]
6 170 ms 170 ms 170 ms lon-ip-hsll-1-gig-0-1-0.telkom-ipnet.co.za [196.
43.9.46]
7 178 ms 177 ms 178 ms 196.25.191.146
8 * 171 ms * 209.85.240.61
9 179 ms 178 ms 179 ms 209.85.253.94
10 182 ms 182 ms 177 ms 209.85.243.33
11 186 ms 187 ms 186 ms 216.239.49.28
12 * * * Request timed out.
13 180 ms 179 ms 180 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.
C:\>
This issue, and a number of others, have been fixed internally, and a new version was supposed to have been deployed, but there were some additional changes required on other components which were only communicated late today, so the deployment has been postponed. I think the email address provided on the page currently goes to /dev/null, so you can try and fill it if you are really bored.
Sweet will just do the usual and wait and see what happens. Give it a few more days and try again. On another note ranger can you check my info again please as it still appears as if I am on the 1Mb uncapped.
Test conducted on 04 April 2013 07:13:32 AM
Download Speed: 977 kbps (122.1 KB/sec transfer rate)
Upload Speed: 418 kbps (52.3 KB/sec transfer rate)
Latency: 29 ms
/me still happy with 2Mbps account...
So far so good since my sign up on the 19th.. 4MB uncapped - no signs of throttling @ all
Which ISP are you with?
ranger, you might have missed my question on the previous page.
The throttling that happened after 300Gb on 4Mb lines in Feb, that didn't seem to happen in March. Which month is correct in terms of what will happen going forward?
Thanks for sorting out my issue ranger, you da Man. I now have the 2Mb uncapped.
Test conducted on 04 April 2013 09:57:32 AM
Download Speed: 1758 kbps (219.8 KB/sec transfer rate)
Upload Speed: 413 kbps (51.6 KB/sec transfer rate)
Latency: 28 ms
Looks so much better than my previous figures.
Thanks ranger.