Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
AfriMan

AfriMan

Afrihost Representative
Company Rep
Joined
May 24, 2012
Messages
17,239
jannier said:
Just got a call from TelkomZA, he really goes out of his way to help and resolve issues.
He does go the extra mile! Damn extra many miles!
He contacted SAIX IPNET on behalf of MTN and AH and got my routing issue resolves.

WA ISP:
Tracing route to webafrica.co.za [41.185.61.34]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 7 ms 7 ms 8 ms cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194]
4 6 ms 7 ms 6 ms vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
5 7 ms 6 ms 6 ms 196.35.115.136
6 6 ms 6 ms 6 ms 196.26.78.33
7 6 ms 6 ms 6 ms wa-is.isdsl.net [196.38.72.84]
8 6 ms 6 ms 7 ms wnls-hr2-vl-140.wa.co.za [41.185.1.1]
9 7 ms 6 ms 7 ms webafrica.co.za [41.185.61.34]

Trace complete.

AH ISP:
Tracing route to webafrica.co.za [41.185.61.34]
over a maximum of 30 hops:

1 * * * Request timed out.
2 18 ms 8 ms 14 ms 41.181.201.93
3 13 ms 7 ms 8 ms 41.181.201.94
4 6 ms 5 ms 5 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 7 ms 5 ms 6 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 9 ms 10 ms 11 ms 196.44.31.106
7 9 ms 20 ms 27 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 8 ms 7 ms 7 ms 41-208-29-209.mtnns.net [41.208.29.209]
9 8 ms 8 ms 12 ms css2-ctn-gi0-2.ip.isnet.net [168.209.6.15]
10 6 ms 10 ms 8 ms mi-za-cpt-br1-gi0-3-108.ip.isnet.net [168.209.28.42]
11 7 ms 7 ms 7 ms 197.96.154.190
12 11 ms 9 ms 9 ms 197.96.154.191
13 8 ms 7 ms 7 ms webafrica.co.za [41.185.61.34]

Trace complete.


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

1 * * * Request timed out.
2 8 ms 8 ms 8 ms 41.181.53.213
3 8 ms 8 ms 7 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 8 ms 7 ms 7 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 9 ms 10 ms 12 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 8 ms 8 ms 8 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 35 ms 28 ms 29 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]
8 30 ms 34 ms 28 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.221]
9 28 ms 45 ms 29 ms 196.30.1.53
10 27 ms 28 ms 28 ms 196.31.220.25
11 28 ms 32 ms 36 ms 196.31.63.206
12 28 ms 29 ms 29 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
13 30 ms 31 ms 29 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.
Click to expand...

From the previous report if this issue, the issue was only able to be resolved on Telkom's side, as it related to a misconfiguration on their MSAN.
 
S

Seeyou

Expert Member
Joined
May 1, 2007
Messages
2,707
Well I can tell you from personal experience the heavier shaping on uncapped has had zero effect, which I must believe your networking team can see.

AfriMan - can one pause an account and then cancel it before the end of the pause period, without incurring charges?
 
AfriMan

AfriMan

Afrihost Representative
Company Rep
Joined
May 24, 2012
Messages
17,239
Seeyou said:
Well I can tell you from personal experience the heavier shaping on uncapped has had zero effect, which I must believe your networking team can see.

AfriMan - can one pause an account and then cancel it before the end of the pause period, without incurring charges?
Click to expand...

We are seeing as we shape Uncapped accounts that Business and Capped are getting more throughput in general. However individual experiences may vary.

You can pause your account for the next month (before the billing run on the 25th). Cancellation will take effect in the same way. You should be able to cancel a paused product directly in ClientZone.
 
S

Seeyou

Expert Member
Joined
May 1, 2007
Messages
2,707
AfriMan said:
We are seeing as we shape Uncapped accounts that Business and Capped are getting more throughput in general. However individual experiences may vary.

You can pause your account for the next month (before the billing run on the 25th). Cancellation will take effect in the same way. You should be able to cancel a paused product directly in ClientZone.
Click to expand...

Perhaps in other parts of the country, but I'm still getting 500k/sec downloads on a 20mbps line in the late evenings, and streaming performance is pretty crap during the same period, down here in Cape Town.

