Afrihost CAPPED ADSL Feedback (MTN)

Status
Not open for further replies.
i am thinking of ditching my uncapped account to get a 150mb capped account. uncapped sucks balls. not been able to stream at more than 1mb/s for a week now

Sorry to hear that. Shaping on Uncapped should not affect your streaming. If you want, I can have a look at your account and find out if there are any problems. Feel free to private message me.
 
Thanks AfriGuy, much appreciated.


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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 9 ms 12 ms 10 ms 105-236-11-193-esr-lo.mtnbusiness.co.za [105.236
.11.193]
3 12 ms 12 ms 12 ms ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178
.89]
4 21 ms 12 ms 12 ms rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
5 13 ms 19 ms 14 ms jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
6 14 ms 12 ms 12 ms qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
7 13 ms 14 ms 17 ms rrba-ip-se-2-wan.telkom-ipnet.co.za [196.25.58.1
7]
8 14 ms 15 ms 13 ms 196.43.25.137
9 15 ms 18 ms 16 ms 196.43.51.78
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * telkom-sa-tienet-gw.telkom-ipnet.co.za [196.25.54.62] reports: Destination net unreachable.

Trace complete.

I know you've been chatting to Afriguy but feel free to send me a private message with your username. I can have a look at your account.
 
Cool, @ bursty-dude
Your SNR is fine, (11.8) so it means your line can potentially sync at about 10Mb.


From my side now though...
http://www.speedtest.net/result/3018012360.png
:(
Someone broke something :(

Code:
Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     7 ms     7 ms     7 ms  105-236-*-*-esr-lo.mtnbusiness.co.za [105.236
.*.*]
  3    10 ms     9 ms     9 ms  ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178
.53]
  4    11 ms    11 ms    10 ms  rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
  5    10 ms    10 ms    10 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    11 ms    11 ms    11 ms  rrba-ip-se-2-wan.telkom-ipnet.co.za [196.25.58.1
7]
  8    12 ms    11 ms    11 ms  196.43.25.137
  9    12 ms    12 ms    11 ms  196.43.39.166
 10     *       11 ms    12 ms  rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
 11    14 ms    14 ms    13 ms  nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.34]
 12    14 ms    14 ms    13 ms  telkom.co.za [196.43.22.222]

Trace complete.

Pinging bbc.co.uk [212.58.251.195] with 32 bytes of data:
Reply from 212.58.251.195: bytes=32 time=177ms TTL=112
Reply from 212.58.251.195: bytes=32 time=177ms TTL=112
Reply from 212.58.251.195: bytes=32 time=177ms TTL=112
Reply from 212.58.251.195: bytes=32 time=177ms TTL=112

Ping statistics for 212.58.251.195:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 177ms, Maximum = 177ms, Average = 177ms

Compared to your speedtest, your traceroute looks fine :( I'd be happy to look at your account and find out what the problem is.
 
Hi there Afriguy/Afrigirl

Seems like my line isn't too happy at the moment.

C:\Users\Paul>tracert telkom.co.za

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

1 1 ms <1 ms 2 ms 10.0.0.2
2 41 ms 34 ms 23 ms 105-236-9-65-esr-lo.mtnbusiness.co.za [105.236.9
.65]
3 56 ms 40 ms 54 ms 41.181.221.254
4 112 ms 51 ms 56 ms tb-dca-2.za--qux-c.za.mtnbusiness.net [41.181.19
8.188]
5 40 ms 32 ms 22 ms unc-cpt-1.mtnns.net [196.44.18.8]
6 270 ms 110 ms 103 ms tb-pr-1.za--tb-cr-2.za-a.mtnns.net [196.44.18.14
3]
7 42 ms 48 ms 51 ms wblv-ip-se-2-gw.telkom-ipnet.co.za [196.25.165.1
97]
8 25 ms 31 ms 49 ms 196.43.25.205
9 100 ms 67 ms 63 ms 196.43.39.162
10 45 ms 51 ms 58 ms rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
11 48 ms 57 ms * nbsc-ip-bssr-2-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.34]
12 49 ms 45 ms 44 ms nbsc-ip-rcache-1-vif0.telkom-ipnet.co.za [196.43
.22.222]

