View Relay "ididnteditheconfig"

Fingerprint: 393D3E72CA5A2E03C1B6EB785F822D318FC41CAC | Family: 1 relay | 0xFFFFFFFF Random Person <nobody AT... | AS39287 | Sweden | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, Fast, Exit (4)
DNS Health
Relay Unreachable (via exitdnshealth.1aeo.com)
BW Verified
6/7 BW Auths Measured 136 Kbit/s Median
Stability
Not Overloaded | UP 10h 15m 38s ago | UP 62% (1M)
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen
1w 2d 6h ago
BW Weight
0.01% of Network | 123 Mbit/s Observed By Relay
Version
0.4.9.8 Recommended
Issues Detected:
  • 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 : Weighted Fractional Uptime 57.9% is below 98% requirement
    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 : Time Known 6.5 days is below 8 days requirement (1.5 more days needed)
    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 : Uptime or MTBF below network median for most authorities
    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.
  • HSDir: requires V2Dir (tunnelled-dir-server) : HSDir requires the relay to support tunnelled directory requests (V2Dir flag). This relay is missing V2Dir — the descriptor likely does not include tunnelled-dir-server, usually because DirCache 0 is set in torrc.
    Suggestion: Remove DirCache 0 from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includes tunnelled-dir-server. You can check with: grep tunnelled-dir-server /var/lib/tor/cached-descriptors
  • HSDir: WFU below threshold : WFU 57.9% below 98% required for HSDir
    Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency.
  • 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.

Connectivity and Location

Addresses
OR Address
45.142.141.134:9721
[2a0a:3840:8078:141:0:2d8e:8d86:1337]:9721
Exit Address
45.142.141.134
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Sweden Sweden
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS39287
AS Name
Materialism s.r.l. (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 7 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, Fast, Exit
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 9/9
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 Below (0/9 DA) No DirPort, no tunnelled-dir-server (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 123.2 Mbit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (1/9 DA) Median: 0.7d (1/9 DA above threshold)
Min/Max: 0.7d / 16786.5d (9/9 DA, Voting / Total Eligible)		 ≥21.2d - 51.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥340.7d
Uptime Below (0/9 DA) 0.4d (R) ≥13.4d - 13.7d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/9 DA) 1/9 DA assigned Stable ≥21.2d - 51.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥340.7d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 58.3% (0/9 DA above threshold)
Min/Max: 57.0% / 59.0% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 6.4d (0/9 DA above threshold)
Min/Max: 6.1d / 6.6d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (1/9 DA) 1/9 DA assigned Stable ≥21.2d - 51.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥340.7d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 58.3% (0/9 DA above threshold)
Min/Max: 57.0% / 59.0% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 1.6 more days) Median: 6.4d (0/9 DA above threshold)
Min/Max: 6.1d / 6.6d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 123.2 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.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-05-27 10:15:07).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
123.16 Mbit/s
Advertised Bandwidth
123.16 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
717 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-05-27 10:15:07

