Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
kohlhtor said:
I get no reply from critical care your support is crap fix this
Manny have the same problem
Click to expand...

Our Critical Care Team remains the best avenue for support. I shall ask them to get in touch with you again.
 
There's something wrong with Afrihost's IPC. Probably congested again etc. as per normal...

Afrihost:
tracert www.afrihost.com

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 31 ms 31 ms 32 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 40 ms 39 ms 39 ms 169-1-5-132.ip.afrihost.co.za [169.1.5.132]
5 34 ms 33 ms 35 ms 41.164.52.42
6 66 ms 64 ms 65 ms 172.18.1.162
7 69 ms 69 ms 65 ms cloudflare.ixp.joburg [196.46.25.198]
8 63 ms 61 ms 60 ms 104.20.31.244

Web Africa comparison:
tracert www.afrihost.com

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 13 ms 13 ms 12 ms cdsl1-ctn-vl2376-ipc.ip.isnet.net [196.38.72.206]
4 12 ms 12 ms 13 ms cdsl1-ctn-vl2376.ip.isnet.net [196.38.72.205]
5 11 ms 12 ms 12 ms 196.35.115.128
6 13 ms 12 ms 12 ms mi-za-cpt-p7-te0-7-0-0.ip.isnet.net [168.209.2.12]
7 64 ms 63 ms 60 ms 168.209.0.177
8 60 ms 67 ms 65 ms 196.26.0.130
9 36 ms 37 ms 37 ms cloudflare.ixp.joburg [196.46.25.198]
10 36 ms 36 ms 36 ms 104.20.31.244

Trace complete.
 
Vio said:
There's something wrong with Afrihost's IPC. Probably congested again etc. as per normal...

Afrihost:
tracert www.afrihost.com

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 31 ms 31 ms 32 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 40 ms 39 ms 39 ms 169-1-5-132.ip.afrihost.co.za [169.1.5.132]
5 34 ms 33 ms 35 ms 41.164.52.42
6 66 ms 64 ms 65 ms 172.18.1.162
7 69 ms 69 ms 65 ms cloudflare.ixp.joburg [196.46.25.198]
8 63 ms 61 ms 60 ms 104.20.31.244

Web Africa comparison:
tracert www.afrihost.com

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 13 ms 13 ms 12 ms cdsl1-ctn-vl2376-ipc.ip.isnet.net [196.38.72.206]
4 12 ms 12 ms 13 ms cdsl1-ctn-vl2376.ip.isnet.net [196.38.72.205]
5 11 ms 12 ms 12 ms 196.35.115.128
6 13 ms 12 ms 12 ms mi-za-cpt-p7-te0-7-0-0.ip.isnet.net [168.209.2.12]
7 64 ms 63 ms 60 ms 168.209.0.177
8 60 ms 67 ms 65 ms 196.26.0.130
9 36 ms 37 ms 37 ms cloudflare.ixp.joburg [196.46.25.198]
10 36 ms 36 ms 36 ms 104.20.31.244

Trace complete.
Click to expand...

Afrihost is not care about support
 
And higher
bb29b850d7e83085b3ec12af96d2e07c.jpg

Is know 20:00 afrihost going home we have no problem !
 
Hi guys, I have sent all your test results over to our NOC Team and they are currently looking into - and monitoring traffic in the South. We're not seeing any obvious causes for high latency at the moment, but our Team are busy investigating. I'll reach out to you individually via PM if we need any further tests and update the thread with any general announcements once I hear back from the NOC Team. Thanks for testing.
 
Yeah something is up with AH for sure. I have a 20mb line.

Speedtest to London:

AH
5693262534.png

Telkom
5693244284.png

Tracert to bbc.co.uk:

AH

Tracing route to bbc.co.uk [212.58.244.23]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 72 ms 68 ms 72 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
4 60 ms 61 ms 61 ms 169-1-5-132.ip.afrihost.co.za [169.1.5.132]
5 61 ms 62 ms 62 ms 41.164.52.42
6 107 ms 105 ms 104 ms ix-ae-7-0.tcore1.KLT-Cape-Town.as6453.net [41.206.164.53]
7 226 ms 225 ms 226 ms if-p-6.core2.PV9-Lisbon.as6453.net [41.206.164.6]
8 265 ms 262 ms 262 ms if-xe-0-0-0-2000.tcore1.PV9-Lisbon.as6453.net [80.231.158.1]
9 249 ms 246 ms 248 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
10 276 ms * 266 ms if-ae-19-2.tcore2.L78-London.as6453.net [80.231.138.22]
11 253 ms 255 ms 245 ms if-ae-2-2.tcore1.L78-London.as6453.net [80.231.131.2]
12 250 ms 248 ms * if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
13 258 ms 257 ms 262 ms 195.219.83.102
14 * * * Request timed out.
15 270 ms 259 ms 258 ms unknown.Level3.net [212.187.139.230]
16 * * * Request timed out.
17 277 ms 270 ms 271 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
18 269 ms 268 ms 269 ms 132.185.255.148
19 264 ms 263 ms 264 ms 212.58.244.23

