Hi,
Have anyone else been having problems with 504 Gateway Timeout Errors using Telkom as an ISP?
We have a site hosted in the US and we have received multiple queries from clients that can not access some pages after logging in because of the 504 Gateway timeout errors. After some investigating I realized that the only common denominator is that all these clients are using Telkom as their ISP. We got no complaints from any clients using Afrihost, Axxess or WebAfrica (These are also the ISPs that I have tested - other than Telkom)
So I went and did some more investigating. We contacted the hosting company and were told that they can not see a problem from their side.
Now doing a traceroute, there are some Telkom connections timing out.
Here is the first part of the traceroute (without giving away too much sensitive information)
Using the mtr tool without DNS, 196.43.33.134 returns a packet loss of 90% on average.
Also this error is not persistent. Sometimes the page loads and the other times the 504 error. Now I am wondering if one of the Telkom routers has a to sensitive threshold before dropping packets.
Anyone else experiencing 504 errors?
Suggestions on solving this problem? I don't really know where to start with solving this or who to contact.
Regards
Have anyone else been having problems with 504 Gateway Timeout Errors using Telkom as an ISP?
We have a site hosted in the US and we have received multiple queries from clients that can not access some pages after logging in because of the 504 Gateway timeout errors. After some investigating I realized that the only common denominator is that all these clients are using Telkom as their ISP. We got no complaints from any clients using Afrihost, Axxess or WebAfrica (These are also the ISPs that I have tested - other than Telkom)
So I went and did some more investigating. We contacted the hosting company and were told that they can not see a problem from their side.
Now doing a traceroute, there are some Telkom connections timing out.
Here is the first part of the traceroute (without giving away too much sensitive information)
Code:
1 10.0.1.2 (10.0.1.2) 3.717 ms 3.808 ms 3.958 ms
2 dsl-243-68-01.telkomadsl.co.za (41.243.68.1) 29.894 ms 29.957 ms 30.034 ms
3 * * wfor-ip-cat-1-vlan-913.telkom-ipnet.co.za (196.43.33.134) 31.241 ms
4 * * *
5 196.43.10.130 (196.43.10.130) 57.719 ms 57.779 ms 57.851 ms
6 196.43.33.5 (196.43.33.5) 58.641 ms 41.268 ms 37.744 ms
7 ams-ip-dir-globalc-pos-4-0-1.telkom-ipnet.co.za (196.43.18.38) 231.569 ms 232.643 ms 234.316 ms
8 so-0-2-0.ar2.AMS2.gblx.net (64.210.21.45) 265.094 ms 267.378 ms 268.614 ms
....Using the mtr tool without DNS, 196.43.33.134 returns a packet loss of 90% on average.
Also this error is not persistent. Sometimes the page loads and the other times the 504 error. Now I am wondering if one of the Telkom routers has a to sensitive threshold before dropping packets.
Anyone else experiencing 504 errors?
Suggestions on solving this problem? I don't really know where to start with solving this or who to contact.
Regards
