View Relay "janitormentor"

Fingerprint: 64A8837A97AF71775C84DE0EDA94552AAEDC424F | Family: 3 relays | PGK <tor at the-goober.net> | AS56322 | Hungary | Linux

Health Status

Consensus
In Consensus (8/9 Directory Auths)
Flags
Running, Valid, V2Dir (3)
BW Verified
0/7 BW Auths Measured 160 Kbit/s Median
Stability
Overloaded | DOWN 2h 15m 43s ago
Reachability
IPv4: 8/9 | v6: None configured(Directory Auths)
First Seen
2h 15m 43s ago
BW Weight
0.00% of Network | 1 Mbit/s Observed By Relay
Version
0.4.9.11 Not Recommended
Issues Detected:
  • Not getting the Fast flag : Only 3/9 authorities vote Fast (5 needed). bastet, dannenberg, gabelmoo, moria1 and tor26 counted this relay as 0 (no measurement, relay-reported bandwidth ignored).
    Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports. A low measurement means the scanners see your relay underperforming compared with other relays that report a similar speed. Clients only build circuits through Fast relays, so a relay near the threshold can gain and lose most of its traffic from one hourly consensus to the next.
  • Guard: requires Fast flag : Guard flag requires having the Fast flag first
    Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports.
  • Guard: requires Stable flag : Guard flag requires having the Stable flag first
    Suggestion: Get Stable flag by maintaining consistent uptime. Stable requires uptime and MTBF at or above network median (typically 2-3 weeks of stable running).
  • Guard: bandwidth below threshold : 0/9 authorities credit this relay with enough bandwidth for Guard (5 needed): at least 16.8 Mbit/s (AuthDirGuardBWGuarantee) or a place in their top 25% (80.0 Mbit/s – 296.0 Mbit/s). dizum, faravahar and longclaw used the relay-reported 1.4 Mbit/s. bastet, dannenberg, gabelmoo, moria1 and tor26 counted this relay as 0 (no measurement, relay-reported bandwidth ignored).
    Suggestion: Guard requires a bandwidth of at least AuthDirGuardBWGuarantee (16.8 Mbit/s by default) or one in the top 25% of relays, judged by each authority the same way as for Fast. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx.
  • Guard: WFU below threshold : 0/9 authorities meet guard-wfu (≥98%; dizum: ≥96.488%; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, moria1 and tor26 measured 0.0%–0.6%.
    Suggestion: WFU measures recent uptime (recent downtime weighs more heavily). To improve: 1) Minimize restarts, 2) Use systemd with Restart=always, 3) Monitor for OOM kills, 4) Schedule updates during low-traffic periods.
  • Not eligible for Stable flag : 0/9 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, moria1 and tor26 do not.
    Suggestion: Stable flag requires uptime/MTBF at or above network median. Keep your relay running continuously for 2-3 weeks. Avoid restarts. Use reliable hardware and network connection.
  • HSDir: requires Fast flag : HSDir flag requires having the Fast flag first
    Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports.
  • HSDir: requires Stable flag : HSDir flag requires having the Stable flag first
    Suggestion: Get Stable flag by maintaining consistent uptime. Stable requires uptime and MTBF at or above network median (typically 2-3 weeks of stable running). Avoid restarts.
  • Low bandwidth authority measurements : Only 0/7 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
    Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.
  • Tor version not recommended : Running Tor version 0.4.9.11 which is not on the recommended list.
    Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases.
  • General Overload Active : Relay reported general overload at 2026-10-30 00:00 UTC. Reported timestamps use hour precision, so the displayed minute is not an exact incident time. The flag does not identify which trigger fired. Investigation paths are Tor's internal OOM handling, dropped ntor onionskins, and TCP port exhaustion.
    Suggestion: Inspect CPU and memory with htop, Tor service logs, host or container memory headroom, and the effective MaxMemInQueues. When the process was killed or restarted, check kernel OOM logs separately. A kernel OOM kill is a different mechanism from Tor freeing memory itself. MetricsPort: tor_relay_load_oom_bytes_total. Broken down by subsys. An increase measures bytes freed by Tor’s internal OOM handling. It is not an invocation count and it is not proof of a kernel OOM kill. Review Tor’s onionskin and drop messages, and whether the CPU is saturated or contended. The general-overload flag does not say this trigger fired. MetricsPort: tor_relay_load_onionskins_total{type="ntor",action="dropped"} and {type="ntor_v3",action="dropped"}. Compare each with the matching action="processed" series. Inspect both supported handshake types. Review Tor logs, socket usage, and the host’s ephemeral-port allocation. On Linux, ss -s and reading net.ipv4.ip_local_port_range are useful starting checks. MetricsPort: tor_relay_load_tcp_exhaustion_total. An increase records additional exhaustion events. See the Tor overload troubleshooting guide.
