The honor once again fell to Russian search index Yandex (Я́ндекс), whose bot scored the mega. Closest on either side were...really? Wow, Feely both times (-2,+11)
Recent millions (and how long it took to get there) 68M 22 Apr 2011 09:48:31 (43:06:31:32) 67M 10 Mar 2011 02:16:59 (38:02:40:30) 66M 30 Jan 2011 23:36:29 (40:10:12:28) 65M 21 Dec 2010 13:24:01 (40:21:54:19) 64M 10 Nov 2010 15:29:42 (43:15:20:56) 63M 28 Sep 2010 01:08:46 (48:09:34:15) 62M 10 Aug 2010 15:34:31 (46:22:39:41) 61M 24 Jun 2010 16:54:50 (47:01:26:19) 60M 08 May 2010 15:28:31 (49:04:35:32) 59M 20 Mar 2010 10:52:59 (47:11:02:10) 58M 31 Jan 2010 22:50:49 (48:06:33:39)
Our current Quantcast rating as I type this: 151,246
I just went back looking at some of the old Mega Click Threads and it's kind of funny how 10 million was a pretty big deal. The winner even got a custom title, but I don't know what it was because he's now inactive. Then 20 million came and went and CRZ didn't even acknowledge it, 25 million brought a little discussion, 30 and 40 were uneventful. Fifty million should have been a bigger deal and that seemed to have just passed us all by.
It just now took me longer than it should have to find the counter on the main page. I'm also not sure where I was going with this. Can you tell this is very idle time and I'm just waiting around and that I also have no way to wrap this up?
It seems to me that there has been a noticeable uptick in traffic given that from 58 to 63 m it was 46 to 49 days per, and since then it has been at least 5 days quicker per million. Do you have any statistics on say, overall source of activity? i.e. registered users vs. non-registered users who followed a static link (from crz.net or slashwrestling.com or just came to the main page) vs. search engine hits vs. all other link referrals (twitter, facebook, links appearing wherever else)? Was just kind of curious which section of traffic is responsible for the extra hits.
I get the same thing. Switched back/forth between full graphics & dial-up, and refreshed, it it still does the same thing. I'm using Firefox 1.0.7 at work. I noticed this at home, where I use a newer version of Firefox.