Trace complete.

Telkom

Tracing route to bbc.co.uk [212.58.244.22]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.asus.com [192.168.1.1]
2 * * * Request timed out.
3 22 ms 21 ms 21 ms ipc-2-up.south.dsl.telkomsa.net [105.226.0.22]
4 21 ms 20 ms 20 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
5 20 ms 20 ms 21 ms 196.25.190.209
6 164 ms 163 ms 163 ms lon-ip-hsll-1-gig-7-1-0.telkom-ipnet.co.za [196.43.9.58]
7 176 ms 177 ms 178 ms ldn-b5-link.telia.net [62.115.35.89]
8 182 ms 189 ms 183 ms atos-ic-315186-ldn-b5.c.telia.net [62.115.144.161]
9 * * * Request timed out.
10 197 ms 202 ms 207 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
11 188 ms 182 ms 182 ms 132.185.255.148
12 197 ms 186 ms 180 ms 212.58.244.22
 
yup..same story tonight concerning rotten latency once again [300ms in overwatch again (cpt)].. why am I not surprised. you going to fix whatever suddenly broke last night?
 
10Meg Line in Hout Bay

Telkom:
5693317070.png

AFRIHOST:
5693331682.png

Both with ISP provided DNS.

I was seeing issues last night so switched to TELKOM and all was fine.
Switched back to AFRIHOST for this test.

Returning to TELKOM now so I can actually use the internet.
 
Local 2mbit line:
Web Africa
5693358882.png

Afrihost
5693365532.png

Look at the difference in local ping...
 
Thanks Afrihost!

AfrihostSteam.PNG

Star Trek Online has also been ok for the most part tonight

|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.254 - 0 | 81 | 81 | 0 | 0 | 1 | 0 |
| No response from host - 100 | 17 | 0 | 0 | 0 | 0 | 0 |
| jhb-up1.ip.adsl.co.za - 3 | 77 | 75 | 28 | 31 | 51 | 29 |
| jhb-rx1.ip.adsl.co.za - 5 | 69 | 66 | 27 | 30 | 57 | 30 |
| jhb-net1.ip.adsl.co.za - 0 | 81 | 81 | 37 | 79 | 120 | 44 |
| 169-1-5-74.ip.afrihost.co.za - 2 | 77 | 76 | 46 | 90 | 157 | 102 |
| 41.169.57.216 - 0 | 81 | 81 | 39 | 81 | 118 | 54 |
|ix-ae-7-0.tcore1.JSO-Johannesburg.as6453.net - 0 | 81 | 81 | 30 | 43 | 97 | 40 |
|if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net - 0 | 81 | 81 | 266 | 277 | 328 | 270 |
| if-ae-5-10.tcore2.PV9-Lisbon.as6453.net - 0 | 81 | 81 | 261 | 270 | 285 | 263 |
| if-ae-2-2.tcore1.PV9-Lisbon.as6453.net - 0 | 81 | 81 | 256 | 281 | 333 | 258 |
|if-ae-1-3.tcore1.SV8-Highbridge.as6453.net - 0 | 81 | 81 | 255 | 263 | 296 | 267 |
| if-ae-6-2.thar1.NJY-Newark.as6453.net - 3 | 73 | 71 | 254 | 258 | 284 | 255 |
| if-ae-1-3.thar2.NJY-Newark.as6453.net - 56 | 25 | 11 | 0 | 260 | 262 | 261 |
|if-ae-14-15.tcore2.NTO-New-York.as6453.net - 0 | 81 | 81 | 279 | 311 | 347 | 298 |
| be3011.ccr21.jfk05.atlas.cogentco.com - 0 | 81 | 81 | 260 | 280 | 323 | 265 |
| be2061.ccr42.jfk02.atlas.cogentco.com - 0 | 81 | 81 | 273 | 317 | 362 | 304 |
| be2096.ccr22.bos01.atlas.cogentco.com - 0 | 81 | 81 | 262 | 270 | 288 | 262 |
|te0-0-0-0.rcr11.b002133-1.bos01.atlas.cogentco.com - 0 | 81 | 81 | 262 | 312 | 352 | 282 |
| 38.111.40.114 - 0 | 81 | 81 | 265 | 282 | 318 | 277 |
| 198.49.243.252 - 0 | 81 | 81 | 291 | 326 | 369 | 313 |
| 208.95.186.130 - 0 | 81 | 81 | 264 | 273 | 302 | 269 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Click to expand...

If the packet loss hadn't been there, it would have been better though.
This is on an 8meg capped account.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X