Afrihost New Network Feedback - Part 3

[Phinix]

Those stats won't alway change, but we find that sync gets iffy on some lines that are connected for a certain length of time.

It really depends, but we usually aim for 24 hours max wherever we can.

How long have you been waiting?

I replied to the ticket at 9.26pm last night. So just over 18 hours.

 

[Blazzok]

Seems like my trace is doing the same. I'll check with our admins what could be happening

Any other examples showing the same?

I'm being router via Australia as well.

Tracing route to reddit.com [151.101.1.140]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ARCHER_D2 [192.168.1.1]
2 1 ms 1 ms 1 ms 192.168.10.1
3 * * * Request timed out.
4 47 ms 45 ms 42 ms jhb-up1.ip.adsl.co.za [169.1.5.5]
5 44 ms 46 ms 43 ms jhb-rx1.ip.adsl.co.za [169.1.5.18]
6 65 ms 43 ms 44 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
7 43 ms 63 ms 42 ms 169-1-5-74.ip.afrihost.co.za [169.1.5.74]
8 43 ms 44 ms 43 ms 41.169.57.216
9 391 ms 391 ms 390 ms ix-xe-0-0-0-2.thar2.1MH-Sydney.as6453.net [180.87.29.121]
10 497 ms 496 ms 500 ms 220.101.73.73
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 520 ms 518 ms 522 ms 59.154.142.178
15 510 ms 511 ms 514 ms bundle-ether18.cha-edge902.brisbane.telstra.net [139.130.61.73]
16 514 ms 510 ms 509 ms bundle-ether2.woo-edge902.brisbane.telstra.net [203.50.11.147]
17 * * * Request timed out.
18 503 ms 503 ms 507 ms 151.101.1.140

Trace complete.

On a different note, I also have 100% packet loss at times (this a bit after I did the trace).

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

 

[Johnatan56]

Bras.afrihost.com at a smooth 21ms. Will game after dinner, will see how it goes but not optimistic.

 

[AfriFella]

I'm being router via Australia as well.



On a different note, I also have 100% packet loss at times (this a bit after I did the trace).

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 155.239.255.250:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

We have sent your results onto our NOC Team. We'll provide you with more information on the routing issue as soon as we have it.

 

[AfriFella]

View attachment 410338

Bras.afrihost.com at a smooth 21ms. Will game after dinner, will see how it goes but not optimistic.

Are you still working with our CC Team?

 

[Johnatan56]

Are you still working with our CC Team?

Well they're just asking for results, not much else.


This is before the game starts, no one else using the network. Only Skype and League will be running.
Wrote the same message to them on clientzone.

EDIT: 255ms ping... should be 170ms...

 

[Johnatan56]

All right.
Starting the game: 255ms ping EUW LoL, should have 175-180ms.
Random teleporting/catchup with 800-1200ms latency bursts.
Not sorted.

Pretty much unplayable.

 

[Johnatan56]

EDIT:
Btw this was from your man:

How was your performance over the weekend?

Our NOC team did not see any issues over the weekend.

Please re-test for me tonight, so we can investigate.

Thanks

Have a great day and please let me know if I can help with anything else!

Warm regards

Quite a few posted here that they had issues, so your NOC team needs to start gaming. That was at 9:10am.
I then said I'll try to game tonight, no reply.

What's the point of this support ticket if there is no one in real time to actually work with you?
"critical care" yet no support on weekends, the issue occurs in the evening, pretty much becomes extreme at 20h30 till 22h00, with noticeable packet loss from tracerts, your networking team should have better tools than I to monitor this.

This has been a lousy month, first billing error, then fiber break, on top of that packet loss every evening. Not sure why I'm even trying this if "critical care" a.k.a. last line of defense support isn't even available to run diagnostics etc. during the time of the issue which is their peak network time. What's the point of me "gathering" this info if nothing is done? It's feeling a lot like Telkom's escalation of faults, an absolute waste of time.
Also 24 hours to reply for a "critical" support ticket is crazy, at least make him reply at 9.30pm instead of 9.30am.

EDIT 2:


Should I be paying <90% of the price as I only get that many packets through the first bloody hop onto your network. And the London peering point is also your responsibility to sort out, it's been giving issues since mid of Dec. if you followed this thread.

 

[medicnick83]

I'm having issues AGAIN!

 

[Phinix]

Ok well now I'm getting annoyed.

Every evening things just become painfully slow. Even youtube cant load a 1080P video at the moment, but is seamless during the day.

And what is wrong with support that they take more then 24 hours between each reply?

 

[xbxbau5]

Yep, getting pretty much same results here.

On AfriGreen account, with default DNS settings.
169.1.1.3 & 169.1.1.3

Here's my Tracert to one of the League servers.