Great, I'll pause my service and check back again next month.
 
AfriMan

AfriMan

Afrihost Representative
Company Rep
Joined
May 24, 2012
Messages
17,239
Seeyou said:
Perhaps in other parts of the country, but I'm still getting 500k/sec downloads on a 20mbps line in the late evenings, and streaming performance is pretty crap during the same period, down here in Cape Town.

Great, I'll pause my service and check back again next month.
Click to expand...

We're still monitoring demand issues in the South, as per the website notice. Once we've run more tests, we'll know whether the performance has improved as we expect.
 
roadcat

roadcat

Expert Member
Joined
Mar 23, 2006
Messages
2,636
jannier said:
Just got a call from TelkomZA, he really goes out of his way to help and resolve issues.
He does go the extra mile! Damn extra many miles!
He contacted SAIX IPNET on behalf of MTN and AH and got my routing issue resolves.

WA ISP:
Tracing route to webafrica.co.za [41.185.61.34]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 7 ms 7 ms 8 ms cdsl2-ctn-vl2473-ipc.ip.isnet.net [196.38.72.194]
4 6 ms 7 ms 6 ms vlan2473.cdsl2-ctn.isdsl.net [196.38.72.193]
5 7 ms 6 ms 6 ms 196.35.115.136
6 6 ms 6 ms 6 ms 196.26.78.33
7 6 ms 6 ms 6 ms wa-is.isdsl.net [196.38.72.84]
8 6 ms 6 ms 7 ms wnls-hr2-vl-140.wa.co.za [41.185.1.1]
9 7 ms 6 ms 7 ms webafrica.co.za [41.185.61.34]

Trace complete.

AH ISP:
Tracing route to webafrica.co.za [41.185.61.34]
over a maximum of 30 hops:

1 * * * Request timed out.
2 18 ms 8 ms 14 ms 41.181.201.93
3 13 ms 7 ms 8 ms 41.181.201.94
4 6 ms 5 ms 5 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 7 ms 5 ms 6 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 9 ms 10 ms 11 ms 196.44.31.106
7 9 ms 20 ms 27 ms nl-ha-2.za--rb-cr-1.za-a.mtnns.net [196.44.0.121]
8 8 ms 7 ms 7 ms 41-208-29-209.mtnns.net [41.208.29.209]
9 8 ms 8 ms 12 ms css2-ctn-gi0-2.ip.isnet.net [168.209.6.15]
10 6 ms 10 ms 8 ms mi-za-cpt-br1-gi0-3-108.ip.isnet.net [168.209.28.42]
11 7 ms 7 ms 7 ms 197.96.154.190
12 11 ms 9 ms 9 ms 197.96.154.191
13 8 ms 7 ms 7 ms webafrica.co.za [41.185.61.34]

Trace complete.


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

1 * * * Request timed out.
2 8 ms 8 ms 8 ms 41.181.53.213
3 8 ms 8 ms 7 ms ipc-send-tb-3a.mtnbusiness.net [41.181.53.214]
4 8 ms 7 ms 7 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
5 9 ms 10 ms 12 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 8 ms 8 ms 8 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]
7 35 ms 28 ms 29 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]
8 30 ms 34 ms 28 ms jh-dca-2.za--jh-cr-1.za-a.mtnns.net [196.44.0.221]
9 28 ms 45 ms 29 ms 196.30.1.53
10 27 ms 28 ms 28 ms 196.31.220.25
11 28 ms 32 ms 36 ms 196.31.63.206
12 28 ms 29 ms 29 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
13 30 ms 31 ms 29 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.
Click to expand...

Hmm, wonder if he can sort the same issue out for me in PE. Will PM him.
 
S

steel_dog

Senior Member
Joined
Jul 5, 2010
Messages
769
AfriMan said:
We're still monitoring demand issues in the South, as per the website notice. Once we've run more tests, we'll know whether the performance has improved as we expect.
Click to expand...
Hey Afriman.
Things are still erratic in CPT.
Local is once again reasonable... hitting high 7mbps.
International is maxing out badly at mid 2mbps.
Pings are showing latency spikes.

