View Relay "obzgs5tbmn4q"

Fingerprint: CBB1D64A64085AA0BC71CE592CBE5BBCFD738FBF | Operator: obzgs5tbmn4q.org (16 relays) ✓ Validated | Family: 16 relays | email:obzgs5tbmn4q[]proton.me... | AS215659 | United States of America | Linux

Consensus
In Consensus (8/8 Directory Auths)
BW Verified
5/5 BW Auths Measured 36 Kbit/s Median
Stability
Not Overloaded | UP 2d 22h 40m ago | UP 87% (1M)
Reachability
IPv4: 8/9 (Directory Auths)
BW Weight
0.00% of Network | 40 Mbit/s Observed By Relay
Version
0.4.9.6 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 90.8% 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.
  • 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: WFU below threshold : WFU 90.8% 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.
Notes:
  • Partial IPv4 reachability: 8/9 authorities can reach this relay

Addresses
OR Address
45.38.20.240:9007
[2a0f:85c1:356:1b63::1]:9007
Exit Address
45.38.20.240
Reachability (Directory Authorities)
IPv4
8/9
Location
Country
United States of America United States of America
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS215659
AS Name
Aokigahara SRL (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 4 operators)

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (5): Running: 8/8 | Valid: 8/8 | V2Dir: 8/8 | Fast: 8/8 | Stable: 2/8 | HSDir: 0/8 | Guard: 1/8 | Exit: 8/8
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (8/8 DA) 8/8 authorities reached relay ≥5/8 DA ORPort reachable
IPv6 Reachability Meets (4/4 DA) 4/4 tested authorities reached relay ≥3/4 tested (majority) (≥3/4 DA)
Valid Descriptor Meets (8/8 DA) 8/8 authorities assigned Valid Not blacklisted + valid descriptor (≥5/8 DA)
V2Dir DirPort Available Meets (8/8 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/8 DA)
Fast Speed Meets (8/8 DA) 41.0 Mbit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (1/8 DA) Median: 0.5d (1/8 DA above threshold)
Min/Max: 0.1d / 20570.5d (8/8 DA, Voting / Total Eligible)
≥16.5d - 58.9d (varies) (≥5/8 DA)
Uptime Below (0/8 DA) 2.9d (R) ≥10.4d - 10.9d (varies) (≥5/8 DA)
HSDir Prereq: Fast Meets (8/8 DA) 8/8 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (2/8 DA) 2/8 DA assigned Stable ≥16.5d - 58.9d (varies) (≥5/8 DA)
Prereq: V2Dir Meets (8/8 DA) 8/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Below (1/8 DA) Median: 91.4% (1/8 DA above threshold)
Min/Max: 58.2% / 98.2% (8/8 DA, Voting / Total Eligible)
≥98.0% (≥5/8 DA)
Time Known Meets (7/8 DA) Median: 21.4d (8/8 DA above threshold)
Min/Max: 9.7d / 83.0d (8/8 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/8 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Meets (8/8 DA) 8/8 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (2/8 DA) 2/8 DA assigned Stable ≥16.5d - 58.9d (varies) (≥5/8 DA)
Prereq: V2Dir Meets (8/8 DA) 8/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Below (1/8 DA) Median: 91.4% (1/8 DA above threshold)
Min/Max: 58.2% / 98.2% (8/8 DA, Voting / Total Eligible)
≥98% (≥5/8 DA)
Time Known Meets (8/8 DA) Median: 21.4d (8/8 DA above threshold)
Min/Max: 9.7d / 83.0d (8/8 DA, Voting / Total Eligible)
≥8 days (≥5/8 DA)
Bandwidth Meets (8/8 DA) 41.0 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.0 Mbit/s (≥5/8 DA)
Exit Exit Policy Meets (8/8 DA) Port 80: Yes | Port 443: Yes (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/8 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-04-29 12:45:03).

Capacity (Relay Reported)
Observed Bandwidth
40.97 Mbit/s
Advertised Bandwidth
40.97 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
26 TB (6 months)
1mo: 3.9 TB | 6mo: 26 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-04-29 12:45:03

Measured By
5/5 Bandwidth Authorities
Median Measurement
36.5 Kbit/s
Min / Max
9.6 Kbit/s / 44.8 Kbit/s
Deviation
35.2 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0015% of network (25th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0045% (9th pctl)

Uptime Metrics
Current Status
UP 2d 22h 40m ago
Overall Uptime (1M/6M/1Y/5Y)
87.9%/97.4%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (87.9%/97.4%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
3w 1d 14h ago (2026-04-06 23:00:00)
Last Seen
5h 46m 39s ago (2026-04-29 08:00:00)
Last Restarted
2d 22h 40m ago (2026-04-26 15:06:29)
Last Changed Address
2026-04-26 17:00:00
Overload Status: Not Overloaded — No overload conditions reported.

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

DNS Health
Status
Not Tested
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 45.38.20.240:*
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, 29 Apr 2026 13:46:37 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-04-29 12:45:03).

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 (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) No N No
dannenberg (DE) Yes Yes Yes N Yes Valid, V2Dir, Fast, Exit 41.0 Mbit/s | 816.0 Kbit/s 41.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 90.8% | 98% 21.3d | 8d 0.3d | 46.4d 2.9d | 10.9d 90.8% | 98.0% 21.3d | 1.0d 2026-04-29 09:15:38 41.0 Kbit/s
dizum (NL) Yes Yes Yes N Yes Running, Valid, V2Dir, Fast, Exit 41.0 Mbit/s | 816.0 Kbit/s 41.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 84.7% | 98% 10.3d | 8d 0.2d | 42.5d 2.9d | 10.4d 84.7% | 98.0% 10.3d | 1.0d 2026-04-28 16:13:34 41.0 Kbit/s
faravahar (US) Yes Yes Yes N Yes Running, Valid, V2Dir, Fast, Exit 41.0 Mbit/s | 816.0 Kbit/s 41.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 95.5% | 98% 39.1d | 8d 0.8d | 58.9d 2.9d | 10.9d 95.5% | 98.0% 39.1d | 1.0d 2026-04-29 09:15:38 41.0 Kbit/s
gabelmoo (DE) Yes Yes Yes Y Yes Running, Valid, V2Dir, Fast, Exit 41.0 Mbit/s | 816.0 Kbit/s 41.0 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 92.0% | 98% 21.5d | 8d 0.4d | 57.3d 2.9d | 10.9d 92.0% | 98.0% 21.5d | 1.0d 2026-04-29 09:15:38 23.2 Kbit/s
longclaw (US) Yes Yes Yes Y Yes Running, Valid, V2Dir, Fast, Stable, Guard, Exit 41.0 Mbit/s | 816.0 Kbit/s 41.0 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 98.2% | 98% 83.0d | 8d 13.7d | 63.3d 2.9d | 10.9d 98.2% | 98.0% 83.0d | 1.0d 2026-04-29 09:15:38 32.0 Kbit/s
maatuska (SE) Yes Yes Yes Y Yes Running, Valid, V2Dir, Fast, Exit 41.0 Mbit/s | 816.0 Kbit/s 41.0 Mbit/s | 328.0 Mbit/s OR 16.0 Mbit/s 92.3% | 98% 25.2d | 8d 0.5d | 16.5d 2.9d | 10.7d 92.3% | 98.0% 25.2d | 1.0d 2026-04-29 09:15:38 9.6 Kbit/s
moria1 (US) Yes Yes Yes Y Yes Valid, V2Dir, Fast, Stable, Exit 41.0 Mbit/s | 8.4 Mbit/s 41.0 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 58.2% | 98% 9.7d | 8d 20570.5d | 280.2d 2.9d | 12.2d 58.2% | 98.0% 9.7d | 9.8d 2026-04-29 09:15:38 44.8 Kbit/s
tor26 (AT) Yes Yes Yes Y Yes Valid, V2Dir, Fast, Exit 41.0 Mbit/s | 816.0 Kbit/s 41.0 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 80.0% | 98% 11.9d | 8d 0.1d | 59.0d 2.9d | 11.1d 80.0% | 98.0% 11.9d | 1.0d 2026-04-29 09:15:38 19.2 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.