Afrihost Uncapped ADSL Feedback (Pt2)

Status
Not open for further replies.
AfriMan said:
That would not be due to shaping. Pings and latency from our tests are running as normal. can you PM me or post a traceroute so I can take a look?
Click to expand...

Here's one for ya:

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

  1     1 ms     1 ms    <1 ms  DD-WRT [192.168.1.1]
  2    10 ms     9 ms    15 ms  105-236-6-65-esr-lo.mtnbusiness.co.za [105.236.6.65]
  3   168 ms   134 ms   142 ms  ipc-recieve-jh-3a.za.mtnbusiness.net [41.181.178.29]
  4   160 ms   191 ms   160 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
  5   120 ms   154 ms   115 ms  jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
  6   344 ms   339 ms   338 ms  am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.141]
  7   351 ms   356 ms   353 ms  core2.ams.net.google.com [195.69.145.100]
  8   350 ms   403 ms   363 ms  209.85.254.95
  9   511 ms   470 ms   462 ms  72.14.238.69
 10   507 ms   552 ms   587 ms  209.85.240.29
 11   519 ms   639 ms   746 ms  72.14.235.89
 12   498 ms   492 ms   496 ms  209.85.243.114
 13   437 ms   444 ms   441 ms  64.233.174.87
 14     *        *        *     Request timed out.
 15   445 ms   439 ms   440 ms  vc-in-f94.1e100.net [74.125.131.94]

:(

Hey, at least it's not my exchange...
 
HapticSimian said:
Here's one for ya:

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

  1     1 ms     1 ms    <1 ms  DD-WRT [192.168.1.1]
  2    10 ms     9 ms    15 ms  105-236-6-65-esr-lo.mtnbusiness.co.za [105.236.6.65]
  3   168 ms   134 ms   142 ms  ipc-recieve-jh-3a.za.mtnbusiness.net [41.181.178.29]
  4   160 ms   191 ms   160 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
  5   120 ms   154 ms   115 ms  jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
  6   344 ms   339 ms   338 ms  am-tpr-1.nl--am-cr-1.nl-a.mtn.net [209.212.111.141]
  7   351 ms   356 ms   353 ms  core2.ams.net.google.com [195.69.145.100]
  8   350 ms   403 ms   363 ms  209.85.254.95
  9   511 ms   470 ms   462 ms  72.14.238.69
 10   507 ms   552 ms   587 ms  209.85.240.29
 11   519 ms   639 ms   746 ms  72.14.235.89
 12   498 ms   492 ms   496 ms  209.85.243.114
 13   437 ms   444 ms   441 ms  64.233.174.87
 14     *        *        *     Request timed out.
 15   445 ms   439 ms   440 ms  vc-in-f94.1e100.net [74.125.131.94]

:(

Hey, at least it's not my exchange...
Click to expand...

Definitely not looking great there. I'd suggest a quick router reboot or a hard reboot (20-30 minutes). We've seen a few people need to refresh their connection to get back to normal levels :(
 
Mine..

1 <1 ms <1 ms <1 ms 192.168.0.254
2 8 ms 7 ms 7 ms 105-236-3-1-esr-lo.mtnbusiness.co.za [105.23
1]
3 130 ms 132 ms 131 ms ipc-recieve-rb-2a.za.mtnbusiness.net [41.181
.65]
4 122 ms 125 ms 118 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.
6]
5 109 ms 107 ms 102 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.3
]
6 160 ms 126 ms 128 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181
.115]
7 312 ms 311 ms 310 ms core2.ams.net.google.com [195.69.145.100]
8 309 ms 314 ms 390 ms 209.85.254.95
9 460 ms 479 ms 490 ms 72.14.238.69
10 486 ms 503 ms 497 ms 209.85.254.231
11 457 ms 460 ms 458 ms 209.85.254.199
12 345 ms 343 ms 343 ms 72.14.233.215
13 321 ms 323 ms 317 ms 72.14.235.215
14 296 ms 289 ms 292 ms ham02s11-in-f17.1e100.net [173.194.113.145]
 