Tracing route to 185.40.65.1 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 130 ms 130 ms 127 ms cpt-tx2.ip.adsl.co.za [169.1.5.81]
4 57 ms 59 ms 63 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
5 152 ms 134 ms 137 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
6 247 ms 78 ms 57 ms 41.164.52.40
7 114 ms 129 ms 136 ms ix-ae-7-0.tcore1.KLT-Cape-Town.as6453.net [41.20
6.164.53]
8 210 ms 226 ms 376 ms if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.1
59.57]
9 187 ms 199 ms 276 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.1
58.5]
10 265 ms 270 ms 273 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.2
31.158.30]
11 242 ms 237 ms 235 ms if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.2
31.139.1]
12 * * * Request timed out.
13 179 ms 179 ms 181 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.
130.130]
14 276 ms 284 ms 283 ms 195.219.83.102
15 * * * Request timed out.
16 * * 186 ms 213.19.195.234
17 * 1184 ms * 104.160.141.44
18 290 ms 283 ms 285 ms 104.160.141.103
19 196 ms 191 ms 191 ms 104.160.141.107
20 * * * Request timed out.


Here's another Tracert with my free WA account and default DNS settings
168.210.2.2 & 8.8.8.8

Tracing route to 185.40.65.1 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 36 ms 37 ms 37 ms 196.38.75.70
4 44 ms 44 ms 44 ms 196.38.75.69
5 37 ms 36 ms 36 ms 196.35.115.128
6 37 ms 38 ms 37 ms mi-za-cpt-p7-te0-0-0-0.ip.isnet.net [168.209.6.1
2]
7 188 ms 187 ms 187 ms core1b-dock-ge-0-4-2-1.ip.isnet.net [168.209.201
.6]
8 191 ms 188 ms 186 ms core2b-dock-ten-0-4-0-0sub8.ip.isnet.net [168.20
9.246.66]
9 181 ms 181 ms 181 ms xe-4-3-2.edge3.London1.Level3.net [195.50.124.33
]
10 * * * Request timed out.
11 * 210 ms 209 ms 213.19.195.234
12 * * * Request timed out.
13 219 ms 219 ms 219 ms 104.160.141.103
14 200 ms 201 ms 201 ms 104.160.141.107
15 202 ms 201 ms 202 ms 185.40.65.1

Trace complete.

All right.
Starting the game: 255ms ping EUW LoL, should have 175-180ms.
Random teleporting/catchup with 800-1200ms latency bursts.
Not sorted.

Pretty much unplayable.

 

[thewusman]

Since around 4 Jan 2017, Showmax and Netflix have become pixelated messes (40mbps VDSL crew checking in) from around 8pm to 10pm.

Hopping onto my free WebAfrica account and things are perfectly HD.

Welcome to the hell that is either a) new capped shaping or b) eastern and western cape lack of capacity.

Cue email from Gian in 6 months saying "sorry we messed up things will get better".

 

[DeatheCore]

Seems like my trace is doing the same. I'll check with our admins what could be happening

Any other examples showing the same?

Trace done at time of posting.

Tracing route to reddit.com [151.101.65.140]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.2
2 * * * Request timed out.
3 52 ms 53 ms 48 ms cpt-rx2.ip.adsl.co.za [169.1.5.82]
4 14 ms 14 ms 16 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 19 ms 14 ms 12 ms 41.164.52.40
6 32 ms 31 ms 32 ms 172.18.1.164
7 378 ms 376 ms 375 ms ix-xe-0-0-0-2.thar2.1mh-sydney.as6453.net [180.87.29.121]
8 482 ms 472 ms 471 ms 220.101.73.73
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 486 ms 479 ms 479 ms 59.154.142.178
13 483 ms 483 ms 483 ms bundle-ether18.cha-edge902.brisbane.telstra.net [139.130.61.73]
14 484 ms 484 ms 484 ms bundle-ether2.woo-edge902.brisbane.telstra.net [203.50.11.147]
15 * * * Request timed out.
16 489 ms 488 ms 488 ms 151.101.65.140

Trace complete.

And just for information purposes:

Pinging bras.afrihost.com [155.239.255.250] with 32 bytes of data:
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63
Reply from 155.239.255.250: bytes=32 time=13ms TTL=63
Reply from 155.239.255.250: bytes=32 time=11ms TTL=63

 

[squish0601]

Since around 4 Jan 2017, Showmax and Netflix have become pixelated messes (40mbps VDSL crew checking in) from around 8pm to 10pm.

Hopping onto my free WebAfrica account and things are perfectly HD.

Welcome to the hell that is either a) new capped shaping or b) eastern and western cape lack of capacity.

Cue email from Gian in 6 months saying "sorry we messed up things will get better".

Lol.
All the money was spent back buying the mtn shares

 

[medicnick83]