Notes:
  • Partial IPv4 reachability: 8/9 authorities can reach this relay
    Suggestion: Some authorities cannot reach you: maatuska. This may be temporary or due to geographic routing issues.

Connectivity and Location

Addresses
OR Address
hulkutopia.the-goober.net
91.219.238.221:443
Reachability (Directory Authorities)
IPv4
8/9
IPv6
None configured
Location
Country
Hungary Hungary
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS56322
AS Name
ServerAstra Kft. (BGP.tools)
AS Rarity
Epic (score: 3/5, 0.08% consensus weight, 10 operators)

Flags and Eligibility

Current Flags (3): Running, Valid, V2Dir
Eligible Flags (3): Running: 8/9 | Valid: 8/9 | V2Dir: 8/9 | Fast: 3/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 0/9
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (8/9 DA) 8/9 authorities reached relay ≥5/9 DA ORPort reachable
Valid Descriptor Meets (8/9 DA) 8/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Meets (8/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Below (3/9 DA) 1.4 Mbit/s (3 DA relay-reported)
0 bit/s (5 DA unmeasured, counted as 0)		 ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (0/9 DA) Median: 0.0d (1/9 DA above threshold)
Min/Max: 0.0d / 609.9d (8/9 DA, Voting / Total Eligible)		 ≥5.3d - 8.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9336.2d
Uptime Below (0/9 DA) 0.1d (R) ≥3.5d - 3.6d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (3/9 DA) 3/9 DA assigned Fast
1.4 Mbit/s (3 DA relay-reported)
0 bit/s (5 DA unmeasured, counted as 0)		 ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/9 DA) 1/9 DA assigned Stable ≥5.3d - 8.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9336.2d
Prereq: V2Dir Meets (8/9 DA) 8/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Below (0/9 DA) 0.1d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.8d Time Known
Guard Prereq: Fast Below (3/9 DA) 3/9 DA assigned Fast
1.4 Mbit/s (3 DA relay-reported)
0 bit/s (5 DA unmeasured, counted as 0)		 ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/9 DA) 1/9 DA assigned Stable ≥5.3d - 8.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9336.2d
Prereq: V2Dir Meets (8/9 DA) 8/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 0.1% (0/9 DA above threshold)
Min/Max: 0.0% / 0.6% (8/9 DA, Voting / Total Eligible)		 ≥98%; dizum: ≥96.488% (≥5/9 DA)
Time Known Partial (8/9 DA) Median: 56.7d (8/9 DA above threshold)
Min/Max: 9.7d / 58.4d (8/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 1.4 Mbit/s (3 DA relay-reported)
0 bit/s (5 DA unmeasured, counted as 0)		 ≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-296.0 Mbit/s) (≥5/9 DA)
Exit Exit Policy Below (0/9 DA) Port 80: No | Port 443: No (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/9 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-10-30 03:15:06).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
1.38 Mbit/s
Advertised Bandwidth
1.38 Mbit/s
Rate Limit
8.39 Mbit/s
Burst Limit
25.17 Mbit/s
Total Data
N/A
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-30 03:15:06

