Afrihost Business Uncapped Feedback

Status
Not open for further replies.

AfriGuy

Afrihost
Company Rep
Joined
Jun 12, 2013
Messages
14,236
So, all of a sudden slow pings again, and the classic symptoms of exchange congestion. Will it actually be exchange congestion this time, or not, as it was also not the 2 times I have had these symptoms?

Please check this, I am in Centurion, and it is very unusable at the moment:

tracert www.racedepartment.com

Tracing route to www.racedepartment.com [31.204.128.181]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Broadcom.Home [192.168.1.1]
2 106 ms 124 ms 120 ms 105-236-4-129-esr-lo.mtnbusiness.co.za [105.236.4.129]
3 113 ms 118 ms 127 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178.77]
4 * 116 ms 126 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.120]
5 72 ms 78 ms 228 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 136 ms 178 ms 143 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 338 ms 359 ms 383 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
8 * * * Request timed out.
9 262 ms 266 ms 274 ms 109.200.218.154
10 341 ms 337 ms 309 ms 80ge.br2-cr0.smartdc.rtd.i3d.net [188.122.95.92]
11 311 ms 298 ms 292 ms hosted-by.i3d.net [31.204.128.181]

Trace complete.


And confirmation from IPC that it is exchange congestion would be nice, not assumptions.

This is definitely exchange related, the latency on the 2nd hop is too high :( Is your line with us?
 

AfriGuy

Afrihost
Company Rep
Joined
Jun 12, 2013
Messages
14,236
MTN seems broken today. Cannot get more than 300-400Kb/s on a 10Mb business uncapped.

Fix your silly network Afrihost.


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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 6 ms 6 ms 105-236-14-1-esr-lo.mtnbusiness.co.za [105.236.1
4.1]
3 165 ms 164 ms 163 ms ipc-recieve-ng-1a.mtnbusiness.net [41.181.201.14
]
4 162 ms 161 ms 162 ms ng-mse-1--ng-cr-1-a.za.mtnns.net [196.44.27.68]

5 167 ms 166 ms 170 ms jh-cr-1.za--ng-cr-1.za.mtnns.net [196.44.31.176]

6 * * * Request timed out.
7 * * * Request timed out.
8 306 ms 306 ms * jh-pr-1.za--jh-cr-2.za.mtnns.net [196.44.0.222]

9 * * * Request timed out.
10 331 ms 320 ms 324 ms CORE.GP-CN-HET-MEE-1.TO.GP-MR-VOD-MEE-1.DFA.P2P.
10G.za.africainx.net [41.84.12.151]
11 * 329 ms 328 ms 41-66-132-242-f2.HET001-CPE-1-to-GP-CN-HET-MEE-1
.africainx.net [41.66.132.242]
12 316 ms 315 ms 313 ms core-access-switch1.jnb1.host-h.net [197.189.193
.1]
13 331 ms 330 ms 333 ms row-access-switch1-row7-8.jnb1.host-h.net [197.1
89.193.39]
14 339 ms * 330 ms 41.203.24.42

Strange seeing the higher latency here. We aren't aware of increased latency on our end, but PM me your info and I'll take a closer look at this for you :)
 

vinodh

Expert Member
Joined
Jan 11, 2009
Messages
2,978
Don't complain about things like this dammit, also your address and Wifi password would be appreciated.

Unfortunately, that speed was a glitch. International speeds is still bad. Getting 2mb instead of 10mb. Local is 5mb.
 

Bursty-dude

Expert Member
Joined
Apr 28, 2011
Messages
1,289
Line has been dead since just after 9am this morning.
Not dead as in slow, dead as in no connection........

Router ADSL light shows green, but there is no connection at all.
Rebooted countless times and no luck.

I think I must send Afrihost an invoice detailing my data usage from my cellphone for today. My better half has my Tab2 with the Mifi SIM in it, so I can't use that either.

Edited to add: now there is a connection again.
Support ticket opened about 10 minutes ago (I did not have time to do it earlier), and now we have some action again!

Thanks to whoever attended to the support ticket!
3176977685.png
 
Last edited:

vinodh

Expert Member
Joined
Jan 11, 2009
Messages
2,978
Pity. We could've been best friends :( :p

True. I would have allocated at least 10 out those 50megs to you so that you could sit outside my house and download Linux distros. That dream ended so quickly...
 

