Sound like a Chrome specific issue then.
Maybe look at clearing all your settings on Chrome?
Did the site previous redirect you to HTTPS?
Nope doesn't redirect me at all. Just goes straight to that error message.
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Sound like a Chrome specific issue then.
Maybe look at clearing all your settings on Chrome?
Did the site previous redirect you to HTTPS?
Nope doesn't redirect me at all. Just goes straight to that error message.
Hhhmm, OK.
Maybe look at removing the domain from Chrome's HSTS list? Worth a shot.
Not really sure why Chrome would be generating that error unless something is being cached.
Not sure if I'm alone, but it seems AfriGreen is now suffering due to the extra load from all the MTN account guys coming over.
Could barely make a Skype call just now. Had to switch over to a Telkom backup account.
How would I do that?
Not sure if I'm alone, but it seems AfriGreen is now suffering due to the extra load from all the MTN account guys coming over.
Could barely make a Skype call just now. Had to switch over to a Telkom backup account.
Actually I've also noticed Afrigreen account little slower right now. http download speeds fluctuating. Not as bad as yours though but am seeing slight dip.
Afrigreen is handling the demand very well.
Are there any tests that I can take a look at?
Nope for now I'm staying on Telkom. Need to get some work done.
Will evaluate later today.
Who's arm can we pull/twist/kiss to get onto the new network sooner?
Are you able to paste some tests here please?
IPC isn't breaking a sweat.
Last Result:
Download Speed: 7056 kbps (882 KB/sec transfer rate)
Upload Speed: 694 kbps (86.8 KB/sec transfer rate)
Latency: 76 ms
10/16/2015, 12:59:34 PM
Speed looks fine but latency is very high. That's on local server.
Here's a traceroute too
Tracing route to www.mightyupload.com [104.28.28.74]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 13 ms 8 ms 9 ms 169-1-5-6.ip.afrihost.co.za [169.1.5.6]
4 57 ms 8 ms 9 ms 169-1-5-52.ip.afrihost.co.za [169.1.5.52]
5 9 ms 8 ms 29 ms africainx.jb1.napafrica.net [196.46.25.135]
6 9 ms 8 ms 8 ms 41-66-181-59-3b.CLO008-CDN-local-VLAN-321.africa
inx.net [41.66.181.59]
7 9 ms 8 ms 8 ms 104.28.28.74
Trace complete.
Also removed standard bank site from hsts list and when trying to access it, still getting ERR_CONNECTION_RESET
Latency looks very low here. Where are you based?
As for the Chrome issue, you'll need to troubleshoot further on Chrome itself. Maybe look at uninstalling and re-installing.
Afrigreen is handling the demand very well.
Are there any tests that I can take a look at?
Tracing route to www.exa.co.za [197.221.2.20]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.1.0.254
2 5 ms 6 ms 6 ms 169-0-54-1.ip.afrihost.co.za [169.0.54.1]
3 29 ms 27 ms 30 ms 169-1-5-5.ip.afrihost.co.za [169.1.5.5]
4 113 ms 98 ms 152 ms 169-1-5-18.ip.afrihost.co.za [169.1.5.18]
5 806 ms 702 ms 478 ms 169-1-5-52.ip.afrihost.co.za [169.1.5.52]
6 29 ms 28 ms 28 ms africainx.jb1.napafrica.net [196.46.25.135]
7 25 ms 25 ms 30 ms CORE.WC-RO-HET-MEE-1.TO.WC-RO-MEC-2.AINX.P2P.10G.za [41.84.13.37]
8 26 ms 24 ms 26 ms 41-66-133-2-3.HET001-CPE-1.africainx.net [41.66.133.2]
9 27 ms 25 ms 26 ms 41.204.206.38
10 97 ms 83 ms 25 ms www20.cpt1.host-h.net [197.221.2.20]
Trace complete.
Maybe see what is going on with this European gaming site please ..... is it them, or is it Afrigreen?
http://i59.tinypic.com/2efpytk.jpg
I already have AfriGreen details. I want details for the new super duper network. One of you guys mentioned that a few users have been moved over to it.
Just for you I switched back to AfriGreen to test. I have the same erratic latency issue. This is what causes my Skype calls to be useless on AfriGreen
Code:Tracing route to www.exa.co.za [197.221.2.20] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms 10.1.0.254 2 5 ms 6 ms 6 ms 169-0-54-1.ip.afrihost.co.za [169.0.54.1] 3 29 ms 27 ms 30 ms 169-1-5-5.ip.afrihost.co.za [169.1.5.5] 4 113 ms 98 ms 152 ms 169-1-5-18.ip.afrihost.co.za [169.1.5.18] 5 806 ms 702 ms 478 ms 169-1-5-52.ip.afrihost.co.za [169.1.5.52] 6 29 ms 28 ms 28 ms africainx.jb1.napafrica.net [196.46.25.135] 7 25 ms 25 ms 30 ms CORE.WC-RO-HET-MEE-1.TO.WC-RO-MEC-2.AINX.P2P.10G.za [41.84.13.37] 8 26 ms 24 ms 26 ms 41-66-133-2-3.HET001-CPE-1.africainx.net [41.66.133.2] 9 27 ms 25 ms 26 ms 41.204.206.38 10 97 ms 83 ms 25 ms www20.cpt1.host-h.net [197.221.2.20] Trace complete.
Hhhmm, that's a bit weird.
What happens when you ping 169.1.5.52?
Pinging 169.1.5.52 with 32 bytes of data:
Reply from 169.1.5.52: bytes=32 time=29ms TTL=60
Reply from 169.1.5.52: bytes=32 time=28ms TTL=60
Reply from 169.1.5.52: bytes=32 time=31ms TTL=60
Reply from 169.1.5.52: bytes=32 time=28ms TTL=60
Tracing route to www.exa.co.za [197.221.2.20]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 10.1.0.254
2 6 ms 6 ms 6 ms 169-0-54-1.ip.afrihost.co.za [169.0.54.1]
3 28 ms 27 ms 27 ms 169-1-5-5.ip.afrihost.co.za [169.1.5.5]
4 31 ms 27 ms 27 ms 169-1-5-18.ip.afrihost.co.za [169.1.5.18]
5 29 ms 29 ms 72 ms 169-1-5-52.ip.afrihost.co.za [169.1.5.52]
6 29 ms 39 ms 42 ms africainx.jb1.napafrica.net [196.46.25.135]
7 25 ms 83 ms 80 ms CORE.WC-RO-HET-MEE-1.TO.WC-RO-MEC-2.AINX.P2P.10G.za [41.84.13.37]
8 50 ms 25 ms 25 ms 41-66-133-2-3.HET001-CPE-1.africainx.net [41.66.133.2]
9 81 ms 116 ms 161 ms 41.204.206.38
10 35 ms 32 ms 24 ms www20.cpt1.host-h.net [197.221.2.20]
Trace complete.