SiteMeter Crashes Popular Sites in IE7

Just in the news that SiteMeter a popular analytics software has been crashing several popular blogs like Problogger, Consumerist, PerezHilton and thousands of other blogs using the Sitemeter as their analytics tool.

Check out the screen shots below which confirms the sites are breaking in IE7, we just wrote a article on how you could fix the issues without being aware of the sitemeter crashes just a hour ago.

Check out the screenshots below which confirm the sitemeter crashes.

ie7-pererhilton

Works in Firefox

firefox-perezhilton

consumerist-ie7

If you are using sitemeter as your analytics, please disable it till they fix this issue, or your visitors will not be able to navigate in Internet Explorer 7.

Thanks to the hat tip to our anonymous email tipper.

After Reading This Post Other People Went on to Read: »

Comment Using Facebook

4 Responses to this Article | Share your Opinions/Comments

We moderate comments to prevent spam. Moderation is done within few hours. Please try and stay on topic and refrain from using abusive language. If you think there is a problem with this post, please email the post author or send us an email at tips@techie-buzz.com with the URL and the problem you see and we will rectify it as soon as we can.

  1. Mark on August 2nd, 2008 at 7:36 am #

    The programmers at Site Meter must not realize that there are no weekends off when you provide a service to thousands, tens of thousands or more people around the world. Someone will have a lump in their throat once they know they have caused an issue effecting all of their java based users.

    Mark

  2. Hammad on August 2nd, 2008 at 12:15 pm #

    i experienced this as well
    my site was down and the traffic was less when i checked my analytics and so i removed sitemeter after reading about it…
    thanks

  3. Sandip on August 3rd, 2008 at 11:28 pm #

    i guess blogsdna was unaffected by this i haven’t seen any traffic drop (which might be coz my readers are mostly firefox one :P) and i am using old sitemeter script this might be due to newer sitemeter code.. need to check it.