Measured By
6/7 Bandwidth Authorities
Not measured by: dannenberg
Median Measurement
136.0 Kbit/s
Min / Max
80.0 Kbit/s / 336.0 Kbit/s
Deviation
256.0 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0109% of network (64th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0328% (47th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 10h 15m 38s ago
Overall Uptime (1M/6M/1Y/5Y)
62.7%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (62.7%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
1w 2d 6h ago (2026-05-18 04:00:00)
Last Seen
1h 15m 38s ago (2026-05-27 09:00:00)
Last Restarted
10h 15m 38s ago (2026-05-27 00:00:00)
Last Changed Address
2026-05-18 04:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-05-27 03:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
0xFFFFFFFF Random Person <nobody AT example dot com>
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
393D3E72CA5A2E03C1B6EB785F822D318FC41CAC (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

Platform
Linux — Tor 0.4.9.8 on Linux
Version
0.4.9.8 — Recommended
Version Status
Recommended

Exit Health & Policy

DNS Health
Status
Relay Unreachable (failed last 1 scan)
Error
Tor Circuit Error: Construction timed out
First Hop
DFRI94 (SE) D83908874C184E62470B6BABF43A262C08842030
Exit Address Used
45.142.141.134
Tested: 2026-05-26 19:06:02 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
reject: 
  25
  119
  135-139
  445
  563
  1214
  4661-4666
  6346-6429
  6699
  6881-6999
IPv6 Exit Policy Summary
None
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 45.142.141.134:*
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 Wed, 27 May 2026 10:15:37 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-05-27 10:15:07).

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 v6 Flags Fast (Relay|T) Guard BW (Relay|Threshold) Guard WFU (M|T) Guard TK (M|T) Stable MTBF (M|T) Stable Uptime (Relay|T) HSDir WFU (M|T) HSDir TK (M|T) Desc Published Cons Wt (Authority)
bastet (US) Yes Yes Yes — Y Yes Yes Running, Valid, Fast, Exit 123.2 Mbit/s | 816.0 Kbit/s 123.2 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 57.9% | 98% 6.5d | 8d 0.7d | 50.5d 0.4d | 13.4d 57.9% | 98.0% 6.5d | 1.0d 2026-05-27 00:00:00 128.0 Kbit/s
dannenberg (DE) Yes Yes Yes — Y Yes Yes Running, Valid, Fast, Exit 123.2 Mbit/s | 816.0 Kbit/s 123.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 59.0% | 98% 6.4d | 8d 0.7d | 46.6d 0.4d | 13.7d 59.0% | 98.0% 6.4d | 1.0d 2026-05-27 00:00:00 80.0 Kbit/s
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, Fast, Exit 123.2 Mbit/s | 816.0 Kbit/s 123.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 58.2% | 98% 6.6d | 8d 0.7d | 21.2d 0.4d | 13.7d 58.2% | 98.0% 6.6d | 1.0d 2026-05-27 00:00:00 80.0 Kbit/s
faravahar (US) Yes Yes Yes — N Yes Yes Running, Valid, Fast, Exit 123.2 Mbit/s | 816.0 Kbit/s 123.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 58.7% | 98% 6.4d | 8d 0.7d | 51.7d 0.4d | 13.7d 58.7% | 98.0% 6.4d | 1.0d 2026-05-27 00:00:00 80.0 Kbit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, Fast, Exit 123.2 Mbit/s | 816.0 Kbit/s 123.2 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 58.3% | 98% 6.6d | 8d 0.7d | 53.0d 0.4d | 13.8d 58.3% | 98.0% 6.6d | 1.0d 2026-05-27 00:00:00 168.0 Kbit/s
longclaw (US) Yes Yes Yes — Y Yes — Running, Valid, Fast, Exit 123.2 Mbit/s | 816.0 Kbit/s 123.2 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 58.7% | 98% 6.4d | 8d 0.7d | 58.0d 0.4d | 13.7d 58.7% | 98.0% 6.4d | 1.0d 2026-05-27 00:00:00 136.0 Kbit/s
maatuska (SE) Yes Yes Yes — Y Yes Yes Running, Valid, Fast, Exit 123.2 Mbit/s | 816.0 Kbit/s 123.2 Mbit/s | 328.0 Mbit/s OR 16.0 Mbit/s 58.2% | 98% 6.3d | 8d 0.7d | 24.6d 0.4d | 13.5d 58.2% | 98.0% 6.3d | 1.0d 2026-05-27 00:00:00 280.0 Kbit/s
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, Fast, Stable, Exit 123.2 Mbit/s | 8.4 Mbit/s 123.2 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 57.0% | 98% 6.1d | 8d 16786.5d | 340.7d 0.4d | 14.2d 57.0% | 98.0% 6.1d | 9.9d 2026-05-27 00:00:00 336.0 Kbit/s
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, Fast, Exit 123.2 Mbit/s | 816.0 Kbit/s 123.2 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 58.9% | 98% 6.4d | 8d 0.7d | 54.0d 0.4d | 13.8d 58.9% | 98.0% 6.4d | 1.0d 2026-05-27 00:00:00 168.0 Kbit/s

— = not tested/available • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known

Bandwidth Values Explained:
Relay Reported = Your relay's self-reported bandwidth from its descriptor (observed_bandwidth). Used for flag eligibility (Guard, Fast).
Authority Measured = Bandwidth measured by authority's sbws scanner. Used for consensus weight (path selection probability).
Why different? Authorities verify your reported bandwidth independently. 6 of 9 authorities run bandwidth scanners; 3 use relay-reported values directly.
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.