Afrihost New Network Feedback - Part 2

Status
Not open for further replies.
Vio said:
That was on IS CT Quake Live server. ping is ~18ms then spikes up to 50-60ms only did it on Afrihost account.

Doing the same **** at the moment.
Click to expand...

now it's fine again....
 
EU and Mweb both a mess tonight,

Trace Route to Sipgate.de
1 * * *
2 dbn-up2.ip.adsl.co.za (169.1.5.173) 17.013 ms 15.128 ms 15.116 ms
3 dbn-up2.ip.adsl.co.za (169.1.5.174) 15.930 ms 15.034 ms 15.436 ms
4 dbn-in1.ip.adsl.co.za (169.1.5.204) 15.596 ms 15.719 ms 15.878 ms
5 41.162.84.192 (41.162.84.192) 21.446 ms 20.027 ms 20.224 ms
6 172.18.1.162 (172.18.1.162) 32.998 ms 34.350 ms 33.489 ms
7 ix-ae-7-0.tcore1.JSO-Johannesburg.as6453.net (41.206.178.29) 33.555 ms 34.243 ms 33.741 ms
8 if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net (41.206.178.2) 193.183 ms 188.992 ms 189.694 ms
9 if-ae-5-80.tcore2.PV9-Lisbon.as6453.net (80.231.159.57) 204.501 ms 205.512 ms 205.729 ms
10 if-ae-2-2.tcore1.PV9-Lisbon.as6453.net (80.231.158.5) 202.526 ms 208.508 ms 209.678 ms
11 if-ae-1-3.tcore1.SV8-Highbridge.as6453.net (80.231.158.30) 208.472 ms 214.108 ms 213.396 ms
12 if-ae-2-2.tcore2.SV8-Highbridge.as6453.net (80.231.139.1) 222.234 ms 201.115 ms 201.303 ms
13 if-ae-11-2.tcore1.L78-London.as6453.net (80.231.139.42) 193.888 ms 192.716 ms 193.362 ms
14 if-ae-17-2.tcore1.LDN-London.as6453.net (80.231.130.130) 199.342 ms 198.556 ms 199.587 ms
15 195.219.83.102 (195.219.83.102) 200.334 ms 201.781 ms 200.579 ms
16 ae-1-60.edge4.Frankfurt1.Level3.net (4.69.154.8) 304.273 ms 307.134 ms 314.904 ms
17 ae-1-60.edge4.Frankfurt1.Level3.net (4.69.154.8) 313.415 ms 310.236 ms 314.437 ms
18 te2-2.c102.f.de.plusline.net (212.162.24.58) 316.343 ms 305.761 ms 312.189 ms
19 82.98.102.13 (82.98.102.13) 302.765 ms 301.825 ms 303.314 ms
20 82.98.98.250 (82.98.98.250) 304.321 ms 307.466 ms 315.603 ms
21 212.19.42.26 (212.19.42.26) 307.026 ms 307.909 ms 300.845 ms
22 sipgate.de (217.10.79.9) 308.717 ms 298.796 ms 300.610 ms
Click to expand...

Trace Route to bbc.co.uk
1 * * *
2 dbn-up2.ip.adsl.co.za (169.1.5.173) 17.278 ms 17.818 ms 17.382 ms
3 dbn-up2.ip.adsl.co.za (169.1.5.174) 15.261 ms 14.362 ms 13.531 ms
4 dbn-in1.ip.adsl.co.za (169.1.5.204) 13.955 ms 13.761 ms 13.977 ms
5 41.162.84.192 (41.162.84.192) 14.268 ms 14.867 ms 14.536 ms
6 172.18.1.162 (172.18.1.162) 37.731 ms 36.272 ms 32.044 ms
7 * * *
8 if-ae-2-2.tcore1.JSO-Johannesburg.as6453.net (216.6.55.85) 186.163 ms 198.872 ms 184.797 ms
9 if-ae-4-2.tcore1.KLT-Cape-Town.as6453.net (41.206.178.2) 184.830 ms 185.293 ms 184.055 ms
10 if-ae-5-40.tcore2.PV9-Lisbon.as6453.net (80.231.159.89) 203.755 ms 195.205 ms 195.221 ms
11 if-ae-2-2.tcore1.PV9-Lisbon.as6453.net (80.231.158.5) 196.996 ms 197.918 ms 198.106 ms
12 if-ae-1-3.tcore1.SV8-Highbridge.as6453.net (80.231.158.30) 196.662 ms 197.125 ms 196.619 ms
13 if-ae-2-2.tcore2.SV8-Highbridge.as6453.net (80.231.139.1) 201.679 ms 195.929 ms 195.876 ms
14 if-ae-11-2.tcore1.L78-London.as6453.net (80.231.139.42) 387.226 ms 389.017 ms 387.768 ms
15 if-ae-17-2.tcore1.LDN-London.as6453.net (80.231.130.130) 393.152 ms 392.972 ms 392.945 ms
16 195.219.83.102 (195.219.83.102) 396.373 ms 395.401 ms 395.386 ms
17 * * *
18 * * *
19 NIU-SOLUTIO.ear1.London15.Level3.net (212.187.173.210) 301.956 ms 301.271 ms 301.074 ms
20 * * *
21 * * *
22 ae0.er01.cwwtf.bbc.co.uk (132.185.254.93) 345.656 ms 339.413 ms 344.687 ms
23 132.185.255.165 (132.185.255.165) 302.531 ms 302.484 ms 301.830 ms
24 212.58.246.78 (212.58.246.78) 302.756 ms 310.136 ms 312.647 ms
Click to expand...

