The world’s longest news story

TL;DR

Reuters' extended live coverage of Japan shows how a liveblog can combine immediate reporting, context, media and visible corrections during a fast-moving event. The useful unit is each verified update, supported by clear chronology and editorial judgment.

  • Why it matters: readers need reliable updates while a developing event is still incomplete and uncertain.
  • How it works: reporters add verified facts, explanatory context, media and corrections in a time-ordered record.
  • Reality check: Reuters closed this Japan liveblog after 14 days, producing a report that reached 298 pages.
  • Case in point: separate confirmed information from background and pending reports so changes remain legible to readers.

When Reuters closed its liveblog of the triple disaster in Japan after 14 days of live reporting, the resulting story was 298 pages long — the world’s longest news story.

Reuters correspondents reported what was happening on the ground through words, audio and video, while reporters back in the newsroom provided backgrounders and global context for a story that evolved by the minute. Photojournalists kept the blog supplied with a steady stream of photos of collapsed buildings, rescue workers, survivors and a mass grave. A lively discussion about the role of media in Japan coverage unfolded right in the blog. At one point in the days following the earthquake, Reuters’ liveblog received as many as 25,000 unique users, all watching at the same time. Readers tuned in from every continent on the planet.

People latched onto the liveblog not just for facts but for a sense of being present—imperfect updates, raw reactions, even small corrections as more info trickled in. There’s something about that mix (a combination of uncertainty, shared concern, and unvarnished truth) that traditional, polished reporting rarely captures. It reads much closer to real life: jittery, sometimes fragmented, always urgent. If you were refreshing the feed in those weeks, you know what I mean—nobody cared about perfect prose. They just wanted to know what was really happening.

Looking back with the benefit of hindsight in 2025, it's actually wild how this approach has become the default in disaster coverage now. Liveblogs aren't just for earthquakes or massive news anymore—you see them spun up for elections, protests, even tech launches. There's an expectation of transparency in journalism that this model helped jumpstart. Not every experiment has paid off, but it's changed newsroom habits for good. Readers have gotten used to being let in on the messy process, and it's hard to imagine things ever snapping back to the old ways.

Similar to how it distributes its more traditional reporting, Reuters syndicated its live coverage to media outlets in the U.S. and Canada, including Maclean's and CityNews.

The result? A nuanced, calm report that stood out amidst the hysteria of sensationalized media coverage.

Frequently asked questions

How can an editor keep a liveblog useful as it grows?

Give each update a clear time, a precise fact and enough context to explain why it matters. Add links or short background passages when a new development depends on earlier reporting. A consistent format helps readers scan the latest information without losing the sequence that led to it. Editors should also keep headlines, labels and timestamps accurate when the story changes quickly.

When should a live update be corrected instead of deleted?

Correct an update when the original item was published in good faith but later reporting changes a material detail. State what changed, add the corrected information and preserve a readable trail where appropriate. Remove content only when it creates a serious safety, legal or privacy problem. The goal is to prevent a false statement from spreading while showing readers that verification is an ongoing process.

What should a newsroom preserve after a liveblog closes?

Preserve the final chronology, significant updates, explanatory context and any corrections that help a later reader understand the event. Add a concise closing note that identifies the final status and directs readers to durable follow-up reporting. Review links, captions and embedded material before archiving. This turns a stream of updates into a useful public record rather than leaving readers with an unfinished feed.

MM Matt Montenegro