View Relay "porchmonkee"

Fingerprint: 69AA5F2C124318F4F76C913EDD76C11F951C77C9 | Family: 1 relay | AS49683 | United States of America | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
1/6 BW Auths Measured 38 Kbit/s Median
Stability
Not Overloaded | UP 23h 27m 1s ago | UP 2% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
BW Weight
0.00% of Network | 38 Mbit/s Observed By Relay
Version
0.4.9.11 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: Time Known below threshold : Time Known 1.0 days is below 8 days requirement (7.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: Time Known below threshold : Time Known 24.7 hours below 25 hours (dir-spec default)
    Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
  • 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.
  • Low bandwidth authority measurements : Only 1/6 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.

Addresses
OR Address
185.116.236.31:14888
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
AS49683
AS Name
MASSIVEGRID LTD (BGP.tools)
AS Rarity
Epic (score: 3/5, <0.05% consensus weight, 11 operators)

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 5/9 | Stable: 0/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) 38.1 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 (0/9 DA) Median: 1.0d (0/9 DA above threshold)
Min/Max: 0.4d / 1.0d (9/9 DA, Voting / Total Eligible)
≥7.0d - 11.8d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8173.7d
Uptime Below (0/9 DA) 1.0d (R) ≥6.8d - 7.4d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (5/9 DA) 5/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 (0/9 DA) 0/9 DA assigned Stable ≥7.0d - 11.8d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8173.7d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Majority: 100.0% (8/9 DA)
Min/Med/Max: 79.3% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Below (0/9 DA) Median: 1.0d (0/9 DA above threshold)
Min/Max: 0.9d / 1.0d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Meets (5/9 DA) 5/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 (0/9 DA) 0/9 DA assigned Stable ≥7.0d - 11.8d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8173.7d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Majority: 100.0% (8/9 DA)
Min/Med/Max: 79.3% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 7.0 more days) Median: 1.0d (0/9 DA above threshold)
Min/Max: 0.9d / 1.0d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 38.1 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-320.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-08-18 01:45:11).

Capacity (Relay Reported)
Observed Bandwidth
38.14 Mbit/s
Advertised Bandwidth
38.14 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
149 GB (1 year)
1mo: 406 MB | 6mo: 406 MB | 1y: 149 GB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-08-18 01:45:11

Measured By
1/6 Bandwidth Authorities
Not measured by: dannenberg, faravahar, gabelmoo, longclaw, tor26
Median Measurement
38.1 Kbit/s
Min / Max
192 bit/s / 38.1 Kbit/s
Deviation
37.9 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (3th pctl) | Guard: N/A | Middle: 0.0000% (3th pctl) | Exit: N/A

Uptime Metrics
Current Status
UP 23h 27m 1s ago
Overall Uptime (1M/6M/1Y/5Y)
2.0%/0.0%/4.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
—/—/3.4%/—
Hibernating
No
Timestamps
First Seen
9mo 4w 1h ago (2025-10-24 00:00:00)
Last Seen
1h 46m 42s ago (2026-08-18 00:00:00)
Last Restarted
23h 27m 1s ago (2026-08-17 02:19:41)
Last Changed Address
2026-08-17 01:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator Identity

Source: AROI Validation API — 2026-08-17 18:00 UTC

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

Platform
Linux — Tor 0.4.9.11 on Linux
Version
0.4.9.11Recommended
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 Tue, 18 Aug 2026 01:46:41 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-08-18 01:45:11).

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 N Yes Running, Valid, V2Dir, Fast 38.1 Mbit/s | 816.0 Kbit/s 38.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.0d | 8d 1.0d | 9.0d 1.0d | 6.9d 100.0% | 98.0% 1.03d | 1.04d 2026-08-17 12:56:49 38.1 Kbit/s
dannenberg (DE) Yes Yes No Y Yes Running, Valid, V2Dir 38.1 Mbit/s | 816.0 Kbit/s 38.1 Mbit/s | 320.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.0d | 8d 1.0d | 11.8d 1.0d | 8.5d 100.0% | 98.0% 1.03d | 1.04d 2026-08-17 12:56:49 38.1 Kbit/s
dizum (NL) Yes Yes No N Yes Running, Valid, V2Dir, Fast 38.1 Mbit/s | 816.0 Kbit/s 38.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.0d | 8d 1.0d | 11.3d 1.0d | 7.2d 100.0% | 98.0% 1.03d | 1.04d 2026-08-17 12:56:49 38.1 Kbit/s
faravahar (US) Yes Yes No Y Yes Running, Valid, V2Dir, Fast 38.1 Mbit/s | 816.0 Kbit/s 38.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.0d | 8d 1.0d | 11.2d 1.0d | 7.6d 100.0% | 98.0% 1.03d | 1.04d 2026-08-17 12:56:49 38.1 Kbit/s
gabelmoo (DE) Yes Yes No Y Yes Running, Valid, V2Dir 38.1 Mbit/s | 816.0 Kbit/s 38.1 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.0d | 8d 1.0d | 12.9d 1.0d | 7.4d 100.0% | 98.0% 1.03d | 1.04d 2026-08-17 12:56:49 38.1 Kbit/s
longclaw (US) Yes Yes No Y Yes Running, Valid, V2Dir, Fast 38.1 Mbit/s | 816.0 Kbit/s 38.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.0d | 8d 1.0d | 16.3d 1.0d | 7.5d 100.0% | 98.0% 1.03d | 1.04d 2026-08-17 12:56:49 38.1 Kbit/s
maatuska (SE) Yes Yes No N Yes Running, Valid, V2Dir, Fast 38.1 Mbit/s | 816.0 Kbit/s 38.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 79.3% | 98% 0.9d | 8d 0.4d | 7.0d 1.0d | 7.3d 79.3% | 98.0% 0.9d | 1.0d 2026-08-17 12:56:49 38.1 Kbit/s
moria1 (US) Yes Yes No Y Yes Running, Valid, V2Dir 38.1 Mbit/s | 8.4 Mbit/s 38.1 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.0d | 8d 1.0d | 8173.7d 1.0d | 6.8d 100.0% | 98.0% 1.0d | 9.8d 2026-08-17 12:56:49 192 bit/s
tor26 (AT) Yes Yes No Y Yes Running, Valid, V2Dir 38.1 Mbit/s | 816.0 Kbit/s 38.1 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.0d | 8d 1.0d | 12.6d 1.0d | 7.5d 100.0% | 98.0% 1.03d | 1.04d 2026-08-17 12:56:49 38.1 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.