Trace complete.

C:\Users\Paul>

http://www.speedtest.net/result/3018618371.png
 
It would seem the international bugs are back :/

https://www.dropbox.com/s/h9i64gvgq61clkf/Screenshot 2013-10-08 09.30.00.png
https://www.dropbox.com/s/u94jb0nzc25z80u/Screenshot 2013-10-08 09.43.38.png

Local works 100s, but international is pretty rough. For a 10Meg line this isn't very good.

Code:
Tracing route to ftp.ubuntu.com [91.189.92.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     7 ms     7 ms     6 ms  -esr-lo.mtnbusiness.co.za []
  3    12 ms    12 ms    10 ms  ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178
.89]
  4    11 ms    11 ms    11 ms  rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
  5    30 ms    29 ms    28 ms  jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
  6    27 ms    28 ms    30 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
  7   198 ms   193 ms   193 ms  am-cr-1.nl--jh-cr-2.za-a.mtn.net [196.44.31.215]

  8   207 ms   212 ms   204 ms  am-cr-2.nl--am-cr-1.nl-b.mtnns.net [209.212.111.
249]
  9   218 ms   217 ms   225 ms  ls-cr-1.uk--am-cr-2.nl-a.mtnns.net [196.44.31.15
4]
 10   197 ms   232 ms   198 ms  ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.20
3]
 11   216 ms   215 ms   216 ms  195.50.122.181
 12   225 ms   219 ms   221 ms  vl-3505-ve-119.csw1.London1.Level3.net [4.69.166
.2]
 13   215 ms   211 ms   210 ms  ae-1-51.edge5.London1.Level3.net [4.69.139.75]
 14   206 ms   208 ms   208 ms  SOURCE-MANA.edge5.London1.Level3.net [212.187.13
8.82]
 15   224 ms   212 ms   209 ms  ftp.ubuntu.com [91.189.92.200]

Trace complete.
 
It would seem the international bugs are back :/

https://www.dropbox.com/s/h9i64gvgq61clkf/Screenshot 2013-10-08 09.30.00.png
https://www.dropbox.com/s/u94jb0nzc25z80u/Screenshot 2013-10-08 09.43.38.png

Local works 100s, but international is pretty rough. For a 10Meg line this isn't very good.

Code:
Tracing route to ftp.ubuntu.com [91.189.92.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     7 ms     7 ms     6 ms  -esr-lo.mtnbusiness.co.za []
  3    12 ms    12 ms    10 ms  ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178
.89]
  4    11 ms    11 ms    11 ms  rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
  5    30 ms    29 ms    28 ms  jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
  6    27 ms    28 ms    30 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
  7   198 ms   193 ms   193 ms  am-cr-1.nl--jh-cr-2.za-a.mtn.net [196.44.31.215]

  8   207 ms   212 ms   204 ms  am-cr-2.nl--am-cr-1.nl-b.mtnns.net [209.212.111.
249]
  9   218 ms   217 ms   225 ms  ls-cr-1.uk--am-cr-2.nl-a.mtnns.net [196.44.31.15
4]
 10   197 ms   232 ms   198 ms  ls-pr-2.uk--ls-cr-1.uk-a.mtn.net [209.212.111.20
3]
 11   216 ms   215 ms   216 ms  195.50.122.181
 12   225 ms   219 ms   221 ms  vl-3505-ve-119.csw1.London1.Level3.net [4.69.166
.2]
 13   215 ms   211 ms   210 ms  ae-1-51.edge5.London1.Level3.net [4.69.139.75]
 14   206 ms   208 ms   208 ms  SOURCE-MANA.edge5.London1.Level3.net [212.187.13
8.82]
 15   224 ms   212 ms   209 ms  ftp.ubuntu.com [91.189.92.200]

Trace complete.

Latency is looking good to EU, could you run one to a US destination too please?
We aren't seeing any general trends towards poor international speeds.
 
Latency is looking good to EU, could you run one to a US destination too please?
We aren't seeing any general trends towards poor international speeds.

