General Boards > OzIsuzu Forum Bulletin Board
Connection issues with the www.ozisuzu.com.au web server
Richard Puller:
In my case it's improved from aroun 15% success rate up until yesterday to 100% success rate today.
I read that streaming outlets like netflix etc have increased their compression to save bandwidth. That may have an overall effect on the internet generally. Dunno
DannyG:
Thanks for the info and generous offers of financial help (we have had a few offers privately) however it is not about the cost.
Sure I dont want to be outlaying massive amounts of money for a dedicated Australian server if it is not nescasary, so in that way it is about money but I am prepared to cross that bridge when we come to it.
I do understand that there will come a day when we have outgrown our shared server capacity but I am not convinced this is the case with the issue we are having at the moment. Our server stats suggest we are well within our all our capacities.
I have spent a fair amount of time researching the current situation in regards to the world being home and using massive amounts of bandwidth, and connection issues and/or slow downs are very common at the moment, world wide......or at least in countries with poor internet ;)
So I think the best approach at this stage is to ride it out for a while. I am hoping those that are effected are not effected to the point where it is so unbearable they leave us.
I genuinely do apologise for the inconvenience. I will keep pestering godaddy in the back ground and see if they are able to monitor things at their end and ultimately help us out, but I am not holding out a lot of hope.
xcvator:
When I 1st contacted you about this problem ( via myswag) I had been having slowdowns and time outs for about 3 weeks so it's not just a recent thing and was so bad I couldn't even contact you at all
mewgaf:
When I'm out of hospital and not sleeping 23 hrs a day. I'll have a good look into it.
Everybody will have a different trace route to the web server.
If there are routing problems inside godaddy we can raise this and get them to check.
If there are routing problems with an isp we could get godaddy to raise it with the carrier as it will effect all traffic on that trunk.
When I looked at it it was something totally different.
When I feel up to it I'll do some research.
Sorry that's the best I can offer at the moment.
If you wish to reach out and contact me, you are most welcome.
Mark
yvesjv:
Danny and everyone else,
You've done it! :cup:
No timeouts for me this morning, someone must have looked at their routing from the info Danny provided and the 'ahem' gentle noises made over the phone to their support.
Checked with traceroute and the output is now filtered once the hop reaches Singapour... :BangHead:
5 be3.core1.sg1-equinix.sin.aussiebb.net (180.150.2.85) 111.592 ms 111.602 ms 112.042 ms
6 26496.sgw.equinix.com (27.111.228.105) 112.653 ms 110.873 ms 110.861 ms
7 148.72.204.1 (148.72.204.1) 111.062 ms 111.237 ms 110.532 ms
8 * * *
9 * * *
-----snip----
But checking with 'mtr' shows the changes and 0% packet loss all the way!! :toothy9:
Checking tcp:
6.|-- 26496.sgw.equinix.com 0.0% 100 110.7 115.1 109.8 210.1 15.6
7.|-- 148.72.204.1 0.0% 100 110.5 110.7 110.2 112.0 0.3
8.|-- 10.242.0.41 0.0% 100 110.2 110.4 109.9 111.2 0.3
9.|-- 10.242.0.145 0.0% 100 110.3 111.0 110.2 120.0 1.0
10.|-- ip-166-62-6-79.ip.secureserver.net 0.0% 100 111.0 110.8 110.1 111.5 0.3
Checking icmp:
6.|-- 26496.sgw.equinix.com 0.0% 100 110.1 116.0 109.9 181.4 15.4
7.|-- 148.72.204.1 0.0% 100 111.2 110.7 110.2 112.6 0.4
8.|-- 10.242.0.41 0.0% 100 110.9 110.5 110.0 111.1 0.3
9.|-- 10.242.0.147 0.0% 100 111.2 111.0 110.3 117.4 0.8
10.|-- ip-166-62-6-79.ip.secureserver.net 0.0% 100 110.8 110.7 110.0 112.1 0.4
The IPs highlited in bold are from the RFC1918 ranges, usually internally used and not to be leaked on the public www. :sad10:
But hey... timeouts are gone this morning. :headbang:
Let's keep an eye on it for a short while.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version