Afrihost Business Uncapped Feedback - 2

Status
Not open for further replies.
Downloading on afrihost account down the crapper again

Afrihost Business Account tracert

Tracing route to www.movreel.com [89.46.103.114]
over a maximum of 30 hops:

1 1 ms 1 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 104 ms 140 ms 145 ms 41.181.221.245
4 11 ms 10 ms 12 ms 41.181.221.246
5 10 ms 9 ms 9 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
6 10 ms 10 ms 9 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.114]
7 220 ms 209 ms 207 ms 41.181.180.10
8 214 ms 206 ms 207 ms ls-cr-2.uk--rb-cr-1.za.mtnns.net [196.44.31.114]

9 265 ms 216 ms 189 ms ls-pr-1.uk--ls-cr-2.uk-a.mtn.net [209.212.111.20
1]
10 221 ms 208 ms 266 ms TenGigabitEthernet8-2.ar6.LON3.gblx.net [208.48.
238.185]
11 208 ms 206 ms 207 ms p1-0.globalcrossing.londen03.uk.bb.gin.ntt.net [
208.50.13.146]
12 200 ms 211 ms 200 ms ae-4.r22.londen03.uk.bb.gin.ntt.net [129.250.5.2
4]
13 311 ms 230 ms 230 ms ae-3.r21.frnkge03.de.bb.gin.ntt.net [129.250.3.1
38]
14 235 ms 235 ms 234 ms ae-3.r02.frnkge04.de.bb.gin.ntt.net [129.250.4.5
4]
15 258 ms 257 ms 256 ms ae-3.r00.buchro01.ro.bb.gin.ntt.net [129.250.3.2
35]
16 234 ms 234 ms 235 ms te5-15-0-bb1.buc1.ro.m247.ro [83.217.231.70]
17 * * * Request timed out.
18 256 ms 256 ms 267 ms mx-pool114.intelicontacts.com [89.46.103.114]

Trace complete.

Web Africa tracert

Tracing route to www.movreel.com [89.46.103.114]
over a maximum of 30 hops:

1 2 ms 4 ms 2 ms 192.168.0.1
2 * * * Request timed out.
3 11 ms 9 ms 10 ms cdsl1-rba-vl2360-ipc.ip.isnet.net [196.38.73.134
]
4 10 ms 10 ms 10 ms cdsl1-rba-vl2360.ip.isnet.net [196.38.73.133]
5 11 ms 9 ms 9 ms cdsl1-rba-vl150.ip.isnet.net [196.38.73.17]
6 14 ms 10 ms 10 ms core2-pkl-t0-7-0-0.ip.isnet.net [168.209.1.163]

7 185 ms 183 ms 183 ms 168.209.246.66
8 183 ms 182 ms 237 ms xe-0-4-0-6.r02.londen03.uk.bb.gin.ntt.net [83.23
1.235.221]
9 295 ms 176 ms 191 ms ae-4.r22.londen03.uk.bb.gin.ntt.net [129.250.5.2
4]
10 189 ms 279 ms 189 ms ae-3.r21.frnkge03.de.bb.gin.ntt.net [129.250.3.1
38]
11 215 ms 215 ms 215 ms ae-3.r02.frnkge04.de.bb.gin.ntt.net [129.250.4.5
4]
12 288 ms 218 ms 217 ms ae-3.r00.buchro01.ro.bb.gin.ntt.net [129.250.3.2
35]
13 218 ms 215 ms 216 ms 83.217.231.18
14 * * * Request timed out.
15 216 ms 221 ms 223 ms mx-pool114.intelicontacts.com [89.46.103.114]

Trace complete.
 
Anyone at AH care to comment on this?

Tracing route to www.afrihost.com [197.242.144.102]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.1
2 567 ms 470 ms 453 ms 105-236-1-1-esr-lo.mtnbusiness.co.za [105.236.1.
1]
3 53 ms 50 ms 76 ms 41.181.221.214
4 304 ms 433 ms 901 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.118]

5 641 ms 793 ms 673 ms rb-cr-1.za--rb-dca-2.mtnns.net [196.44.31.122]
6 256 ms 270 ms 878 ms 196.44.31.97

7 935 ms 1013 ms 690 ms 196.30.1.53
8 95 ms 128 ms 129 ms 196.31.220.27
9 487 ms 365 ms 377 ms 196.31.63.202
10 418 ms 405 ms 527 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
11 * 377 ms 336 ms cms-gm.afrihost.com [197.242.144.102]