Bursty-dude

Expert Member
Joined
Apr 28, 2011
Messages
1,289
There was a huge ADSL outage in Waterkloof, all fixed now it seems.
Thanks to Khulile from Afrihost for the quick response!
 

AfriGuy

Afrihost
Company Rep
Joined
Jun 12, 2013
Messages
14,236
Hey guys

Just a heads up, the Afrihost online team will be taking a bit of a break. We're on holiday from the 21st - 29th December 2013.

Our support team will be happy to assist on 0116127200 or support@afrihost.com. Happy Holidays!
 

Ho3n3r

Honorary Master
Joined
Apr 5, 2012
Messages
17,058
This is definitely exchange related, the latency on the 2nd hop is too high :( Is your line with us?

The only 2 times I've had these symptoms, it was not exchange-related, as confirmed in the end by Telkom. It's still a possibility, of course, but not guaranteed. I can send you the mails if you want proof.

My line is with you, yes.

It's getting worse, by the way:

Ping:
ping www.racedepartment.com -t

Pinging www.racedepartment.com [31.204.128.181] with 32 bytes of data:
Reply from 31.204.128.181: bytes=32 time=564ms TTL=49
Reply from 31.204.128.181: bytes=32 time=578ms TTL=49
Reply from 31.204.128.181: bytes=32 time=669ms TTL=49
Reply from 31.204.128.181: bytes=32 time=650ms TTL=49
Reply from 31.204.128.181: bytes=32 time=549ms TTL=49
Reply from 31.204.128.181: bytes=32 time=510ms TTL=49
Reply from 31.204.128.181: bytes=32 time=579ms TTL=49
Reply from 31.204.128.181: bytes=32 time=574ms TTL=49
Reply from 31.204.128.181: bytes=32 time=607ms TTL=49
Reply from 31.204.128.181: bytes=32 time=514ms TTL=49
Reply from 31.204.128.181: bytes=32 time=452ms TTL=49
Reply from 31.204.128.181: bytes=32 time=492ms TTL=49
Reply from 31.204.128.181: bytes=32 time=521ms TTL=49
Reply from 31.204.128.181: bytes=32 time=575ms TTL=49
Reply from 31.204.128.181: bytes=32 time=549ms TTL=49
Reply from 31.204.128.181: bytes=32 time=616ms TTL=49
Reply from 31.204.128.181: bytes=32 time=668ms TTL=49
Reply from 31.204.128.181: bytes=32 time=712ms TTL=49
Reply from 31.204.128.181: bytes=32 time=657ms TTL=49
Reply from 31.204.128.181: bytes=32 time=486ms TTL=49
Reply from 31.204.128.181: bytes=32 time=472ms TTL=49
Reply from 31.204.128.181: bytes=32 time=510ms TTL=49
Reply from 31.204.128.181: bytes=32 time=590ms TTL=49
Reply from 31.204.128.181: bytes=32 time=703ms TTL=49
Reply from 31.204.128.181: bytes=32 time=751ms TTL=49
Reply from 31.204.128.181: bytes=32 time=603ms TTL=49
Reply from 31.204.128.181: bytes=32 time=603ms TTL=49
Reply from 31.204.128.181: bytes=32 time=659ms TTL=49
Reply from 31.204.128.181: bytes=32 time=681ms TTL=49
Reply from 31.204.128.181: bytes=32 time=689ms TTL=49
Reply from 31.204.128.181: bytes=32 time=739ms TTL=49
Reply from 31.204.128.181: bytes=32 time=768ms TTL=49

Ping statistics for 31.204.128.181:
Packets: Sent = 32, Received = 32, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 452ms, Maximum = 768ms, Average = 602ms


Traceroute:
tracert www.racedepartment.com

Tracing route to www.racedepartment.com [31.204.128.181]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Broadcom.Home [192.168.1.1]
2 350 ms 329 ms 303 ms 105-236-4-129-esr-lo.mtnbusiness.co.za [105.236.4.129]
3 316 ms 315 ms 264 ms ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178.53]
4 251 ms 217 ms 230 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 273 ms 259 ms 263 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 350 ms 329 ms 318 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 613 ms 552 ms 500 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
8 * * * Request timed out.
9 583 ms 654 ms 663 ms 109.200.218.154
10 591 ms 609 ms 629 ms 80ge.br3-cr0.smartdc.rtd.i3d.net [188.122.95.93]
11 732 ms 758 ms 697 ms hosted-by.i3d.net [31.204.128.181]

