Submitted or created by: Daniel Stenberg, Richard Ward …
Before Internet Relay Chat existed, digital communication was largely asynchronous. Email, Usenet newsgroups, and bulletin board systems defined online interaction throughout the early and mid-1980s. These systems worked well for sharing information, but they lacked immediacy. Conversations unfolded slowly, and spontaneous interaction between large groups was rare.
Some early real-time systems did exist. Bitnet Relay Chat allowed live text communication but was confined to specific academic networks. Multi-User Dungeons (MUDs) offered shared text environments, yet they were designed primarily as games rather than general communication tools. None of these systems combined simplicity, scalability, and Internet-native design in a way that allowed widespread adoption.
As TCP/IP networks expanded across universities and research institutions, particularly in Europe and North America, demand grew for a real-time, multi-user communication system that could operate across independent networks. IRC emerged to fill that gap.
The Creation of IRC and Its Early Expansion
IRC was invented in August 1988 by Jarkko Oikarinen, a Finnish programmer working at the University of Oulu. Oikarinen’s inspiration came from a combination of existing systems, particularly Bitnet Relay Chat and the multi-user text adventures known as MUDs, which allowed multiple players to interact in shared text Internet Relay Chat was created in August 1988 by Jarkko “WiZ” Oikarinen, a Finnish programmer working at the University of Oulu’s Department of Information Processing Science. IRC began as an enhancement to a bulletin board system running on tolsun.oulu.fi. Jarkko’s initial goal was to modernize the BBS with features inspired by Usenet and real-time messaging, but the chat component quickly became the central focus.
Using code contributions and ideas from Jyrki Kuoppala and Jukka Pihl, Jarkko implemented a lightweight text-based system capable of supporting multiple simultaneous users. Early testing occurred on a single machine, but the design soon evolved to allow multiple servers to link together. This server-to-server model eliminated the need for central control and became one of IRC’s most defining architectural decisions.
Once the software was released beyond the University of Oulu, Kuoppala installed a second server, later known as irc.cs.hut.fi, forming the first IRC network. Additional servers soon appeared at universities in Helsinki and Tampere, followed by expansion across Finland’s academic network (FUNET) and later NORDUnet, connecting Scandinavia to the wider Internet.
By November 1988, IRC had spread internationally. One of the first non-Finnish users, Vijay Subramaniam, helped introduce IRC to North American universities. By mid-1989, around 40 servers were online worldwide. Although user counts remained small, IRC had proven that global, real-time communication over TCP/IP was both practical and scalable.
Early Software, Clients, and Community Growth
As IRC usage expanded, usability became increasingly important. In 1989, Michael Sandrof released ircII, a client that significantly improved the user experience. It introduced advanced command handling, scripting, and support for managing multiple channels efficiently. ircII became the dominant IRC client for years and helped standardize many conventions still in use today.
Early IRC users were primarily academics, programmers, and technically inclined hobbyists with access to university or research networks. The ability to communicate instantly across continents fostered a strong sense of collaboration. IRC became a place to debug code, exchange technical knowledge, organize projects, and socialize in ways that were previously impossible.
The platform’s flexibility encouraged experimentation. Users began writing scripts and bots to automate tasks such as moderation, information retrieval, and entertainment. These early automation efforts laid the foundation for IRC’s long-standing bot culture and influenced later chat platforms.
Network Splits and the Emergence of Major IRC Networks
IRC’s decentralized design allowed rapid growth, but it also made governance difficult. Disagreements over configuration, security, and development direction frequently resulted in network splits rather than centralized resolution.
In 1990, attempts to collaboratively develop a new server version on a test network called ChNet collapsed due to internal disputes. Later that year, a major conflict emerged when a loosely managed network—later referred to as A-net—allowed unrestricted server connections, leading to widespread nickname collisions and abuse.
When the problematic server eris.berkeley.edu refused to impose stricter controls, it was quarantined, triggering the creation of EFnet (Eris-Free Network). EFnet quickly became the dominant IRC network as most major servers joined it, while A-net gradually disappeared.
Additional networks soon followed. Short-lived efforts like TubNet reflected growing frustration with instability, while more enduring forks focused on structural reform. In 1992, Undernet emerged with the goal of reducing bandwidth usage and addressing channel chaos. It introduced timestamps, improved routing, and centralized services that allowed channel registration and protection, marking a significant shift in how IRC networks operated.
Standardization, Services, and Divergence
In May 1993, the IRC protocol was formally documented as RFC 1459. While it provided a baseline specification, it deliberately excluded many widely used features such as CTCP, text formatting, and character encoding. As a result, networks continued to extend the protocol independently, increasing divergence over time.
In 1994, Undernet itself split, giving rise to DALnet. DALnet emphasized user experience and stability, introducing features that reshaped expectations for IRC usage: nickname ownership, channel registration, longer nicknames, and extensive network-wide moderation tools. Many of these features were implemented in 1995 and became standard on later networks.
By the mid-1990s, philosophical and technical disagreements culminated in The Great Split of 1996, which created IRCnet. Regional differences became more pronounced, with European and North American networks evolving separately. By the late 1990s, IRC consisted of several major networks, each with distinct policies, cultures, and technical extensions.
Cultural Impact and Peak Popularity
Throughout the 1990s and early 2000s, IRC became a central hub for online culture. Gamers used it to organize multiplayer matches and clans. Hobbyists formed communities around shared interests. Developers relied on IRC for real-time collaboration, support, and coordination, particularly within the growing open-source movement.
IRC also played a role in real-world events. During the Gulf War in 1991, IRC carried live discussions and reports, demonstrating its value as a real-time information platform. Over time, informal social norms emerged—channel operators, etiquette rules, and slang—that shaped early Internet culture and influenced later online communities.
User numbers peaked in the early 2000s. Several major networks regularly exceeded 100,000 daily users, with QuakeNet briefly surpassing 200,000. Despite its text-only interface, IRC had become one of the most widely used real-time communication systems on the Internet.
Decline, Continuity, and Lasting Influence
As the Internet shifted toward consumer-friendly platforms, IRC faced increasing competition from graphical instant messaging services such as AIM, ICQ, and MSN Messenger, followed later by web-based and mobile chat applications. These platforms offered easier setup, multimedia features, and centralized moderation, appealing to a broader audience.
IRC usage declined steadily after the mid-2000s, but the protocol never disappeared. Instead, it became more specialized. Networks like Freenode—later replaced in 2021 by Libera.Chat after a major administrative split—continued to serve developers and open-source communities. EFnet, Undernet, and IRCnet remain active, though on a smaller scale.
IRC’s influence extends far beyond its current user base. Modern platforms such as Slack, Discord, and Microsoft Teams inherit core concepts pioneered by IRC: channels, role-based permissions, bot automation, and real-time text collaboration. IRC demonstrated that decentralized, global communication could function without corporate ownership or heavy infrastructure.
Decades and decades more after its creation, IRC remains a living piece of Internet history. Its longevity is not the result of constant reinvention, but of a simple, robust design that solved a fundamental problem—and solved it well.