Every couple of months, someone publishes a piece titled "IRC is dead" or "The decline of IRC" or "Why nobody uses IRC anymore." I've been reading these obituaries since about 2005. At some point you'd think the patient would have the courtesy to actually die.
IRC isn't what it was in 2003. That much is obviously true. But the gap between "not at peak popularity" and "dead" is enormous, and the people writing these pieces rarely bother to check who's actually using IRC and why.
The Death Narrative
The "IRC is dead" narrative usually goes something like this: IRC peaked in the early 2000s with millions of users. Then MSN Messenger, AIM, and Skype took the casual users. Facebook Messenger and WhatsApp took the social users. Slack took the workplace users. Discord took the gaming and community users. What's left?
The narrative isn't entirely wrong — each of those transitions did reduce IRC's user base. But it conflates "fewer total users" with "dead," which is like saying that jazz is dead because fewer people listen to it than pop music. Something can be a niche without being extinct.
The Actual Numbers
Let's look at what we can measure. Libera.Chat, the largest IRC network as of 2026, consistently hosts between 40,000 and 50,000 simultaneous users. OFTC hosts another 10,000-15,000. EFnet, IRCnet, Undernet, QuakeNet, and other networks add tens of thousands more. In total, there are probably 100,000-150,000 unique users connected to public IRC networks at any given time.
That's not counting private IRC networks. Companies, hackerspaces, gaming communities, and other organizations run their own IRC servers that don't appear in public statistics. Some of these are small (a few dozen users), some are substantial (thousands). There's no way to measure this accurately, but it's a non-trivial additional user base.
Is 150,000 simultaneous users a lot? Compared to Discord's hundreds of millions of registered users, no. Compared to Slack's millions of daily active users, no. But compared to, say, the number of people using Matrix (the most often-cited open alternative to IRC), it's competitive. And compared to zero — which is what "dead" would mean — it's significant.
Who Still Uses IRC
The remaining IRC user base isn't random. It's concentrated in specific communities where IRC's properties are genuinely valued:
Open-source development: This is IRC's stronghold. The Linux kernel, GCC, LLVM, PostgreSQL, many Apache projects, Python, Rust, and hundreds of smaller projects maintain IRC channels (primarily on Libera.Chat and OFTC) as their official or semi-official communication channels. For many open-source developers, IRC is where work happens.
System administration and DevOps: Sysadmins tend to prefer tools that are lightweight, scriptable, and don't require a web browser. IRC fits all three criteria. Many data centers, hosting companies, and DevOps teams use IRC for real-time communication and alerting.
Security research: The security community has deep roots in IRC and many researchers continue to use it, particularly for informal knowledge exchange and coordination around vulnerability disclosure.
Academic and research communities: Some research groups, particularly in computer science and physics, maintain IRC channels for collaboration. The protocol's simplicity and text-only nature make it accessible from any environment, including remote servers and restricted networks.
Privacy-conscious users: IRC can be used over Tor, requires no personal information to participate, and generates no user profile data. For people who value communication privacy, this is significant.
What IRC Does Better
IRC persists because it has genuine advantages that no modern platform fully replicates:
Simplicity: An IRC client uses negligible system resources. You can run irssi on a server with 256MB of RAM. Try running the Discord client on that. Or Slack. The resource efficiency of text-based IRC is unmatched.
Scriptability: IRC clients like irssi and WeeChat have powerful scripting interfaces. You can automate almost anything — monitoring, alerting, bot interaction, log processing. This makes IRC integrate naturally into sysadmin and developer workflows.
No vendor lock-in: IRC is an open protocol. You can choose any client, any server, any network. You can run your own server. You can switch networks without losing your tools. Your data isn't trapped in anyone else's platform.
No account required: On many networks, you can connect and participate without registering anything. No email, no phone number, no real name. For quick, anonymous participation, nothing matches this.
Transparency: IRC's protocol is text-based and well-documented. You can see exactly what your client sends and receives. There's no opaque binary protocol, no hidden telemetry, no mysterious API calls. For security-minded users, this transparency is valuable.
Bouncers and logging: With a bouncer like ZNC, you can have persistent connections, message playback, and searchable logs on your own infrastructure. You control the data, not a third-party service.
What IRC Does Worse
It would be dishonest not to acknowledge IRC's real weaknesses:
No built-in history: When you join a channel, you see nothing before your arrival unless the network or a bot provides some kind of playback. This is the single biggest barrier to adoption. Modern users expect to scroll back and see what they missed.
No rich media: IRC is text. You can share URLs, but there's no inline image display, no file uploads, no reactions, no threads. For communities that communicate through screenshots, code snippets with syntax highlighting, and embedded media, this is a real limitation.
Setup complexity: Getting IRC working well — with a bouncer for persistence, SASL for authentication, TLS for encryption, proper client configuration — requires more effort than signing up for Discord. The learning curve deters casual users.
Discovery: Finding active channels and communities on IRC requires knowing where to look. There's no equivalent of Discord's server directory or Slack's public workspace listings. This makes IRC invisible to people who don't already know about it.
Mobile experience: While IRC clients exist for mobile platforms, the experience is generally inferior to purpose-built mobile chat apps. Push notifications, background connectivity, and resource usage on mobile are all challenges that IRC clients haven't fully solved.
Bridges and Interoperability
One of the most interesting developments in the IRC ecosystem is bridging — connecting IRC channels to other platforms. Tools like Matterbridge, Heisenbridge (for Matrix), and various custom bots relay messages between IRC and Discord, Matrix, Slack, and other platforms.
This allows communities to maintain their IRC presence while accommodating users who prefer other platforms. It's not perfect — some features don't translate well across protocols, and bridged messages can feel awkward — but it's a pragmatic solution that keeps IRC relevant in a multi-platform world.
The Matrix protocol, in particular, has deep IRC integration. Many Matrix users connect to IRC channels through built-in bridges, and some IRC channels are now majority-Matrix users without the IRC regulars even noticing. Whether this is good (IRC remains accessible) or bad (IRC becomes a backend for a different protocol) is debatable.
The Future of IRC
IRC isn't going to reclaim its early-2000s dominance. That era is over, and the communication landscape has diversified permanently. But IRC also isn't going to disappear. Its user base is self-selecting for people who value its specific properties — simplicity, openness, scriptability, privacy — and those people aren't switching to Discord any time soon.
The IRCv3 working group continues to extend the protocol with modern capabilities — message tags, labeled responses, server-time, account tracking, and other features that address IRC's historical limitations without breaking its fundamental simplicity. These extensions make IRC more competitive with modern platforms while preserving what makes it distinct.
My prediction — for whatever a prediction from a guy who's been wrong about technology more times than he'd like to admit is worth — is that IRC will stabilize at roughly its current level. Not growing, not dying. A permanent niche, like Emacs or FreeBSD or vinyl records. Used by a dedicated community that knows exactly what it wants and has no interest in switching to whatever's fashionable this year.
And honestly? That's fine. Not everything needs to be mainstream to be valuable.
Frequently Asked Questions
How many people use IRC in 2026?
Approximately 100,000-150,000 users are connected to public IRC networks at any given time, with Libera.Chat hosting the largest share (40,000-50,000). Private IRC networks add an unknown but significant additional user base. The total is far below IRC's peak of millions of simultaneous users in the early 2000s but remains substantial.
What's the best IRC network to join in 2026?
For open-source and technical communities, Libera.Chat is the most active network. OFTC is a strong alternative, particularly for Debian-related projects. For the traditional IRC experience, EFnet and IRCnet remain active. The best network depends on what communities you want to participate in.
Is Discord replacing IRC?
Discord has absorbed much of the casual and gaming-oriented user base that IRC once served. However, the communities that remain on IRC — primarily open-source developers, sysadmins, and privacy-conscious users — have largely chosen IRC deliberately over Discord. The two platforms serve different user populations with different priorities.
Can IRC and Matrix coexist?
They already do. Matrix bridges allow Matrix users to participate in IRC channels and vice versa. Several major IRC channels are bridged to Matrix rooms, creating a hybrid community that spans both protocols. Whether this bridging strengthens IRC (by expanding its reach) or weakens it (by making the native IRC experience less essential) remains an open question.
FAQ
Is IRC dead?
No. While concurrent user counts have dropped from peaks of over a million in the early 2000s, IRC remains actively used by open-source projects, security communities, and technical users. Libera.Chat alone has around 50,000 users.
What replaced IRC?
Discord, Slack, and Matrix have taken market share for different use cases. Discord dominates gaming and general communities, Slack dominates enterprise, and Matrix targets federated communication. None fully replaces IRC's simplicity.
Should I start a new project on IRC?
It depends on your audience. For open-source developer communities, IRC (especially Libera.Chat) remains viable. For broader audiences, Matrix with an IRC bridge or Discord may have lower friction for new users.