• Sign Up
Back to All Topics
Neurons
ScubaEd | 02/02/2012 03:13 PM

Has anybody noticed how unreliable the Quirky site becomes at some times of the day?

Tow or three times a day the site would become completely unresponsive, or simply generates errors left and right. Most of the time with unpredictable outcomes.

Responses
Neurons
ScubaEd | 02/02/2012 | 03:22 PM

Report from Hostracker from a few minutes ago:
 
http://quirky.com
 
Location Result Page Size Response time KB/sec IP Partner
 
Received responses: 1 Ok 50 Fail Average: 2.04 sec 0.04
 
Orlando, FL, US Ok 88 2.04 sec 0.04 50.16.200.236 Apto Hosting
Gunzenhausen, Germany Http error:503 607 30.20 sec 50.16.200.236 AppVZ
Kiev, Ukraine Http error:503 607 29.50 sec 50.16.200.236 Global Digital Services
Kharkiv, Ukraine Http error:503 607 30.32 sec 50.16.200.236 ITL
Los Angeles, CA, US Http error:503 607 35.68 sec 50.16.200.236 PremiumReseller
Montreal, Quebec, Ca Http error:503 607 39.05 sec 50.16.200.236 XP-Hosting.com
Gunzenhausen, Germany Http error:503 607 30.22 sec 50.16.200.236 FastHost
London, UK Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.03 sec 50.16.200.236 VirtualSplits
Nuremberg, Germany Http error:503 607 33.21 sec 50.16.200.236 VPS-server.ru
Dallas, TX, US Http error:503 607 30.58 sec 50.16.200.236 Provisov.Net
Bangkok, Thailand Http error:503 607 30.57 sec 50.16.200.236 Chaiyo Hosting
Montreal, CA Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.02 sec 50.16.200.236 TUWEBHOST
Los Angeles, CA, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.51 sec 50.16.200.236 West Cost Hosting
Kwun Tong, Hong Kong Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.25 sec 50.16.200.236 Entinity Information Technology Solutions
Birmingham, UK Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.09 sec 50.16.200.236 Joomla Hosting
Falkenstein, Germany Http error:503 607 30.20 sec 50.16.200.236 WhoAPI
Moscow, Russia Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.13 sec 50.16.200.236 JustHost
Haarlem, Netherlands Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.09 sec 50.16.200.236 Steadyhost
Lansing, MI, US Http error:503 607 30.09 sec 50.16.200.236 Rioserver
Donetsk, Ukraine Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.14 sec 50.16.200.236 HostLife
Scranton, PA, US Http error:503 607 34.33 sec 50.16.200.236 Valkira
Gunzenhausen, Germany Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.10 sec 50.16.200.236 aBajt
Amsterdam, Netherlands Http error:503 607 30.20 sec 50.16.200.236 IntoHost
Fort Lee,NJ,US Http error:503 607 30.22 sec 50.16.200.236 ProGoldHost.net
Amsterdam, Netherlands Http error:503 607 30.18 sec 50.16.200.236 PDhost
New York, NY, US Http error:503 607 30.02 sec 50.16.200.236 HostGW.com Webhosting
Amsterdam, Netherlands Http error:503 607 33.21 sec 50.16.200.236 Hostmaster, Ltd.
Dallas, TX, US Http error:503 607 33.07 sec 50.16.200.236 Custom Hosting Solutions
Dallas, TX, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.04 sec 50.16.200.236 Arvixe, LLC
Kiev, Ukraine Http error:503 607 33.26 sec 50.16.200.236 HOSTED
Dallas, TX, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.04 sec 50.16.200.236 HostPojok.Com
WanChai, Hong Kong Http error:Http_client.No_reply 40.22 sec 50.16.200.236 Zolar Co Ltd
Kiev, Ukraine Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.14 sec 50.16.200.236 Hvosting
Toronto, ON, CA Http error:503 607 39.05 sec 50.16.200.236 OnyxNetUa
Frankfurt, Germany Http error:503 607 30.19 sec 50.16.200.236 AllServ.Net.UA
Kiev, Urkaine Http error:503 607 30.29 sec 50.16.200.236 HostService.ua
El Segundo, CA, US Http error:503 607 30.14 sec 50.16.200.236 JOGLO Hosting
East Lansing, MI, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.03 sec 50.16.200.236 NIMHOST
Zaporozhye, Ukraine Http error:503 607 33.27 sec 50.16.200.236 Alpha V
Moscow, Russia Http error:503 607 30.27 sec 50.16.200.236 NTCom LLC
Kiev, Ukraine Http error:503 607 30.26 sec 50.16.200.236 ABCname
Nurnberg, Germany Http error:503 607 30.20 sec 50.16.200.236 UpgradeHost.ru
London, UK Http error:503 607 30.19 sec 50.16.200.236 HostLinc
Hampshire, UK Http error:503 607 32.03 sec 50.16.200.236 PremiumReseller
Moscow, RU Http error:503 607 30.26 sec 50.16.200.236 HOSTLEX
Moscow, Russia Http error:503 607 30.25 sec 50.16.200.236 OpenHosting
Dallas, TX, US Http error:503 607 30.08 sec 50.16.200.236 Eskhosting
Kiev, Ukraine Http error:503 607 30.27 sec 50.16.200.236 ITQua
Montreal, Quebec, Ca Http error:503 607 30.05 sec 50.16.200.236 NordGate networks
Gdansk, Poland Http error:503 607 30.23 sec 50.16.200.236 HCX Hosting
Amsterdam, Netherlands Failure("Domain lookup failure:quirky.com Exception:Not_found") ServerClub

Edited At: 03:22 PM - 02/02/2012
Img_20120116_192234
MarcD | 02/02/2012 | 05:02 PM

For the past 10 minutes all I get for any idea I click on is a page saying:
Quirky
Aww crap.
We've encountered an error.

Abigail and avery xmas 2011 001
Jaynus | 02/02/2012 | 05:06 PM

@Marc same here. WTF I just submitted and I think voting is down. Great.

Edited At: 05:06 PM - 02/02/2012
Mail
Elizabeth Wingfield | 02/02/2012 | 06:45 PM

I am having problems with the infinite scroll getting stuck in a loop of products.
.
I guess this means Spam-o-Rama was a hack?
Scuba, will you (pretty please) translate the meaning of that gobbldeygook? It is your words I love, not your code :)

Edited At: 06:46 PM - 02/02/2012
Candle-light-bulb_325x325
wunderlicht | 02/03/2012 | 08:18 AM

they must have worked on the databases, yesterday night i noticed that all of my hidden ideas are now not hidden...grrrrr

Img_20120116_192234
MarcD | 02/03/2012 | 08:30 AM

All Recent Activity under 'My Account' after 11am yesterday is gone.

Neurons
ScubaEd | 02/03/2012 | 11:42 AM

@EW, Spam-o-Rama was not a hack. It was just a misguided poster going by hand on every single topic...
 
The problem, I believe, is bugs, over bugs, and patches over patches, on top high server loads (too many users?). I have taken some looks at the public code and it is a bit messy, their fixes seem to add to the mess. They seem to need a few more web programmers in the team.
 
The gobbledegook up there is just a test of Quirky.com from 51 locations around the world at that particular time (when I noticed the issues). Of those only 1 (Orlando) went through without errors.


Submit Your Response