Trace Route to sip.mweb.net
1 * * *
2 dbn-up2.ip.adsl.co.za (169.1.5.173) 17.208 ms 17.875 ms 17.897 ms
3 dbn-up2.ip.adsl.co.za (169.1.5.174) 17.182 ms 18.807 ms 17.704 ms
4 dbn-in1.ip.adsl.co.za (169.1.5.204) 17.914 ms 17.356 ms 17.019 ms
5 optinet.ixp.durban (196.10.141.75) 738.912 ms 240.230 ms 133.803 ms
6 197-82-7-2.dbn.mweb.co.za (197.82.7.2) 136.923 ms 135.818 ms 136.962 ms
7 te0-0-0-0.vic-p-1.optinet.net (197.84.4.38) 131.793 ms 131.749 ms 131.773 ms
8 197-80-7-15.jhb.mweb.co.za (197.80.7.15) 310.046 ms 130.331 ms 130.295 ms
9 197-81-226-81.jhb.mweb.co.za (197.81.226.81) 135.509 ms 131.306 ms 230.530 ms
10 197-81-226-61.jhb.mweb.co.za (197.81.226.61) 317.687 ms 136.755 ms 138.921 ms
11 197-81-229-4.jhb.mweb.co.za (197.81.229.4) 137.452 ms 236.521 ms 137.450 ms
12 197-81-229-23.jhb.mweb.co.za (197.81.229.23) 130.547 ms 232.072 ms 230.039 ms
13 sip.voip.mweb.net (196.28.95.12) 135.971 ms 137.758 ms 237.695 m
Click to expand...
 
Thanks for the posting the traceroutes guys, I've sent them to our Team to have a look at, we'll defintely figure out how we can improve your experience.
 
AfriGenie said:
Thanks for the posting the traceroutes guys, I've sent them to our Team to have a look at, we'll defintely figure out how we can improve your experience.
Click to expand...

No offense, but these traceroutes has been posted for months already now... And you've been sending it to your "network team" for just as long. Any idea on when we will hear what is actually wrong, or even better, when it will be resolved?

I can't remember when last I was able to use my AH account at night - it's pathetic, to say the least.
 
The last 4 nights latency has been high again this time of the evening

When all goes well earlier
Code: 
Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     1 ms     1 ms    <1 ms  10.100.0.1 
  3     *        *        *     Request timed out.
  4    21 ms    19 ms    20 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  5    26 ms    22 ms    19 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  6    21 ms    22 ms    21 ms  optinet.ixp.capetown [196.10.140.15] 
  7    23 ms    22 ms    24 ms  te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2] 
  8    19 ms    19 ms    19 ms  vl12.cpt-hscore-2.optinet.net [197.84.5.254] 
  9    20 ms    19 ms    19 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
 10    20 ms    19 ms    19 ms  gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]

Code: 
Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2     1 ms    <1 ms    <1 ms  10.100.0.1 
  3     *        *        *     Request timed out.
  4    35 ms    31 ms    32 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  5    21 ms    19 ms    20 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  6    19 ms    19 ms    19 ms  optinet.ixp.capetown [196.10.140.15] 
  7    51 ms    52 ms    50 ms  te0-0-0-1.cpt-p-2.optinet.net [197.84.7.34] 
  8    38 ms    36 ms    35 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238] 
  9    20 ms    19 ms    19 ms  196.28.178.66 
 10    19 ms    20 ms    19 ms  gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234] 
 11    20 ms    19 ms    19 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 12    20 ms    20 ms    23 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 13    20 ms    19 ms    20 ms  41-86-110-200.mweb.co.za [41.86.110.200]

