View Relay "MyWin10Relay"

Fingerprint: 3FA2F44F8CB535E2F404A5B49036B11C619A25FC | Family: 1 relay | toremail.uncoiled453@passmail.net | AS29518 | Sweden | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast (4)
BW Verified
4/6 BW Auths Measured 32 Kbit/s Median
Stability
Not Overloaded | UP 1d 9h 36m ago
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
1d 9h 15m ago
BW Weight
0.00% of Network | 33 Mbit/s Observed By Relay
Version
0.4.9.5 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 23.2 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.

Connectivity and Location

Addresses
OR Address
83-233-230-116.cust.bredband2.com
83.233.230.116:1338
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Sweden Sweden
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS29518
AS Name
Bredband2 AB (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 3 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 7/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) 33.0 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: 1.0d / 1.0d (9/9 DA, Voting / Total Eligible)		 ≥11.8d - 52.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥430.3d
Uptime Below (0/9 DA) 1.4d (R) ≥8.0d - 10.0d (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 (0/9 DA) 0/9 DA assigned Stable ≥11.8d - 52.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥430.3d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Majority: 100.0% (9/9 DA) ≥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.9d
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 (0/9 DA) 0/9 DA assigned Stable ≥11.8d - 52.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥430.3d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Majority: 100.0% (9/9 DA) ≥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) 33.0 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-304.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-03-04 17:45:07).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
33.00 Mbit/s
Advertised Bandwidth
32.77 Mbit/s
Rate Limit
32.77 Mbit/s
Burst Limit
65.54 Mbit/s
Total Data
563 MB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-04 17:45:07

Measured By
4/6 Bandwidth Authorities
Not measured by: longclaw, tor26
Median Measurement
32.8 Kbit/s
Min / Max
2000 bit/s / 56.0 Kbit/s
Deviation
54.0 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0001% of network (10th pctl) | Guard: N/A | Middle: 0.0004% (9th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 1d 9h 36m ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
1d 9h 15m ago (2026-03-03 09:00:00)
Last Seen
1h 15m 42s ago (2026-03-04 17:00:00)
Last Restarted
1d 9h 36m ago (2026-03-03 08:38:49)
Last Changed Address
2026-03-03 09:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-03-04 09:00 UTC

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

Software and Version

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

Exit Policy

IPv4 Exit Policy Summary
reject: 
  1-65535
IPv6 Exit Policy Summary
None
Full Exit Policy
reject *:*

Last fetch was at Wed, 04 Mar 2026 18:15:41 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-04 17:45: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 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 33.0 Mbit/s | 816.0 Kbit/s 33.0 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.0d | 8d 1.0d | 56.3d 1.4d | 9.6d 100.0% | 98.0% 0.97d | 1.04d 2026-03-03 16:14:51 2000 bit/s
dannenberg (DE) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 33.0 Mbit/s | 816.0 Kbit/s 33.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.0d | 8d 1.0d | 11.8d 1.4d | 8.2d 100.0% | 98.0% 0.97d | 1.04d 2026-03-03 16:14:51 32.8 Kbit/s
dizum (NL) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 33.0 Mbit/s | 816.0 Kbit/s 33.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.0d | 8d 1.0d | 42.7d 1.4d | 8.0d 100.0% | 98.0% 0.97d | 1.04d 2026-03-03 16:14:51 32.8 Kbit/s
faravahar (US) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 33.0 Mbit/s | 816.0 Kbit/s 33.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.0d | 8d 1.0d | 48.6d 1.4d | 10.0d 100.0% | 98.0% 0.97d | 1.04d 2026-03-03 16:14:51 32.8 Kbit/s
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 33.0 Mbit/s | 816.0 Kbit/s 33.0 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.0d | 8d 1.0d | 58.8d 1.4d | 10.1d 100.0% | 98.0% 0.97d | 1.04d 2026-03-03 16:14:51 39.2 Kbit/s
longclaw (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 33.0 Mbit/s | 816.0 Kbit/s 33.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.0d | 8d 1.0d | 59.0d 1.4d | 9.6d 100.0% | 98.0% 0.97d | 1.04d 2026-03-03 16:14:51 32.8 Kbit/s
maatuska (SE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 33.0 Mbit/s | 816.0 Kbit/s 33.0 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.0d | 8d 1.0d | 39.2d 1.4d | 10.1d 100.0% | 98.0% 0.97d | 1.04d 2026-03-03 16:14:51 56.0 Kbit/s
moria1 (US) Yes Yes No — Y Yes Running, Valid, V2Dir 33.0 Mbit/s | 8.4 Mbit/s 33.0 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.9d | 8d 1.0d | 430.3d 1.4d | 10.8d 100.0% | 98.0% 0.9d | 9.9d 2026-03-03 16:14:51 2160 bit/s
tor26 (AT) Yes Yes No — Y Yes Running, Valid, V2Dir 33.0 Mbit/s | 816.0 Kbit/s 33.0 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.0d | 8d 1.0d | 52.7d 1.4d | 10.1d 100.0% | 98.0% 0.97d | 1.04d 2026-03-03 16:14:51 32.8 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.