View Relay "NoToAllTaxIncrease"

Fingerprint: A2781C952E83B0F07F7749D6977DDB988B480F6F | Family: 1 relay | follow@jisedaiundo-com.invalid | AS2518 | Japan | Linux

Health Status

Consensus
In Consensus (has Running flag)
Flags
Fast, Running, Stable, V2Dir, Valid (5)
BW Verified
Measured
Stability
Overloaded | DOWN 2d 11h 15m ago | UP 92% (1M)
Reachability
N/A
First Seen
2mo 4w 1d ago
BW Weight
0.00% of Network | 18 Mbit/s Observed By Relay
Version
0.4.9.11 Not Recommended
Issues Detected:
  • General Overload Active : Relay reported general overload at 2026-10-10 13:00 UTC. This indicates OOM killer invocation, onionskin queue saturation, or TCP port exhaustion.
    Suggestion: Check CPU/memory with htop. Review logs for "out of memory" or "onionskins" warnings. Consider increasing MaxMemInQueues in torrc. Verify TCP ports available.

Connectivity and Location

Addresses
OR Address
FL1-221-171-92-136.stm.mesh.ad.jp
221.171.92.136:65000
Reachability (Directory Authorities)
Status
Reachability data unavailable
Location
Country
Japan Japan
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS2518
AS Name
BIGLOBE Inc. (BGP.tools)
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
18.49 Mbit/s
Advertised Bandwidth
18.49 Mbit/s
Rate Limit
25.17 Mbit/s
Burst Limit
41.94 Mbit/s
Total Data
1.8 TB (6 months)
1mo: 1.4 TB | 6mo: 1.8 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-13 08:45:07

Measured By
Yes (≥3 authorities)
Network Participation: Consensus Weight: 0.0001% of network (8th pctl) | Guard: N/A | Middle: N/A | Exit: N/A
History
Throughput and write/read, last 6 months Throughput and write/read, last 30 days
1M 6M

Uptime and Stability

Uptime Metrics
Current Status
DOWN 2d 11h 15m ago
Overall Uptime (1M/6M/1Y/5Y)
92.1%/97.6%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
—/87.3%/—/—
Hibernating
No
Timestamps
First Seen
2mo 4w 1d ago (2026-07-15 10:00:00)
Last Seen
2d 11h 15m ago (2026-10-10 22:00:00)
Last Restarted
2d 19h 56m ago (2026-10-10 13:19:12)
Last Changed Address
2026-10-10 06:00:00
[Warning] OVERLOADED — General overload at 2026-10-10 13:00 UTC
General Overload (from /details)
Status
Reported
When
2026-10-10 13:00 UTC (2 days ago)

OOM killer, onionskin queue saturation, or TCP port exhaustion. Flag remains 72h after last event (Tor spec 328).

File Descriptor Exhaustion (from /bandwidth)
Status
Not Reported
Rate Limits (from /bandwidth)

No rate limit data from /bandwidth endpoint.

Recommendations
  • Check CPU/memory: htop
  • Review MaxMemInQueues in torrc
History
Uptime, last 6 months Uptime, last 30 days
1M 6M

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-10-13 00:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
follow@jisedaiundo-com.invalid
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
A2781C952E83B0F07F7749D6977DDB988B480F6F (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

Platform
Linux — Tor 0.4.9.11 on Linux
Version
0.4.9.11 — Not Recommended
Version Status
Obsolete — Update urgently. See torproject.org/download

Exit Health & Policy

DNS Health
Not an exit relay — DNS health testing does not apply.
IPv4 Exit Policy Summary
reject: 
  1-65535
IPv6 Exit Policy Summary
None
Full Exit Policy
reject *:*

Last fetch was at Tue, 13 Oct 2026 09:15:38 GMT.