Port 2552: The Akka Port — How a Default Became a Convention

Port 2552 is unassigned by IANA. No RFC describes it. No official body claimed it. And yet, if you have ever stood up an Akka cluster, you know this port — because it is the default remoting port for Akka Classic, the distributed actor framework built on the JVM.

This is how conventions form on the Internet. One config file, one sensible default, millions of copies.

What Range It Belongs To

Port 2552 falls in the registered port range (1024–49151). These ports are neither the sacred well-known ports (0–1023, requiring root/admin to bind) nor the ephemeral ports the OS hands out temporarily for outgoing connections. Registered ports are the middle ground: anyone can bind to them, but IANA maintains a registry so that services can stake a claim.

Port 2552 never staked that claim. IANA shows it as unassigned.

The Akka Convention

Akka is a toolkit for building concurrent, distributed, and fault-tolerant applications on the JVM. Its remoting system lets actor systems on different machines send messages to each other — by address, the same way you address a letter.

The default configuration for Akka Classic Remoting (using Netty TCP transport) looks like this:

akka {
  remote {
    netty.tcp {
      hostname = "127.0.0.1"
      port = 2552
    }
  }
}

That port = 2552 line is baked into Akka's reference configuration. Every tutorial, every getting-started guide, every cluster example in the Akka documentation shows seed nodes at ports 2551 and 2552. The pair became idiomatic — 2551 for the first node, 2552 for the second.¹

The result: across thousands of real production systems, port 2552 means "there is an Akka actor system here."

The Successor

When Akka introduced the Artery transport (the modern replacement for Classic Remoting), the default port moved to 25520 — the old port, multiplied by ten, with a zero appended. The legacy is written into the new number.²

If you see port 25520, you are looking at a newer Akka deployment. If you see 2552, it is running Classic Remoting — which Akka has deprecated, though deprecation and reality part ways slowly in production infrastructure.

Security Considerations

Akka remoting is not designed to be exposed to the open Internet. It was built for trusted internal networks — data center traffic between nodes you own. An exposed Akka remoting port can allow:

• Remote code execution through serialized message injection
• Cluster membership manipulation
• Information disclosure about actor system internals

If you find port 2552 open on a machine, it should be behind a firewall, accessible only from trusted cluster peers. If it is accessible from the public Internet, that is a misconfiguration worth investigating immediately.

How to Check What's Listening

On Linux/macOS:

# Show what process is using port 2552
ss -tlnp | grep 2552
# or
lsof -i :2552

On Windows:

netstat -ano | findstr :2552

Remotely (check if port is open):

nc -zv hostname 2552
# or
nmap -p 2552 hostname

If you see a Java process listening, you are almost certainly looking at an Akka actor system.

Why Unassigned Ports Matter

The IANA registry is a coordination mechanism, not a law. Any process can bind to any unassigned port. What the registry prevents is two legitimate services independently choosing the same number and creating conflicts at scale.

Port 2552 is a case study in what happens without registration: a popular framework chose it informally, and now it is effectively reserved by convention across a significant portion of the JVM ecosystem. The registry would say "unassigned." The real world would say "Akka."

Unassigned ports are the frontier of the port space — unclaimed land that gets homesteaded by software, defaults, and the inertia of examples that get copied.