Afrihost Capped ADSL Feedback (MTN) - New beginning

Status
Not open for further replies.
And now it's back to perfect. What changed?

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

1 1 ms 1 ms <1 ms 192.168.4.253
2 * * * Request timed out.
3 27 ms 26 ms 26 ms 41.181.51.181
4 33 ms 33 ms 33 ms 41.181.51.182
5 34 ms 32 ms 32 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
6 27 ms 26 ms 26 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 52 ms 52 ms 53 ms pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66]
8 52 ms 52 ms 51 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
9 52 ms 52 ms 52 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.
 
RickNRoller said:
And now it's back to perfect. What changed?

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

1 1 ms 1 ms <1 ms 192.168.4.253
2 * * * Request timed out.
3 27 ms 26 ms 26 ms 41.181.51.181
4 33 ms 33 ms 33 ms 41.181.51.182
5 34 ms 32 ms 32 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
6 27 ms 26 ms 26 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 52 ms 52 ms 53 ms pe-cr-2.za--el-mse-1.za.mtnns.net [196.44.31.66]
8 52 ms 52 ms 51 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
9 52 ms 52 ms 52 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.
Click to expand...

As long as it stays like that, that is good.

I'm not sure exactly what happened, I'm trying to get additional information.
 
Tracing route to afrihost.com [41.181.185.18]
over a maximum of 30 hops:

1 <1 ms 1 ms 1 ms www.routerlogin.com [192.168.0.200]
2 * * * Request timed out.
3 8 ms 7 ms 8 ms 41.181.53.149
4 8 ms 7 ms 7 ms ipc-recieve-tb-1a.mtnbusiness.net [41.181.53.150]
5 8 ms 7 ms 8 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
6 9 ms 8 ms 8 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 27 ms 28 ms 28 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
8 27 ms 27 ms 28 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
9 28 ms 27 ms 27 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.

Mine is not too bad at all, also in Cape Town
 
Spoke too soon. Mine just died again.

Traceroute has started…

traceroute to afrihost.com (41.181.185.18), 64 hops max, 72 byte packets
1 tomatousb.workgroup (192.168.0.1) 0.527 ms 0.312 ms 0.249 ms
2 * * *
3 41.181.53.213 (41.181.53.213) 112.112 ms 144.933 ms 80.699 ms
4 ipc-send-tb-3a.mtnbusiness.net (41.181.53.214) 199.301 ms * *
5 * tb-dca-2.za--qux-c.za.mtnbusiness.net (41.181.198.188) 25.814 ms 147.516 ms
6 unc-cpt-1.mtnns.net (196.44.18.8) 65.653 ms 131.269 ms *
7 * jh-cr-1.za--tb-cr-2.za.mtnns.net (196.44.31.66) 96.757 ms *
8 jh-dca-1.za--jh-cr-1.za-a.mtnns.net (196.44.0.217) 85.571 ms 162.560 ms 131.044 ms
9 18.185.181.41.in-addr.aserv.co.za (41.181.185.18) 140.882 ms 250.850 ms 73.816 ms



AfriGuy said:
That's good to hear :)
What's your latency looking like at the moment? I'm trying to get an issue trended and investigated that seems to be affecting Capped account.
Click to expand...
 
Spoke too soon. Mine just died again.

Traceroute has started…

traceroute to afrihost.com (41.181.185.18), 64 hops max, 72 byte packets
1 tomatousb.workgroup (192.168.0.1) 0.527 ms 0.312 ms 0.249 ms
2 * * *
3 41.181.53.213 (41.181.53.213) 112.112 ms 144.933 ms 80.699 ms
4 ipc-send-tb-3a.mtnbusiness.net (41.181.53.214) 199.301 ms * *
5 * tb-dca-2.za--qux-c.za.mtnbusiness.net (41.181.198.188) 25.814 ms 147.516 ms
6 unc-cpt-1.mtnns.net (196.44.18.8) 65.653 ms 131.269 ms *
7 * jh-cr-1.za--tb-cr-2.za.mtnns.net (196.44.31.66) 96.757 ms *
8 jh-dca-1.za--jh-cr-1.za-a.mtnns.net (196.44.0.217) 85.571 ms 162.560 ms 131.044 ms
9 18.185.181.41.in-addr.aserv.co.za (41.181.185.18) 140.882 ms 250.850 ms 73.816 ms



