Following the logic, I found the problem. Just a Hosts entry from something I was testing last month & forgot to remove.![]()
Glad you got that sorted out, can be very frustrating!
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
Following the logic, I found the problem. Just a Hosts entry from something I was testing last month & forgot to remove.![]()
It was fine for the first two days i was with AH. Been like this since IPC went down the other day.
The worst part is the replies from AH staff - these are quotes from emails I got last time I corresponded with AH Support.
Complaining about Origin updating at 10kbps over a weekend: "...that's pretty much the speed you get on..."
The other gem is: "Please be advised that the leader's score board is not linked to the shaping policy in any way
and is just and used to show the highest bandwidth users in relation to their line
speeds, The shaping policy depends on the congestion on the network and not how much
bandwidth a user has moved."
That one is in direct contradiction of the AUP, which states "For our high bandwidth users users, non-Realtime Internet traffic (such as torrents) will be dynamically shaped during peak network usage ... with higher bandwidth users getting shaped more than lower bandwidth users, and the higher bandwidth users will not get full speeds during these times"
What gives?
I am not sure where you are in the country, but just maybe you route also via the east coast, and maybe that route has some pressure as it is only restoration and not the normal routes,
Maybe things will get better when the cable breaks are repaired and traffic is routing via normal routes again.
Yes I was actually quoting to your other post, about how some can move so much data and you guys getting shaped.?? Did you maybe quote the wrong post?Not seeing how that's linked to what I posted.
Anyway, those emails are from before the cables broke.
Well all the traffic was re-routed via WACS fallback when cables where broken, but since EASSY has temp restoration routes in place since 30/03/2013 you guys are routing via the Durban IPC out on the east coast again.
Yes I was actually quoting to your other post, about how some can move so much data and you guys getting shaped.
So Thought it might be due to the restoration routes running that you guys are more aggressively shaped now.
Maybe when the cables are back up you guys will get less aggressively shaped.
Just an assumption.
Hi Afriman
Is there a reason that I'm getting routed differently to the other users?
The worst part is the replies from AH staff - these are quotes from emails I got last time I corresponded with AH Support.
Complaining about Origin updating at 10kbps over a weekend: "...that's pretty much the speed you get on..."
The other gem is: "Please be advised that the leader's score board is not linked to the shaping policy in any way
and is just and used to show the highest bandwidth users in relation to their line
speeds, The shaping policy depends on the congestion on the network and not how much
bandwidth a user has moved."
That one is in direct contradiction of the AUP, which states "For our high bandwidth users users, non-Realtime Internet traffic (such as torrents) will be dynamically shaped during peak network usage ... with higher bandwidth users getting shaped more than lower bandwidth users, and the higher bandwidth users will not get full speeds during these times"
What gives?
Remember that from each IPC routing, especially overseas, will be slightly different depending on which network nodes are closest to you - i.e. the shortest path to the destination. Cape Town users will route directly over WACS, for example, to the UK, while Durban users will go over EASSy and Joburg users are essentially sent over the fastest link. Best to compare with a Joburg user for a accurate comparison.
I understand how routing works but 300ms interational latency is terrible and its really not what I want. Had under 200ms before we got put back on EASSy. Will this improve anytime soon?
I understand how routing works but 300ms interational latency is terrible and its really not what I want. Had under 200ms before we got put back on EASSy. Will this improve anytime soon?
The routing on EASSy is using a temporary restoral path, so there could well be some latency introduced. Once the cable is fully repaired, everything should be back to normal. We're diverting as little traffic as possible over EASSy until we know all is well again, though we don't have an ETR.
So we deliberately getting put on a substandard cable? That's not very reassuring considering new customers are affected and arnt sure they made the right choice.
So we deliberately getting put on a substandard cable? That's not very reassuring considering new customers are affected and arnt sure they made the right choice.