IdlePhaedrus
Expert Member
- Joined
- Jan 31, 2005
- Messages
- 1,621
- Reaction score
- 500
Apologies, did not mean to derail the thread.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
LMAOIts funny, when I started in this (IT) business many moons ago we talked in baud. The first modem I ever worked with was 2.6kb (some here will probably be more venerable). We took information from a power-plant, ran it through an 'artificial intelligence' interface and suggested requirements for further maintenance or better maintenance schedules. I think I was around 21 at the time, it was all very exciting and a very long time ago.
At the time ZA had a surplus of electricity, in fact we almost had the cheapest electricity in the world. We even had a single power station dedicated to training technicians that was off the grid and people came from all over the globe to train there.
This has obviously all changed and gone away. We now have a deficit of electricity, and there is no longer a place to train new technicians, and the average consumer probably has to pay more than any other consumer in an equal economy worldwide.
Further, many large firms who are energy intensive have actually suffered worse power restrictions in the last two years than the average consumer (votes required for someone?).
Sorry for the rant, if you get your pirated movie at 50% speed, tough. If your business suffers as a result of speed loss, fine, complain.
But, remember some business did very well at 2.6kb, and would probably doing just fine now if it weren't for politics.
Phaedrus
Yes. Do the other accounts work fine when you leave them on for a prolonged period? Otherwise something is wrong somewhere with regards to MTN routing :/ (I would say the account is at fault, but this seems to have been fixed for most users now)
Does Axxess work well?
Z



