I haven't been able to get Fotolia's page today. Does anybody else has this problem?

Denis

Thank you, I appreciate your response. Strange for me, I can get everywhere else except Fotolia. Oh well at least I'm glad the site is still selling images.  I guess I have a few things to figure out. Denis

The US one.

No problem for me in US.

It happened to me couple of months ago.  Someone here (sorry I don't remember who  ) told me to delete my cookies and my temporary internet files.  It worked!

Claude

I finally called my internet provider and after being guided through a few technical steps, the tech thought that Fotolia was blocking me for some reason because everybody else but me could get through.

So I called Fotolia directly and a friendly tech told me that my account was still active and that no action had been initiated to block my IP address. Furthermore, the Fotolia tech guided me to do a "Trace" from my computer to their website so that I could prove to my internet provider that it was their responsability to figure this problem.

I called my provider, "Rogers Cable" (in Ottawa, Canada) and after reporting the above mention, they were willing to further investigate this problem. If anyone of you are technically knowledgable about this kind of problem, below I have inserted the route traced from my computer to Fotolia.com.  Somehow it is blocking somewhere one third of the way?? My provider said they will get back to me within 48hrs.

Tracing route to fotolia.com [89.202.137.26]
over a maximum of 30 hops:

  1     9 ms    14 ms     9 ms  10.43.96.1
  2     7 ms     9 ms     8 ms  gw03.slnt.phub.net.cable.rogers.com [66.185.90.1
45]
  3    10 ms     9 ms     8 ms  gw01.slnt.phub.net.cable.rogers.com [66.185.93.1
97]
  4    14 ms    12 ms    13 ms  so-4-1-0.gw02.ym.phub.net.cable.rogers.com [66.1
85.83.198]
  5    57 ms    55 ms    55 ms  pos-3-0.igw01.chfdrl.phub.net.cable.rogers.com [
66.185.81.1]
  6    62 ms    54 ms    55 ms  if-5-0.core2.CT8-Chicago.teleglobe.net [66.110.1
4.5]
  7    75 ms    76 ms    75 ms  if-2-0-0-719.core4.AEQ-Ashburn.teleglobe.net [21
6.6.42.49]
  8    76 ms    76 ms    77 ms  ix-6-0-2.core4.AEQ-Ashburn.teleglobe.net [216.6.
42.14]
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 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.

Basically it appears one or more of the servers that usually serves the route to FT for you is down.
There is nothing FT or your ISP can do about it if this is in fact the case.

Cranky MIZ
The voice of reason

Thanks, you're probably right. I guess it is just a matter of time. Denis

It seem offline to me this morning