Outage – Explosion at The Planet

Dear Members,

Introduction
We would like to offer you our sincere apologies for the interruption in service many of you experienced last weekend. During the outage our forum remained online and we attempted to keep all of our members up-to-date via our Service Status announcements.

What happened?
On Saturday 31 May at approximately 11pm GMT there was an explosion in The Planet Data Center in Houston Texas. Electrical gear shorted, creating an explosion and fire that knocked down three walls. Thankfully there were no human casualties.

On the instructions of the Fire Department, The Planet then turned off all power to the Data Center resulting in 9,000 servers being knocked offline.

How did the outage at The Planet affect StatCounter?
This affected StatCounter in a number of ways:

  • Some of our database servers went down
  • Our dns servers were temporarily offline
  • Some of our incoming mail servers went down
  • Our blog was unavailable
  • Some of our web servers went down
  • Some of our partitions were knocked offline

How did this mean for StatCounter members?
Different members were affected in different ways.

Members with projects on the following partitions were most seriously affected:
c1 (PN 0), c7 (PN 6) , c8 (PN 7), c14 (PN 13), c16 (PN 15), c17 (PN 16)
These members lost between 24 and 30 hours of stats over Sunday GMT and part of Monday morning.

Members with projects on the following partitions were unable to log into their accounts for a number of hours following the outage but stats continued to be recorded:
c4 (PN 3), c5 (PN 4), c6 (PN 5), c12 (PN 11)

New members and people who had just created new projects with StatCounter in the hours immediately prior to the outage temporarily “lost” their accounts/projects. This is because, since these projects were not on our last back-up, restoring the back-up did not “bring up” their projects. In this case, our advice is to generate a new project and re-install the StatCounter code on your site.

All other members lost about 3-5 hours of stats from approximately 11pm GMT on Saturday night. In addition members experienced difficulties reaching the StatCounter site and logging into their accounts.

As servers at The Planet come back online we continue to work to try to recover as many stats as possible to minimise the loss of information experienced.

Why doesn’t StatCounter have its own Data Center?
By outsourcing our server technology, we can keep costs down, minimize downtime and devote more resources to our members.

Why was StatCounter using The Planet?
StatCounter is powered by over 130 servers. These are located in a number of Data Centers in the United States and in Ireland and are spread among a number of hosting providers although our main hosting partner is The Planet.

We chose The Planet as our main hosting partner as they are the largest dedicated hosting service in the world and due to the apparent reliability of the service they provide.

We believed The Planet to be one of the most reliable and redundant data center providers in the world, particularly as they host servers in multiple centers in Houston and Dallas.

From The Planet website:
With multiple state-of-the art data centers located in Dallas and Houston, Texas, The Planet provides On Demand IT Infrastructure backed by complete redundancy in power, HVAC, fire suppression, network connectivity, and security. So if any of our data centers experiences a disruption for any reason, your eggs (or servers) are never in one basket.

The Planet have let us down, and in turn, we have let you down. For this we are truly sorry.

What did The Planet do wrong?
Accidents are a fact of life, however, we believe that, had The Planet operated in the professional manner we expected from an organisation of its standing, the disruption experienced could have been substantially lessened.

For example, The Planet have hosted our DNS for a number of years, however, it was only this weekend we discovered that, although our DNS servers are on different subnets within The Planet, the servers are actually all in the same location. We will be submitting a complaint to The Planet in this regard. We fully expected that The Planet would have implemented a geographical spread in our DNS servers – this was not something that we thought we would have to request or confirm – particularly since we have servers spread through all The Planet data centers. We have now secured the services of a new geographically spread, redundant DNS provider.

We also feel that the extent of the damage could have been acknowledged and communicated by The Planet in a more timely fashion. While we decided to implement our back-up plans early on, others waited many hours in the hope that The Planet would come back online, only to find that restoration of service was continually delayed.

In addition, we found that our efforts to communicate with The Planet were largely ignored or dismissed with a “template” response. This was particularly galling as we received a presentation glass globe (see below) and a letter from The Planet CEO on FRIDAY thanking us for being one of their largest customers… then Saturday… THIS!

Thank you For making a world of Difference – The Planet ???

Why couldn’t The Planet get the Data Center back more quickly?
We don’t know. Hundreds of angry customers have been asking this question.

What action did StatCounter take when this accident happened?
We immediately began work to restore full service as soon as possible.

  • Initially, and in the absence of any official information from The Planet, we worked to establish exactly what was causing the problems.
  • We started a thread in our Service Status forum to advise our members of the situation – this thread has been updated continuously.
  • We added a notice to out homepage to advise members that service was limited.
  • We procured the services of a properly redundant and geographically spread dns service and re-routed all our servers immediately.
  • We prioritised the restoration of all our affected partitions from our latest back-up taken in the hours before the outage in order to resume tracking stats.
  • We configured new servers.
  • We redirected web servers which were temporarily down due to the outage.
  • We responded to as many tickets as possible to try to explain the situation to our members.
  • We migrated our affected mail servers to a new data center.

How will StatCounter prevent this happening in the future?
The bitter irony of this recent episode is that we have been working on our new beta system since September last year. We decided to develop this new StatCounter system for a number of reasons, one of the major motivations being to improve the architecture of our system so as to insulate it against major outages such as the one just experienced. Considering that we have never before experienced an outage of this magnitude, we are bitterly disappointed that our new system was not up and running before this episode.

Once “normal” service is restored, work will continue on the beta project as planned. The sooner we launch the beta, the sooner we can minimise our vulnerability to this kind of outage.