Trace complete.


I'm quite desperate for this to be sorted, to be honest.
 

AfriGuy

Afrihost
Company Rep
Joined
Jun 12, 2013
Messages
14,236
The only 2 times I've had these symptoms, it was not exchange-related, as confirmed in the end by Telkom. It's still a possibility, of course, but not guaranteed. I can send you the mails if you want proof.

My line is with you, yes.

It's getting worse, by the way:

Ping:
ping www.racedepartment.com -t

Pinging www.racedepartment.com [31.204.128.181] with 32 bytes of data:
Reply from 31.204.128.181: bytes=32 time=564ms TTL=49
Reply from 31.204.128.181: bytes=32 time=578ms TTL=49
Reply from 31.204.128.181: bytes=32 time=669ms TTL=49
Reply from 31.204.128.181: bytes=32 time=650ms TTL=49
Reply from 31.204.128.181: bytes=32 time=549ms TTL=49
Reply from 31.204.128.181: bytes=32 time=510ms TTL=49
Reply from 31.204.128.181: bytes=32 time=579ms TTL=49
Reply from 31.204.128.181: bytes=32 time=574ms TTL=49
Reply from 31.204.128.181: bytes=32 time=607ms TTL=49
Reply from 31.204.128.181: bytes=32 time=514ms TTL=49
Reply from 31.204.128.181: bytes=32 time=452ms TTL=49
Reply from 31.204.128.181: bytes=32 time=492ms TTL=49
Reply from 31.204.128.181: bytes=32 time=521ms TTL=49
Reply from 31.204.128.181: bytes=32 time=575ms TTL=49
Reply from 31.204.128.181: bytes=32 time=549ms TTL=49
Reply from 31.204.128.181: bytes=32 time=616ms TTL=49
Reply from 31.204.128.181: bytes=32 time=668ms TTL=49
Reply from 31.204.128.181: bytes=32 time=712ms TTL=49
Reply from 31.204.128.181: bytes=32 time=657ms TTL=49
Reply from 31.204.128.181: bytes=32 time=486ms TTL=49
Reply from 31.204.128.181: bytes=32 time=472ms TTL=49
Reply from 31.204.128.181: bytes=32 time=510ms TTL=49
Reply from 31.204.128.181: bytes=32 time=590ms TTL=49
Reply from 31.204.128.181: bytes=32 time=703ms TTL=49
Reply from 31.204.128.181: bytes=32 time=751ms TTL=49
Reply from 31.204.128.181: bytes=32 time=603ms TTL=49
Reply from 31.204.128.181: bytes=32 time=603ms TTL=49
Reply from 31.204.128.181: bytes=32 time=659ms TTL=49
Reply from 31.204.128.181: bytes=32 time=681ms TTL=49
Reply from 31.204.128.181: bytes=32 time=689ms TTL=49
Reply from 31.204.128.181: bytes=32 time=739ms TTL=49
Reply from 31.204.128.181: bytes=32 time=768ms TTL=49

Ping statistics for 31.204.128.181:
Packets: Sent = 32, Received = 32, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 452ms, Maximum = 768ms, Average = 602ms


Traceroute:
tracert www.racedepartment.com

Tracing route to www.racedepartment.com [31.204.128.181]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Broadcom.Home [192.168.1.1]
2 350 ms 329 ms 303 ms 105-236-4-129-esr-lo.mtnbusiness.co.za [105.236.4.129]
3 316 ms 315 ms 264 ms ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178.53]
4 251 ms 217 ms 230 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 273 ms 259 ms 263 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 350 ms 329 ms 318 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 613 ms 552 ms 500 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
8 * * * Request timed out.
9 583 ms 654 ms 663 ms 109.200.218.154
10 591 ms 609 ms 629 ms 80ge.br3-cr0.smartdc.rtd.i3d.net [188.122.95.93]
11 732 ms 758 ms 697 ms hosted-by.i3d.net [31.204.128.181]

Trace complete.


I'm quite desperate for this to be sorted, to be honest.