Code:
Pinging guildwars.com [64.25.35.116] with 32 bytes of data:
Reply from 64.25.35.116: bytes=32 time=335ms TTL=233
Reply from 64.25.35.116: bytes=32 time=327ms TTL=233
Reply from 64.25.35.116: bytes=32 time=343ms TTL=233
Reply from 64.25.35.116: bytes=32 time=339ms TTL=233

Code:
Tracing route to guildwars.com [64.25.35.116]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     7 ms     7 ms     7 ms  ****
  3    38 ms    40 ms    41 ms  ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178
.53]
  4    39 ms    40 ms    41 ms  rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
  5    47 ms    46 ms    28 ms  jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
  6    24 ms    24 ms    25 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
  7   189 ms   187 ms   186 ms  xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41.
89]
  8   300 ms   300 ms   299 ms  4.69.162.157
  9   329 ms   329 ms   329 ms  ae-58-223.ebr2.Amsterdam1.Level3.net [4.69.153.2
09]
 10   308 ms   307 ms   313 ms  ae-46-46.ebr2.London1.Level3.net [4.69.143.74]
 11   312 ms   312 ms   309 ms  ae-41-41.ebr1.NewYork1.Level3.net [4.69.137.66]

 12   310 ms   306 ms   313 ms  ae-10-10.ebr2.Washington12.Level3.net [4.69.148.
50]
 13   327 ms   335 ms   325 ms  ae-1-100.ebr1.Washington12.Level3.net [4.69.143.
213]
 14   302 ms   302 ms   311 ms  ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105]
 15   330 ms   336 ms   339 ms  ae-63-63.ebr3.Atlanta2.Level3.net [4.69.148.241]

 16   321 ms   319 ms   328 ms  ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
 17   326 ms   320 ms   324 ms  ae-83-83.csw3.Dallas1.Level3.net [4.69.151.157]

 18   327 ms   323 ms   354 ms  ae-3-80.edge2.Dallas1.Level3.net [4.69.145.139]

 19   309 ms   310 ms   312 ms  4.59.197.34
 20   324 ms   335 ms   338 ms  guildwars.com [64.25.35.116]

Trace complete.
 
Code:
Pinging guildwars.com [64.25.35.116] with 32 bytes of data:
Reply from 64.25.35.116: bytes=32 time=335ms TTL=233
Reply from 64.25.35.116: bytes=32 time=327ms TTL=233
Reply from 64.25.35.116: bytes=32 time=343ms TTL=233
Reply from 64.25.35.116: bytes=32 time=339ms TTL=233

Code:
Tracing route to guildwars.com [64.25.35.116]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     7 ms     7 ms     7 ms  ****
  3    38 ms    40 ms    41 ms  ipc-recieve-rb-1a.za.mtnbusiness.net [41.181.178
.53]
  4    39 ms    40 ms    41 ms  rb-dca-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.1
20]
  5    47 ms    46 ms    28 ms  jh-cr-1.za--rb-cr-2.za.mtnns.net [196.44.0.42]
  6    24 ms    24 ms    25 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
  7   189 ms   187 ms   186 ms  xe-4-1-0.edge5.Amsterdam1.Level3.net [212.72.41.
89]
  8   300 ms   300 ms   299 ms  4.69.162.157
  9   329 ms   329 ms   329 ms  ae-58-223.ebr2.Amsterdam1.Level3.net [4.69.153.2
09]
 10   308 ms   307 ms   313 ms  ae-46-46.ebr2.London1.Level3.net [4.69.143.74]
 11   312 ms   312 ms   309 ms  ae-41-41.ebr1.NewYork1.Level3.net [4.69.137.66]

 12   310 ms   306 ms   313 ms  ae-10-10.ebr2.Washington12.Level3.net [4.69.148.
50]
 13   327 ms   335 ms   325 ms  ae-1-100.ebr1.Washington12.Level3.net [4.69.143.
213]
 14   302 ms   302 ms   311 ms  ae-6-6.ebr1.Atlanta2.Level3.net [4.69.148.105]
 15   330 ms   336 ms   339 ms  ae-63-63.ebr3.Atlanta2.Level3.net [4.69.148.241]

 16   321 ms   319 ms   328 ms  ae-7-7.ebr3.Dallas1.Level3.net [4.69.134.21]
 17   326 ms   320 ms   324 ms  ae-83-83.csw3.Dallas1.Level3.net [4.69.151.157]

 18   327 ms   323 ms   354 ms  ae-3-80.edge2.Dallas1.Level3.net [4.69.145.139]

 19   309 ms   310 ms   312 ms  4.59.197.34
 20   324 ms   335 ms   338 ms  guildwars.com [64.25.35.116]

