View Relay "FuzzyVoltage"
Fingerprint: 14D5BB0E0B8CF8D5BDE22F953ED4D50041011F7A |
Family: 1 relay
|
fuzzyvoltage921@cock.li |
AS215365
|
Germany
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- DNS Health
- Healthy (17.8s, 82nd percentile) (via exitdnshealth.1aeo.com)
- BW Verified
- 6/7 BW Auths Measured 88 Mbit/s Median
- Stability
- Not Overloaded | UP 2d 8h 49m ago | UP 87% (1M)
- Reachability
- IPv4: 9/9 | v6: 8/8(Directory Auths)
- BW Weight
- 0.01% of Network | 70 Mbit/s Observed By Relay
- Version
- 0.4.9.15 Recommended
-
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: WFU below threshold
: 0/9 authorities meet guard-wfu (≥98%; 5 needed). E30CF7B3, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 measured 65.1%–90.9%.
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. -
Guard: Time Known below threshold
: 0/9 authorities meet guard-tk (≥8 days; E30CF7B3: ≥5 days 11 hours 43 minutes 50 seconds; 5 needed). E30CF7B3, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 have known this relay for 4.9 days–5.9 days.
Suggestion: Time Known tracks how long authorities have observed your relay. This resets if: 1) Identity key changes, 2) Long downtime makes authorities forget you. Just keep running stably. -
Not eligible for Stable flag
: 1/9 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). E30CF7B3, 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 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. -
High consensus weight deviation
: Large variation in Consensus Weight values across authorities (see 'Cons Wt' column in Per-Authority Details below)
Suggestion: Consensus weight measurements vary significantly between authorities. This can affect traffic distribution. Ensure stable network connection and consistent bandwidth availability.
Addresses
- OR Address
-
threatoff.eu
5.83.158.7:443
[2a14:7c0:1002:1973::]:443 - Exit Address
- 5.83.158.7
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- 8/8 (1 don't test)
Location
- Country
-
Germany
- Interactive Map
- View in RouteFluxMap
Eligibility Flag Vote Details
| Flag | Metric | Status | Relay Value | Threshold Required |
|---|---|---|---|---|
| Running | IPv4 Reachability | Meets (9/9 DA) | 9/9 authorities reached relay | ≥5/9 DA ORPort reachable |
| IPv6 Reachability | Meets (8/8 DA) | 8/8 tested authorities reached relay | ≥5/8 tested (majority) (≥5/8 DA) | |
| Valid | Descriptor | Meets (9/9 DA) | 9/9 authorities assigned Valid | Not blacklisted + valid descriptor (≥5/9 DA) |
| V2Dir | DirPort Available | Meets (9/9 DA) | Tunnelled: Yes (no DirPort) (R) | Tunnelled directory via ORPort or DirPort (≥5/9 DA) |
| Fast | Speed | Meets (9/9 DA) | 31.2 Mbit/s – 152.0 Mbit/s (6 DA measured) 70.9 Mbit/s (3 DA relay-reported) |
≥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 (1/9 DA) | Median: 3.4d (1/9 DA above threshold) Min/Max: 1.2d / 11591.7d (9/9 DA, Voting / Total Eligible) |
≥2.3d - 8.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥12663.9d |
| Uptime | Below (0/9 DA) | 2.4d (R) | ≥5.0d - 5.1d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 31.2 Mbit/s – 152.0 Mbit/s (6 DA measured) 70.9 Mbit/s (3 DA relay-reported) |
≥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 (2/9 DA) | 2/9 DA assigned Stable | ≥2.3d - 8.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥12663.9d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Below (1/9 DA) | 2.4d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.6d Time Known |
|
| Guard | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 31.2 Mbit/s – 152.0 Mbit/s (6 DA measured) 70.9 Mbit/s (3 DA relay-reported) |
≥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 (2/9 DA) | 2/9 DA assigned Stable | ≥2.3d - 8.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥12663.9d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Below (0/9 DA) | Median: 90.4% (0/9 DA above threshold) Min/Max: 65.1% / 90.9% (9/9 DA, Voting / Total Eligible) |
≥98% (≥5/9 DA) | |
| Time Known | Below (0/9 DA) | Median: 5.9d (0/9 DA above threshold) Min/Max: 4.9d / 5.9d (9/9 DA, Voting / Total Eligible) |
≥8 days; E30CF7B3: ≥5 days 11 hours 43 minutes 50 seconds (≥5/9 DA) | |
| Bandwidth | Meets (9/9 DA) | 31.2 Mbit/s – 152.0 Mbit/s (6 DA measured) 70.9 Mbit/s (3 DA relay-reported) |
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-248.0 Mbit/s) (≥5/9 DA) | |
| Exit | Exit Policy | Meets (9/9 DA) | Port 80: Yes | Port 443: Yes (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-11-20 10:15:05).
Capacity (Relay Reported)
- Observed Bandwidth
- 70.95 Mbit/s
- Advertised Bandwidth
- 70.95 Mbit/s
- Rate Limit
- 8.59 Gbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
- 748 GB (1 month)
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-20 10:15:05
- Measured By
-
6/7
Bandwidth Authorities
Not measured by: faravahar - Consensus Weight
- 88.0 Mbit/s (median of 6 measurements)
- Measured Min / Max
- 31.2 Mbit/s / 152.0 Mbit/s
- Deviation
- 120.8 Mbit/s [Warning] High variation
History
Uptime Metrics
- Current Status
- UP 2d 8h 49m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 87.2%/0.0%/0.0%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (87.2%/0.0%/0.0%/0.0%)
- Hibernating
- No
Timestamps
- First Seen
- 6d 20h 15m ago (2026-11-13 14:00:00)
- Last Seen
- 1h 15m 38s ago (2026-11-20 09:00:00)
- Last Restarted
- 2d 8h 49m ago (2026-11-18 01:25:58)
- Last Changed Address
- 2026-11-13 14:00:00
Evaluated 2026-11-20 10:15 UTC. /details snapshot 2026-11-20 09:00:00 UTC (cached 14s ago). /bandwidth snapshot 2026-11-20 02:00:00 UTC (cached 7h ago).
General Overload (from /details)
- Status
- No general overload report in available data
File Descriptor Exhaustion (from /bandwidth)
- Status
- No file-descriptor exhaustion report in available data
Rate Limits (from /bandwidth)
- Status
- No rate-limit report in available data
- Rate Limit
- —
- Burst Limit
- —
- Write counter
- —
- Read counter
- —
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
History
Operator Identity
Source: AROI Validation API — 2026-11-19 23:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- fuzzyvoltage921@cock.li
Family Configuration
- Family Support
- None — No family membership configured
- Effective Members: 0
- none
- Effective Member: 1
14D5BB0E0B8CF8D5BDE22F953ED4D50041011F7A (this relay)
- Alleged Members: 0
- none
- Indirect Members: 0
- none
DNS Health
- Status
- Healthy (avg. 17.8s, 82nd percentile)
- Query Domain
a9bcdf825ad94fc281849da014d9db47.14d5bb0e.tor.exit.validator.1aeo.com- DNS Result
-
Resolved to
64.65.4.1 - Upstream Resolver
-
Cloudflare
(public resolver)
Cloudflare 100% (~49 estimated queries) - Cross-Validation
- 4/4 instances succeeded
- First Hop
- Quintex474 (US) BB271B45E32A938A81B91D9FED0A72441F106834
- Exit Address Used
5.83.158.7- Per-Instance Results
-
Cross Validation Attempt 1: Success, 17.3s (cv1_w1) Cross Validation Attempt 2: Success, 19.7s (cv2_w1) Cross Validation Attempt 3: Success, 22.8s (cv3_w1) Cross Validation Attempt 4: Success, 11.4s (cv4_w1)
IPv4 Exit Policy Summary
reject: 25 119 135-139 445 563 1214 4661-4666 6346-6429 6699 6881-6999
IPv6 Exit Policy Summary
reject: 25 119 135-139 445 563 1214 4661-4666 6346-6429 6699 6881-6999
Full Exit Policy
reject 0.0.0.0/8:* reject 169.254.0.0/16:* reject 127.0.0.0/8:* reject 192.168.0.0/16:* reject 10.0.0.0/8:* reject 172.16.0.0/12:* reject 5.83.158.7:* reject *:25 reject *:119 reject *:135-139 reject *:445 reject *:563 reject *:1214 reject *:4661-4666 reject *:6346-6429 reject *:6699 reject *:6881-6999 accept *:*
Last fetch was at Fri, 20 Nov 2026 10:15:38 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-20 10:15:05).
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 | v6 | 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) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| E30CF7B3 | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Exit | 31.2 Mbit/s (M) | 816.0 Kbit/s | 31.2 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s | 89.1% | 98% | 5.1d | 5d | 2.9d | 3.9d | 2.4d | 5.1d | 2026-11-20 07:26:36 | 31.2 Mbit/s (M) |
| dannenberg (DE) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Exit | 104.0 Mbit/s (M) | 816.0 Kbit/s | 104.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s | 90.5% | 98% | 5.9d | 8d | 3.4d | 8.2d | 2.4d | 5.1d | 2026-11-20 07:26:36 | 104.0 Mbit/s (M) |
| dizum (NL) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, V2Dir, Fast, Exit | 70.9 Mbit/s (R) | 816.0 Kbit/s | 70.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 90.5% | 98% | 5.9d | 8d | 3.4d | 6.8d | 2.4d | 5.1d | 2026-11-20 07:26:36 | 70.9 Mbit/s (R) |
| faravahar (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Exit | 70.9 Mbit/s (R) | 816.0 Kbit/s | 70.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 90.4% | 98% | 5.9d | 8d | 3.4d | 7.0d | 2.4d | 5.1d | 2026-11-20 07:26:36 | 70.9 Mbit/s (R) |
| gabelmoo (DE) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Exit | 152.0 Mbit/s (M) | 816.0 Kbit/s | 152.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s | 90.5% | 98% | 5.9d | 8d | 3.4d | 8.3d | 2.4d | 5.1d | 2026-11-20 07:26:36 | 152.0 Mbit/s (M) |
| longclaw (US) | Yes | Yes | Yes | — | Y | Yes | N/T | Running, Valid, V2Dir, Fast, Exit | 128.0 Mbit/s (M) | 816.0 Kbit/s | 128.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s | 90.4% | 98% | 5.9d | 8d | 3.4d | 9.1d | 2.4d | 5.1d | 2026-11-20 07:26:36 | 128.0 Mbit/s (M) |
| maatuska (SE) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir, Exit | 70.9 Mbit/s (R) | 816.0 Kbit/s | 70.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 90.9% | 98% | 5.8d | 8d | 3.4d | 2.3d | 2.4d | 5.1d | 2026-11-20 07:26:36 | 70.9 Mbit/s (R) |
| moria1 (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, Exit | 88.0 Mbit/s (M) | 8.4 Mbit/s | 88.0 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s | 87.3% | 98% | 4.9d | 8d | 11591.7d | 12663.9d | 2.4d | 5.0d | 2026-11-20 07:26:36 | 88.0 Mbit/s (M) |
| tor26 (AT) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Exit | 76.0 Mbit/s (M) | 816.0 Kbit/s | 76.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s | 65.1% | 98% | 5.3d | 8d | 1.2d | 8.3d | 2.4d | 5.1d | 2026-11-20 07:26:36 | 76.0 Mbit/s (M) |
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
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.
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.