Afrihost cant handle the load?
probably the influx of mweb, read mderp, users ;/
Code: 
Tracing route to www.mybroadband.co.za [41.203.21.137]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.0.0.66
  2    20 ms    18 ms    18 ms  105-236-2-129-esr-lo.mtnbusiness.co.za [105.236.2.129]
  3   180 ms   184 ms   177 ms  ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178.89]
  4   156 ms   134 ms   128 ms  rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
  5   154 ms   163 ms   159 ms  jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
  6   144 ms   147 ms   145 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
  7   169 ms   175 ms   171 ms  196.44.31.99
  8   131 ms   135 ms   151 ms  ge10-1-1sub0.te3.jnb6.za.mtnbusiness.net [196.31.220.8]
  9   131 ms   130 ms   127 ms  tengigabitethernet9-1.gw21.jnb6.za.mtnbusiness.net [196.31.220.27]
 10   116 ms   117 ms   119 ms  tengigabitethernet5-2.hr9.jnb6.za.mtnbusiness.net [196.31.63.150]
 11   141 ms   140 ms   140 ms  core-router1.jnb2.host-h.net [196.30.213.108]
 12   141 ms   140 ms   142 ms  core-access-switch1-vlan1001.jnb.host-h.net [41.72.136.53]

 13   173 ms   177 ms   174 ms  mybroadband.co.za [41.203.21.137]

Trace complete.
Click to expand...
 
AfriMan said:
Definitely not looking great there. I'd suggest a quick router reboot or a hard reboot (20-30 minutes). We've seen a few people need to refresh their connection to get back to normal levels :(
Click to expand...

Stay off the 'net for half an hour...? Are you mental?! :p

I'll give it a bash once I've finished watching this episode of Warehouse 13 in 1998 Youtube 240p resolution.
 
Running some tests on my side, also just seeing some crazy latency. Escalating this to our team. I think we've unshaped too many people too quickly and now the network is trying to compensate.

Should have this pinned down in a few minutes :(
 
18.8% Download/ 6.25% P2P

10pm and this are still the shaping :confused: think they need to upgrade there capacity and i am thinking of moving all 22 accounts over to afrihost then the shaping be implemented all the time... :confused::confused:
 
Also getting funny latency on the third hop

And Google not going local either :(

This is from a 6 mbps business uncapped account, client zone mentions no shaping

Could their IPC be congesting ?

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

1 <1 ms <1 ms <1 ms 192.168.1.254
2 6 ms 10 ms 6 ms 105-236-4-129-esr-lo.mtnbusiness.co.za [105.236.4.129]
3 35 ms 36 ms 45 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178.77]
4 40 ms 55 ms 49 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.146]
5 102 ms 84 ms 83 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95]
6 91 ms 89 ms 92 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
7 283 ms 284 ms 304 ms core2.ams.net.google.com [195.69.145.100]
8 234 ms 225 ms 237 ms 209.85.254.90
9 440 ms 438 ms 455 ms 72.14.238.153
10 422 ms 391 ms 424 ms 209.85.254.233
11 429 ms 461 ms 422 ms 209.85.254.199
12 289 ms 268 ms 286 ms 72.14.233.166
13 280 ms 279 ms 277 ms 72.14.235.215
14 283 ms 294 ms 283 ms ham02s11-in-f31.1e100.net [173.194.113.159]

Trace complete.
 
I definitely think Afrihost has too many customers, and not enough bandwidth to go around for everyone. I think its just a matter of hanging in there.

I wish Mweb didn't go mental right now hehe
 
Latencies are slowly stabilising. we should reach normal levels soon. I'm still seeing intermittent spikes on my side, but at least we're in the range of acceptable for now. We'll monitor through the night and the morning to keep everything as smooth as possible from our side.
 
ainsin said:
I definitely think Afrihost has too many customers, and not enough bandwidth to go around for everyone. I think its just a matter of hanging in there.

I wish Mweb didn't go mental right now hehe
Click to expand...

I agree. 10:30pm - 1mbps uncapped - "Shaping Policy: 25% Download/ 12.5% P2P"
 
Tracing route to www.google.co.za [173.194.113.191]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.1.1
2 20 ms 21 ms 22 ms 105-236-3-129-esr-lo.mtnbusiness.co.za [105.236.
3.129]
3 22 ms 21 ms 22 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178
.77]
4 47 ms 30 ms 39 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 26 ms 26 ms 24 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
6 28 ms 26 ms 31 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 * 230 ms 214 ms core2.ams.net.google.com [195.69.145.100]
8 333 ms 225 ms 257 ms 209.85.254.90
9 381 ms 381 ms 379 ms 209.85.253.249
10 377 ms 383 ms 381 ms 209.85.254.213
11 365 ms 364 ms 365 ms 209.85.254.207
12 275 ms 223 ms 222 ms 72.14.233.30
13 235 ms 226 ms 222 ms 72.14.235.213
14 221 ms 221 ms 221 ms ham02s12-in-f31.1e100.net [173.194.113.191]

