There is no way they can achieve that uptime claim, nor should they try to say they have 99.9999% aka "six nines". That's 31.5 seconds a year, and even a well-designed network is going to have that much at some level. I mean, the VPSes might be distributed across hardware, but a failure of some component might mean that it's still "up", but seriously degraded during the transition. How useful is that for "uptime"? It becomes a bragging right. How about if all routes to a large provider, like Level(3) are down for a reset period, or are re-routed through Cogent, which is maxed out on all peering with L3 at 99% packet loss levels? Is that really uptime? Sure, that's out of their control, but the situation with their own website being down for some people right now underscores that lofty claims are meant to be broken.
Now that they're beating that Joyent drum a little more: watch them fall down under a DoS attack that Amazon could bat away at this point. I'm by no means supporting Amazon, but Joyent is still a small company with big claims. I predict they will fall apart when Sun stops making hardware, and when their engineers argue over whatever trendy "wrong way to do it" Node-type technologies that they're jacking off over next.
When you are talking about "X nines, in retrospect, from a small sample" it's meaningless, and they know it. All it means is, they've had 100% uptime, because they've been lucky enough to avoid a crash. And by 100% uptime, I'm sure that's "100% of crashes weren't in our opinion our fault".
I signed up to check it out, and it definitely looks cool... The connection is lightning fast, but I'm wondering what other server options you'll have in the future. I'd love to have a few servers that are I/O beasts, and others full of 128GB or 256GB of RAM. Right now, we pay so much to Amazon each month, and we're playing with other options.
Yeah, we're going to announce a number of new hardware profiles in the coming weeks. We'll eventually have a number of "extreme" hardware profiles that are specialized for certain use cases.
Excellent use of Fiddler... I'm going to try this on a few apps that have seemed terribly slow, even on wi-fi. I take that back: I need to use this with every app that I've been semi-trusting.
For development, this seems like a great catch-all tool to make sure expected best practices are actually working........ or if someone completely ignored them / forgot to implement.
They replaced several of mine for free, waiving all shipping and repair costs. I can't think of another experience I've had like that. They're also a US company, and they have the best online gaming experience... those are just a few of the reasons I can think of.
One of the reasons why one does not typically experience something like that is because most companies would go out of business if they blew that much money on a faulty product. Microsoft has other revenue streams that allow them to throw billions at any problem.
