Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
I did. My inbox is a bit messy from this weekend though :( I'll get to is ASAP dude.

Okay no problem. I still have one or two days before I want to do that, so just as long as I don't land in the deep end and then get stuck with a R1000 bill next month :p
 
Hop 12 timed out again.
Speeds are OK, for now. And still no feedback from anyone regarding this issue.

Tracing route to www.google.com [74.125.136.103]
over a maximum of 30 hops:

1 5 ms <1 ms <1 ms 192.168.0.1
2 19 ms 21 ms 49 ms 105-236-11-193-esr-lo.mtnbusiness.co.za [105.236
.11.193]
3 28 ms 17 ms 15 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178
.77]
4 17 ms 14 ms 20 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 25 ms 23 ms 13 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 19 ms 18 ms 14 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 217 ms 203 ms 192 ms core2.ams.net.google.com [195.69.145.100]
8 189 ms 190 ms 193 ms 209.85.254.95
9 335 ms 348 ms 335 ms 72.14.238.69
10 334 ms 333 ms 335 ms 209.85.255.87
11 200 ms 231 ms 199 ms 216.239.49.38
12 * * * Request timed out.
13 194 ms 196 ms 190 ms ea-in-f103.1e100.net [74.125.136.103]

Trace complete.
 
Hop 12 timed out again.
Speeds are OK, for now. And still no feedback from anyone regarding this issue.

Tracing route to www.google.com [74.125.136.103]
over a maximum of 30 hops:

1 5 ms <1 ms <1 ms 192.168.0.1
2 19 ms 21 ms 49 ms 105-236-11-193-esr-lo.mtnbusiness.co.za [105.236
.11.193]
3 28 ms 17 ms 15 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178
.77]
4 17 ms 14 ms 20 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 25 ms 23 ms 13 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 19 ms 18 ms 14 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 217 ms 203 ms 192 ms core2.ams.net.google.com [195.69.145.100]
8 189 ms 190 ms 193 ms 209.85.254.95
9 335 ms 348 ms 335 ms 72.14.238.69
10 334 ms 333 ms 335 ms 209.85.255.87
11 200 ms 231 ms 199 ms 216.239.49.38
12 * * * Request timed out.
13 194 ms 196 ms 190 ms ea-in-f103.1e100.net [74.125.136.103]

Trace complete.

I'll do my best to get feedback to you ASAP.
 
Hop 12 timed out again.
Speeds are OK, for now. And still no feedback from anyone regarding this issue.

12 * * * Request timed out.
Trace complete.

If a hop in question does not allow external pings then you will see it as "Request timed out". Its's not uncommon by any means.
 
What's up at Afrihost this morning? Can connect but no internet browsing or email downloads. Have reset browser but no difference.
 
What's up at Afrihost this morning? Can connect but no internet browsing or email downloads. Have reset browser but no difference.

Mine works fine hey. Grabbed today's viewing material at full speed.
 
Hmm. There's something seriously busted now (Gauteng).

Code:
tracert afrihost.co.za

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

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     7 ms     7 ms     6 ms  105-236-11-193-esr-lo.mtnbusiness.co.za [105.236
.11.193]
[B]  3     *        *       10 ms  ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178
.65]
[/B]  4    11 ms    11 ms    10 ms  rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
  5    11 ms    10 ms    11 ms  jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
  6    10 ms    10 ms    10 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
  7    12 ms    11 ms    12 ms  tengigabitethernet5-1.hr15.jnb6.za.mtnbusiness.n
et [196.31.63.198]
  8    12 ms    12 ms    11 ms  cms-gm.afrihost.com [197.242.144.102]

Trace complete.

That's been the case on a few traceroutes now.
Other symptoms include close-to-dead browsing. Usenet seem to be relatively unaffected so I'm unsure of what the problem is.
 
Hmm. There's something seriously busted now (Gauteng).

Code:
tracert afrihost.co.za

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

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     7 ms     7 ms     6 ms  105-236-11-193-esr-lo.mtnbusiness.co.za [105.236
.11.193]
[B]  3     *        *       10 ms  ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178
.65]
[/B]  4    11 ms    11 ms    10 ms  rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
  5    11 ms    10 ms    11 ms  jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
  6    10 ms    10 ms    10 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
  7    12 ms    11 ms    12 ms  tengigabitethernet5-1.hr15.jnb6.za.mtnbusiness.n
et [196.31.63.198]
  8    12 ms    12 ms    11 ms  cms-gm.afrihost.com [197.242.144.102]

Trace complete.

That's been the case on a few traceroutes now.
Other symptoms include close-to-dead browsing. Usenet seem to be relatively unaffected so I'm unsure of what the problem is.

I think our engineers are trying to address the issues on the DSL network, so there could be some ripple effects to other aspects of the network. Should stabilise as soon as we figure out what's happened in KZN :(
 
Randburg - Dead

Same issue as others - dropping packets on IPC
 
I think our engineers are trying to address the issues on the DSL network, so there could be some ripple effects to other aspects of the network. Should stabilise as soon as we figure out what's happened in KZN :(

Okay, thanks for the update :)
 
Wow! It seems to be back to almost where it was 3 weeks ago:
3034438759.png


Tracing route to www.google.com [74.125.136.99]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 10 ms 9 ms 9 ms 105-236-11-193-esr-lo.mtnbusiness.co.za [105.236
.11.193]
3 12 ms 12 ms 12 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181.178
.65]
4 13 ms 15 ms 12 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 13 ms 12 ms 12 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 12 ms 12 ms 11 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 189 ms 190 ms 189 ms core2.ams.net.google.com [195.69.145.100]
8 188 ms 188 ms 188 ms 209.85.254.95
9 334 ms 335 ms 335 ms 72.14.238.69
10 338 ms 341 ms 337 ms 209.85.255.73
11 192 ms 192 ms 201 ms 209.85.254.189
12 * * * Request timed out.
13 189 ms 188 ms 189 ms ea-in-f99.1e100.net [74.125.136.99]

Trace complete.




Make no mistake, even with hassles like we've been having, I still love Afrihost.
 
Hey guys

Just wanna touch base on what was discussed earlier with AfriMan - we're seeing things mostly returned to normal. Should be all good now :)
 
Still running fine my side as well, even though the better half is downloading something via Wifi:
3035468273.png

Tracing route to www.google.com [74.125.136.104]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 9 ms 9 ms 105-236-11-193-esr-lo.mtnbusiness.co.za [105.236
.11.193]
3 12 ms 11 ms 12 ms ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178
.89]
4 12 ms 12 ms 13 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 13 ms 13 ms 18 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 12 ms 11 ms 12 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 193 ms 192 ms 193 ms core2.ams.net.google.com [195.69.145.100]
8 188 ms 189 ms 188 ms 209.85.254.90
9 337 ms 346 ms 337 ms 72.14.238.153
10 342 ms 341 ms 368 ms 209.85.255.73
11 195 ms 195 ms 192 ms 209.85.255.49
12 * * * Request timed out.
13 193 ms 194 ms 191 ms ea-in-f104.1e100.net [74.125.136.104]

Trace complete.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X