View Relay "BuzzMeeks"

Fingerprint: C1824557C71760F4F5D4B0331FD4FC1CA161AE31 | Family: 1 relay | mn3m0n1c@pm.me | AS701 | United States of America | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
5/7 BW Auths Measured 3840 bit/s Median
Stability
Not Overloaded | UP 12h 52m 9s ago | UP 15% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
BW Weight
0.00% of Network | 21 Mbit/s Observed By Relay
Version
0.4.9.14 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 56.7% 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.0 days is below 8 days requirement (2.0 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: WFU below threshold : WFU 56.7% 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.

Addresses
OR Address
pool-71-121-177-148.bltmmd.fios.verizon.net
71.121.177.148:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
United States of America United States of America
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS701
AS Name
Verizon Business (BGP.tools)
AS Rarity
Epic (score: 3/5, 0.06% consensus weight, 20 operators)

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 7/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 (9/9 DA) 9/9 authorities reached relay ≥5/9 DA ORPort reachable
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) 21.4 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.3d (1/9 DA above threshold)
Min/Max: 0.3d / 18266.5d (9/9 DA, Voting / Total Eligible)
≥6.1d - 9.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10198.2d
Uptime Below (0/9 DA) 0.5d (R) ≥5.7d - 5.7d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (7/9 DA) 7/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 ≥6.1d - 9.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10198.2d
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: 56.9% (0/9 DA above threshold)
Min/Max: 55.5% / 57.9% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 5.9d (0/9 DA above threshold)
Min/Max: 5.6d / 6.0d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.7d
Guard Prereq: Fast Meets (7/9 DA) 7/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 ≥6.1d - 9.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10198.2d
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: 56.9% (0/9 DA above threshold)
Min/Max: 55.5% / 57.9% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 2.1 more days) Median: 5.9d (0/9 DA above threshold)
Min/Max: 5.6d / 6.0d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 21.4 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.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-17 23:00:36).

Capacity (Relay Reported)
Observed Bandwidth
21.44 Mbit/s
Advertised Bandwidth
1.02 Mbit/s
Rate Limit
1.02 Mbit/s
Burst Limit
2.05 Mbit/s
Total Data
486 GB (5 years)
1mo: 159 GB | 6mo: 159 GB | 1y: 196 GB | 5y: 486 GB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-17 23:00:36

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Median Measurement
3840 bit/s
Min / Max
1024 bit/s / 13.6 Kbit/s
Deviation
12.6 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0007% of network (14th pctl) | Guard: N/A | Middle: 0.0021% (30th pctl) | Exit: N/A

Uptime Metrics
Current Status
UP 12h 52m 9s ago
Overall Uptime (1M/6M/1Y/5Y)
15.8%/2.4%/5.7%/11.1%
Flag Uptime (1M/6M/1Y/5Y)
13.3%/2.2%/4.8%/9.3%
Hibernating
No
Timestamps
First Seen
1y 11mo 2w ago (2024-11-08 00:00:00)
Last Seen
2h 6m 18s ago (2026-10-17 22:00:00)
Last Restarted
12h 52m 9s ago (2026-10-17 11:14:09)
Last Changed Address
2026-10-09 11:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator Identity

Source: AROI Validation API — 2026-10-17 16:00 UTC

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

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

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 Sun, 18 Oct 2026 00:06:03 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-10-17 23:00:36).

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) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 21.4 Mbit/s | 816.0 Kbit/s 21.4 Mbit/s | 184.0 Mbit/s OR 16.0 Mbit/s 56.7% | 98% 6.0d | 8d 0.3d | 9.0d 0.5d | 5.7d 56.7% | 98.0% 6.0d | 1.0d 2026-10-17 11:14:14 6800 bit/s
dannenberg (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 21.4 Mbit/s | 816.0 Kbit/s 21.4 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 57.8% | 98% 5.9d | 8d 0.4d | 6.1d 0.5d | 5.8d 57.8% | 98.0% 5.9d | 1.0d 2026-10-17 11:14:14 13.6 Kbit/s
dizum (NL) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 21.4 Mbit/s | 816.0 Kbit/s 21.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 56.5% | 98% 6.0d | 8d 0.3d | 9.0d 0.5d | 5.7d 56.5% | 98.0% 6.0d | 1.0d 2026-10-17 11:14:14 1024 bit/s
faravahar (US) Yes Yes No — Y Yes Valid, V2Dir 21.4 Mbit/s | 816.0 Kbit/s 21.4 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 57.2% | 98% 5.9d | 8d 0.4d | 9.5d 0.5d | 6.3d 57.2% | 98.0% 5.9d | 1.0d 2026-10-17 11:14:14 1024 bit/s
gabelmoo (DE) Yes Yes No — Y Yes Valid, V2Dir, Fast 21.4 Mbit/s | 816.0 Kbit/s 21.4 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 57.8% | 98% 6.0d | 8d 0.4d | 9.0d 0.5d | 5.7d 57.8% | 98.0% 6.0d | 1.0d 2026-10-17 11:14:14 11.2 Kbit/s
longclaw (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 21.4 Mbit/s | 816.0 Kbit/s 21.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 56.5% | 98% 5.9d | 8d 0.3d | 9.2d 0.5d | 5.7d 56.5% | 98.0% 5.9d | 1.0d 2026-10-17 11:14:14 1024 bit/s
maatuska (SE) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 21.4 Mbit/s | 816.0 Kbit/s 21.4 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 56.9% | 98% 5.7d | 8d 0.3d | 8.8d 0.5d | 5.7d 56.9% | 98.0% 5.7d | 1.0d 2026-10-17 11:14:14 1024 bit/s
moria1 (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Stable 21.4 Mbit/s | 8.4 Mbit/s 21.4 Mbit/s | 192.0 Mbit/s OR 16.0 Mbit/s 57.9% | 98% 5.6d | 8d 18266.5d | 10198.2d 0.5d | 5.7d 57.9% | 98.0% 5.6d | 9.7d 2026-10-17 11:14:14 3840 bit/s
tor26 (AT) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 21.4 Mbit/s | 816.0 Kbit/s 21.4 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 55.5% | 98% 5.9d | 8d 0.3d | 9.3d 0.5d | 5.7d 55.5% | 98.0% 5.9d | 1.0d 2026-10-17 11:14:14 11.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.