Operating a Tor Relay from Japan: Scarcity, Network Diversity, and Contribution

Japan has world-class broadband infrastructure, extensive fiber deployment, major Internet exchanges, and sophisticated hosting providers.

Yet the number of publicly visible Tor relays in Japan can be surprisingly small—often only a few dozen Running relays in a given consensus snapshot.

The apparent contradiction becomes easier to understand when broadband speed is separated from public-server suitability.

1. Fast Internet Does Not Automatically Mean Relay-Friendly Internet

A Tor public relay must accept inbound connections from the Internet.

A connection can deliver:

1 Gbit/s download

while still being unsuitable for hosting public services.

The important distinction is:

outbound Internet access
vs.
inbound public reachability

2. IPv4-over-IPv6 in Japan

Japanese broadband increasingly uses technologies such as:

• DS-Lite
• MAP-E
• other IPv4-over-IPv6 mechanisms

These systems can provide excellent ordinary Internet performance while complicating IPv4 server hosting.

With DS-Lite, IPv4 NAT commonly occurs in the provider network rather than on the customer’s own router.

This can prevent arbitrary inbound IPv4 port forwarding.

MAP-E may provide more flexibility, but the customer can still have only a restricted subset of ports from a shared IPv4 address.

For public Tor relay operation, this matters greatly.

3. A Public IPv4 Address Remains Valuable

A traditional public IPv4 connection allows a straightforward architecture:

Public IPv4
     ↓
Router/NAT
     ↓
TCP port forwarding
     ↓
Tor ORPort

This remains one of the simplest residential environments for operating a public relay.

As such connections become less common, the number of technically capable potential home relay operators also decreases.

4. Router Connection Capacity Matters

A Tor relay can maintain thousands of concurrent TCP sessions.

That is a very different workload from ordinary web browsing.

A consumer router that performs perfectly for:

streaming
gaming
web browsing
video conferencing

may behave poorly when maintaining several thousand NAT/conntrack states for long periods.

Relay hosting therefore favors routers with:

• sufficiently large connection-tracking tables
• reliable firmware
• adequate RAM
• stable CPU performance
• predictable port-forwarding behavior

5. Continuous Operation Is Another Barrier

A useful public relay should ideally stay online continuously.

This means the operator must be willing to provide:

24/7 server uptime
electricity
bandwidth
maintenance
security updates
stable networking

This is more commitment than simply running Tor Browser occasionally.

6. Public Relay IP Reputation Can Discourage Home Operators

A public Tor relay’s IP address is intentionally listed in Tor directory data.

Some third-party anti-abuse systems do not carefully distinguish:

Tor Guard
Tor Middle
Tor Exit

and may broadly classify the address as:

Tor-related IP

This can occasionally cause:

• additional CAPTCHAs
• signup restrictions
• anti-fraud challenges
• service blocks

A non-exit relay does not send ordinary Tor users’ public Internet traffic from its IP, so its abuse profile is dramatically different from an Exit. Nevertheless, coarse reputation systems can still create inconvenience.

7. Exit Relays Have an Even Higher Barrier

Running an Exit from a residential connection is a completely different risk category.

Public Internet destinations see the Exit address as the source of Tor users’ outgoing connections.

This can generate:

• abuse complaints
• copyright complaints
• automated blocks
• legal misunderstandings

Consequently, even people willing to operate Middle or Guard relays may reasonably refuse to operate Exits.

8. Relay Count Reflects Operator Culture as Much as Infrastructure

Tor relays do not generate direct financial rewards.

Running one is usually motivated by:

• privacy advocacy
• research
• technical interest
• public-interest infrastructure
• support for censorship resistance

A country can therefore have excellent broadband and still have relatively few Relay operators.

Conversely, one university, privacy organization, or relay-friendly hosting provider can operate many relays and noticeably increase another country’s count.

9. One Relay Is Not Necessarily One Operator

A country showing:

60 Running relays

does not necessarily have 60 independent operators.

One organization may run:

5
10
20

relay instances.

For network resilience, operator diversity therefore matters alongside raw relay count.

10. Geographic and ASN Diversity

A relay can contribute more than raw bandwidth.

Consider two scenarios:

Scenario A:
10 new relays
all in one data center
all in one ASN
all operated by one organization

versus:

Scenario B:
several relays
different operators
different ASNs
different access networks

Scenario B adds stronger infrastructure diversity even with fewer total machines.

11. Measuring a Single Relay’s Numerical Contribution

If a country has:

60 Running relays

then one additional relay represents approximately:

1 / 60 ≈ 1.7%

of the relay count.

This is a useful way to understand visibility, but it must not be confused with:

1.7% of national Tor bandwidth

or:

1.7% of national consensus weight

Those depend on measured performance.

12. Country Counts Are Dynamic

Tor relay counts change from one consensus to another.

Reasons include:

• new relays joining
• maintenance
• server reboots
• temporary network failures
• relays shutting down
• public IP changes
• reachability changes
• GeoIP classification changes

A count such as:

58

should therefore be interpreted as:

The number of relays considered Running in that particular network snapshot.

It is not a permanent national registry.

13. Country Is Determined from IP Geolocation

A relay does not declare:

Country Japan

in its Tor configuration.

Public Tor metrics derive the country from the relay’s public OR address using GeoIP data.

Similarly, ASN information is inferred from Internet routing databases.

As a result:

public IP
  ↓
GeoIP → country
  ↓
BGP data → ASN

Conclusion

Japan’s small Tor relay population is not evidence of weak Internet infrastructure.

It reflects the intersection of:

modern shared-IPv4 access architectures
public-server reachability requirements
residential router limitations
continuous-operation requirements
IP reputation side effects
lack of financial incentive
limited operator participation

In such an environment, an independently operated, stable relay on a distinct network can provide value far beyond simply adding one more number to a country count.