Photo of Hudson River plane crash downs TwitPic
The rapid-fire spread of a close-up photo of the US Airways plane that crashed in the Hudson River Thursday resulted in the service that hosted the picture going down.
This photo, of the US Airways jet that crashed into the Hudson River Thursday, brought so much traffic to TwitPic that the site, which allows users of several mobile phones to post pictures to Twitter, saw its servers get overloaded. Click image for larger version.
(Credit: Janis Krums)TwitPic, an application that allows users to take pictures from their mobile phones and append them to Twitter posts, went down after at least 7,000 people attempted to view the photo of the airplane taken from a commuter ferry by Sarasota, Fla., resident Janis Krums.
According to Noah Everett, the founder of TwitPic, who still runs the service by himself, after the photo of the plane was re-tweeted by a large number of people and then picked up by several news sites, including Silicon Alley Insider, the resulting traffic was too much for the site's servers.
Everett called it a "snowball effect."
In fact, Everett said this wasn't the first time someone had used TwitPic to post a photo of an airplane accident. He explained that a passenger on a Continental Airlines plane that went off the runway in Denver in December used the service to post a photo. But that time, the service was able to stay up.
Perhaps because of the national interest in an airplane accident taking place in direct view of Manhattan, the traffic produced by Krums' photo was higher than in the case of the Denver accident, Everett suggested.
And while the circumstances of Thursday's accident were unfortunate--though, miraculously, no one died in the crash--Everett admitted that the fact that Krums' photo got so much attention was validation of the utility of TwitPic.
"We haven't gotten so much press coverage before," Everett said.
"It's shocking, and it's a good feeling--though (also) not a good feeling because it's bad news," Everett said.
He also said that he's got additional servers that are soon going to be in place.
"In a month's time (something like) this will not affect us anymore," he explained. "We're working to be able to handle our growth, but this is definitely a wake-up call showing the power of breaking news and TwitPic."
Everett said that there had been about 7,000 views of the picture before the site went down, and that there were about 500 additional requests to view it every 15 or 20 seconds.
He also said that while he couldn't be immediately sure, it was likely that Krums had used an Apple iPhone to take the picture, given that it was 600x800 pixels, the average size of an iPhone picture.
By 2:35 p.m. Pacific, about two hours after the photo was taken, TwitPic was back up.
Everett said, "I hope it stays up. I'll be working on this through the night."
Daniel Terdiman is a staff writer at CNET News covering games, Net culture, and everything in between. E-mail Daniel. 






I'm glad no one was hurt.
BTW, native iPhone camera resolution is 1600 x 1200 pixels.
even though the IPhone camera sucks ! people r actually using that thing !
if only digital cameras had Internet !
BTW great news that no one got hurt , it's a Miracle
There's gotta be a better way to say that. I'm pretty sure I get your general idea... but yea... there's gotta be a better way to say that.
When the engines are shut down, they take time to fire back up and there's a procedure for that. There wasn't enough time obviously so he ended up landing in the water and being labeled a hero.
That's the actual scoop coming from someone who works for the airline.
- by radams04 February 25, 2009 9:29 AM PST
- It was a great job not just for the pilot known as Sully but also from the flight assistants that calmed the passengers and help to get a successfully end of the story. I found a video in here about with the American hero sully interview, the story is told by him and the flight assistants. Very interesting : http://cnettv.cnet.com/2001-1_53-50005196.html?tag=rtcol%3brelvideos
- Like this Reply to this comment
-
(12 Comments)