Trace complete.
 
ainsin said:
I definitely think Afrihost has too many customers, and not enough bandwidth to go around for everyone. I think its just a matter of hanging in there.

I wish Mweb didn't go mental right now hehe
Click to expand...

I don't believe that is the case. Pretty much every other ISP has reported high usage over the last two days. We know that there is an upward trend in usage. We believe it's linked to iOS updates, however torrents still account for major portion of the usage on the network.

Unless Telkom just added 30% more DSL users onto the network, it's very likely that the usage trend will subside (as it has done with other iOS updates, in my experience) and things will return to normal shortly. We'll do everything we can to manage the trend from our side until it dies down.
 
killerbyte said:
Tracing route to www.google.co.za [173.194.113.191]
over a maximum of 30 hops:

1 2 ms 1 ms 1 ms 192.168.1.1
2 20 ms 21 ms 22 ms 105-236-3-129-esr-lo.mtnbusiness.co.za [105.236.
3.129]
3 22 ms 21 ms 22 ms ipc-recieve-rb-3a.za.mtnbusiness.net [41.181.178
.77]
4 47 ms 30 ms 39 ms rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
5 26 ms 26 ms 24 ms jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
6 28 ms 26 ms 31 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 * 230 ms 214 ms core2.ams.net.google.com [195.69.145.100]
8 333 ms 225 ms 257 ms 209.85.254.90
9 381 ms 381 ms 379 ms 209.85.253.249
10 377 ms 383 ms 381 ms 209.85.254.213
11 365 ms 364 ms 365 ms 209.85.254.207
12 275 ms 223 ms 222 ms 72.14.233.30
13 235 ms 226 ms 222 ms 72.14.235.213
14 221 ms 221 ms 221 ms ham02s12-in-f31.1e100.net [173.194.113.191]

Trace complete.
Click to expand...

Let's give the changes we've made some time to settle. I'm seeing a big reduction in latency from my tests. Still not normal or optimal, but should be within acceptable range for most services. We should be at completely normal levels shortly, as we move out of peak usage time as well.
 
Starting to look a bit better...

Code: 
Tracing route to any-rc.a01.yahoodns.net [98.139.102.145]
over a maximum of 30 hops:

  1     1 ms     1 ms     1 ms  DD-WRT [192.168.1.1]
  2     9 ms    10 ms     9 ms  105-236-6-65-esr-lo.mtnbusiness.co.za [105.236.6.65]
  3    10 ms    10 ms    10 ms  ipc-recieve-jh-4a.za.mtnbusiness.net [41.181.178.41]
  4    10 ms    10 ms    10 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165.115]
  5    13 ms    12 ms    23 ms  jh-dca-2.za--qux-b.za.mtnbusiness.net [41.181.165.114]
  6   208 ms   208 ms   207 ms  ls-pr-1.uk--ls-cr-2.uk-a.mtn.net [209.212.111.201]
  7   204 ms   213 ms   283 ms  ge-1-1-0.pat1.the.yahoo.com [195.66.224.129]
  8   284 ms   285 ms   279 ms  UNKNOWN-216-115-96-X.yahoo.com [216.115.96.30]
  9   289 ms   309 ms   284 ms  ae-5.pat1.bfz.yahoo.com [216.115.96.65]
 10   285 ms   292 ms   285 ms  ae-3.msr1.bf1.yahoo.com [216.115.100.29]
 11   305 ms   303 ms   305 ms  xe-9-0-0.clr2-a-gdc.bf1.yahoo.com [98.139.232.105]
 12   289 ms   293 ms   290 ms  et17-1.fab5-1-sat.bf1.yahoo.com [98.139.128.85]
 13   286 ms   290 ms   286 ms  po-10.bas1-1-prd.bf1.yahoo.com [98.139.129.29]
 14   286 ms   288 ms   286 ms  w2.rc.vip.bf1.yahoo.com [98.139.102.145]

ainsin said:
I definitely think Afrihost has too many customers, and not enough bandwidth to go around for everyone. I think its just a matter of hanging in there.

I wish Mweb didn't go mental right now hehe
Click to expand...

See, now this I don't get. You don't actually need to think; the links posted in this very thread show that the last 48 hours or so has seen more data traverse the Johannesburg Internet Exchange than any similar period in the last 12 months. Something out of the ordinary's going on, and it has little to nothing to do with any one ISP not having enough bandwidth to go around.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X