These results confirm an exchange related issue. Maybe not congestion but it's definitely on the exchanges level. We can only control the latencies levels from hop 3 onwards.
If the line is with us please mail our Support team so we can have a fault logged for you.
 

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
The only 2 times I've had these symptoms, it was not exchange-related, as confirmed in the end by Telkom. It's still a possibility, of course, but not guaranteed. I can send you the mails if you want proof.

My line is with you, yes.

It's getting worse, by the way:

Ping:
ping www.racedepartment.com -t

Pinging www.racedepartment.com [31.204.128.181] with 32 bytes of data:
Reply from 31.204.128.181: bytes=32 time=564ms TTL=49
Reply from 31.204.128.181: bytes=32 time=578ms TTL=49
Reply from 31.204.128.181: bytes=32 time=669ms TTL=49
Reply from 31.204.128.181: bytes=32 time=650ms TTL=49
Reply from 31.204.128.181: bytes=32 time=549ms TTL=49
Reply from 31.204.128.181: bytes=32 time=510ms TTL=49
Reply from 31.204.128.181: bytes=32 time=579ms TTL=49
Reply from 31.204.128.181: bytes=32 time=574ms TTL=49
Reply from 31.204.128.181: bytes=32 time=607ms TTL=49
Reply from 31.204.128.181: bytes=32 time=514ms TTL=49
Reply from 31.204.128.181: bytes=32 time=452ms TTL=49
Reply from 31.204.128.181: bytes=32 time=492ms TTL=49
Reply from 31.204.128.181: bytes=32 time=521ms TTL=49
Reply from 31.204.128.181: bytes=32 time=575ms TTL=49
Reply from 31.204.128.181: bytes=32 time=549ms TTL=49
Reply from 31.204.128.181: bytes=32 time=616ms TTL=49
Reply from 31.204.128.181: bytes=32 time=668ms TTL=49
Reply from 31.204.128.181: bytes=32 time=712ms TTL=49
Reply from 31.204.128.181: bytes=32 time=657ms TTL=49
Reply from 31.204.128.181: bytes=32 time=486ms TTL=49
Reply from 31.204.128.181: bytes=32 time=472ms TTL=49
Reply from 31.204.128.181: bytes=32 time=510ms TTL=49
Reply from 31.204.128.181: bytes=32 time=590ms TTL=49
Reply from 31.204.128.181: bytes=32 time=703ms TTL=49
Reply from 31.204.128.181: bytes=32 time=751ms TTL=49
Reply from 31.204.128.181: bytes=32 time=603ms TTL=49
Reply from 31.204.128.181: bytes=32 time=603ms TTL=49
Reply from 31.204.128.181: bytes=32 time=659ms TTL=49
Reply from 31.204.128.181: bytes=32 time=681ms TTL=49
Reply from 31.204.128.181: bytes=32 time=689ms TTL=49
Reply from 31.204.128.181: bytes=32 time=739ms TTL=49
Reply from 31.204.128.181: bytes=32 time=768ms TTL=49

Ping statistics for 31.204.128.181:
Packets: Sent = 32, Received = 32, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 452ms, Maximum = 768ms, Average = 602ms


Traceroute:
tracert www.racedepartment.com

Tracing route to www.racedepartment.com [31.204.128.181]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Broadcom.Home [192.168.1.1]
2 350 ms 329 ms 303 ms 105-236-4-129-esr-lo.mtnbusiness.co.za [105.236.4.129]
3 316 ms 315 ms 264 ms ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178.53]
4 251 ms 217 ms 230 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 273 ms 259 ms 263 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 350 ms 329 ms 318 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 613 ms 552 ms 500 ms ls-pr-1.uk--ls-cr-1.uk-a.mtn.net [209.212.111.83]
8 * * * Request timed out.
9 583 ms 654 ms 663 ms 109.200.218.154
10 591 ms 609 ms 629 ms 80ge.br3-cr0.smartdc.rtd.i3d.net [188.122.95.93]
11 732 ms 758 ms 697 ms hosted-by.i3d.net [31.204.128.181]

Trace complete.


I'm quite desperate for this to be sorted, to be honest.

BOOM! Im back People :D Ive been away for a while but I can now help people once again :p