Trace complete.

Edit ... East region.
 
Anyone at AH care to comment on this?

Tracing route to www.afrihost.com [197.242.144.102]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.1
2 567 ms 470 ms 453 ms 105-236-1-1-esr-lo.mtnbusiness.co.za [105.236.1.
1]
3 53 ms 50 ms 76 ms 41.181.221.214
4 304 ms 433 ms 901 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.118]

5 641 ms 793 ms 673 ms rb-cr-1.za--rb-dca-2.mtnns.net [196.44.31.122]
6 256 ms 270 ms 878 ms 196.44.31.97

7 935 ms 1013 ms 690 ms 196.30.1.53
8 95 ms 128 ms 129 ms 196.31.220.27
9 487 ms 365 ms 377 ms 196.31.63.202
10 418 ms 405 ms 527 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
11 * 377 ms 336 ms cms-gm.afrihost.com [197.242.144.102]


Trace complete.
Could you run a trace on another ISP account?

Just for conclusive evidence it's AH related as I can almost guarantee they will ask the same or blame the exchange :-/
 
Anyone at AH care to comment on this?

Tracing route to www.afrihost.com [197.242.144.102]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.1
2 567 ms 470 ms 453 ms 105-236-1-1-esr-lo.mtnbusiness.co.za [105.236.1.
1]
3 53 ms 50 ms 76 ms 41.181.221.214
4 304 ms 433 ms 901 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.118]

5 641 ms 793 ms 673 ms rb-cr-1.za--rb-dca-2.mtnns.net [196.44.31.122]
6 256 ms 270 ms 878 ms 196.44.31.97

7 935 ms 1013 ms 690 ms 196.30.1.53
8 95 ms 128 ms 129 ms 196.31.220.27
9 487 ms 365 ms 377 ms 196.31.63.202
10 418 ms 405 ms 527 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
11 * 377 ms 336 ms cms-gm.afrihost.com [197.242.144.102]


Trace complete.

Your line or exchange is at fault, not isp

Code:
Tracing route to afrihost.com [197.242.144.102]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     8 ms     8 ms     9 ms  105-236-14-65-esr-lo.mtnbusiness.co.za [105.236.14.65]
  3    13 ms    10 ms    12 ms  ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178.89]
  4    13 ms    11 ms    12 ms  rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
  5    21 ms    12 ms    10 ms  jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
  6    11 ms    10 ms    11 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
  7    13 ms    15 ms    13 ms  196.44.31.99
  8    14 ms    14 ms    12 ms  196.30.1.53
  9    14 ms    14 ms    14 ms  196.31.220.27
 10    13 ms    12 ms    12 ms  196.31.63.202
 11    12 ms    12 ms    11 ms  vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
 12    13 ms    12 ms    19 ms  cms-gm.afrihost.com [197.242.144.102]
 
That high latency at the exchange can also be caused by you doing a lot of uploads at the moment, like iCloud/Google+ photo backups or the like.

Saturating your upload wreaks havoc on everything else.
 
Could you run a trace on another ISP account?

Just for conclusive evidence it's AH related as I can almost guarantee they will ask the same or blame the exchange :-/

They logged a fault on my behalf with Telkom.
Dude came out and sorted the line.

Spose I could do the whole guest account thing, and go round in circles, but the last time I did this .... it just ended up in an argument.

This year, I am trying to be cool with AH and hope they will reciprocate ....

When they see this post they will immediately get their smartest techie to check it out, or call in a bunch of favours and get the Tekom side sorted .....

/waits in anticipation for resolution because posting here is painful .... but not as bad as being caller number 94
 
Still dropping packets with afrihost because of IPC hop...

C:\Users\Neil>ping www.google.co.za

Pinging www.google.co.za [216.58.223.35] with 32 bytes of data:
Reply from 216.58.223.35: bytes=32 time=51ms TTL=53
Request timed out.
Reply from 216.58.223.35: bytes=32 time=43ms TTL=53
Request timed out.

Ping statistics for 216.58.223.35:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 51ms, Average = 47ms

C:\Users\Neil>ping www.google.co.za

Pinging www.google.co.za [216.58.223.35] with 32 bytes of data:
Reply from 216.58.223.35: bytes=32 time=73ms TTL=53
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 216.58.223.35:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 73ms, Maximum = 73ms, Average = 73ms

C:\Users\Neil>tracert www.google.co.za

