Google Reader was the web’s dominant RSS reader, and on July 1, 2013 Google switched it off. Launched out of Google Labs on October 7, 2005, Reader did one thing exceptionally well: it collected the feeds of every blog, news site, and webcomic a person subscribed to and presented them in one fast, keyboard-driven inbox. For the news-obsessed it became indispensable — the home page of the open web — and over eight years it quietly accumulated tens of millions of users and a genuinely devoted core. Google never ran an ad against it, and that, in the end, was the problem.
The announcement came on March 13, 2013, buried in a corporate blog post cheerfully titled “A second spring of cleaning.” Reader, Google said, would be retired on July 1 because “usage has declined” and the company wanted to “focus on fewer products.” The reaction was immediate and disproportionate to the size of a free RSS tool: a Change.org petition gathered roughly 150,000 signatures within days, rival readers were swamped overnight, and a generation of power users concluded — loudly, and not for the last time — that Google could not be trusted to keep anything alive that it could not monetize.
What made the death sting was that it looked self-inflicted. In October 2011 Google had stripped Reader of its beloved built-in sharing and social features and rerouted them through Google+, the social network Google was then betting the company on. The de-featuring alienated the very users who made Reader special, depressed engagement, and supplied, eighteen months later, the “declining usage” that justified the shutdown. Reader was not killed because it was failing; it was made to fail, then cited as a failure.
Its users scattered to Feedly, NewsBlur, Inoreader, and The Old Reader, and RSS survived — more fragmented, less central, but alive. What did not survive was the assumption that a free, beloved Google product was a permanent fixture. Reader became the founding artifact of the “Google graveyard,” the case every subsequent shutdown is measured against, and a durable lesson in what it means to build your routine on something you don’t pay for.
Adobe Flash Player was, for most of two decades, how the web moved. First released on January 1, 1996 as FutureSplash Player, passed to Macromedia and then to Adobe with its December 2005 acquisition, Flash became the near-universal browser plugin for animation, games, and video — and on December 31, 2020 Adobe stopped supporting it, then activated a kill-switch that blocked Flash content from running on January 12, 2021. After twenty-four years, the runtime that built an era of the web was deliberately set to expire on a date, like milk.
At its height Flash was effectively ambient. Adobe claimed the player reached the neighborhood of a billion internet-connected desktops, present on essentially every browser that mattered; if a site had an intro animation, a banner ad, an embedded cartoon, a casual game, or — crucially — streaming video, it almost certainly ran on Flash. It powered Newgrounds, Homestar Runner, an entire generation of browser games, and the early years of YouTube. For animators and hobbyist developers it was the most accessible creative runtime ever shipped: draw, script a little ActionScript, export, embed.
What killed Flash was not a competitor product but a convergence of structural forces it could not answer. It carried chronic, well-documented security vulnerabilities that made it one of the most reliably exploited pieces of software on any machine. It was a CPU-hungry, battery-draining plugin built for the mouse-and-desktop world precisely as computing moved to touch and mobile — and in April 2010 Steve Jobs published “Thoughts on Flash,” refusing it on the iPhone and iPad and citing openness, security, performance, and battery life. Meanwhile HTML5, WebGL, and later WebAssembly absorbed, in the open browser itself, nearly everything Flash had done. Adobe announced the end on July 25, 2017, with Apple, Google, Microsoft, Mozilla, and Facebook coordinating the wind-down.
Flash’s death was unusually orderly and unusually total — a runtime, not a service, so there was no server to leave running. What it endangered was the content: tens of thousands of games and animations that existed only as Flash files. That, more than the player itself, is what people raced to save.
GeoCities was where millions of ordinary people first built something on the web, and on October 26, 2009 Yahoo switched off the US service and deleted nearly all of it. Founded in November 1994 as Beverly Hills Internet and renamed GeoCities, the service gave anyone a free homepage — at first 2 MB of space — and organized those pages into themed “neighborhoods” with names like Hollywood, SiliconValley, Tokyo, and SunsetStrip. It was the handmade web in its purest form: under-construction GIFs, MIDI files that played on load, hit counters, blinking text, and the unfiltered enthusiasms of a generation discovering it could publish.
It was also enormous. By 1999 GeoCities was reportedly the third-most-visited site on the entire web, behind only AOL and Yahoo itself, and at its end it still served on the order of 38 million pages and drew something like 177 million annual visitors. Yahoo bought it at the very top of the dot-com boom, on January 28, 1999, for about $3.57 billion in stock — a price that captured exactly how central the amateur homepage seemed to the web’s future, right before that future moved elsewhere.
What moved elsewhere was self-expression. Blogging platforms, then MySpace, then Facebook and YouTube gave people easier ways to post without hand-coding HTML, and the personal homepage faded as a form. GeoCities, by then a neglected Yahoo property carrying years of accumulated pages and no obvious business model, was wound down: Yahoo announced the closure in 2009 and pulled the plug on the US service that October. The Japanese version, run separately, lasted until March 31, 2019.
This is one of the sober entries. The wit belongs to the corporate arithmetic — a $3.6 billion purchase deleted for housekeeping — but not to what was lost. When GeoCities went dark, millions of personal pages, the first websites countless people ever made, family tributes, fan shrines, and small homemade archives, were erased at once. The thing that saved a piece of it was not Yahoo but Archive Team, a volunteer collective that raced the clock to mirror as much of the neighborhoods as it could before deletion.
AIM — AOL Instant Messenger — was how a generation of Americans first talked to their friends online, and on December 15, 2017 it was switched off after twenty years. Launched as a standalone app in May 1997, AIM turned the buddy list, the away message, and the soft door-creak of a friend logging on into the texture of everyday social life. For students especially it was the after-school commons: you came home, you signed on, and the little window told you who else was there. It was the place a whole cohort learned what it felt like to be reachable.
At its height it was dominant. AIM reached roughly 61 million users by 2000 and held something like 52 percent of the US instant-messaging market by the mid-2000s, the clear leader over Yahoo Messenger, MSN Messenger, and the ICQ network AOL also owned. Its cultural footprint outran even its user count: the away message — the little broadcast status you left when you stepped away — was a precursor to the tweet and the status update, a way of performing your mood to your buddy list before “posting” was a verb.
What killed AIM was not a better instant messenger; it was the disappearance of the need for a standalone one. Text messaging moved real-time chat into the phone in everyone’s pocket. Then Gchat folded messaging into email, and Facebook folded the buddy list into the social graph everyone already lived in. The behavior AIM pioneered didn’t die — it migrated into devices and platforms that did it without a separate program to open. AIM’s parent, AOL, declined alongside it, sold to Verizon in 2015 and folded into the Oath media division; by March 2017 AIM was down to single-digit millions of users, and keeping its aging OSCAR messaging protocol running for them no longer made sense.
This entry is wry about the corporate decline — a company once worth hundreds of billions reduced to a media-division line item — but gentle about the thing itself. AIM was where a lot of people had their first online conversations, their first crushes typed at midnight, their first sense of an internet that was social. It was outgrown rather than defeated, and that is its own kind of ending.
ICQ was the program that taught the world to chat, and on June 26, 2024 its owner switched it off after twenty-eight years. Built in 1996 by the tiny Israeli startup Mirabilis — five developers, including Yair Goldfinger, Sefi Vigiser, Amnon Amir, Arik Vardi, and the elder Yossi Vardi — ICQ was among the first stand-alone instant messengers to reach a mass audience. Its name was a pun on “I Seek You,” and for a generation it defined what real-time presence felt like: a green flower in the system tray, a numeric user ID you memorized like a phone number, and a notification sound so iconic that “uh-oh” still triggers Pavlovian recognition decades later.
The growth was extraordinary for its moment. ICQ was freely downloadable, spread by word of mouth, and at its peak around 2001 the service reported more than 100 million registered accounts. That success made it an acquisition target almost immediately: AOL bought Mirabilis on June 8, 1998 for $287 million up front plus up to $120 million in performance-based payments — a landmark price for a two-year-old chat client. ICQ then began a long ownership migration that mirrors a quarter-century of internet history: AOL held it for over a decade, sold it in April 2010 to Digital Sky Technologies (soon Mail.ru Group) for a reported $187.5 million, and Mail.ru later rebranded as VK.
Under each owner ICQ slowly receded in the West, displaced first by AIM and MSN Messenger, then by SMS, Facebook, WhatsApp, and the smartphone. But it never fully died; it lingered for years in pockets of Eastern Europe and the former Soviet Union, where Mail.ru kept it alive. The end came as a corporate housekeeping note: VK announced in May 2024 that ICQ would close on June 26 and steered remaining users toward VK Messenger and VK WorkSpace.
What its users lost was less a tool than a memory — the first screen name, the first contact list, the first stranger met online. ICQ did not collapse in scandal or run out of money. It simply outlived the era it had invented, and was finally retired by a successor company with newer apps to promote.
Yahoo Answers was the open internet’s communal question box — a place where anyone could ask anything and anyone could answer — and on May 4, 2021 Yahoo switched it off after sixteen years. Launched to the public on December 8, 2005, the service let users post questions on any topic, vote on responses, and earn points for participation. For a stretch in the late 2000s it was one of the most-visited reference destinations on the web: in 2009 Yahoo claimed roughly 200 million users worldwide and millions of daily visitors, and for a time a Yahoo Answers result sat near the top of an enormous share of long-tail Google searches.
Then it became something stranger and more durable than a reference site: a meme. The very openness that made Yahoo Answers useful also filled it with malformed, surreal, and unintentionally hilarious questions — the most famous, “how is babby formed,” posted in 2006 and immortalized by Something Awful and a wave of YouTube parodies. For millions, Yahoo Answers stopped being where you went for answers and became where you went to laugh, a generator of internet folklore even as its credibility as a knowledge source eroded.
That erosion was the official cause of death. As Google’s own answer boxes, Wikipedia, Reddit, Quora, and Stack Overflow absorbed the serious questions, Yahoo Answers’ usage fell steadily — by one third-party measure, US monthly active users dropped from around 24 million in early 2010 to under 6 million by late 2015. By the time Verizon owned Yahoo, the site was a low-traffic relic carrying real moderation and infrastructure costs. The company announced the shutdown on April 5, 2021, froze new posts on April 20, closed the doors on May 4, and gave users until June 30 to download their contributions as a JSON archive.
What was lost was uneven: a vast, messy corpus of human curiosity and community help, alongside a comedic artifact of the early social web. Yahoo Answers did not fail dramatically; it simply outlived its usefulness as the internet learned better ways to ask and answer.
Google Wave was the most exciting product nobody could use, then the most baffling product nobody wanted, and on April 30, 2012 Google shut off its servers and gave the code to the Apache Software Foundation. Announced on May 28, 2009 at the Google I/O developer conference, Wave was pitched with a line that became famous: what would email look like if it were invented today? The answer was a single real-time medium that fused email, instant messaging, documents, and wikis into shared “waves” where every keystroke appeared live, conversations could be replayed from the beginning, and bots and extensions could plug in anywhere. The demo, led by Google Maps co-creators Lars and Jens Rasmussen, drew rapturous applause and instant hype.
Then Google did something that would define the saga: it made Wave artificially scarce. Rather than a public launch, it opened a limited preview to 100,000 users in September 2009, each able to dole out a few invitations, turning access into a status symbol and the wider audience into spectators. By the time Wave opened to the general public in May 2010, the buzz had curdled into a single, devastating question that no one — not even Google — could answer cleanly: what is this actually for?
The reckoning was swift. On August 4, 2010, barely three months after the public launch and a little over a year after the standing-ovation debut, Google announced it would stop developing Wave as a standalone product, citing a lack of user adoption. The service lingered as a courtesy: existing waves went read-only on January 31, 2012, and the servers were switched off on April 30, 2012. Google had already, in December 2010, donated the code to Apache, where it became Apache Wave (the “Wave in a Box” server) — a project that never left incubator status and was formally retired on January 15, 2018.
Few users lost data they grieved, because few had truly committed; Wave’s tragedy was not a bereaved community but squandered brilliance. It remains the textbook case of a technically dazzling product undone by hype it could not satisfy and a purpose it could never articulate.
Picasa was the fast, much-loved desktop application for finding, organizing, and lightly editing the photos already sitting on your hard drive, and on March 15, 2016 Google stopped supporting it. First released by a small company called Lifescape on October 15, 2002, Picasa was acquired by Google in July 2004 and from that point given away free. It did something that, in retrospect, feels almost quaint: it scanned your computer, gathered every image into one clean library, and let you crop, retouch, tag faces, and make albums without uploading anything to anyone. For more than a decade it was the default answer to “how do I deal with all these photos,” and it earned a loyalty that outlived its own updates.
The end was announced on February 12, 2016, in a blog post titled “Moving on from Picasa” by Anil Sabharwal, the head of Google Photos. The desktop application would no longer be supported as of March 15, 2016; the companion Picasa Web Albums service would begin shutting down on May 1, 2016. The stated reason was consolidation: Google wanted to “focus entirely on a single photo service in Google Photos” rather than “divide our efforts across two different products.” Picasa was not failing. It was simply on the wrong side of a strategy.
That strategy was the cloud. Google Photos, launched in May 2015, was mobile-first, automatic, and stored everything on Google’s servers — the opposite of Picasa’s local, you-own-the-files model. Killing Picasa was a bet that people no longer wanted to manage a library on a machine they controlled; they wanted it managed for them, somewhere else. For most users that bet was right. For the considerable minority who valued Picasa precisely because it kept their photos on their own disk and out of anyone’s cloud, the discontinuation was a quiet eviction from a workflow that had no real successor.
The desktop app, notably, did not detonate. Google did not push a kill switch; the program kept running on machines that already had it, unsupported and slowly aging. But “still works for now” is not the same as “alive,” and Picasa joined the long ledger of beloved Google products retired in the name of focus — this time not because users left, but because the company decided where they ought to keep their pictures.
Internet Explorer was the browser that conquered the web and then spent a decade as the punchline of it, and on June 15, 2022 Microsoft retired the IE11 desktop application for good. Launched in August 1995 as part of the Microsoft Plus! pack for Windows 95, IE rode the most powerful distribution advantage in computing history — it came bundled with Windows, the operating system on nearly every PC on earth — to crush Netscape in the first browser war. By 2002 and 2003 it held roughly 95 percent of the market, a dominance so total it became the subject of a landmark U.S. antitrust case over exactly that bundling.
Then, having won, Microsoft stopped trying. With Netscape vanquished, IE6 — released in August 2001 — was left to ossify for years, becoming a byword for security holes and broken web standards that web developers cursed and corporate IT departments could not escape. While IE stood still, the web moved: Firefox arrived in 2004 with tabs and standards compliance, and Google’s Chrome, launched in 2008, was faster and cleaner. In May 2012, Chrome overtook Internet Explorer as the most-used browser in the world. IE’s share collapsed, and the program acquired its enduring second career — the thing you opened once on a new PC to go download Chrome or Firefox, and then never touched again.
Microsoft eventually accepted the defeat it had inflicted on itself. It replaced IE with Microsoft Edge in 2015, and on June 15, 2022, after more than 25 years, the IE11 desktop application officially retired and went out of support, progressively redirecting to Edge. Legacy compatibility was preserved through “IE mode” inside Edge, which Microsoft committed to supporting through at least 2029 — a tacit admission that decades of intranets and enterprise apps had been built to IE’s idiosyncrasies and could not simply be abandoned.
What IE leaves behind is the canonical story of how a monopoly rots. It did not lose because it ran out of users or money; it lost because, once unchallenged, it quit innovating, accumulated a mountain of security and standards debt, and watched faster rivals dismantle a position that had looked permanent. The browser that once was the internet for most people ended as a compatibility shim and a meme.
Windows Phone was Microsoft’s genuinely good third mobile operating system, and it died not for lack of quality but for lack of apps. Launched as Windows Phone 7 on October 21, 2010, it broke decisively from the iPhone-and-grid template with “Live Tiles” — dynamic, color-blocked panels that surfaced information on the home screen instead of static icons. Reviewers praised the design’s clarity and originality, and on the well-built Nokia Lumia hardware it had a real argument as the most distinctive phone you could buy. By 2017 active development had effectively ended; Microsoft confirmed the platform’s last release would reach end of support on December 10, 2019.
The cause of death has a name developers used at the time: the “app gap.” A modern phone is only as useful as its software, and Windows Phone never attracted the breadth of apps that iOS and Android took for granted. The pattern was a vicious circle — too few users to justify the cost of building and maintaining an app, and too few apps to attract more users. Headline services arrived late, in crippled form, or never at all, and every missing or outdated app was another reason for a buyer to choose an iPhone or an Android instead. The OS could be elegant; the ecosystem was empty, and the ecosystem is what people actually live in.
The bet that was supposed to break the cycle made the failure catastrophic instead. In 2014 Microsoft bought Nokia’s devices and services business for roughly 7.2 billion dollars, aiming to control the hardware and force scale. In July 2015 it wrote down approximately 7.6 billion dollars on that acquisition — more than the purchase price — and cut about 7,800 jobs, overwhelmingly in the phone division. The numbers told the story plainly: Microsoft had spent billions trying to buy its way into a market whose users were already locked into two other ecosystems, and the market refused to follow.
Windows Phone’s discontinuation is the textbook case of the app-gap death and of network effects that money cannot purchase. It was not killed by a rival feature or a scandal; it was starved. A platform with no users gets no apps, a platform with no apps gets no users, and Microsoft, despite all its resources, never found the lever to break that loop before the loop broke the product.
Parse was a mobile backend-as-a-service — a hosted set of tools that let an app developer skip building and running servers entirely — and on January 28, 2017 Facebook switched it off. Founded in 2011 by Tikhon Bernstam, Ilya Sukhar, James Yu, and Kevin Lacker, Parse sold a deceptively simple promise: write your iOS or Android app, point it at Parse for data storage, user logins, and push notifications, and never think about a database, a server, or a sysadmin again. For a generation of mobile startups and solo developers, that promise was irresistible, and Parse grew fast.
In April 2013 Facebook acquired the company in a deal widely reported at roughly $85 million, its first serious move into paid developer tools. Under Facebook’s banner Parse kept growing; by 2014 it was reported to power around 500,000 mobile apps, and at shutdown TechCrunch noted that at one point some 600,000 apps relied on the platform. For nearly three years it looked like a rare example of a developer service that an acquisition had strengthened rather than smothered.
Then, on January 28, 2016, Facebook announced that Parse would be wound down over exactly one year and shut for good on January 28, 2017. There was no scandal, no security breach, no collapse in usage cited — only a corporate decision to focus elsewhere. Facebook gave developers a year, a database-migration guide, and, unusually, the platform’s own source code, open-sourced the same day as Parse Server so that anyone could stand up their own copy. It was about as graceful as a shutdown gets, and it still stranded hundreds of thousands of apps whose owners had to scramble to migrate or go dark.
That is the lasting weight of the Parse story. Tens of thousands of developers had taken Facebook at its word and built their products on infrastructure they did not control. When the owner’s priorities changed, the polite one-year window did nothing to change the basic fact: every one of those teams now had to rebuild the foundation of a shipping product, on a deadline they did not set, for a reason that had nothing to do with them.
Mailbox was the iOS email app that arrived in February 2013 as the most wanted download in the App Store, and on February 26, 2016 its owner Dropbox switched it off without ceremony. Built by a tiny San Francisco startup called Orchestra, it reimagined the mobile inbox around two gestures — a short swipe to archive, a long swipe to snooze a message until later — and around the idea, briefly seductive, that email could be tamed into a to-do list you actually cleared. For a few weeks in early 2013 it was the most talked-about app in technology.
What made Mailbox a phenomenon before anyone had used it was the waitlist. Rather than open the doors, Orchestra made every new user take a numbered ticket and watch a live queue counter tick down the hundreds of thousands of people ahead of them. The artificial scarcity worked exactly as designed: it manufactured demand, generated weeks of press, and turned a free email client into an event. Then, barely a month after launch, Dropbox acquired the company for a figure reported at roughly $100 million — and the app’s real purpose quietly changed.
Because the acquisition was never really about email. Dropbox, then racing to justify a multibillion-dollar valuation, wanted Orchestra’s design talent and a beachhead on mobile, and Mailbox was the vehicle. The app got an Android version and a Mac beta in 2014, and then very little else. By late 2015 Dropbox had decided that its future was workplace collaboration, that email was not core, and — in its own words — that it could not “fundamentally fix” the inbox. On December 7, 2015 it announced that Mailbox and its photo app Carousel would both close.
When the servers went dark on February 26, 2016, the lesson was already written: Mailbox was an acqui-hire that was never built to last, a beloved product acquired chiefly for the people who made it. The gestures it popularized — swipe to archive, snooze for later — outlived the app by years, absorbed into Gmail, Outlook, and Apple Mail. The app itself became a tidy parable about what happens when a product millions queued for becomes, on the acquirer’s balance sheet, a means to an end.
Skype was the service that taught the world it could call anyone, anywhere, for free over the internet — and on May 5, 2025 Microsoft switched it off and folded its users into Teams. Launched on August 29, 2003 by the Swedish entrepreneur Niklas Zennström and the Dane Janus Friis, built by a team of Estonian engineers, Skype turned a personal computer into a phone. “To Skype” became a verb; a grandparent video-calling grandchildren across an ocean became, for a while, the defining image of what the consumer internet was for. At its height around 2013 Microsoft reported some 300 million monthly users.
Skype’s commercial history was a relay of owners who struggled to know what they held. In September 2005 eBay bought it for roughly $2.6 billion, on a theory — that buyers and sellers would want to talk — that never materialized; it took a $1.4 billion writedown in 2007 and sold most of its stake in 2009. In May 2011 Microsoft acquired Skype for $8.5 billion, its largest purchase to that point, and wired it into Windows, the Xbox, and Office; for a few years Skype was simply how people made internet calls.
Then the ground shifted. Apple’s FaceTime made video calling a default on every iPhone; WhatsApp made free calls and messages frictionless for billions; Zoom became the verb of the pandemic that Skype should have been; and Microsoft’s own Teams, launched in 2016, steadily annexed the use cases Skype had pioneered. By 2023 its daily users had fallen to around 36 million, even as Teams crossed hundreds of millions.
On February 28, 2025 Microsoft announced that Skype would retire on May 5, 2025, with users migrated to the free version of Teams or able to export their data. The fate is “Merged” rather than “Shut Down” only on a technicality: contacts and chats carried over to Teams, but the standalone product that invented mass consumer VoIP, after 22 years, was gone. Skype was killed less by any single rival than by the entire category it had created, and finally by the owner that decided one free communications app was enough.