Trace complete.

Also looking good, so really strange that you're seeing slower international speeds :(
Could you drop me a PM with your info, I'll see if I can spot something on my end.
 
Starting at about 5.30, things improved.
Usenet seems to run at ~620KB/s now which is better, but still not where it did last week (news.afrihost.co.za) If I enable my backup account it jumps to 1MB/s.
ftp.ubuntu.com still sits at lowish speeds. It maxed out at 300KB/s just now.
 
Starting at about 5.30, things improved.
Usenet seems to run at ~620KB/s now which is better, but still not where it did last week (news.afrihost.co.za) If I enable my backup account it jumps to 1MB/s.
ftp.ubuntu.com still sits at lowish speeds. It maxed out at 300KB/s just now.

Will have to follow up with Afriguy on this. Hope he's able to assist you.
 
What's cooking? I think it might be your IPC....

Code:
tracert telkom.co.za

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    7 ms     7 ms     7 ms  105-236--esr-lo.mtnbusiness.co.za [105.236
.]
  3  [B] 349 ms   354 ms   354 ms  ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178
.89][/B]
  4   369 ms   354 ms   348 ms  rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
  5   356 ms   358 ms   366 ms  jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
  6   341 ms   350 ms   369 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
  7   374 ms   369 ms   365 ms  rrba-ip-se-2-wan.telkom-ipnet.co.za [196.25.58.1
7]
  8   384 ms   379 ms   365 ms  196.43.25.137
  9   379 ms   375 ms   370 ms  196.43.39.162
 10   343 ms   341 ms   343 ms  rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
 11   370 ms   362 ms   361 ms  nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
 12   357 ms   351 ms   356 ms  telkom.co.za [196.43.22.222]

Trace complete.
 
What's cooking? I think it might be your IPC....

Code:
tracert telkom.co.za

Tracing route to telkom.co.za [196.43.22.222]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    7 ms     7 ms     7 ms  105-236--esr-lo.mtnbusiness.co.za [105.236
.]
  3  [B] 349 ms   354 ms   354 ms  ipc-recieve-rb-4a.za.mtnbusiness.net [41.181.178
.89][/B]
  4   369 ms   354 ms   348 ms  rb-cr-1.za--rb-dca-1.za-a.mtnns.net [196.44.0.14
6]
  5   356 ms   358 ms   366 ms  jh-cr-2.za--rb-cr-1.za-a.mtnns.net [196.44.31.95
]
  6   341 ms   350 ms   369 ms  qux-jh-dca-2.za-b.za.mtnbusiness.net [41.181.165
.115]
  7   374 ms   369 ms   365 ms  rrba-ip-se-2-wan.telkom-ipnet.co.za [196.25.58.1
7]
  8   384 ms   379 ms   365 ms  196.43.25.137
  9   379 ms   375 ms   370 ms  196.43.39.162
 10   343 ms   341 ms   343 ms  rrba-ip-bssr-1-ge-2-48.telkom-ipnet.co.za [196.4
3.23.6]
 11   370 ms   362 ms   361 ms  nbsc-ip-bssr-1-atm-5-0-0-1.telkom-ipnet.co.za [1
96.43.23.30]
 12   357 ms   351 ms   356 ms  telkom.co.za [196.43.22.222]

Trace complete.

We're trying to replicate and investigate this on our end.
 
Status
Not open for further replies.
Top
Sign up to the MyBroadband newsletter
X