Tracing route to www.google.co.za [216.58.223.35]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.254
2 31 ms 31 ms 32 ms 105-236-15-1-esr-lo.mtnbusiness.co.za [105.236.15.1]
3 * 33 ms 35 ms ipc-recieve-jh-4a.za.mtnbusiness.net [41.181.178.41]
4 33 ms 34 ms * qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
5 * 49 ms 91 ms jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
6 46 ms * * 41.181.180.10
7 * * 34 ms rb-cr-2.za--jh-cr-1.za.mtnns.net [196.44.0.43]
8 34 ms 35 ms 35 ms 41.181.139.99
9 36 ms 38 ms 34 ms 72.14.194.74
10 35 ms 39 ms 37 ms 72.14.239.129
11 40 ms 51 ms 45 ms jnb01s08-in-f3.1e100.net [216.58.223.35]

Trace complete.

_____________________________________________________________________________
Ping with Webafrica
C:\Users\Neil>ping www.google.co.za

Pinging www.google.co.za [216.58.223.35] with 32 bytes of data:
Reply from 216.58.223.35: bytes=32 time=37ms TTL=54
Reply from 216.58.223.35: bytes=32 time=36ms TTL=54
Reply from 216.58.223.35: bytes=32 time=37ms TTL=54
Reply from 216.58.223.35: bytes=32 time=37ms TTL=54

Ping statistics for 216.58.223.35:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 37ms, Average = 36ms
____________________________________________________________


on the Afrihost tracert it is dropping packets at the ipc-recieve-jh-4a.za.mtnbusiness.net [41.181.178.41]

I tried changing my DNS to 197.8.8.8 and 8.8.8.8 secondary with no change

NNTP, torrents and browsing running at a fair speed
 
Last edited:
Lag again this evening starting at about the same time:

Pinging ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150] with 32 bytes of data:

Reply from 41.181.53.150: bytes=32 time=65ms TTL=59
Reply from 41.181.53.150: bytes=32 time=74ms TTL=59
Reply from 41.181.53.150: bytes=32 time=62ms TTL=59
Reply from 41.181.53.150: bytes=32 time=50ms TTL=59
Reply from 41.181.53.150: bytes=32 time=68ms TTL=59
Reply from 41.181.53.150: bytes=32 time=84ms TTL=59
Reply from 41.181.53.150: bytes=32 time=53ms TTL=59
Reply from 41.181.53.150: bytes=32 time=65ms TTL=59
Reply from 41.181.53.150: bytes=32 time=68ms TTL=59
Reply from 41.181.53.150: bytes=32 time=71ms TTL=59
Reply from 41.181.53.150: bytes=32 time=54ms TTL=59
Reply from 41.181.53.150: bytes=32 time=64ms TTL=59
Reply from 41.181.53.150: bytes=32 time=70ms TTL=59
Reply from 41.181.53.150: bytes=32 time=66ms TTL=59

Tracing route to ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms dsldevice.domain.name [192.168.0.2]
2 9 ms 9 ms 9 ms 105-236-10-129-esr-lo.mtnbusiness.co.za [105.236.10.129]
3 66 ms 63 ms 72 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
 
Well now, back to square 1...

Oh well...

Afrihost
Traceroute output:
1 * * *
2 41.181.221.213 (41.181.221.213) 114.017 ms 59.331 ms 105.554 ms
3 41.181.221.214 (41.181.221.214) 56.457 ms 28.264 ms 28.237 ms
4 rb-dca-2.za--qux-b.za.mtnbusiness.net (41.181.165.118) 38.229 ms 32.394 ms 33.093 ms
5 rb-dca-2.za--rb-cr-1.mtnns.net (196.44.31.122) 29.099 ms 28.814 ms 34.221 ms
6 196.44.31.97 (196.44.31.97) 30.511 ms 45.926 ms
jh-dca-2.za--jh-cr-1.za-a.mtnns.net (196.44.0.221) 29.391 ms
7 196.30.1.53 (196.30.1.53) 33.798 ms 33.818 ms 34.797 ms
8 196.31.220.27 (196.31.220.27) 27.937 ms 43.550 ms 31.332 ms
9 196.31.63.202 (196.31.63.202) 38.777 ms 33.515 ms 38.522 ms
10 vl9-ah-ha-2.za.mtnbusiness.net (196.30.42.133) 33.930 ms 34.106 ms 33.928 ms
11 cms-gm.afrihost.com (197.242.144.102) 36.810 ms 35.218 ms 37.087 ms

