Nieman Foundation at Harvard
HOME
          
LATEST STORY
Die Welt’s analytics system de-emphasizes clicks and demystifies what it considers a “quality” story
ABOUT                    SUBSCRIBE
June 28, 2012, 5:18 p.m.
Reporting & Production
supreme-court-scotus-cc

Anatomy of a spike: How SCOTUS Blog dealt with its biggest traffic day ever

Health-care decision day meant spending big money to keep the site from crashing at exactly the wrong time.

Ten-year-old SCOTUS Blog has been a go-to authority on the health care challenge since the beginning, which made today its Oscar night, Super Bowl, and Christmas morning all wrapped into one. But on the Internet, success comes with a darker side: server crashes. SCOTUS Blog was prepared. The traffic buildup was already intense on Monday:

To put that 500,000-in-one-day in context, it had nearly 1 million over the three days of oral arguments this spring. (Other sites were prepping too; just before the decision was handed down, New York Times developer Jacob Harris tweeted a graph showing a huge traffic spike.)

For SCOTUS Blog, preparing meant investing in server upgrades, even if they would only be used for a short burst of traffic.

To help offload the burden, SCOTUS Blog shut down its main site at peak times and redirected visitors to a dedicated page off-server. That was hosted on WPEngine, a server company that specializes in optimized WordPress installations. And the minute-by-minute liveblog was pushed off to CoverItLive, with an embed put on the WPEngine site. The liveblog page had its own special “Sponsored by Bloomberg Law” message in its header.

And for the moment of maximum interest — the seconds after the decision was announced — SCOTUS Blog publisher Tom Goldstein advised they’d be going to Twitter first. “As a purely formal matter, we will ‘break’ the story of the health care decision on Twitter. So you can follow @scotusblog, if you’d like,” he wrote in the liveblog. “But don’t follow us just for that reason, because we will have the news here on the live blog less than 5 seconds later.”

By 9:08 a.m., he said there were already 70,000 people reading the liveblog and that the site had already logged 1 million hits for the day. His guesstimate for the day’s traffic? “My best bet is 250,000 [concurrent liveblog readers] at the time of the decision.” Goldstein kept liveblog readers updated.

9:16 a.m.: “100,000 live blog readers.”

9:29 a.m.: “145,000 on the liveblog.”

9:33 a.m.: “The previous record for our live blog was 100,000, on Monday. The previous record for our daily hits was 500,000, also Monday.”

9:43 a.m.: “218,000”

9:43 a.m.: “We are at less than 1% of our own server capacity. We’ve shifted the principal processing to CoverItLive, which expects it can handle >3 million.”

9:56 a.m.: “FWIW, the count going into 10am is 344,000 contemporaneous readers.”

10:03 a.m.: “1,000 requests to the liveblog per second.”

10:06 a.m.: “520,000 contemporaneous readers.”

At 10:09 a.m., SCOTUS Blog broke the news on Twitter. At this writing, that tweet’s been retweeted 2,927 times and favorited 142 times. (Also, it was accurate.)

10:22 a.m.: “866,000 liveblog readers.”

That’s roughly the city of San Francisco.

From there, SCOTUS Blog switched into analysis, commentary, and smart aggregation of other sites’ analysis and commentary. But the traffic kept coming, if at a slower pace.

1:11 p.m.: “SCOTUSBlog just clipped over 3 million hits!”

2:17 p.m.: “Thanks to everyone for sticking with us this whole time. There are still over 80,000 people following the live blog.”

CoverItLive said it was the second most popular U.S. event they’ve hosted in 2012, behind only ESPN’s NFL draft coverage.

By 2:46 p.m., SCOTUS Blog staffers were ready to celebrate:

And by 5:09 p.m., they were really ready to celebrate:

Photo of the Supreme Court by Kjetil Ree used under a Creative Commons license.

POSTED     June 28, 2012, 5:18 p.m.
SEE MORE ON Reporting & Production
SHARE THIS STORY
   
Show comments  
Show tags
 
Join the 15,000 who get the freshest future-of-journalism news in our daily email.
Die Welt’s analytics system de-emphasizes clicks and demystifies what it considers a “quality” story
Every story’s performance reduced to a single score: a reductionist take on journalism or a way to make a news organization’s values concrete?
Good news, publishers: People will read your long stories on their phones (for two minutes, anyway)
People will read longer content on their smartphones, a new Pew report finds.
Tampa just lost a daily newspaper; is this the continuation of an old trend or the start of a new one?
Buy a company, milk the cash flow, sell off assets, shut it down: It can be a profitable formula. Is this the end game for some metro newspapers?
What to read next
0
tweets
“Investigative brand journalism”: The Guardian and Amazon step into the next level of sponsored content
The series isn’t overtly promotional, but its tone is very different from that of recent true crime coverage like Serial and Making a Murderer.
0Hot Pod: As more podcasts become TV shows, can their founders retain creative control?
Plus: Podcasts as time-shifted cable TV; MTV News launches its first podcasts; Postloudness moves beyond Mailchimp.
0Live, local, late breaking: On Facebook Live, news outlets take a cue from TV (but don’t call it TV)
“This opens up all kind of new ways and products to tell stories that are not so focused on production values.”
These stories are our most popular on Twitter over the past 30 days.
See all our most recent pieces ➚
Fuego is our heat-seeking Twitter bot, tracking the links the future-of-journalism crowd is talking about most on Twitter.
Here are a few of the top links Fuego’s currently watching.   Get the full Fuego ➚
Encyclo is our encyclopedia of the future of news, chronicling the key players in journalism’s evolution.
Here are a few of the entries you’ll find in Encyclo.   Get the full Encyclo ➚
Global Voices
Placeblogger
San Francisco Chronicle
InvestigateWest
GateHouse Media
The Awl
Newsmax
Semana
U.S. News & World Report
New England Center for Investigative Reporting
Frontline
Topix