Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Twitter was down

status.twitterstat.us

Post reply on HN
Print view View original

201–210 of 544 posts

Re: Twitter was down

#201

Post by [deleted] »

eljimmy wrote: post #93
lukey_q wrote: post #25

A lot of high-profile outages recently. Can't actually remember the last time Twitter went fully down. Have to confess I immediately assumed an issue with my own connection, even though every other site is working. Unrelated, but for some reason the phrase "I have no mouth and I must scream" just popped into my head

Yesterday, Stripe went down for a half hour, and the later yesterday, Google's Android Payment Validation API went down for more than 2 hours. Stripe at least acknowledged their downtime. Google was oblivious, made no update to any of their status pages. Really horrendous awareness and support from Google per usual.

[deleted]

Re: Twitter was down

#202

Post by emerongi »

idlewords wrote: post #152
oneeyedpigeon wrote: post #133

Earlier quoted context omitted.

> It took a while to return, so he used the time to explain how, in an ordinary setup ... This one was visible from such a great distance, it's a wonder neither of you spotted it as it happened! I love your post — reminds me of BOFH :)

The guy had an amazing beard, with streaks of white in it! He looked like a great wizard to me. I remember even as we noticed people were frantic, saying to one another "oh man, another outage, thank goodness it's not us!"

And now it's a full-blown sitcom scene

Re: Twitter was down

#203

Post by xvector »

matwood wrote: post #168
rossdavidh wrote: post #100

Ok, this is too many high-profile, apparently unrelated outages in the last month to be completely a coincidence. Hypotheses: 1) software complexity is escalating over time, and logically will continue to until something makes it stop. It has now reached the point where even large companies cannot maintain high reliability. 2) internet volume is continually increasing over time, and periodically we hit a point where…

Reddit was also partially down this morning.

Reddit's down weekly, though, so that's no big deal.

Re: Twitter was down

#204

Post by wtallis »

rossdavidh wrote: post #143
idlewords wrote: post #105

Earlier quoted context omitted.

Write a script to fire random events and you will notice they sometimes cluster in ways that look like a pattern.

You know, it would be cool if you found stats on the downtime metrics of these various high-profile recent outages, and calculated the odds of having such a cluster. Statistics is hard, though, and avoiding a "Texas Bulls-eye" would be hard.

"Celebrities die 2.7183 at a time": http://ssp.impulsetrain.com/celebrities.html

Re: Twitter was down

#207

Post by roywiggins »

squarefoot wrote: post #109
0xFFFE wrote: post #85

Earlier quoted context omitted.

I share your sentiment to a certain extent, but I believe Twitter is a necessary evil. There should be an alternative to main stream media for people.

Sadly, for most people Twitter is mainstream media.

Twitter is not that popular. The problem is that mainstream journalists spend too much time on it and confuse it for the real world. How many "news" stories are just repackaged tweets? A lot.

Re: Twitter was down

#208

Post by papito »

rossdavidh wrote: post #100

Ok, this is too many high-profile, apparently unrelated outages in the last month to be completely a coincidence. Hypotheses: 1) software complexity is escalating over time, and logically will continue to until something makes it stop. It has now reached the point where even large companies cannot maintain high reliability. 2) internet volume is continually increasing over time, and periodically we hit a point where…

#1. I think the art of keeping things simple is being lost. These days people will mush together ten different cloud services and 5,000 dependencies just for a Hello World.

Re: Twitter was down

#209

Post by sbmthakur »

idlewords wrote: post #82

So storytime! I worked at Twitter as a contractor in 2008 (my job was to make internal hockey-stick graphs of usage to impress investors) during the Fail Whale era. The site would go down pretty much daily, and every time the ops team brought it back up, Twitter's VCs would send over a few bottles of really fancy imported Belgian beer (the kind with elaborate wire bottle caps that tell you it's expensive). I would in…

This reminded me of something too!

I used to work(on backend) on a popular app(in my country) which had a good number of users. One day I was asked to work with some infra/sysadmin folks who wanted to fix some issues with the servers in our inventory. We happily updated kernels and even rebooted servers a few time. I came back to my team and saw them deeply engrossed into production logs. Turns out few of the servers that were "fixed" were actually production servers. I almost shouted the F word when I listed all IPs. This confusion happened because the server guys used data IPs and we used management IPs. This exposed serious miscommunication among our teams. But fun times indeed!

Post reply on HN