View Relay "plebelet"

Fingerprint: BB02A454CBF3365E52BA9713D34CB7A169FC4D79 | Family: 1 relay | johan@freemail | AS14956 | United States of America | Linux

Health Status

Consensus
In Consensus (7/8 Directory Auths)
Flags
Running, Valid, Exit (3)
DNS Health
Not Tested (via exitdnshealth.1aeo.com)
BW Verified
0/5 BW Auths Measured
Stability
Not Overloaded | UP 3h 30m 11s ago | UP 100% (1M)
Reachability
IPv4: 7/9 | v6: 6/8 (Directory Auths)
First Seen
2h 46m 39s ago
BW Weight
0 Kbit/s Observed By Relay
Version
0.4.9.6 Recommended
Issues Detected:
  • Guard: requires Fast flag : Guard flag requires having the Fast flag first
    Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • 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 4.3% 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 Fast flag : HSDir flag requires having the Fast flag first
    Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • 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 4.3% 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.
  • Low bandwidth authority measurements : Only 0/5 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.
Notes:
  • Partial IPv4 reachability: 7/9 authorities can reach this relay

Connectivity and Location

Addresses
OR Address
107.189.27.145:443
[2602:fa59:5:915::1]:443
Reachability (Directory Authorities)
IPv4
7/9
IPv6
6/8 (1 don't test)
Location
Country
United States of America United States of America
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS14956
AS Name
RouterHosting LLC (BGP.tools)
AS Rarity
Epic (score: 3/5, 0.06% consensus weight, 3 operators)

Flags and Eligibility

Current Flags (3): Running, Valid, Exit
Eligible Flags (4): Running: 7/8 | Valid: 7/8 | V2Dir: 7/8 | Fast: 0/8 | Stable: 1/8 | HSDir: 0/8 | Guard: 0/8 | Exit: 7/8
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (7/8 DA) 7/8 authorities reached relay ≥5/8 DA ORPort reachable
IPv6 Reachability Meets (6/7 DA) 6/7 tested authorities reached relay ≥4/7 tested (majority) (≥4/7 DA)
Valid Descriptor Meets (7/8 DA) 7/8 authorities assigned Valid Not blacklisted + valid descriptor (≥5/8 DA)
V2Dir DirPort Available Below (0/8 DA) No DirPort, no tunnelled-dir-server (R) Tunnelled directory via ORPort or DirPort (≥5/8 DA)
Fast Speed Below (0/8 DA) 0 bit/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: 2.5d (1/8 DA above threshold)
Min/Max: 1.3d / 906.5d (7/8 DA, Voting / Total Eligible)		 ≥16.5d - 54.8d (varies) (≥5/8 DA)
[Stricter] moria1: ≥315.7d
Uptime Below (0/8 DA) 0.1d (R) ≥9.1d - 9.1d (varies) (≥5/8 DA)
HSDir Prereq: Fast Below (0/8 DA) 0/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 (1/8 DA) 1/8 DA assigned Stable ≥16.5d - 54.8d (varies) (≥5/8 DA)
[Stricter] moria1: ≥315.7d
Prereq: V2Dir Below (0/8 DA) 0/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Below (0/8 DA) Median: 5.2% (0/8 DA above threshold)
Min/Max: 4.3% / 8.7% (7/8 DA, Voting / Total Eligible)		 ≥98.0% (≥5/8 DA)
Time Known Meets (6/8 DA) Median: 31.9d (7/8 DA above threshold)
Min/Max: 9.9d / 33.2d (7/8 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/8 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below (0/8 DA) 0/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 (1/8 DA) 1/8 DA assigned Stable ≥16.5d - 54.8d (varies) (≥5/8 DA)
[Stricter] moria1: ≥315.7d
Prereq: V2Dir Below (0/8 DA) 0/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Below (0/8 DA) Median: 5.2% (0/8 DA above threshold)
Min/Max: 4.3% / 8.7% (7/8 DA, Voting / Total Eligible)		 ≥98% (≥5/8 DA)
Time Known Meets (7/8 DA) Median: 31.9d (7/8 DA above threshold)
Min/Max: 9.9d / 33.2d (7/8 DA, Voting / Total Eligible)		 ≥8 days (≥5/8 DA)
Bandwidth Below (0/8 DA) 0 bit/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 (7/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-05-02 09:45:08).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
0.00 Kbit/s
Advertised Bandwidth
Unknown
Rate Limit
40.96 Mbit/s
Burst Limit
122.88 Mbit/s
Total Data
47 TB (6 months)
1mo: 12 TB | 6mo: 47 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-05-02 09:45:08

Measured By
0/5 Bandwidth Authorities
Not measured by: gabelmoo, longclaw, maatuska, moria1, tor26
Median Measurement
0 bit/s
Min / Max
0 bit/s / 0 bit/s
Network Participation: Consensus Weight: N/A | Guard: N/A | Middle: N/A | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 3h 30m 11s ago
Overall Uptime (1M/6M/1Y/5Y)
100.0%/95.8%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (100.0%/95.8%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
2h 46m 39s ago (2026-05-02 08:00:00)
Last Seen
1h 46m 39s ago (2026-05-02 09:00:00)
Last Restarted
3h 30m 11s ago (2026-05-02 07:16:28)
Last Changed Address
2026-05-02 08:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-05-02 02:00 UTC

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

Software and Version

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

Exit Health & Policy

DNS Health
Status
Not Tested
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 107.189.27.145:*
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 Sat, 02 May 2026 10:46:37 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-05-02 09:45:08).

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) No — — — N No — — — — — — — — — — — —
dannenberg (DE) Yes Yes Yes — N Yes Yes Running, Valid, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 4.3% | 98% 31.7d | 8d 1.3d | 47.9d 0.1d | 9.1d 4.3% | 98.0% 31.7d | 1.0d 2026-05-02 07:16:47 —
dizum (NL) No — — — N No — — — — — — — — — — — —
faravahar (US) Yes Yes Yes — N Yes Yes Running, Valid, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 5.2% | 98% 32.0d | 8d 1.6d | 56.1d 0.1d | 9.1d 5.2% | 98.0% 32.0d | 1.0d 2026-05-02 07:16:47 —
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 304.0 Mbit/s OR 16.0 Mbit/s 8.7% | 98% 33.2d | 8d 2.8d | 54.8d 0.1d | 9.1d 8.7% | 98.0% 33.2d | 1.0d 2026-05-02 07:16:47 —
longclaw (US) Yes Yes Yes — Y Yes — Running, Valid, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 240.0 Mbit/s OR 16.0 Mbit/s 8.2% | 98% 32.2d | 8d 2.5d | 62.8d 0.1d | 9.1d 8.2% | 98.0% 32.2d | 1.0d 2026-05-02 07:16:47 —
maatuska (SE) Yes Yes Yes — Y Yes Yes Running, Valid, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 328.0 Mbit/s OR 16.0 Mbit/s 8.7% | 98% 31.5d | 8d 2.6d | 16.5d 0.1d | 9.1d 8.7% | 98.0% 31.5d | 1.0d 2026-05-02 07:16:47 —
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, Stable, Exit 0 bit/s | 8.4 Mbit/s 0 bit/s | 224.0 Mbit/s OR 16.0 Mbit/s 4.8% | 98% 9.9d | 8d 906.5d | 315.7d 0.1d | 9.1d 4.8% | 98.0% 9.86d | 9.91d 2026-05-02 07:16:47 —
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 296.0 Mbit/s OR 16.0 Mbit/s 5.1% | 98% 31.9d | 8d 1.6d | 53.6d 0.1d | 9.1d 5.1% | 98.0% 31.9d | 1.0d 2026-05-02 07:16:47 —

— = 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.