And now when things are not great
Code: 
Tracing route to www.mweb.co.za [196.2.63.110]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2    <1 ms    <1 ms    <1 ms  10.100.0.1 
  3     *        *        *     Request timed out.
  4   101 ms    94 ms    94 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  5    18 ms    18 ms    35 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  6    20 ms    19 ms    19 ms  optinet.ixp.capetown [196.10.140.15] 
  7   104 ms   108 ms   111 ms  te0-7-0-3.cpt-p-2.optinet.net [197.84.7.2] 
  8    94 ms    79 ms    73 ms  vl12.cpt-hscore-2.optinet.net [197.84.5.254] 
  9   104 ms   105 ms   121 ms  vp-02-14.bb.ctn.c27.za.net [196.28.178.70] 
 10   119 ms   118 ms   118 ms  gig5-2-cpt-opt-65-1.optinet.net [196.41.133.166]

Code: 
Tracing route to www.news24.com [41.86.110.200]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  10.1.0.254 
  2    <1 ms    <1 ms    <1 ms  10.100.0.1 
  3     *        *        *     Request timed out.
  4    97 ms    96 ms    92 ms  cpt-rx2.ip.adsl.co.za [169.1.5.82] 
  5    22 ms    18 ms    20 ms  cpt-net1.ip.adsl.co.za [169.1.5.128] 
  6    19 ms    19 ms    19 ms  optinet.ixp.capetown [196.10.140.15] 
  7   102 ms   100 ms   106 ms  te0-0-0-1.cpt-p-2.optinet.net [197.84.7.34] 
  8    79 ms    86 ms    83 ms  vl11.cpt-hscore-1.optinet.net [197.84.5.238] 
  9    89 ms   100 ms   104 ms  196.28.178.66 
 10    21 ms    20 ms    21 ms  gig5-1-cpt-opt-65-1.optinet.net [196.41.133.234] 
 11    99 ms    93 ms    88 ms  OPTI-CPT-N1-Hosting.optinet.net [197.84.196.6] 
 12    20 ms    20 ms    20 ms  197-84-208-146.cpt.mweb.co.za [197.84.208.146] 
 13    84 ms    85 ms    87 ms  41-86-110-200.mweb.co.za [41.86.110.200]
 
savage said:
No offense, but these traceroutes has been posted for months already now... And you've been sending it to your "network team" for just as long. Any idea on when we will hear what is actually wrong, or even better, when it will be resolved?

I can't remember when last I was able to use my AH account at night - it's pathetic, to say the least.
Click to expand...

I fully agree, and I'm on a Business account...my Cybersmart account is flying full speed. Common Afrihost...fix your network...
 
I will just leave it here


Tracing route to sipgate.de [217.10.79.9]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 * * * Request timed out.
3 25 ms 25 ms 24 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
4 108 ms 100 ms 97 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 103 ms 106 ms 108 ms 41.164.52.40
6 29 ms 27 ms 24 ms ix-ae-7-0.tcore2.KLT-Cape-Town.as6453.net [41.206.165.25]
7 174 ms 173 ms 172 ms if-ae-2-2.tcore1.KLT-Cape-Town.as6453.net [41.206.164.253]
8 178 ms 177 ms 179 ms if-ae-5-10.tcore2.PV9-Lisbon.as6453.net [80.231.159.93]
9 200 ms 188 ms 184 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
10 178 ms 183 ms 179 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
11 172 ms 173 ms 175 ms if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
12 * 180 ms 179 ms if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
13 180 ms 173 ms 173 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
14 173 ms 173 ms 175 ms 195.219.83.102
15 351 ms 357 ms 342 ms ae-2-70.edge4.Frankfurt1.Level3.net [4.69.154.72]
16 349 ms 356 ms 361 ms ae-2-70.edge4.Frankfurt1.Level3.net [4.69.154.72]
17 282 ms 280 ms 275 ms te2-2.c102.f.de.plusline.net [212.162.24.58]
18 281 ms 273 ms 285 ms 82.98.102.13
19 287 ms 284 ms 287 ms 82.98.98.250
20 281 ms 283 ms 283 ms 212.19.42.26
21 344 ms 337 ms 332 ms sipgate.de [217.10.79.9]

Trace complete.
 
