It happens time and time again: when news breaks, the Internet slows.
It's quite obvious at this point that the Internet has muscled its way into the lives of anyone who needs information. And Michael Jackson's death Thursday had as great an impact on the Internet as anything in the history of the medium that didn't involve the World Trade Center.
Can a system that has trouble keeping up with ever-increasing demand for its services be considered a reliable source of information when a true crisis emerges? After an editor banished a budding argument between CNET News' Tom Krazit and Declan McCullagh from a company-wide mailing list, we decided to let them fight it out here.
Tom: How can any system that doesn't work precisely when people need it the most be considered the future of communications?
In a way, it took the death of perhaps the greatest entertainer of the last century to expose a key truth of this century: our new favorite communications tool, the Internet, buckles in times of crisis. News sites, including this one, were sluggish or completely offline at the peak of demand for information, forcing many to go back in time and flip on the television.
What if something really happens? How can companies trying to build information-related businesses on the Internet ever hope to supplant existing communications networks if they fail at the moment of truth? CNN's telecast didn't go down Thursday.
Declan: I think it's a little unfair to say the Internet "buckles in times of crisis." Sure, a few Web sites--Google News, The Los Angeles Times, TMZ, Yahoo, MSNBC--had slowdowns or outages. (That list includes our own CNET and CBS Interactive sites, which experienced serious problems for about half an hour.)
Some news Web sites slowing down or becoming unreachable for 30 minutes is not the same thing as the Internet "buckling." If an earthquake were to take out the trans-Pacific cable landings in California's Morro Bay, San Luis Obispo, and Grover Beach, if car bombs knocked out MAE East and MAE West, and if a hurricane laid low the cable landings in Long Island and New Jersey, that might--might!--qualify.
In fact, yesterday's sad news about Michael Jackson demonstrated not the vulnerability, but the resilience of the modern Internet ecosystem. True, a few sites were having problems. But The Los Angeles Times' report about Jackson's coma, and its subsequent report about his death, were picked up and mirrored widely. Even if you couldn't get through to the Times, you could get through to innumerable blogs and others news sites citing it. Or you could just wait a few minutes for the traffic to die down.
Was this really such an inconvenience?
Tom: Ok, I'll concede the point about the broader Internet: near as I could tell, ICanHazCheeseburger.com was performing like a champ yesterday.
But this is a systemic problem with the Internet, or perhaps put more accurately, the Web. The more people who demand the service provided by an information Web site, the harder it gets for that site to provide that information. CNN/MSNBC/et al don't buckle when millions of people change the channel to watch O.J. meander down a Los Angeles freeway or the opening salvos of the Iraq War.
In an online world where businesses are spending billions trying to shift information consumption patterns onto the Web, how can these outages be tolerated? You're right, it's very easy to navigate elsewhere if you can't find what you are looking for on Site A. But if you can't depend on Site A in times of crisis, you're not going to go back there in future times of crisis, hurting the reputation of that site as a reliable source of information.
Even Google was unable to handle the load. And if Google can't, nobody can. This is a serious problem for online businesses, especially as people continue to come online in emerging economies and with mobile devices.
Akamai's visual representation of the effect demand for information about Michael Jackson had on the Internet Thursday.
(Credit: Akamai)Declan: I was using Google News pretty frequently during the time that Michael Jackson's fate was uncertain, and noticed no problems. Others, including some of our colleagues, did. I suspect that Google is using a different set of servers for Google News vs. its main search engine. So it's not so much that Google couldn't design a system to handle an unusual spike in traffic, but that it chose not to do so.
Let me put this argument another way: You said that the Internet "fail[s] at the moment of truth" but lauded "existing communication networks" that supposedly work just fine. Well, existing communication networks fail too. If more than a small fraction of telephone customers try to get a dial tone at once, there's a problem. Ever try to make a call on Mother's Day or with a cell phone at a conference? You're likely to get a fast busy signal or "all circuits are busy" message. Telephone companies could design for higher usage, but have chosen not to. They've figured out that the costs outweigh the benefits.
(Similarly, printed newspapers sell out very, very early on days like Election Day. Is this "fail[ing] at the moment of truth?")
It's really more of an economic than an engineering problem. Is it worth it to add an extra, say, threefold server and bandwidth capacity for that hour or so a year when it's needed? Or pay Akamai's overage charges? Probably not; the revenue may not cover the fees. So if your average rate is 100 users/sec, you might build for 1,000 users/sec max and then not be able to handle those once-a-year occasions when the rate is 5,000 users/sec.
An economist might say the solution to this situation is to ration by price. News pages might normally be free, but under times of high load, a micropayment would be charged. That way, the people who want or need the information the most would get it. Of course this means we need a micropayment infrastructure; I'm not holding my breath...
Tom: We're talking about how to respond to instant demand for information in the modern era. You're right, telephone networks can get overwhelmed. That's why we haven't used the telephone as the primary information source since "Thriller" was released.
Television doesn't get overwhelmed in these situations. The entire state of California could turn to CNN right now and nothing would flinch. If the entire state of California clicked on this story right now, our building might explode.
The Internet has choke points that will limit its ability to be the primary source of information to the world. Yet, companies continue to build businesses around the idea of the Internet as a dominant source of information to the world, neglecting the thorny networking problems that will only continue to get worse as traffic grows and our demand for real-time news increases.
Declan: Aha! I think we're nearing agreement.
We know that providing servers and purchasing bandwidth to handle millions of people an hour is expensive, and may not always scale well. One way to deal with this is to make it much easier for ad-supported news organizations to purchase overflow capacity; perhaps the additional revenue would justify the additional expense. If there's sufficient demand, I'm sure someone will come up with it if Akamai doesn't offer it already. Or news organizations could strip extraneous graphics off of their sites for that hour or so of peak usage--basically entering an emergency text-only mode. (Anyone still using the Lynx Web browser would love it!)
Another option is to recognize the limitations of the medium. Because radio and TV are broadcast, they'll always be more efficient at reaching hundreds of millions of people at once. So maybe CNN.com can't compete with CNN Headline News right now. But if the worst that happens is major news Web sites get a little slow for some 30 minutes a year, I'm not going to worry about The Death Of Online News; the Internet is robust and distributed enough that sufficiently important information about the next 9/11 attack will be distributed one way or another.
In other words, until we achieve technocratical perfection, there's nothing wrong with a bit of redundancy in our lives: keep that old transistor radio and some spare batteries around for a backup.
Tom: Seriously, we didn't even talk about the real Achillies Heel in this whole system: the power grid.
The White House has denied that it has "abandoned YouTube as the provider of the embedded videos on the president's official home page."
In the report written by Chris Soghoian, a contributor to CNET's Blog Network, the author correctly noted that President Obama's weekly video address was distributed via a Flash player from Akamai instead of YouTube. But the author also wrote that the White House was bowing to pressure from privacy activists. White House officials acknowledged switching players but denied making any permanent decisions about them, or that they were motivated by privacy concerns.
"This week we tested a new way of presenting the President's weekly address by using a player developed in-house," Nick Shapiro, a White House spokesman, wrote in an e-mail. "This decision is more about better understanding our internal capabilities than it is a position on third-party solutions or a policy. The weekly address was also published in third-party video hosting communities and we will likely continue to embed videos from these services on WhiteHouse.gov in the future."
Those "third-party solutions" Shapiro is talking about include YouTube. The Web's largest video site continues to see video contributions to the White House channel, according to Scott Rubin, a YouTube spokesman.
"The White House hasn't ditched us at all," Rubin said. "If you look at the White House's YouTube channel, you'll see videos are being posted. We're just really excited that there are channels on YouTube that help us see what's going on with the federal government."
(Credit:
Akamai)
Web usage spiked on Thursday as people looked for news of the U.S. Airways jet that went down in New York's Hudson River.
Shortly before 5 p.m. EST, Akamai, which has assembled a content delivery network used by many global news organizations such as CNN, CBS, NBC, Reuters, and the BBC, reported a huge spike in Internet usage as people looked for news and video of the event.
The crash now ranks as the seventh biggest Internet news event since Akamai started tracking spikes in traffic in 2005. The plane crash, which miraculously resulted in no fatalities or serious injuries, ranks just ahead of the post-Election Day 2008 coverage.
Election night 2008, when Barack Obama was elected the 44th president of the United States, had the biggest spike in Internet usage. Over 8 million visitors per minute went online on November 4, Akamai's data shows. About 4.9 million visitors per minute were clicking on Web sites after the U.S. Airways crash landing.
Akamai is expecting a record-breaking spike in Net traffic on Tuesday when President-elect Obama becomes the first African-American to be president of the U.S.
Of course, my colleague Charles Cooper thinks all this hoopla made over keeping score of which news events elicit the most activity in the virtual world is silly. Check out his contrarian view of these virtual reactions in his latest column.
The Netflix Player by Roku
(Credit: CNET Networks)Some Apple TV owners have complained for several weeks that it takes much longer now to download and playback high-definition movies.
"I started downloading an hour back and it says it will take two hours," wrote someone with the user name Reachg. "It's already 25 percent downloaded but it's not letting me play. In the past I was able to play the movie in 10 minutes max...seems something is happening."
The complaints at Apple's forums first appeared on November 14. That was the day after Roku, maker of the Netflix Player, notified customers it had received complaints from some device owners about a marked drop-off in quality of their streaming video. The Netflix Player and Apple TV are set-top boxes that enable owners to watch Web video on TV sets.
What we have here are two set-top boxes that almost simultaneously experience dramatically reduced streaming quality in the case of the Netflix Player, and longer download times in the case of Apple TV. Coincidence?
It's possible but it's worth digging a little to see whether the two cases are connected. A Roku executive told me on Monday that the problems with the company's box occurred at about the same time Netflix was making changes to its content distribution network (CDN).
Steve Swasey, Netflix spokesman declined to comment, citing the company's policy of not discussing vendors. (Apple also declined to comment.) But sources close to Netflix said the Web's top movie-rental service uses multiple CDN companies, including Akamai and Limelight Networks.
Akamai also delivers much of Apple's video content for iTunes. Jeff Young, an Akamai spokesman, said the company's isn't to blame, at least for Netflix's problems. He acknowledged that Akamai performs some services for Netflix, but they don't include anything having to do with the company's streaming video service. Netflix's streaming service is now offered on multiple devices, including Microsoft's Xbox 360.
Young said Akamai executives had not been informed about any problems at Apple TV and were looking into the problem.
I was told by an industry source that it's easy to blame Akamai and CDNs for these kind of problems, but often the glitches are the result of a company's own servers or other back-end infrastructure. The one thing that's crystal clear is none of the companies are providing customers with much information and are very tight-lipped about what they know.
On Roku's message board, several Netflix customers ask why the company hasn't notified them that there's a problem.
Microsoft and Akamai Technologies are teaming up on high-definition video streaming efforts for PCs, the companies said Tuesday.
Akamai plans to release a beta service, AdaptiveEdge Streaming for Microsoft Silverlight, early next year to select media customers. It will run on Windows Server 2008 with Microsoft's Silverlight media player.
The move comes as broadband increasingly becomes a fixture in homes and as consumer expectations grow for smooth-running video on PCs. The clarity of HD images is also in video on PCs.
Microsoft will bring its new Web server technology, Internet Information Services 7.0 Smooth Streaming (IIS7.0), to the table. It is designed to let people view video streams with instant start-up times and without the play-and-pause jerkiness that can come with buffering. The technology aims to provide smooth streaming video by making real-time adjustments to changes in connectivity speeds.
Akamai plans to market the service to media companies worldwide. It will eventually become a feature of the IIS7 Media Pack.
"We've seen firsthand the growing demand for HD online content among our customer base," Tim Napoleon, Akamai's digital media chief strategist, said in a statement.
He noted that images broadcast over the television offer the same consistent quality for all viewers, but that such is not the case with streaming video on PCs. Each viewer may have a different experience on a computer, depending on connectivity speeds at any given moment.
The announcement comes after Microsoft unveiled plans two weeks ago for its Silverlight 2 media player. The new version carries features such as deep zoom, enhancements to cross-platform support, and support for digital rights management.
- prev
- 1
- next