C:\Users\Nick>ping 8.8.8.8 -t

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=104ms TTL=52
Reply from 8.8.8.8: bytes=32 time=99ms TTL=52
Request timed out.
Reply from 8.8.8.8: bytes=32 time=118ms TTL=52
Reply from 8.8.8.8: bytes=32 time=113ms TTL=52
Reply from 8.8.8.8: bytes=32 time=111ms TTL=52
Reply from 8.8.8.8: bytes=32 time=122ms TTL=52
Reply from 8.8.8.8: bytes=32 time=114ms TTL=52
Reply from 8.8.8.8: bytes=32 time=117ms TTL=52
Reply from 8.8.8.8: bytes=32 time=119ms TTL=52
Reply from 8.8.8.8: bytes=32 time=122ms TTL=52
Request timed out.
Reply from 8.8.8.8: bytes=32 time=116ms TTL=52
Reply from 8.8.8.8: bytes=32 time=112ms TTL=52
Reply from 8.8.8.8: bytes=32 time=120ms TTL=52
Reply from 8.8.8.8: bytes=32 time=121ms TTL=52
Request timed out.
Reply from 8.8.8.8: bytes=32 time=120ms TTL=52
Reply from 8.8.8.8: bytes=32 time=123ms TTL=52
Reply from 8.8.8.8: bytes=32 time=120ms TTL=52
Reply from 8.8.8.8: bytes=32 time=119ms TTL=52
Request timed out.
Reply from 8.8.8.8: bytes=32 time=109ms TTL=52
Reply from 8.8.8.8: bytes=32 time=98ms TTL=52
Reply from 8.8.8.8: bytes=32 time=92ms TTL=52
Reply from 8.8.8.8: bytes=32 time=111ms TTL=52
Request timed out.
Reply from 8.8.8.8: bytes=32 time=103ms TTL=52
Reply from 8.8.8.8: bytes=32 time=115ms TTL=52
Request timed out.
Reply from 8.8.8.8: bytes=32 time=113ms TTL=52
Reply from 8.8.8.8: bytes=32 time=112ms TTL=52
Reply from 8.8.8.8: bytes=32 time=116ms TTL=52
Reply from 8.8.8.8: bytes=32 time=88ms TTL=52
Reply from 8.8.8.8: bytes=32 time=93ms TTL=52
Reply from 8.8.8.8: bytes=32 time=118ms TTL=52
Reply from 8.8.8.8: bytes=32 time=123ms TTL=52
Reply from 8.8.8.8: bytes=32 time=113ms TTL=52
Reply from 8.8.8.8: bytes=32 time=269ms TTL=52
Reply from 8.8.8.8: bytes=32 time=50ms TTL=52
Reply from 8.8.8.8: bytes=32 time=118ms TTL=52
Reply from 8.8.8.8: bytes=32 time=121ms TTL=52
Request timed out.
Reply from 8.8.8.8: bytes=32 time=114ms TTL=52
Reply from 8.8.8.8: bytes=32 time=120ms TTL=52
Reply from 8.8.8.8: bytes=32 time=124ms TTL=52
Request timed out.

 

[medicnick83]

tracert www.afrihost.co.za

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 102 ms 100 ms 101 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
4 12 ms 9 ms * cpt-net1.ip.adsl.co.za [169.1.5.128]
5 10 ms 10 ms 10 ms optinet.ixp.capetown [196.10.140.15]
6 31 ms 33 ms 29 ms te0-0-0-1.cpt-p-2.optinet.net [197.84.7.34]
7 32 ms 34 ms 31 ms te0-7-0-0.cpt-p-1.optinet.net [197.84.4.33]
8 32 ms 30 ms 31 ms te0-0-0-0.vic-p-2.optinet.net [197.84.4.35]
9 35 ms 34 ms 32 ms 197-84-4-100.cpt.mweb.co.za [197.84.4.100]
10 30 ms 32 ms 30 ms 101.te0-0-2-0.vic-tr-1.optinet.net [197.80.7.4]
11 30 ms 30 ms 30 ms 197-81-226-77.jhb.mweb.co.za [197.81.226.77]
12 33 ms 31 ms 63 ms 197-81-226-53.jhb.mweb.co.za [197.81.226.53]
13 29 ms 30 ms 30 ms 197-81-229-2.jhb.mweb.co.za [197.81.229.2]
14 30 ms 30 ms 29 ms 197-81-229-9.jhb.mweb.co.za [197.81.229.9]
15 29 ms 28 ms 29 ms 41-86-112-68.mweb.co.za [41.86.112.68]

Trace complete.

 

[squish0601]

bras.afrihost.com is your exchange, if it gets really high in the evenings it's your exchange and not the Afrihost network. Should easily be able to confirm by using another ISP's trial account.

Um...read again, if I ping bras I get 25ms and less.
As to evenings pointing to my exchange, not sure how you come to that conclusion.
Was moved to brand new isam, total of 11 users on that exchange as telkom hasn't set final date of migration.
Trial account on webafrica solves problem.

 

[Johnatan56]

Haha! everyones back from holiday and internet usage is up.

This past festive season pretty much confirmed fault is congestion on Afrihost network. Since 25 Dec pings was PERFECT!!! everything went pear shaped once we hit the 4 Jan.
Its also very clear if you run tests during day vs evening. Day pings in 20's, hit 6pm you are about 180's.

Not to mention if you ping bras.afrihost.com, any time of day, you consistently get >25ms.
If you ping afrihost.com, day time, pings are consistently 20's. As soon as you hit evenings, its becomes 180's

...

 

[squish0601]

...

Awkward... Haha.
Typo, should be <25ms.

Apologies

 

[Blazzok]

HTTP download going at a full 8 KB/s. Didn't realise that I missed dial-up so much until now.