ICQ did not really die with a press conference, a farewell video, or a dramatic product blog written by someone trying to make shutdown sound noble. It died with a short notice, a redirected web page, and a sound people could still hear in their heads. On June 26, 2024, the messenger that taught millions of people what online presence felt like stopped working after nearly 28 years. The official message was blunt enough to feel almost funny: ICQ would stop working, and users could move to VK Messenger or VK WorkSpace instead.
Table of Contents
The strange thing is that most people did not mourn ICQ as software. They mourned a noise. A cartoonish, nasal, impossible-to-forget “uh-oh” or “oh-oh” that once bounced through bedrooms, offices, dorm rooms, cybercafés, family computers, and beige Windows desktops. The messenger itself had accounts, contact lists, status icons, numbers, privacy messes, ads, ownership changes, and a long slow fade. The sound cut through all of that. It was the whole product reduced to less than a second.
A shutdown that sounded older than the web
ICQ’s ending felt unusually quiet because the service had already become a memory before it became unavailable. By the time VK, its final owner, pulled the plug, ICQ was no longer the tool most people used to reach anyone. It had become a reference point, a password-shaped fragment of youth, a green flower icon in the attic of the internet. Coverage of the shutdown kept returning to the same few artifacts: the flower, the number, the buddy list, and that notification sound. Heise called the “Uh-Oh” annoying but unforgettable, the kind of default alert early users still had “in their ears.”
That is what makes ICQ worth opening again mentally, even if the product no longer opens properly. Many dead services leave behind screenshots. ICQ left behind muscle memory. You may forget what its settings panel looked like. You may not remember whether your username had a number, an underscore, or some teen-era flourish you would now deny under oath. But the moment someone writes “uh-oh,” the sound often arrives intact. It is not remembered as a file. It is remembered as an interruption.
ICQ was created in 1996 by Mirabilis, an Israeli software company, and launched at a moment when mainstream internet use still had a sense of ceremony. You logged on. You waited. You heard the modem. You entered a place. Britannica credits Yair Goldfinger, Arik Vardi, Sefi Vigiser, and Amnon Amir as the software developers behind it, and notes that ICQ arrived as a way for personal computer users to communicate instantly with one another.
The name itself was a little joke: ICQ sounded like “I seek you.” That compact bit of wordplay now feels almost too innocent for the internet that followed. It was social software before social software became a growth machine. The service gave each user a number, displayed whether people were online, and made presence feel like a new human sense. Someone was not just reachable. They were there, green-lit and alive behind a small flower.
The last “uh-oh” matters because ICQ helped invent the emotional grammar of being reachable. The web already had chat rooms and IRC before ICQ, but ICQ made one-to-one online attention feel personal, immediate, and portable across a contact list. You did not have to enter a room full of strangers. You could collect your own people. You could see them appear. You could wait for them. You could be disappointed when they stayed offline.
That sounds ordinary now because ICQ’s ideas won so completely that they became invisible. Presence indicators, contact lists, unread alerts, private chats, status signals, user IDs, and the tiny thrill of seeing someone come online are now buried inside every phone. ICQ’s design did not survive as a dominant app. Its assumptions did. Modern messaging is full of richer media, encryption fights, algorithmic surfaces, stickers, reactions, voice notes, and read receipts, but the core emotional loop is still familiar: someone is there, someone wants you, the machine makes a sound.
The little noise that became the product
The “uh-oh” was not polite. It sounded less like a notification and more like a tiny creature catching you doing something. It had a comic bounce to it, almost a slapstick quality. That mattered. Modern notification sounds often try to be neutral, soft, elegant, or brand-safe. ICQ’s alert had a personality that bordered on rude. It barged in.
That personality is why the sound survived the service. A good product sound does not merely announce an event; it teaches the body what the event means. With ICQ, the alert meant someone had crossed the line from elsewhere into your immediate space. It was not background system audio. It was social arrival. The little “uh-oh” said: your quiet is over, someone is here.
Le Monde’s shutdown piece framed the sound as an ancestor of the notification rush that later became normal on smartphones. That is a sharp way to see it. ICQ’s alert did not just tell users they had a message. It trained them to feel the message before they read it. The noise created anticipation, impatience, sometimes irritation, sometimes delight. It turned waiting into a loop.
That tiny loop is now everywhere. Phones have turned the ICQ reflex into a permanent climate. Pings, badges, haptics, banners, typing bubbles, preview lines, delivery ticks, and lock-screen stacks all descend from the same basic trick: interrupt the user with just enough signal to make them want the next piece. ICQ’s version feels primitive only because it was so naked about it. No ambient gradient. No gentle animation. Just a voice-like sound and a blinking envelope.
The reason people still search for the ICQ sound is not only nostalgia. It is evidence from the early emotional web. It captures a phase when online life still felt like an event rather than an environment. A message was not one item in a flood. It was the arrival of a person. The sound carried that difference. It had the weight of scarcity.
That scarcity changed the way people heard it. If the internet was not always on, then an online friend was not always available. Dial-up connections, shared family computers, school schedules, time zones, and unstable access made presence feel fragile. Seeing a contact pop online meant timing had aligned. Hearing the “uh-oh” could feel like the computer had opened a door.
ICQ’s sound also worked because it had no shame about being memorable. Many interface sounds are designed to disappear into use. This one did not disappear. It stuck. It became quoteable as text. “Uh-oh” became a written stand-in for the product, a little sonic logo people could type in comments decades later. When a service’s audio can be written down and still heard by readers, the brand has escaped the screen.
What the ICQ sound carried
| Signal | What it meant then | Why it still lands |
|---|---|---|
| The “uh-oh” alert | Someone sent a message | It tied attention to a voice-like cue |
| The green flower | Someone was online | It made presence visible and cute |
| The UIN | You had a fixed identity | People treated numbers like early internet fingerprints |
| The contact list | Your people were gathered | It made private networks feel manageable |
| The blinking envelope | Something was waiting | It gave unread messages a tiny drama |
The table is small because ICQ’s magic was small. It did not need a feed, a creator economy, a discovery tab, or a daily engagement ritual dressed as community. Its strongest parts were blunt signals: here, away, message, number, sound. The product felt intimate because it was built from cues that users could understand instantly.
The UIN was the social handle before the handle
ICQ’s other great artifact was the UIN, the User Identification Number. Before usernames became identity theater, ICQ gave you digits. Heise points out that the number worked like a telephone number for the PC era, solving a basic problem: computers did not have unique personal identifiers the way phones did.
A number sounds cold until people begin to attach status to it. Early ICQ numbers became a kind of fossil record. Shorter numbers suggested you had arrived earlier. A five-, six-, or seven-digit ICQ number could feel like proof that you had been online before the crowd. It was not just an identifier. It was seniority. It said you were there when the room was still being built.
That is funny now because the web later trained people to fight for names instead of numbers. Handles became personal brands. Domains became real estate. Usernames became scarce cultural property. But ICQ’s numeric identity had a different charge. It was less performative and more infrastructural. You did not craft it. You received it. Then it became yours because other people used it to find you.
The UIN also gave ICQ a strangely bureaucratic intimacy. You could know someone through a number that felt both anonymous and personal. It was not a phone number, but it behaved like one. You could write it down. You could pass it to a friend. You could put it on a personal homepage. You could remember it years later for no rational reason.
Le Monde noted that some users still remembered their ICQ numbers decades later, including people who joked about remembering that number better than a loved one’s phone number. That kind of memory is not about utility. It is about imprinting. Early internet identifiers often fused with selfhood because they arrived when online selfhood still felt new.
The UIN and the “uh-oh” worked together. One made you findable; the other made being found audible. That pairing was the heart of ICQ. The service was not just chat software. It was a machine for turning digital presence into a social event. Someone could seek you. Then the computer would announce that they had succeeded.
Modern platforms tend to hide this machinery behind contact syncing, phone numbers, email discovery, graph imports, and recommended accounts. ICQ made the machinery visible. You had a number. Your friends had numbers. You added them. They appeared. You waited. The sound came. The simplicity made the experience feel almost physical.
Why ICQ felt like a secret door
A lot of early web nostalgia becomes blurry because people confuse the software with the age they were when they used it. ICQ is vulnerable to that. For many users, it belongs to adolescence, first online friendships, long nights, school computers, family PCs, and the thrill of typing things you might not say aloud. But the product itself deserves credit. It caught a real shift in behavior.
Before ICQ, online chat often meant entering shared spaces. ICQ made online conversation feel like a private line. It was not the only tool doing real-time communication, and IRC had deep culture before it, but ICQ packaged the idea for a much broader audience. It lowered the intimidation level. The contact list was a map, not a command line. The interface made the internet feel less like a place you visited and more like a set of people you carried with you.
That is why the product spread so fast. It had the rare early-internet quality of feeling obvious after someone showed it to you. Wired reported in 1998 that AOL was buying Mirabilis in a transaction worth more than $400 million, paying $287 million upfront with contingent payments to follow. At that point ICQ already had an estimated 12 million users worldwide, a startling number for the period.
The acquisition also shows how clearly larger companies understood ICQ’s strategic value. A messenger that stayed on the screen all the time was not just a chat tool; it was a beachhead. Wired quoted AOL’s Steve Case describing the ICQ dashboard as a natural starting point for content, context, and community, language that now sounds like a rough draft of every platform strategy that followed.
ICQ’s innocence, then, has limits. The product was cute, but the business logic around it was already serious. Persistent presence meant persistent attention. A contact list could become a portal. A chat window could become distribution. AOL saw that. Later platforms refined it. The modern internet did not stumble into messaging as infrastructure. Companies learned early that whoever owns the social surface owns the day.
Still, users did not experience ICQ as strategy. They experienced it as access. You could talk to someone across town or across the world without paying for a long call, without waiting for email, without entering a public room, and without pretending the exchange had to be formal. It was casual writing with the rhythm of speech. That combination felt fresh.
Le Monde quotes a sociologist describing how revolutionary it was to “speak by writing” in real time, especially when older modes separated speech and writing more sharply. That phrase catches ICQ’s deep cultural trick. It made typing feel conversational. Not literary, not official, not composed. Just alive.
The sound mattered because it gave that living text a heartbeat. Without the alert, the message could have been another file, another email, another window. With the alert, the message felt embodied. Someone had acted. The system had reacted. You were summoned.
The web learned to ping from tools like this
ICQ’s “uh-oh” now sits in a strange category: the extinct notification that explains the surviving notification culture. It is old enough to feel quaint, but not old enough to be irrelevant. The pattern it helped normalize is still the pattern under modern attention design. A person sends something. The machine interrupts. The user receives a small hit of urgency before meaning arrives.
That separation is crucial. The alert comes before the content. You do not yet know whether the message is romantic, boring, funny, stressful, spammy, or pointless. The sound creates a question. The interface profits from the question. ICQ did this before the question became industrialized.
A modern phone multiplies that question hundreds of times. The ICQ sound was a single doorbell; today’s notification layer is a building full of doorbells. Some are social. Some are commercial. Some are automated. Some are manipulative. Some are useful. The user’s nervous system has to sort them all. ICQ belongs to an earlier moment when the doorbell was still charming because it usually meant a human being.
That does not mean ICQ was pure. Early messaging already had spam, impersonation, security problems, unwanted contact, and the awkwardness of being visible when you did not want to be. Wired’s 1998 acquisition story mentioned security concerns around identity hijacking, even as it noted that those concerns had not slowed user enthusiasm.
Presence itself was a bargain. To know when others were online, you had to become knowable too. The green flower was not just comfort. It was exposure. Away statuses, invisible modes, blocks, authorizations, and privacy settings grew out of that tension. ICQ made people reachable, then forced them to manage the social cost of being reachable.
That tension never left. Every messaging app still negotiates the same bargain. Read receipts, last seen indicators, typing notifications, online dots, activity status, and delivery checks all ask the same question ICQ asked in simpler form: how much of your availability belongs to other people?
ICQ’s “uh-oh” sounds cute partly because we now live inside much less cute descendants of it. Today, a notification may carry work pressure, family obligation, news panic, bank alerts, delivery updates, group-chat noise, promotional nudges, and algorithmic bait. The ICQ alert mostly belonged to a contact list you made by hand. That difference gives the old sound warmth. It was interruption before interruption became a business model.
The long afterlife of a dead messenger
ICQ did not vanish in one clean cultural moment. It faded unevenly across regions, generations, and habits. In some places, MSN Messenger became the bigger teenage memory. In others, AIM dominated. In parts of the Russian-speaking internet, ICQ remained relevant far longer. AOL sold ICQ to Digital Sky Technologies in 2010, a move widely tied to its stronger remaining position in Russia and nearby markets. TechRadar’s later look at the service notes that ICQ still had around 42 million active daily users at the time of that sale.
That late life complicates the simple nostalgia story. For some users, ICQ was not just a 1990s relic. It was a real messenger that survived into the smartphone era, changed owners, adopted mobile features, and tried to keep pace with apps that had younger networks and fresher defaults. TechRadar notes that a 2020 version offered large group chats, private chats, and even a self-chat that acted like rough cloud storage.
The problem was not that ICQ did nothing. The problem was that messaging apps depend on living networks, not just features. A messenger can add tools forever, but if the people you want are elsewhere, the app feels empty. Social software dies first as a habit, then as a contact list, then as infrastructure. The final shutdown merely makes the death official.
That is why the last “uh-oh” lands harder than a version history. It compresses the whole network loss into one sound. Every dead account, every forgotten password, every contact who changed names, every friend who moved to another app, every stranger you once talked to for three hours and never found again — all of that sits behind the joke of the alert.
ICQ’s shutdown notice was not sentimental. The web supplied the sentiment because the product had already planted it years earlier. News stories reached for “uh-oh” in headlines because no other phrase could identify the service so quickly. Heise used it. Engadget used it. Le Monde built its headline around the last “oh oh.” The sound became the obituary’s opening note.
This is rare. Most software dies under the name of the company that owns it. ICQ died under the sound its users remembered. That says more about the quality of the original product than any growth chart. It made an audio mark so specific that writers could summon the whole service with six characters and a hyphen.
The surviving web is full of copies of the sound: videos, ringtone pages, old software archives, forum posts, nostalgia clips, and comments where people type “uh-oh” with the same reflex others use for old startup chimes. This is the internet’s folk museum. Not clean, not official, not always legalistically tidy, but emotionally accurate. People preserve the bits that still trigger memory.
A tiny museum of being online
ICQ is a useful Web Radar subject because it reminds us that the web’s most durable artifacts are not always pages. Sometimes they are sounds, cursors, icons, loading screens, error messages, default avatars, button labels, or little status lights. They survive because they were repeated during emotionally charged use. You do not remember them as design. You remember them as weather.
The “uh-oh” is especially good because it belongs to the pre-smartphone attention era. It is a fossil from the time just before online presence became ambient. A computer sat somewhere. You sat down at it. Your friends were either online or not. Messages arrived in windows. The interface was clunky, but the social feeling was clean enough to understand.
Clean does not mean better. Old internet tools carried their own mess. They could be insecure, intrusive, ugly, unstable, and socially awkward. People romanticize them because distance edits out the bad parts. The ICQ contact list that now feels charming could also be needy, noisy, and full of people you did not want seeing you online. The alert that now feels adorable could become irritating after the tenth message.
Still, the nostalgia is not fake. ICQ captured a first-contact feeling that later platforms could not recreate once everyone was already online. There is no modern equivalent of discovering that written presence can be live. Young users today inherit that fact as normal. ICQ users watched it become normal.
That is the hidden value of revisiting the sound. It turns a dead messenger into a listening exercise. Hear the “uh-oh” now and you hear a web that was still learning how to summon us. The sound is funny because it is crude. It is touching because it is direct. It is unsettling because it points toward the notification world that followed.
A good internet artifact does not only show what a product did. It shows what users were willing to become. ICQ showed that people wanted to be reachable, searchable, interruptible, and visibly present to selected others. It showed that private networks could be built around tiny signals. It showed that typing could feel like hanging out. It showed that a sound could make software feel inhabited.
That may be ICQ’s sharpest lesson for product people. Do not underestimate the small sensory hook. The flower was not just decoration. The UIN was not just account plumbing. The “uh-oh” was not just audio feedback. Together they made the service feel like a place with rituals. Products become memorable when their tiny parts line up with a real user feeling.
ICQ’s final chapter is also a warning. A memorable product is not the same as a durable business. ICQ had a powerful identity, early mass adoption, a huge acquisition, and real influence on the future of messaging. It still lost the daily-use war. Networks move. Defaults harden elsewhere. Younger users form habits on newer tools. A product can be historically important and practically abandoned at the same time.
That split is exactly why the old sound matters. It is the piece that escaped failure. The service shut down. The accounts are gone. The official app is no longer a living social place. But the notification remains playable in memory, quoted in headlines, and instantly recognized by people who were there. ICQ lost the market and kept the echo.
What readers usually ask
Yes. ICQ stopped working on June 26, 2024, according to the shutdown notice reported from its official site and confirmed in coverage at the time. VK’s press service told TASS that the company would focus on VK Messenger and VK WorkSpace instead.
ICQ was created by Mirabilis, an Israeli software company, in 1996. Britannica names Yair Goldfinger, Arik Vardi, Sefi Vigiser, and Amnon Amir as the software developers behind it.
The alert became famous because it was short, weird, human-like, and tied to social arrival. Users heard it when a message came in, so it became emotionally linked to being wanted, interrupted, surprised, or pulled into a conversation. Le Monde’s shutdown piece treated it as an ancestor of the notification dopamine loop now associated with smartphones.
ICQ made online chat feel personal because it centered a private contact list and one-to-one messaging. IRC and other real-time systems already existed, but ICQ packaged presence, identity, and direct messaging in a way that millions of mainstream users could grasp. TechRadar describes ICQ as a centralized service for one-to-one conversations that helped lay groundwork for later messaging services.
People care because ICQ represents the moment online presence became intimate. The service is no longer useful as a messenger, but its signals still explain habits that define digital life now: status, availability, interruption, unread messages, and the tiny thrill of seeing someone appear online.
As a functioning messenger, no. As an internet artifact, yes. ICQ is worth rediscovering through its sounds, screenshots, histories, and memories because it shows how much of modern messaging was already sketched out in the late 1990s.
The echo worth clicking
The best way to revisit ICQ is not to pretend everyone should use it again. That would miss the point. ICQ is interesting because it no longer has to compete. Its value now is archaeological. It lets us inspect an older layer of the social web before the phone swallowed the contact list, before notifications became a constant haze, before every app tried to occupy every idle second.
The last “uh-oh” is funny, but it is not a small thing. It is the sound of a door closing on one version of online life. That version was slower, clumsier, less polished, sometimes worse, sometimes more magical. It was built around the shock of finding other people inside the machine. ICQ did not invent online communication, but it made that shock feel ordinary for millions.
A dead messenger usually becomes irrelevant. ICQ became a shorthand for the first time the internet felt socially alive. The flower icon gave presence a face. The UIN gave identity a number. The alert gave arrival a voice. Those pieces made a product that people could forget using but still remember hearing.
That is why the final “uh-oh” deserves a place in the web’s cabinet of strange treasures. It is not just nostalgia for old software. It is a reminder that the web is made of tiny sensations that later become culture. A sound plays. A window blinks. A person appears. For a second, the whole internet feels like someone came looking for you.
Author:
Jan Bielik
CEO & Founder of Webiano Digital & Marketing Agency

This article is an original analysis supported by the sources cited below
ICQ messenger will stop working from June 26
TASS report on the official shutdown notice and VK’s explanation that it would focus on VK Messenger and VK WorkSpace.
Uh-oh: ICQ is shutting down on June 26
Engadget coverage of the ICQ shutdown and the official direction toward VK alternatives.
Uh-oh – Messenger pioneer ICQ will be shut down at the end of June
Heise background article on ICQ’s shutdown, UIN system, cultural role, and remembered “Uh-Oh” notification sound.
ICQ, le pionnier de la messagerie instantanée, a poussé son dernier oh oh
Le Monde article on ICQ’s final day, the emotional memory of the “oh oh” sound, and the messenger’s place in early online culture.
ICQ
Britannica reference entry on ICQ’s origins, creators, launch period, and acquisition history.
AOL Grabs ICQ Firm
Wired’s 1998 report on AOL’s acquisition of Mirabilis, including the transaction value, user scale, and strategic interest in ICQ.
This pioneering instant messaging platform tried to keep up with the times
TechRadar analysis of ICQ’s later years, ownership changes, mobile-era attempts, and decline.