WebAfrica
Traceroute output:
1 * * *
2 196.38.74.246 (196.38.74.246) 58.674 ms 7.813 ms 7.509 ms
3 cdsl1-umh-gi0-0-0-3102.ip.isnet.net (196.38.74.245) 7.833 ms 7.948 ms 7.717 ms
4 196.26.210.200 (196.26.210.200) 7.822 ms 7.904 ms 7.364 ms
5 mi-za-umh-p7-ten-0-0-1-1.ip.isnet.net (168.209.93.239) 8.155 ms 8.210 ms 8.405 ms
6 mi-za-bry-p7-lo0.ip.isnet.net (168.209.255.208) 20.480 ms 19.511 ms 19.985 ms
7 core2a-bry-gi1-0-0.ip.isnet.net (168.209.218.2) 17.740 ms 18.068 ms 17.263 ms
8 168.209.100.205 (168.209.100.205) 17.880 ms 17.644 ms 17.643 ms
9 196.26.0.10 (196.26.0.10) 17.750 ms 20.042 ms 17.208 ms
10 mtnns-2.jinx.net.za (196.223.14.31) 18.234 ms 19.088 ms 18.487 ms
11 jh-cr-2.za--jh-pr-1.za.mtnns.net (196.44.0.223) 20.409 ms 20.614 ms 19.701 ms
12 196.44.31.99 (196.44.31.99) 19.702 ms 19.802 ms 19.563 ms
13 196.30.1.39 (196.30.1.39) 20.329 ms 20.461 ms 20.445 ms
14 196.31.220.23 (196.31.220.23) 22.488 ms 19.455 ms 19.335 ms
15 196.31.63.206 (196.31.63.206) 19.898 ms 20.116 ms 19.424 ms
16 vl9-ah-ha-2.za.mtnbusiness.net (196.30.42.133) 19.734 ms 20.026 ms 19.200 ms
17 cms-gm.afrihost.com (197.242.144.102) 19.000 ms 19.801 ms 19.952 ms
 
Youtube is buffering 720p lately. Damn annoying. Latency is also rubbish. Loaded up my 1GB Web Africa account and there are definitely no problems with my line.

is it just me or is Afrihost now shaping business lines?

Run the Glasnost test and report back...
 
It happened again! For the third night in a row, at precisely 10:32pm (give or take a few seconds), my NNTP download speed switched from being utterly useless to full speed. This can't be explained away as mere coincidence or natural adjustment to decreased traffic -- it is too abrupt and too precisely timed. It is clear that some form of selective restriction is lifted at that specific time. And come morning (not sure of the time yet), the affected protocols are again reduced to a snail's pace.

Just my experience. Shaping, anyone?
 
Question: Why are windows 10 updates so pathetically slow?

Same thing with downloading star citizen, can't get more than 100KB/s

Not sure if my other issue is AH related but randomly webpages just stop loading as well, quite infuriating!

C:\Users\Michael>pathping google.co.za

Tracing route to google.co.za [66.8.14.48]
over a maximum of 30 hops:
0 TheTouched [192.168.0.4]
1 192.168.0.1
2 105-236-10-65-esr-lo.mtnbusiness.co.za [105.236.10.65]
3 41.181.51.182
4 tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 unc-cpt-1.mtnns.net [196.44.18.8]
6 pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66]
7 jh-dca-2.za--jh-cr-1.za-a.mtnns.net [41.181.180.11]
8 cache.google.com [66.8.14.48]

Computing statistics for 200 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 TheTouched [192.168.0.4]
0/ 100 = 0% |
1 30ms 0/ 100 = 0% 0/ 100 = 0% 192.168.0.1
3/ 100 = 3% |
2 1352ms 98/ 100 = 98% 95/ 100 = 95% 105-236-10-65-esr-lo.mtnbusiness.co.za [105.236.10.65]
0/ 100 = 0% |
3 1151ms 8/ 100 = 8% 5/ 100 = 5% 41.181.51.182
0/ 100 = 0% |
4 1123ms 3/ 100 = 3% 0/ 100 = 0% tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
3/ 100 = 3% |
5 1201ms 6/ 100 = 6% 0/ 100 = 0% unc-cpt-1.mtnns.net [196.44.18.8]
12/ 100 = 12% |
6 --- 100/ 100 =100% 82/ 100 = 82% pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66]
0/ 100 = 0% |
7 --- 100/ 100 =100% 82/ 100 = 82% jh-dca-2.za--jh-cr-1.za-a.mtnns.net [41.181.180.11]
0/ 100 = 0% |
8 1153ms 18/ 100 = 18% 0/ 100 = 0% cache.google.com [66.8.14.48]

