{"id":1530,"date":"2009-07-02T08:19:00","date_gmt":"2009-07-02T16:19:00","guid":{"rendered":"http:\/\/localhost\/uptime"},"modified":"2014-02-21T16:35:11","modified_gmt":"2014-02-22T00:35:11","slug":"uptime","status":"publish","type":"post","link":"https:\/\/needmoredesigns.com\/uptime\/","title":{"rendered":"Uptime"},"content":{"rendered":"
Uptime is a measure of the time a computer system has been “up” and running. It came into use to describe the opposite of downtime, times when a system was not operational. The uptime and reliability of computer and communications facilities is sometimes measured in nines (similar to the unit of metallic purity). “Five nines” means 99.999% availability, which translates to a total downtime of approximately five minutes and fifteen seconds per year. [Wikipedia<\/a>]<\/blockquote>\n
Uptime is increasingly important. For some sites that we’ve developed and that we maintain, there are “incidents” with uptime. We host a recipe site, and every so often something pops up that needs to be dealt with right now<\/i>. That’s just the nature of high traffic websites. You come to expect it.<\/p>\n
We now use a lot of services on the web, and those often require a ton of work to keep up and running at top performance. Some folks do a great job of it, like Google<\/b> and 37signals<\/b>. Some companies fall flat on their face, despite running a service that you’re paying good money for, and that you expect to just work.<\/p>\n