Code: 
Ping statistics for 197.242.144.102: [www.afrihost.com] 
    Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 31ms, Maximum = 176ms, Average = 57ms
 
AfriGuy

AfriGuy

Afrihost
Company Rep
Joined
Jun 12, 2013
Messages
14,236
steel_dog said:
Hey Afriman.
Things are still erratic in CPT.
Local is once again reasonable... hitting high 7mbps.
International is maxing out badly at mid 2mbps.
Pings are showing latency spikes.

Code: 
Ping statistics for 197.242.144.102: [www.afrihost.com] 
    Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 31ms, Maximum = 176ms, Average = 57ms
Click to expand...

The South is looking better, but not 100% just yet :(
Looks like changes are still filtering down, seeing many more positive results.
 
Johnatan56

Johnatan56

Honorary Master
Joined
Aug 23, 2013
Messages
30,961
AfriGuy said:
The South is looking better, but not 100% just yet :(
Looks like changes are still filtering down, seeing many more positive results.
Click to expand...

just started having issues now:
>ping afrihost.com -t

Pinging afrihost.com [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=40ms TTL=58
Reply from 197.242.144.102: bytes=32 time=271ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=93ms TTL=58
Reply from 197.242.144.102: bytes=32 time=35ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=30ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=80ms TTL=58
Reply from 197.242.144.102: bytes=32 time=103ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=36ms TTL=58
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=45ms TTL=58
Reply from 197.242.144.102: bytes=32 time=34ms TTL=58
Reply from 197.242.144.102: bytes=32 time=58ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=38ms TTL=58
Reply from 197.242.144.102: bytes=32 time=491ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=30ms TTL=58
Reply from 197.242.144.102: bytes=32 time=30ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58
Reply from 197.242.144.102: bytes=32 time=115ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=86ms TTL=58
Reply from 197.242.144.102: bytes=32 time=34ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=35ms TTL=58
Reply from 197.242.144.102: bytes=32 time=38ms TTL=58
Reply from 197.242.144.102: bytes=32 time=34ms TTL=58
Reply from 197.242.144.102: bytes=32 time=53ms TTL=58
Request timed out.
Reply from 197.242.144.102: bytes=32 time=58ms TTL=58
Reply from 197.242.144.102: bytes=32 time=46ms TTL=58
Reply from 197.242.144.102: bytes=32 time=219ms TTL=58

Ping statistics for 197.242.144.102:
Packets: Sent = 69, Received = 68, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 491ms, Average = 51ms

What have you done? Didn't have packet loss before.

EDIT: Some more, no packet loss but even higher ping.
ping afrihost.com -t

Pinging afrihost.com [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=780ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=35ms TTL=58
Reply from 197.242.144.102: bytes=32 time=38ms TTL=58
Reply from 197.242.144.102: bytes=32 time=34ms TTL=58
Reply from 197.242.144.102: bytes=32 time=36ms TTL=58
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58
Reply from 197.242.144.102: bytes=32 time=38ms TTL=58
Reply from 197.242.144.102: bytes=32 time=36ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=35ms TTL=58
Reply from 197.242.144.102: bytes=32 time=37ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58
Reply from 197.242.144.102: bytes=32 time=34ms TTL=58
Reply from 197.242.144.102: bytes=32 time=53ms TTL=58
Reply from 197.242.144.102: bytes=32 time=140ms TTL=58
Reply from 197.242.144.102: bytes=32 time=121ms TTL=58
Reply from 197.242.144.102: bytes=32 time=49ms TTL=58
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=36ms TTL=58
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=36ms TTL=58
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58
Reply from 197.242.144.102: bytes=32 time=39ms TTL=58
Reply from 197.242.144.102: bytes=32 time=36ms TTL=58
Reply from 197.242.144.102: bytes=32 time=43ms TTL=58
Reply from 197.242.144.102: bytes=32 time=125ms TTL=58
Reply from 197.242.144.102: bytes=32 time=37ms TTL=58
Reply from 197.242.144.102: bytes=32 time=38ms TTL=58
Reply from 197.242.144.102: bytes=32 time=34ms TTL=58
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=36ms TTL=58
Reply from 197.242.144.102: bytes=32 time=38ms TTL=58
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58
Reply from 197.242.144.102: bytes=32 time=36ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58
Reply from 197.242.144.102: bytes=32 time=61ms TTL=58
Reply from 197.242.144.102: bytes=32 time=131ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=82ms TTL=58
Reply from 197.242.144.102: bytes=32 time=38ms TTL=58
Reply from 197.242.144.102: bytes=32 time=36ms TTL=58
Reply from 197.242.144.102: bytes=32 time=34ms TTL=58

Ping statistics for 197.242.144.102:
Packets: Sent = 59, Received = 59, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 31ms, Maximum = 780ms, Average = 55ms
 
Last edited:
AfriGuy

AfriGuy

Afrihost
Company Rep
Joined
Jun 12, 2013
Messages
14,236
Johnatan56 said:
just started having issues now:
>ping afrihost.com -t

Pinging afrihost.com [197.242.144.102] with 32 bytes of data:
Reply from 197.242.144.102: bytes=32 time=40ms TTL=58
Reply from 197.242.144.102: bytes=32 time=271ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=93ms TTL=58
Reply from 197.242.144.102: bytes=32 time=35ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=30ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=80ms TTL=58
Reply from 197.242.144.102: bytes=32 time=103ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=36ms TTL=58
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=45ms TTL=58
Reply from 197.242.144.102: bytes=32 time=34ms TTL=58
Reply from 197.242.144.102: bytes=32 time=58ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=38ms TTL=58
Reply from 197.242.144.102: bytes=32 time=491ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=30ms TTL=58
Reply from 197.242.144.102: bytes=32 time=30ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=31ms TTL=58
Reply from 197.242.144.102: bytes=32 time=33ms TTL=58
Reply from 197.242.144.102: bytes=32 time=115ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=86ms TTL=58
Reply from 197.242.144.102: bytes=32 time=34ms TTL=58
Reply from 197.242.144.102: bytes=32 time=32ms TTL=58
Reply from 197.242.144.102: bytes=32 time=35ms TTL=58
Reply from 197.242.144.102: bytes=32 time=38ms TTL=58
Reply from 197.242.144.102: bytes=32 time=34ms TTL=58
Reply from 197.242.144.102: bytes=32 time=53ms TTL=58
Request timed out.
Reply from 197.242.144.102: bytes=32 time=58ms TTL=58
Reply from 197.242.144.102: bytes=32 time=46ms TTL=58
Reply from 197.242.144.102: bytes=32 time=219ms TTL=58

Ping statistics for 197.242.144.102:
Packets: Sent = 69, Received = 68, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 491ms, Average = 51ms

What have you done? Didn't have packet loss before.
Click to expand...

No changes have been made to affect this, do you have a traceroute that I can look at?
 
Johnatan56

Johnatan56

Honorary Master
Joined
Aug 23, 2013
Messages
30,961
AfriGuy said:
No changes have been made to affect this, do you have a traceroute that I can look at?
Click to expand...

Looks normal, but having ping spikes. Will wait a while, maybe it will sort itself out.

>tracert afrihost.com

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

1 1 ms 1 ms 1 ms 192.168.1.1
2 8 ms 7 ms 7 ms 105-236-234-65-esr-lo.mtnbusiness.co.za [105.236
.234.65]
3 18 ms 14 ms 16 ms 41.181.221.254
4 12 ms 11 ms 14 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 21 ms 11 ms 13 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 12 ms 21 ms 12 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

7 35 ms 50 ms 36 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]

8 32 ms 35 ms 35 ms 196.44.31.97
9 36 ms 33 ms 34 ms 196.31.220.12
10 34 ms 42 ms 35 ms 196.31.220.25
11 32 ms 31 ms 31 ms 196.31.63.206
12 31 ms 31 ms 31 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
13 42 ms 44 ms 44 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.
 
AfriGuy

AfriGuy

Afrihost
Company Rep
Joined
Jun 12, 2013
Messages
14,236
Johnatan56 said:
Looks normal, but having ping spikes. Will wait a while, maybe it will sort itself out.

>tracert afrihost.com

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

1 1 ms 1 ms 1 ms 192.168.1.1
2 8 ms 7 ms 7 ms 105-236-234-65-esr-lo.mtnbusiness.co.za [105.236
.234.65]
3 18 ms 14 ms 16 ms 41.181.221.254
4 12 ms 11 ms 14 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 21 ms 11 ms 13 ms compj-cpt-1.mtnns.net [196.44.18.2]
6 12 ms 21 ms 12 ms ct-cr-2.za--tb-cr-1.za.mtnns.net [196.44.31.134]

7 35 ms 50 ms 36 ms rb-cr-1.za--ct-cr-2.za.mtnns.net [196.44.31.69]

8 32 ms 35 ms 35 ms 196.44.31.97
9 36 ms 33 ms 34 ms 196.31.220.12
10 34 ms 42 ms 35 ms 196.31.220.25
11 32 ms 31 ms 31 ms 196.31.63.206
12 31 ms 31 ms 31 ms vl9-ah-ha-2.za.mtnbusiness.net [196.30.42.133]
13 42 ms 44 ms 44 ms cms-gm.afrihost.com [197.242.144.102]

Trace complete.
Click to expand...

Keep me posted!
These results don't look too bad, looks like traffic in the South is higher than the East & North - we'll be in calm water soon :)
 
Johnatan56

Johnatan56

Honorary Master
Joined
Aug 23, 2013
Messages
30,961
AfriGuy said:
Keep me posted!
These results don't look too bad, looks like traffic in the South is higher than the East & North - we'll be in calm water soon :)
Click to expand...

At 3:27 pm

Ping statistics for 197.242.144.102:
Packets: Sent = 111, Received = 111, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 228ms, Average = 39ms

Looking better but 228 for a local hop :D

At 3:34pm

Ping statistics for 197.242.144.102:
Packets: Sent = 80, Received = 79, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 360ms, Average = 50ms

Will check again when I get back home at about 1am.
 
AfriGuy

AfriGuy

Afrihost
Company Rep
Joined
Jun 12, 2013
Messages
14,236
Johnatan56 said:
At 3:27 pm

Ping statistics for 197.242.144.102:
Packets: Sent = 111, Received = 111, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 228ms, Average = 39ms

Looking better but 228 for a local hop :D

At 3:34pm

Ping statistics for 197.242.144.102:
Packets: Sent = 80, Received = 79, Lost = 1 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 360ms, Average = 50ms

Will check again when I get back home at about 1am.
Click to expand...

Thanks.
Slight fluctuations may still be seen - but it shouldn't be anything particularly serious.
 
S

steel_dog

Senior Member
Joined
Jul 5, 2010
Messages
769
AfriGuy said:
Thanks.
Slight fluctuations may still be seen - but it shouldn't be anything particularly serious.
Click to expand...
Any reason why International is being pummeled so badly? when Local appears to be... slowing... coming back to typical performance.
I expected issues across both.
 
AfriGuy

AfriGuy

Afrihost
Company Rep
Joined
Jun 12, 2013
Messages
14,236
steel_dog said:
Any reason why International is being pummeled so badly? when Local appears to be... slowing... coming back to typical performance.
I expected issues across both.
Click to expand...

Can't see any obvious reason why :( Although this is generally quite a busy time on the network.
Any test info I can look at?
 
H

HermanTheGerman

Senior Member
Joined
Jan 13, 2008
Messages
560
Steel Dog, that sounds like last mile problems. Maybe your local exchange is congested. AH doesn't throttle capped accounts, period! Datz da reason why we're on those, no? My 100+100 runs like a dream, torrenting 2 huge animes right now (like 1080p full seasons huge) that will be finished in less than 1 hour, my wife is using some forum from her lappy and I'm on MyBB forum. No problems whatsoever.
 
H

HermanTheGerman

Senior Member
Joined
Jan 13, 2008
Messages
560
AfriGuy said:
Keep me posted!
These results don't look too bad, looks like traffic in the South is higher than the East & North - we'll be in calm water soon :)
Click to expand...
You think so? May I remind you that the tourist season is upon us and CPT will have twice the usual number of residents from Nov - Mar? All those tourists wanna skype home, send photos and videos and do all that stuff that tourists do. And they aren't used to sloppy South African "service". Well, maybe if Eskom gives us enough load shedding and nobody can use electronics anyway you'll be spared the worst ambush. :whistling:
 
Status
Not open for further replies.
Top