Measured By
0/7 Bandwidth Authorities
Not measured by: bastet, dannenberg, faravahar, gabelmoo, longclaw, moria1, tor26
Consensus Weight
160.0 Kbit/s (Unmeasured)
Measured Min / Max
N/A / N/A
Network Participation: Consensus Weight: 0.0000% of network (3th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
DOWN 2h 15m 43s ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
N/A
Hibernating
No
Timestamps
First Seen
2h 15m 43s ago (2026-10-30 01:00:00)
Last Seen
2h 15m 43s ago (2026-10-30 01:00:00)
Last Restarted
2h 59m 44s ago (2026-10-30 00:15:59)
Last Changed Address
2026-10-30 01:00:00
[Warning] OVERLOADED — General overload at 2026-10-30 00:00 UTC

Evaluated 2026-10-30 03:15 UTC. /details snapshot 2026-10-30 02:00:00 UTC (cached 12s ago). /bandwidth snapshot 2026-10-29 19:00:00 UTC (cached 6h 30m ago).

Reported timestamps use hour precision, so the displayed minute is not an exact incident time.

General Overload (from /details)
Status
Reported
When
2026-10-30 00:00 UTC (3 hours ago)

The general-overload flag does not say which trigger fired. Possible paths are Tor’s internal memory handling, dropped ntor handshakes, and TCP port exhaustion. Allium treats a valid report as eligible for 72 hours; that cutoff is not proof the relay recovered then.

File Descriptor Exhaustion (from /bandwidth)
Status
No bandwidth record available for this relay
Rate Limits (from /bandwidth)
Status
No bandwidth record available for this relay
Rate Limit
—
Burst Limit
—
Write counter
—
Read counter
—
What to check
  • Tor internal memory pressure
    Inspect CPU and memory with htop, Tor service logs, host or container memory headroom, and the effective MaxMemInQueues. When the process was killed or restarted, check kernel OOM logs separately. A kernel OOM kill is a different mechanism from Tor freeing memory itself.
    MetricsPort: tor_relay_load_oom_bytes_total — Broken down by subsys. An increase measures bytes freed by Tor’s internal OOM handling. It is not an invocation count and it is not proof of a kernel OOM kill.
  • ntor handshake pressure
    Review Tor’s onionskin and drop messages, and whether the CPU is saturated or contended. The general-overload flag does not say this trigger fired.
    MetricsPort: tor_relay_load_onionskins_total{type="ntor",action="dropped"} and {type="ntor_v3",action="dropped"} — Compare each with the matching action="processed" series. Inspect both supported handshake types.
  • TCP port exhaustion
    Review Tor logs, socket usage, and the host’s ephemeral-port allocation. On Linux, ss -s and reading net.ipv4.ip_local_port_range are useful starting checks.
    MetricsPort: tor_relay_load_tcp_exhaustion_total — An increase records additional exhaustion events.
About these reports and MetricsPort

Allium’s eligibility windows are applied to the reported timestamps: 72 hours for general overload and file-descriptor exhaustion, 24 hours for a rate-limit hit. A report at the cutoff is historical. An older report can remain visible after Onionoo or Allium’s cache still has it. The cutoff does not prove the relay recovered at that moment. Allium caches the bandwidth document for 12 hours by default. The snapshot time is when Onionoo published that document. It is not the relay’s event time, and it is not necessarily the extra-info publication time. Cache age is how old Allium’s copy is.

MetricsPort counters are cumulative. Compare samples, and account for process restarts. A nonzero total alone does not show ongoing activity. Gauges describe current values. An unavailable metric is unknown, not zero. Allium does not have this relay’s MetricsPort readings and does not invent them.

The port below is an example for an endpoint you have already configured. MetricsPort must be enabled with restricted access and must not be exposed publicly. Setup stays in the Tor overload troubleshooting guide. 

curl http://127.0.0.1:9035/metrics

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-10-29 19:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
PGK <tor at the-goober.net>
Family Configuration
Family Support
MyFamily Only (3) — Legacy only. Consider migrating to Happy Families. | View Full Family (3)
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Members: 3 
64A8837A97AF71775C84DE0EDA94552AAEDC424F (this relay)
CDDEC3CC4B0FD5054C99B2D2843DE8B609A4CABA
D9D6C35E932FEF7100A00C99C199356E82DAB7E6
Alleged Member: 1
(they don't list you back) 
73E0EAD7C2A9E9603C0DB7EE4743CCEF935EAC3D (not in the network)
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 Fri, 30 Oct 2026 03:15:42 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-10-30 03:15:06).

Per-Authority Details

Each cell shows: your measured value | authority threshold. Green = meets, red = below. Flags: green = all authorities agree, yellow = partial.

Authority Running Valid Exit MiddleOnly BW Scan
(Authority)		 v4 Flags Fast (BW|T) Guard BW (BW|Threshold) Guard WFU (M|T) Guard TK (M|T) Stable MTBF (M|T) Stable Uptime (Relay|T) Desc Published Cons Wt (Authority)
bastet (US) Yes Yes No — Y Yes Running, Valid, V2Dir 0 bit/s (U) | 816.0 Kbit/s 0 bit/s (U) | 192.0 Mbit/s OR 16.8 Mbit/s 0.0% | 98% 56.7d | 8d 0.0d | 6.2d 0.1d | 3.5d 2026-10-30 00:36:00 1.4 Mbit/s (R)
dannenberg (DE) Yes Yes No — Y Yes Running, Valid, V2Dir 0 bit/s (U) | 816.0 Kbit/s 0 bit/s (U) | 296.0 Mbit/s OR 16.8 Mbit/s 0.3% | 98% 43.0d | 8d 0.1d | 7.3d 0.1d | 3.6d 2026-10-30 00:36:00 1.4 Mbit/s (R)
dizum (NL) Yes Yes No — N Yes Valid, V2Dir, Fast 1.4 Mbit/s (R) | 816.0 Kbit/s 1.4 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 0.1% | 96% 48.3d | 8d 0.0d | 5.3d 0.1d | 3.6d 2026-10-30 00:36:00 1.4 Mbit/s (R)
faravahar (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 1.4 Mbit/s (R) | 816.0 Kbit/s 1.4 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 0.1% | 98% 58.2d | 8d 0.1d | 8.8d 0.1d | 3.6d 2026-10-30 00:36:00 1.4 Mbit/s (R)
gabelmoo (DE) Yes Yes No — Y Yes Valid, V2Dir 0 bit/s (U) | 816.0 Kbit/s 0 bit/s (U) | 264.0 Mbit/s OR 16.8 Mbit/s 0.1% | 98% 58.3d | 8d 0.0d | 8.8d 0.1d | 3.6d 2026-10-30 00:36:00 1.4 Mbit/s (R)
longclaw (US) Yes Yes No — Y Yes Valid, V2Dir, Fast 1.4 Mbit/s (R) | 816.0 Kbit/s 1.4 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 0.1% | 98% 58.4d | 8d 0.0d | 8.9d 0.1d | 3.6d 2026-10-30 00:36:00 1.4 Mbit/s (R)
maatuska (SE) No — — — N No — — — — — — — — —
moria1 (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Stable 0 bit/s (U) | 8.4 Mbit/s 0 bit/s (U) | 192.0 Mbit/s OR 16.8 Mbit/s 0.6% | 98% 9.7d | 8d 609.9d | 9336.2d 0.1d | 3.6d 2026-10-30 00:36:00 1.4 Mbit/s (R)
tor26 (AT) Yes Yes No — Y Yes Valid, V2Dir 0 bit/s (U) | 816.0 Kbit/s 0 bit/s (U) | 272.0 Mbit/s OR 16.8 Mbit/s 0.1% | 98% 56.8d | 8d 0.0d | 8.6d 0.1d | 3.6d 2026-10-30 00:36:00 1.4 Mbit/s (R)

N/T = this authority does not test IPv6 • — = not in this vote • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known • Bandwidth source: (M) bandwidth-scanner measurement, (R) relay-reported, (U) unmeasured, counted as 0

Bandwidth Values Explained:
Measured (M) = An authority's bandwidth-scanner measurement of your relay (Measured= in its vote). An authority that has one uses it for the Fast and Guard flags, and the consensus weight is the median of these measurements when 3 or more authorities have one.
Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (Bandwidth= in every vote). An authority without a measurement uses it for flags, unless it has measurements for enough other relays (ignoring-advertised-bws=1); then your relay counts as 0 (U). It sets the consensus weight only when fewer than 3 authorities measured the relay, capped at 20 KB/s (maxunmeasuredbw) while 3 or more authorities publish measurements.
Not published = The authority has no measurement of your relay in its vote and ignores relay-reported bandwidth, yet it voted Fast or its vote has no measurements at all: it judges your relay by a measurement kept from an earlier bandwidth file (0 if none), which its vote doesn't show.
Why different? A low measurement means the bandwidth scanners see your relay underperforming compared with other relays that report a similar speed. Votes list both values in kilobytes per second. Rules: Assigning flags in a vote, Computing a consensus.
Stable Uptime (Two Data Sources):
Relay Uptime = From Onionoo API (last_restarted field). Self-reported uptime from descriptor. Same value for all authorities.
Authority Threshold = From CollecTor vote files (flag-thresholds stable-uptime). Each authority may have different thresholds.
Why two sources? Vote files contain authority thresholds but not per-relay uptime values. Onionoo aggregates relay descriptors which include uptime.