I’m not happy – how do I complain?
We completely understand why you feel aggrieved. Should you wish to submit a complaint to us please do so by logging into your StatCounter account and clicking the “support” link in the top menu bar. Within this area you will be able to submit a ticket to us – we will endeavour to respond to you as soon as possible.

How do StatCounter feel about what happened?
We are so desperately sorry that any of our customers had to experience this outage. We also feel so humbled by the numerous messages of support that we have received. At a time when we feel so terribly for the interruption in service suffered by some of our members, we have been just bowled over to receive so many of messages of encouragement. While we always knew that we had a great bunch of members, your support and patience throughout this episode has been nothing short of incredible and served to help maintain team morale in a very difficult situation. We are so grateful.

Conclusion
We hope this blog post has gone some way towards summarising the main issues relating to the recent outage. Work continues to restore full service. If you have any comments or queries, please do post them below.

219 Comments

  1. Thanks for the explanation. Statcounter clearly acted comeptetly and professionally throughout (with the sole exception of assuming, rather than verifying, that your DNS hosting was geographically spread).

    I hope this will not make you feel that your should move your new system out of beta any quicker – day to day reliability is much more important than the risk of an outage like this.

  2. This couldnot really have happened at a more awkward moment for us, adding a small project which went live on Friday, a project we hope will lead to a bigger partnership. The project relies heavily on stats to show our potential client the value of our services.

    All that said because we were able to keep the client informed, due to the efforts of your team.we got over the glitch. I have to say that we are happy to read that statcounter are already working on a new contigency plan so hopefully outages of this scale cannot happen again.

    These things happen,and are to an extent expected, that they happen is not the main problem, it is how the problem is addressed and communicated to allow your clients to work around that makes the difference.In this regard Statcounter excelled !!

  3. A world of difference ….

    Every other bulletin from Planet bleated on about them “working through the night”. I know you guys worked through the night also, but how many times do you mention it in your announcements? None.

    You did a fantastic job …. now go get some sleep. 😉

  4. Don’t worry about that.

    We personally don’t our stats on Sunday anyway.

    Keep up the good work !!

  5. Hey,

    Don’t sweat it guys. Doing all you can do is the best service anyone can every give.

    Thanks for the excellent work.

  6. I now understand why it took a long time for statcounter to be back. Things happen, so, I am fine with that. I appreciate your efforts to get the service back at your best timely manner.

    Throughout the years I have been using statcounter, it is the best I have found. So, despite this outage, I will keep using it.

  7. Thanks for the clear and transparent explanation.

    NASA has reported that it is safe from crazy Rasberry ants, but perhaps The Planet is not. Houston, we have a problem…

  8. Accidents happen. Also, it’s not your fault. You are doing a great service to us all. Keep up your good work. God bless you all.

  9. No worries…

    It’s not your fault to begin with so no reason to feel so badly about it all.

    Thanks for the great service.

  10. Great detailed explanation, thank you. Unfortunately my stats were briefly up today (Monday) but are now gone again and have been reset to zero. No big deal, just curious why they were there for a few hours and now they’re gone again?
    Anyone else on partition 13 see their stats now? (it’s Monday 11:07 PST).

    StatCounter Team Reponse:
    Hi Kansas,

    Your stats for Monday should definitely be visible in your account. If you are continuing to have trouble please submit a support ticket to us by logging into your account and clicking the “support” link in the top menu bar. We will then be able to look into your account directly.

    Thanks for your patience.

  11. Thanks for all you do on our behalf. Everything’s cool. No harm done. Good luck and hope it works out for you without too many problems to solve.

  12. Boy, when you guys say an explosion, you mean it! I’m amazed you go everything back up so fast.

  13. Statcounter is so far the best for me. I’ve been using your service for a long time, and i feel really satisfied with your service. Accidents like this could happen but it will not affect the excellent service that you give me.

    You guys give us a wonderful and excellent service. Keep on going statcounter. 🙂

  14. Hi there.
    Thanx a lot for updating us, i actually found more about this outage from statscounter than i did from theplanet website updates.
    It seems many companies use this dedicated hosting provider because i noticed that scriptlance.com also was offline for the same reason.

    As it seems “big” hosting providers are not giving back as much as they should.

  15. I was horrified to read of the explosion and relieved to find that no one was injured. My best wishes are with the company and all its employees to recover from this incident.

  16. You guys have a great service. The interuption was quite minor for me. And compared to the product you deliver each day, it was nothing.

  17. You guys are awesome. We are all grateful for your wonderful service.

    Cheers,
    micheailin o’cinnsealach

  18. Wow, a thorough and complete explanation beyond and above the call of duty.

    I know that in this day and age everyone wants everything 24/7 and they want it yesterday. But it’s no big deal.

    The outage didn’t bother me much because it happens — and even then it happens only very rarely. In all my years of using statcounter this is the only major outage I’ve experienced.

  19. Wow, a thorough and complete explanation beyond and above the call of duty.

    I know that in this day and age everyone wants everything 24/7 and they want it yesterday. But it’s no big deal.

    The outage didn’t bother me much because it happens — and even then it happens only very rarely. In all my years of using statcounter this is the only major outage I’ve experienced.

    Some other websites I frequent got knocked off-line too, so I figured it was possibly a server farm outage.

  20. Thanks Guys, This service is simply great. Although we missed our stats and missed Statcounter also but we are happy to see it working again.

    You guys are doing great. Thanks for sharing all the problems with us.

Comments are closed.

Try Statcounter free for 30 days

No credit card required. Downgrade to the free plan anytime.

Try it for FREE!