Ping Test:
ping 197.242.144.102
64 bytes from 197.242.144.102: icmp_req=1 ttl=59 time=34 ms
64 bytes from 197.242.144.102: icmp_req=2 ttl=59 time=34 ms
64 bytes from 197.242.144.102: icmp_req=3 ttl=59 time=38 ms
64 bytes from 197.242.144.102: icmp_req=4 ttl=59 time=36 ms
Request timeout for icmp_seq 5
ping 8.8.8.8
64 bytes from 8.8.8.8: icmp_req=1 ttl=46 time=186 ms
64 bytes from 8.8.8.8: icmp_req=2 ttl=46 time=187 ms
64 bytes from 8.8.8.8: icmp_req=3 ttl=46 time=184 ms
64 bytes from 8.8.8.8: icmp_req=4 ttl=46 time=181 ms
64 bytes from 8.8.8.8: icmp_req=5 ttl=46 time=186 ms
Trace Test:
traceroute -n 197.242.144.102
1 192.168.0.1 1 ms 1 ms 1 ms
2 41.181.51.1 13 ms 17 ms
41.181.198.1 73 ms
3 41.181.198.1 16 ms 15 ms
196.44.18.2 16 ms
4 196.44.18.2 16 ms 18 ms
196.44.31.1 17 ms
5 196.44.31.1 15 ms
196.44.31.6 38 ms 40 ms
6 196.44.31.6 56 ms
196.44.31.9 37 ms 36 ms
7 196.44.31.9 42 ms
196.30.1.5 66 ms 39 ms
8 196.31.220.2 39 ms 33 ms
196.31.63.2 40 ms
9 196.31.63.2 36 ms 36 ms
196.30.42.1 36 ms
10 196.30.42.1 38 ms
197.242.144.1 37 ms 60 ms
11 197.242.144.1 36 ms
traceroute -n 8.8.8.8
1 192.168.0.1 1 ms 1 ms
2 41.181.53.2 16 ms 81 ms
3 41.181.198.1 76 ms 179 ms
4 Request timed out *
196.44.18.2 158 ms
5 196.44.31.6 119 ms
6 72.14.194.7 84 ms
7 Request timed out *
DNS Test:
nslookup [url]www.afrihost.com[/url]
Name: [url]www.afrihost.com[/url]
Address: 197.242.144.102
nslookup [url]www.google.com[/url]
Name: [url]www.google.com[/url]
Address: 173.194.34.84
Name: [url]www.google.com[/url]
Address: 173.194.34.80
Name: [url]www.google.com[/url]
Address: 173.194.34.81
Name: [url]www.google.com[/url]
Address: 173.194.34.83
Name: [url]www.google.com[/url]
Address: 173.194.34.82
nslookup thishouldfail.afrihost.com
** server can't find thisshouldfail.com: NXDOMAIN
/snip
Still slow :/ How does an IS account work?
It may be something with your area's local exchange and routing onto MTN's network. Or it could be the IPC, but that should be mostly sorted now?
Z
IS accounts have been rock solid. Both capped and uncapped... the uncapped Connection one a bit slow in the day... but no issues.
Hmm... sigh... I don't know -_-
It still doesn't make sense how some people are more affected than others?? How is that possible?
Hmm... sigh... I don't know -_-
It still doesn't make sense how some people are more affected than others?? How is that possible?
From my experience, location (routing) makes a big difference, and one just has to find an ISP that works for them.
Afriman did say though that the IPC upgrade was only a partial order, so it wasn't fully upgraded. I think next week will be bad, just not as bad as the last few months.No complaints so far today. But next week will be the acid test.
Tracing route to google.com [74.125.233.70]
over a maximum of 30 hops:
1 <1 ms 1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 355 ms 149 ms 49 ms 41.181.53.213
4 329 ms 187 ms 250 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
5 * 258 ms 57 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
6 254 ms 369 ms * compj-cpt-1.mtnns.net [196.44.18.2]
7 197 ms 161 ms 129 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
8 370 ms 430 ms * rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]
9 304 ms 327 ms 221 ms 41.181.139.109
10 152 ms 121 ms 127 ms 72.14.194.74
11 134 ms 167 ms 63 ms 64.233.174.57
12 45 ms 38 ms 113 ms jnb01s02-in-f6.1e100.net [74.125.233.70]
Trace complete.
Tracing route to google.com [74.125.233.70]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.254
2 * * * Request timed out.
3 17 ms 136 ms 54 ms ti-226-0-245.telkomadsl.co.za [105.226.0.245]
4 26 ms 37 ms 29 ms ti-226-0-246.telkomadsl.co.za [105.226.0.246]
5 69 ms 85 ms 25 ms ti-226-0-13.telkomadsl.co.za [105.226.0.13]
6 48 ms 49 ms 52 ms wbs-ip-ll-1-wan.telkom-ipnet.co.za [165.165.221.
153]
7 119 ms 48 ms 47 ms rrba-ip-lir-1-gig-3-0-0.telkom-ipnet.co.za [196.
43.11.134]
8 39 ms 39 ms 39 ms 72.14.212.1
9 41 ms 41 ms 42 ms 64.233.174.57
10 48 ms 47 ms 47 ms jnb01s02-in-f6.1e100.net [74.125.233.70]
Trace complete.
Not much better after the "all will be fixed" day
Afrihost business 4mb..
![]()
Telkom Capped account..
![]()
Blame Telkom, not AH, those stats look like a line or exchange fault.
PM TelkomZA so he can check up on the status of that exchange.
Log into your router and find your SNR and Attenuation values of your ADSL line, they will indicate the condition of your line, and will help in troubleshooting.
SNR up is 17.7 db, down is 19.9
Attenuation up is 10.9, down is 14.6
Pardon my ignorance, but how do these stats look in term of line quality?
Afriman did say though that the IPC upgrade was only a partial order, so it wasn't fully upgraded. I think next week will be bad, just not as bad as the last few months.
Well, not as far as I am reading the situation. The 20% upgrade was the upgrade that was expected for 10 April and then 18 April. There is a further upgrade of the South IPC planned for the future, which is why it is being called a provisional upgrade. But this is the one that is supposed to solve all our contention woes.
By saying "provisional", it makes me think that this current upgrade is incomplete and is less than what was planned initially for the 18th.
That's exactly how I understand it though.
An upgrade happened last night - it was a fairly significant amount (about 20%) additional capacity, though we've since upped our order to cater for continued growth for the year. We've only received that portion so far - and the upgrade is live.
We should be seeing full throughput on Business and Capped accounts. If you're not seeing that, please post a local speedtest and traceroute ASAP that I can analyze.
Well, this is what I read,
And from what I read it would seem as if this 20% was THE upgrade, and it is live, but more has been ordered as it is needed.