Got the same as everyone else. Ping is bouncing all over:

Afrihost

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 20 ms 21 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
4 21 ms 23 ms 20 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 22 ms 21 ms 20 ms 41.164.52.40
6 56 ms 55 ms 61 ms ix-ae-7-0.tcore2.KLT-Cape-Town.as6453.net [41.206.165.25]
7 237 ms 244 ms 237 ms if-ae-2-2.tcore1.KLT-Cape-Town.as6453.net [41.206.164.253]
8 172 ms 169 ms 172 ms if-ae-5-90.tcore2.PV9-Lisbon.as6453.net [80.231.159.109]
9 176 ms 177 ms 176 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
10 216 ms 225 ms 228 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
11 175 ms 174 ms 174 ms if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
12 175 ms 175 ms 175 ms if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
13 174 ms 173 ms 172 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
14 237 ms 232 ms 241 ms 195.219.83.102
15 * * * Request timed out.
16 * * * Request timed out.
17 169 ms 170 ms 170 ms NIU-SOLUTIO.ear1.London15.Level3.net [212.187.173.210]
18 * * * Request timed out.
19 170 ms 170 ms 170 ms ae0.er02.telhc.bbc.co.uk [132.185.254.105]
20 171 ms 170 ms 170 ms 132.185.255.148
21 175 ms 176 ms 175 ms 212.58.244.22

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 21 ms 20 ms 20 ms ipc-2-up.south.dsl.telkomsa.net [105.226.0.22]
4 21 ms 21 ms 20 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
5 20 ms 20 ms 20 ms 196.25.190.209
6 163 ms 163 ms 163 ms 196.43.9.86
7 179 ms 179 ms 178 ms xe-0-1-0-19.r00.londen10.uk.bb.gin.ntt.net [83.231.146.245]
8 175 ms 175 ms 175 ms ae-6.r24.londen12.uk.bb.gin.ntt.net [129.250.4.20]
9 198 ms 182 ms 182 ms bbc-linx.pr01.thdow.bbc.co.uk [195.66.224.103]
10 * * * Request timed out.
11 * * * Request timed out.
12 182 ms 182 ms 182 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
13 177 ms 177 ms 176 ms 132.185.255.148
14 180 ms 179 ms 179 ms 212.58.244.22

No idea what sipgate is but here you go:

Afrihost

Tracing route to sipgate.de [217.10.79.9]
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 24 ms 20 ms 21 ms cpt-up2.ip.adsl.co.za [169.1.5.106]
4 23 ms 20 ms 25 ms cpt-net1.ip.adsl.co.za [169.1.5.128]
5 21 ms 20 ms 20 ms 41.164.52.40
6 67 ms 65 ms 67 ms ix-ae-7-0.tcore2.KLT-Cape-Town.as6453.net [41.206.165.25]
7 250 ms 276 ms 252 ms if-ae-2-2.tcore1.KLT-Cape-Town.as6453.net [41.206.164.253]
8 179 ms 182 ms 179 ms if-ae-5-2.tcore2.PV9-Lisbon.as6453.net [80.231.159.129]
9 177 ms 175 ms 175 ms if-ae-2-2.tcore1.PV9-Lisbon.as6453.net [80.231.158.5]
10 246 ms 245 ms 237 ms if-ae-1-3.tcore1.SV8-Highbridge.as6453.net [80.231.158.30]
11 175 ms 174 ms 178 ms if-ae-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.139.1]
12 175 ms * 175 ms if-ae-11-2.tcore1.L78-London.as6453.net [80.231.139.42]
13 173 ms 173 ms 173 ms if-ae-17-2.tcore1.LDN-London.as6453.net [80.231.130.130]
14 235 ms 245 ms 271 ms 195.219.83.102
15 276 ms 278 ms 276 ms ae-1-60.edge4.Frankfurt1.Level3.net [4.69.154.8]
16 276 ms 274 ms 275 ms ae-1-60.edge4.Frankfurt1.Level3.net [4.69.154.8]
17 353 ms 351 ms 349 ms te2-2.c102.f.de.plusline.net [212.162.24.58]
18 281 ms 277 ms 281 ms 82.98.102.13
19 313 ms 321 ms 325 ms 82.98.98.250
20 285 ms 286 ms 286 ms 212.19.42.26
21 284 ms 286 ms 286 ms sipgate.de [217.10.79.9]

Telkom

