Slow Loading Site Seals and Comodo Page Timeouts

[Guest]

[surfnmtns]

Hello,

I'm having mutiple issues, outlined below, with the Comodo SSL certs and site seals. These are not one-time events but have been happening consistently for 2-3 weeks. Any ides on how to fix these issues or what is going on? Is anyone else having these issues lately?

I would like to continue using the trust logos but if they impact my web sites this will not do. If I cannot use Comodo's site seal and technology for the SSL without impacting my clients sites, I guess I'll have to buy and recommend other SSLs from now on.

1. Web sites using Comodo certificates have been intermittently responding slowly and the status bar is showing secure.comodo.com trying to load. Removing the javascript for the site seals fixes this issue.

2. When I click on the SSL to show the pop up page with details of the certificate I get and error saying the "Connection has times out. The server at secure.comodo.com is taking too long to respond."

3. When I tracert instantssl.com, shown below, which is the address in the pop up window, the response times are either high or timeout.

4. I am getting Javascript erros in IE 7. First error - Line: 85, Char: 1, Error: Object Expected. Second Error - Line: 668, Char: 1, Error: Object Excpected.


Tracing route to instantssl.com [91.199.212.132]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2     8 ms    10 ms     6 ms  xxx.xxx.xxx.xxx
  3     7 ms     8 ms     6 ms  xxx.xxx-xxx.xxx.xxx.com [xxx.xxx.xxx.xxx]

  4    11 ms    11 ms    13 ms  xxx.xxx-xxx.xxx.xxx.com [xxx.xxx.xxx.xxx]
  5    15 ms    13 ms    11 ms  xxx.xxx-xxx.xxx.xxx.xxx [xxx.xxx.xxx.xxx]
  6    15 ms    16 ms    18 ms  te-1-4.car1.Tustin1.Level3.net [4.79.140.1]
  7    14 ms    13 ms    22 ms  ae-2-3.bar1.Tustin1.Level3.net [4.69.132.218]
  8    11 ms    13 ms    15 ms  ae-0-11.bar2.Tustin1.Level3.net [4.69.136.198]
  9    53 ms    53 ms    53 ms  ae-10-10.ebr1.Dallas1.Level3.net [4.69.136.206]

 10    49 ms    53 ms    53 ms  ae-91-91.csw4.Dallas1.Level3.net [4.69.136.134]

 11    46 ms    51 ms    54 ms  ae-92-92.ebr2.Dallas1.Level3.net [4.69.136.149]

 12    90 ms    85 ms    90 ms  ae-6.ebr3.NewYork1.Level3.net [4.69.137.122]
 13   100 ms    89 ms    90 ms  ae-93-93.csw4.NewYork1.Level3.net [4.69.134.110]

 14    90 ms    89 ms    90 ms  ae-91-91.ebr1.NewYork1.Level3.net [4.69.134.77]

 15   164 ms   159 ms   161 ms  ae-44.ebr2.London1.Level3.net [4.69.137.77]
 16   159 ms   155 ms   155 ms  ae-25-52.car5.London1.Level3.net [4.68.116.51]
 17   151 ms   149 ms   153 ms  217.163.44.206
 18   150 ms   148 ms   150 ms  ge-3-0-0-0.raphael.as34270.net [85.91.232.2]
 19   156 ms   158 ms   159 ms  ge-0-2-0-0.rembrandt.as34270.net [85.91.232.6]
 20   180 ms   179 ms   179 ms  ge-0-0-0-315.davinci.as34270.net [85.91.224.26]

 21   184 ms   179 ms   189 ms  no-dns-yet.inetc.co.uk [85.91.232.14]
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

[robinalden]

surfnmtns,
 I'm sorry that you are having problem reaching the Comodo sites and seals.
Some other people are having the same problem as you but, and I realize this is no comfort to you, the number of people with this problem is small.
We believe the problem you are seeing will either be because of inconsistent DNS results, or possibly out of date information from a transparent proxy provided by your ISP.
If you are able to give us more information about the site you see the problem on and the exact nature of the problem I will look further into this for you.

In answer to your particular points..
1) We have had a public monitor on the JavaScript file you mention for the last few days and it shows as being 100% available from a number of geographically separated locations.
https://secure1.securityspace.com/netmon/report.html?graphID=28112

2) Can you tell me what IP address you see secure.comodo.com resolving to?

3) Our routers will not let you traceroute into our internal network.  You may see long times or intermittent responses from Rembrandt or DaVinci, but these are as a result of rate limiting on ICMP traffic (as used by tracert) and do not reflect TCP/IP routing delays.

4) I guess these are because of the error you report at #1 - i.e. you can't pull the .js file.

Regards
Robin

[surfnmtns]

Hey Robin,

Thanks for the reply. Yeah it is a bit of a concern when it slows the web site to a crawl or will not load at all. This is a general concern when using remote JS scripts. This does seem to be a an intermittent issue but some days or weeks recently it has happened far to often. I'm not really wanting to post the site in question here as it is my clients site but I might be willing to PM it to you.

2) Can you tell me what IP address you see secure.comodo.com resolving to?

Sure, this is the IP from a local ping: 91.199.212.151

Any further insight is much appreciated. Thanks!

[Tags:]