irony: the above was when I had a working connection.

When I can't load pages:
Tracing route to google.co.za [66.8.14.27]
over a maximum of 30 hops:

1 2 ms 2 ms 1 ms 192.168.0.1
2 253 ms 66 ms 30 ms 105-236-10-65-esr-lo.mtnbusiness.co.za [105.236.10.65]
3 50 ms 51 ms 54 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 49 ms 49 ms 49 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 53 ms 50 ms 49 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 85 ms 73 ms 76 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
7 291 ms 306 ms 303 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [41.181.180.11]
8 232 ms 85 ms 79 ms cache.google.com [66.8.14.27]

Trace complete.
 
Last edited:
Is it me or is Afrihost dog slow right now. Im struggling to load webpages at the moment. I can load a speed test and get good results but any other web traffic is almost unusable.

Yeah it's crap for me too. Glasnost test showed shaping on torrent and NNTP. Youtube can't stream worth a damn. Speed tests aren't what they usually are.

If I switch to Web Africa everything works 100%.
 
It happened again! For the third night in a row, at precisely 10:32pm (give or take a few seconds), my NNTP download speed switched from being utterly useless to full speed. This can't be explained away as mere coincidence or natural adjustment to decreased traffic -- it is too abrupt and too precisely timed. It is clear that some form of selective restriction is lifted at that specific time. And come morning (not sure of the time yet), the affected protocols are again reduced to a snail's pace.

Just my experience. Shaping, anyone?

You already know what their answer is going to be.
 
What a crock of shyte ..... :cry:

AH, you have to do something here,

Youtube is non existent for me.

Tracing route to www.afrihost.com [197.242.144.102]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.1
2 567 ms 470 ms 453 ms 105-236-1-1-esr-lo.mtnbusiness.co.za [105.236.1.
1]
3 53 ms 50 ms 76 ms 41.181.221.214
4 304 ms 433 ms 901 ms rb-dca-2.za--qux-b.za.mtnbusiness.net [41.181.16
5.118]
5 641 ms 793 ms 673 ms rb-cr-1.za--rb-dca-2.mtnns.net [196.44.31.122]
6 256 ms 270 ms 878 ms 196.44.31.97
7 935 ms 1013 ms 690 ms 196.30.1.53
8 95 ms 128 ms 129 ms 196.31.220.27
9 487 ms 365 ms 377 ms 196.31.63.202
10 418 ms 405 ms 527 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
11 * 377 ms 336 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.
 
Last edited:
Okay AH,
Now you can't blame Telkom anymore:

Tracing route to afrihost.com [197.242.144.102]
over a maximum of 30 hops:

1 2 ms 2 ms 1 ms 192.168.0.1
2 26 ms 15 ms 12 ms 105-236-3-193-esr-lo.mtnbusiness.co.za [105.236.3.193]
3 15 ms 14 ms 15 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178.77]
4 21 ms 18 ms 17 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.120]
5 15 ms 14 ms 15 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 16 ms 17 ms 15 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 17 ms 16 ms 17 ms 196.44.31.99
8 17 ms 15 ms 16 ms 196.31.220.8
9 16 ms 17 ms 15 ms 196.31.220.27
10 16 ms 24 ms 15 ms 196.31.63.202
11 17 ms 16 ms 15 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
12 17 ms 16 ms 16 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.

WHY ARE YOU SHAPING ACCOUNTS?

http://www.speedtest.net/my-result/4278451794
http://www.speedtest.net/my-result/4278453233

P2P is dead. And I need to download updates for my iDevices and it is so darn slow. So what is up this time?

Every 3 months we do this dance. GET YOU POO TOGETHER AH!
 
Last edited:
They logged a fault on my behalf with Telkom.
Dude came out and sorted the line.

Spose I could do the whole guest account thing, and go round in circles, but the last time I did this .... it just ended up in an argument.

This year, I am trying to be cool with AH and hope they will reciprocate ....

When they see this post they will immediately get their smartest techie to check it out, or call in a bunch of favours and get the Tekom side sorted .....

/waits in anticipation for resolution because posting here is painful .... but not as bad as being caller number 94

We'll definitely help where we can. The results you're posting can only be either a line fault or congestion. We don't have any influence over the 2nd of that route, it's a device on Telkom's network.

If the fault has been logged, just PM me if you're not getting feedback and I'll chase it up for you.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X