Tracing route to sipgate.de [217.10.79.9]
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 21 ms 20 ms 20 ms ipc-2-up.south.dsl.telkomsa.net [105.226.0.22]
4 22 ms 21 ms 20 ms ipc-aggr-2.south.dsl.telkomsa.net [105.226.0.57]
5 20 ms 20 ms 20 ms 165.165.214.213
6 179 ms 179 ms 179 ms 196.43.9.130
7 184 ms 184 ms 183 ms c13-1.netzquadrat.net [80.81.192.75]
8 185 ms 186 ms 184 ms sipgate.de [217.10.79.9]

*EDIT added Telkom results
 
Last edited:
Morning Everyone :)

Thanks to everyone who is posting results. While I understand the frustration of those users who are expressing irritation at posting test results, it's important to understand that this is the only route to getting the issue resolved. We report to the network team, they make adjustments or report to an upstream partner, and then we monitor to see how those changes take. Providing new information helps them assess if the changes have made things better/worse/same and they can react appropriately.

So to those posting the info, please be assured that your information is very useful and the contribution is greatly appreciated. From the MyBB rep team, we really appreciate it especially because this helps us move things along faster and have a constant flow of info to the network team.

Thanks so much, we are definitely going to continue to push for a better performance :)
 
Hi @AfriMan - can one still cancel an account today & not be billed for Dec'16 ?
I've seen old posts where the 23rd of the month was mentioned as the last day to cancel.

Presumably the roll-over data is lost ?

Thanks.
 
BayCityRoller said:
Hi @AfriMan - can one still cancel an account today & not be billed for Dec'16 ?
I've seen old posts where the 23rd of the month was mentioned as the last day to cancel.

Presumably the roll-over data is lost ?

Thanks.
Click to expand...

You might get your cancellation in today if the billing run hasn't started. We moved the date to the 23rd becuase some months we have to start billing earlier becuase of weekends, public holidays, etc.

When you cancel, your monthly data won't be allocated in the following month but any rollover data will remain active. So the cancellation will be set to pending to the end of the following month, when rollover data is no longer valid.
 
I have been watching the pings and latency for a few days since they fixed my line, and I have noticed for myself specifically as follows after random tests:

Diablo 3: Latency of 170~190 before 7:00pm / Latency of 250~320 after 7:00pm
World of Warcraft: Latency of 180/190 & 200/210 Home and World before 7:00pm / Latency of 230/350 & 300/380 Home and World after 7:00pm
The Division: (I wish I could find a latency option) Game is 100% before 7:00pm / Poor Connection to the Server message after 7:00pm
Battefield 1 (Yeah yeah...): Latency of 170 before 7:00pm / Latency of 300+ After 7:00pm

Tested Smyte, Titanfall 2 and a few others, same thing. Latency great before 7:00pm and absolutely horrid after 7:00pm. Wanted to use more colourful language but .....

Switched to my backup account with Vox and latency issues vanished. Switched back to Afrihost and rebooted the router and the issue was still there. Switched to Vox again and latency gone. It literally seems to be the breakout from Local to International. Local is hundreds with a 9 ping to BF4 on Afrihost and 11 on Vox. 30+ to Cape Town servers.
 
WickedMONK3Y said:
I have been watching the pings and latency for a few days since they fixed my line, and I have noticed for myself specifically as follows after random tests:

Diablo 3: Latency of 170~190 before 7:00pm / Latency of 250~320 after 7:00pm
World of Warcraft: Latency of 180/190 & 200/210 Home and World before 7:00pm / Latency of 230/350 & 300/380 Home and World after 7:00pm
The Division: (I wish I could find a latency option) Game is 100% before 7:00pm / Poor Connection to the Server message after 7:00pm
Battefield 1 (Yeah yeah...): Latency of 170 before 7:00pm / Latency of 300+ After 7:00pm

Tested Smyte, Titanfall 2 and a few others, same thing. Latency great before 7:00pm and absolutely horrid after 7:00pm. Wanted to use more colourful language but .....

Switched to my backup account with Vox and latency issues vanished. Switched back to Afrihost and rebooted the router and the issue was still there. Switched to Vox again and latency gone. It literally seems to be the breakout from Local to International. Local is hundreds with a 9 ping to BF4 on Afrihost and 11 on Vox. 30+ to Cape Town servers.
Click to expand...

The tests from other users here is showing same, so I think we're all on the same page. The difficulty is finding our exactly where this is occurring, which the network team are working on. All our health and capacity checks are coming back good, so we're going through everything with a fine tooth comb.
 
Status
Not open for further replies.
Back
Top
Sign up to the MyBroadband newsletter
X