AfriGuy said:
That's good to hear :)
What's your latency looking like at the moment? I'm trying to get an issue trended and investigated that seems to be affecting Capped account.
Click to expand...
 
Yeah same here. Was good while it lasted.

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

1 1 ms 1 ms 1 ms HOME [192.168.4.253]
2 * * * Request timed out.
3 * 78 ms 269 ms 41.181.51.181
4 * 323 ms 181 ms 41.181.51.182
5 147 ms * * tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.198.188]
6 106 ms 51 ms 159 ms unc-cpt-1.mtnns.net [196.44.18.8]
7 79 ms 164 ms 137 ms jh-cr-1.za--tb-cr-2.za.mtnns.net [196.44.31.66]
8 91 ms 306 ms 257 ms jh-dca-1.za--jh-cr-1.za-a.mtnns.net [196.44.0.217]
9 115 ms 154 ms 224 ms 18.185.181.41.in-addr.aserv.co.za [41.181.185.18]

Trace complete.
 
Just a quick update guys, we're starting to see traffic return to normal in the South, things should be back to the previous levels in the next few minutes.
 
Out of interest I decided to try my Afrihost 4GB capped account on the 4mb line I have. Browsing seems fine. Speed test shows excellent results. However P2P is dead. Not even 1kb/s. Have you guys added some heavy (read: blocked p2p) shaping?
 
Tander said:
Out of interest I decided to try my Afrihost 4GB capped account on the 4mb line I have. Browsing seems fine. Speed test shows excellent results. However P2P is dead. Not even 1kb/s. Have you guys added some heavy (read: blocked p2p) shaping?
Click to expand...

We definitely shouldn't be, but we did see network traffic in the East and South drop dramatically about a hour ago, so it could be related to that. Our Team is working on finding out exactly what happened.
 
AfriGenie said:
We definitely shouldn't be, but we did see network traffic in the East and South drop dramatically about a hour ago, so it could be related to that. Our Team is working on finding out exactly what happened.
Click to expand...

As I say, everything else is super fast. P2P is dead. My profile is also incorrect. I am now in the North.
 
AfriGenie said:
We definitely shouldn't be, but we did see network traffic in the East and South drop dramatically about a hour ago, so it could be related to that. Our Team is working on finding out exactly what happened.
Click to expand...

Again, sigh.

Sorry couldn't resist - frustrations run high when on deadlines and just my luck having to work from home when this happens. :p
 
A Non Blonde said:
Again, sigh.

Sorry couldn't resist - frustrations run high when on deadlines and just my luck having to work from home when this happens. :p
Click to expand...

I think we all have a bit of frustration creeping in! And a hint of excitement at the new network!
 
biometrics said:
A bit?!

And no nobody cares about a new network. Fix the thing you have already.
Click to expand...

We can only tweak and massage the current network, we're opting for a new implementation as it offers us significant benefits in being able to monitor, upgrade and control the new network to a degree that we were not able to in the past.
 
AfriGenie said:
We can only tweak and massage the current network, we're opting for a new implementation as it offers us significant benefits in being able to monitor, upgrade and control the new network to a degree that we were not able to in the past.
Click to expand...

Yet it was fine a few weeks ago.

Sorry I don't believe you. And these "new" networks aren't going to be any better. Afrihost is an incompetent company. No reason to believe it will change.

Tell you what, refund me for July and I'll leave these threads immediately.

I ****ING HATE AFRIHOST !!!!!!!!!!!!!
 
Is there any reason why after sorting out your Google cache issue I now get directed to Google.co.uk rather than Google.co.za?
It doesn't bug me, and it is a lot faster, but it seams strange if it is meant to be a local cache.
 
biometrics said:
Yet it was fine a few weeks ago.

Sorry I don't believe you. And these "new" networks aren't going to be any better. Afrihost is an incompetent company. No reason to believe it will change.

Tell you what, refund me for July and I'll leave these threads immediately.

I ****ING HATE AFRIHOST !!!!!!!!!!!!!
Click to expand...

Just drop me a PM with your account details and I will get this done for you.
 
caroper said:
Is there any reason why after sorting out your Google cache issue I now get directed to Google.co.uk rather than Google.co.za?
It doesn't bug me, and it is a lot faster, but it seams strange if it is meant to be a local cache.
Click to expand...

:confused:

Okay now that is strange... Are you using our DNS at the moment?
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X