Firstly, Ho3n3r, That is (unfortunately) most likely exchange congestion (even though Telkom says it is not) :-( However, there are some alternatives to what it could possibly be. Could you answer these questions for me:

  1. What router do you have?
  2. Do you have a filter (POTS) on EVERY single thing connected to your phone line, apart from the router? This includes alarms
  3. Have you done a port reset
  4. Is it possible for you to try connect with a different router?
  5. Is your router hot to the touch when using it? If so - leave it off for a while until it cools down and switch it back on to see if that made a difference.
 

Ho3n3r

Honorary Master
Joined
Apr 5, 2012
Messages
17,058
BOOM! Im back People :D Ive been away for a while but I can now help people once again :p

Firstly, Ho3n3r, That is (unfortunately) most likely exchange congestion (even though Telkom says it is not) :-( However, there are some alternatives to what it could possibly be. Could you answer these questions for me:

  1. What router do you have?
  2. Do you have a filter (POTS) on EVERY single thing connected to your phone line, apart from the router? This includes alarms
  3. Have you done a port reset
  4. Is it possible for you to try connect with a different router?
  5. Is your router hot to the touch when using it? If so - leave it off for a while until it cools down and switch it back on to see if that made a difference.

Hi mate.

You remember our previous discussions, a few weeks ago? Had same symptoms, wasn't congestion - twice. But it's equally possible to be congestion. But AssUMe makes an ass out of you & me.

  1. What router do you have? -> DLink 2640U, as I've had for the last 13 months.
  2. Do you have a filter (POTS) on EVERY single thing connected to your phone line, apart from the router? This includes alarms - I have a POTS filter, I noticed the problem while it was still on. I've taken it off to see if it might be the cause - no difference.
  3. Have you done a port reset -> Yes, Telkom has done it for me. No improvement.
  4. Is it possible for you to try connect with a different router? -> No, I wish I had a spare.
  5. Is your router hot to the touch when using it? If so - leave it off for a while until it cools down and switch it back on to see if that made a difference. -> It was off the whole day yesterday, until I got home, when I put it on, and noticed the problem. Also, I am using a glass with water on top of it to cool it. It is at a normal temperature.

It may also be the router, you never know. I'm not ruling out anything, but it'll be a bit presumptuous to land on congestion and just settle on it, based on past experiences.

Thanks for trying to help. Are you some kind of network techie?
 

Zertop

Expert Member
Joined
Mar 9, 2013
Messages
3,105
Hi mate.

You remember our previous discussions, a few weeks ago? Had same symptoms, wasn't congestion - twice. But it's equally possible to be congestion. But AssUMe makes an ass out of you & me.

  1. What router do you have? -> DLink 2640U, as I've had for the last 13 months.
  2. Do you have a filter (POTS) on EVERY single thing connected to your phone line, apart from the router? This includes alarms - I have a POTS filter, I noticed the problem while it was still on. I've taken it off to see if it might be the cause - no difference.
  3. Have you done a port reset -> Yes, Telkom has done it for me. No improvement.
  4. Is it possible for you to try connect with a different router? -> No, I wish I had a spare.
  5. Is your router hot to the touch when using it? If so - leave it off for a while until it cools down and switch it back on to see if that made a difference. -> It was off the whole day yesterday, until I got home, when I put it on, and noticed the problem. Also, I am using a glass with water on top of it to cool it. It is at a normal temperature.

It may also be the router, you never know. I'm not ruling out anything, but it'll be a bit presumptuous to land on congestion and just settle on it, based on past experiences.

Thanks for trying to help. Are you some kind of network techie?

I'm no network pro, to be honest it's one of my favourite things to do :D Anyway - as you said, its never good to just make an assumption, always good to try out different things :p I don't think it is a heat issue, due to point 5. The only other thing I could recommend is trying a different router. Is there any way for you to go to a neighbours house and do a tracert from there? I know it will probably come across quite creepily :D, but its the best way to figure out if it is an area wide issue or a local line issue :)

Good luck
 

Ho3n3r

Honorary Master
Joined
Apr 5, 2012
Messages
17,058
I'm no network pro, to be honest it's one of my favourite things to do :D Anyway - as you said, its never good to just make an assumption, always good to try out different things :p I don't think it is a heat issue, due to point 5. The only other thing I could recommend is trying a different router. Is there any way for you to go to a neighbours house and do a tracert from there? I know it will probably come across quite creepily :D, but its the best way to figure out if it is an area wide issue or a local line issue :)

Good luck

Hehe no chance, most of them are at least 80, and I don't really know any of them :p

Will struggle this out with Telkom and Afrihost...
 
Status
Not open for further replies.
Top