View Relay "TorRelay"

Fingerprint: 9D7ED61B4FE452BDB7EC7CF9766A15797DB83962 | Family: 1 relay | AS63023 | Switzerland |

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir (3)
BW Verified
5/7 BW Auths Measured 8 Kbit/s Median
Stability
Not Overloaded | Unknown
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
3h 45m 39s ago
BW Weight
0.00% of Network | 0 Kbit/s Observed By Relay
Version
0.4.9.14 Recommended
Issues Detected:
  • Not getting the Fast flag : Only 0/9 authorities vote Fast (5 needed). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 8.0 Kbit/s, below the Fast threshold (816.0 Kbit/s; moria1: 8.4 Mbit/s). dizum, longclaw and maatuska used the relay-reported unknown, below the Fast threshold (816.0 Kbit/s). faravahar judged it by bandwidth not shown in the votes. Its consensus weight, the median of the 5 bandwidth-scanner measurements, is 8.0 Kbit/s.
    Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports. A low measurement means the scanners see your relay underperforming compared with other relays that report a similar speed. Clients only build circuits through Fast relays, so a relay near the threshold can gain and lose most of its traffic from one hourly consensus to the next.
  • Guard: requires Fast flag : Guard flag requires having the Fast flag first
    Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports.
  • 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: bandwidth below threshold : 0/9 authorities credit this relay with enough bandwidth for Guard (5 needed): at least 16.8 Mbit/s (AuthDirGuardBWGuarantee) or a place in their top 25% (80.0 Mbit/s – 280.0 Mbit/s). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 8.0 Kbit/s. dizum, longclaw and maatuska used the relay-reported unknown.
    Suggestion: Guard requires a bandwidth of at least AuthDirGuardBWGuarantee (16.8 Mbit/s by default) or one in the top 25% of relays, judged by each authority the same way as for Fast. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx.
  • Guard: Time Known below threshold : Time Known 0.2 days is below 8 days requirement (7.8 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 Fast flag : HSDir flag requires having the Fast flag first
    Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports.
  • 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 3.7 hours below 25 hours (dir-spec default)
    Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.

Connectivity and Location

Addresses
OR Address
186.246.53.3:8443
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Switzerland Switzerland
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS63023
AS Name
GTHost (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.10% consensus weight, 11 operators)

Flags and Eligibility

Current Flags (3): Running, Valid, V2Dir
Eligible Flags (3): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 0/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 Below (0/9 DA) 8.0 Kbit/s (5 DA measured)
0 bit/s (3 DA relay-reported)
faravahar: not published		 ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (0/9 DA) Median: 0.2d (0/9 DA above threshold)
Min/Max: 0.2d / 0.2d (9/9 DA, Voting / Total Eligible)		 ≥4.9d - 10.8d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9251.3d
Uptime Below (0/9 DA) N/A (R) ≥3.2d - 3.3d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (0/9 DA) 0/9 DA assigned Fast
8.0 Kbit/s (5 DA measured)
0 bit/s (3 DA relay-reported)
faravahar: not published		 ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (0/9 DA) 0/9 DA assigned Stable ≥4.9d - 10.8d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9251.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: 0.2d (0/9 DA above threshold)
Min/Max: 0.2d / 0.2d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥10.0d
Guard Prereq: Fast Below (0/9 DA) 0/9 DA assigned Fast
8.0 Kbit/s (5 DA measured)
0 bit/s (3 DA relay-reported)
faravahar: not published		 ≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (0/9 DA) 0/9 DA assigned Stable ≥4.9d - 10.8d (varies) (≥5/9 DA)
[Stricter] moria1: ≥9251.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.8 more days) Median: 0.2d (0/9 DA above threshold)
Min/Max: 0.2d / 0.2d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 8.0 Kbit/s (5 DA measured)
0 bit/s (3 DA relay-reported)
faravahar: not published		 ≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-280.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-11 21:45:06).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
0.00 Kbit/s
Advertised Bandwidth
Unknown
Rate Limit
Not set
Burst Limit
Not set
Total Data
N/A
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-11 21:45:06

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight
8.0 Kbit/s (median of 5 measurements)
Measured Min / Max
8.0 Kbit/s / 8.0 Kbit/s
Network Participation: Consensus Weight: 0.0000% of network (0th pctl) | Guard: N/A | Middle: 0.0000% (0th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
Unknown
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
N/A
Hibernating
No
Timestamps
First Seen
3h 45m 39s ago (2026-10-11 18:00:00)
Last Seen
1h 45m 39s ago (2026-10-11 20:00:00)
Last Restarted
Unknown
Last Changed Address
2026-10-11 18:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-10-11 14: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 
9D7ED61B4FE452BDB7EC7CF9766A15797DB83962 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

Platform
Version
0.4.9.14 — Recommended
Version Status
Recommended

Exit Health & Policy

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

    







Last fetch was at Sun, 11 Oct 2026 21:45:38 GMT.










Consensus Evaluation






Data from Tor CollecTor (authority votes, fetched 2026-10-11 21:45:06).







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 (BW|T)
    Guard BW (BW|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    
    8.0 Kbit/s (M) | 816.0 Kbit/s
    8.0 Kbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s
    100.0% | 98%
    0.2d | 8d
    0.2d | 10.8d
    N/A | 3.3d
    100.0% | 98.0%
    0.2d | 1.0d
    2026-10-11 17:08:39
    8.0 Kbit/s (M)




    
        
            dannenberg (DE)
        
    
    Yes
    Yes
    No
    —
    Y
    Yes
    
Running, Valid, V2Dir    
    8.0 Kbit/s (M) | 816.0 Kbit/s
    8.0 Kbit/s (M) | 280.0 Mbit/s OR 16.8 Mbit/s
    100.0% | 98%
    0.2d | 8d
    0.2d | 4.9d
    N/A | 3.3d
    100.0% | 98.0%
    0.2d | 1.0d
    2026-10-11 17:08:39
    8.0 Kbit/s (M)




    
        
            dizum (NL)
        
    
    Yes
    Yes
    No
    —
    N
    Yes
    
Running, Valid, V2Dir    
    0 bit/s (R) | 816.0 Kbit/s
    0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s
    100.0% | 98%
    0.2d | 8d
    0.2d | 10.8d
    N/A | 3.3d
    100.0% | 98.0%
    0.2d | 1.0d
    2026-10-11 17:08:39
    —




    
        
            faravahar (US)
        
    
    Yes
    Yes
    No
    —
    Y
    Yes
    
Running, Valid, V2Dir    
    not published | 816.0 Kbit/s
    not published | 280.0 Mbit/s OR 16.8 Mbit/s
    100.0% | 98%
    0.2d | 8d
    0.2d | 11.7d
    N/A | 3.3d
    100.0% | 98.0%
    0.2d | 1.0d
    2026-10-11 17:08:39
    —




    
        
            gabelmoo (DE)
        
    
    Yes
    Yes
    No
    —
    Y
    Yes
    
Running, Valid, V2Dir    
    8.0 Kbit/s (M) | 816.0 Kbit/s
    8.0 Kbit/s (M) | 264.0 Mbit/s OR 16.8 Mbit/s
    100.0% | 98%
    0.2d | 8d
    0.2d | 10.8d
    N/A | 3.3d
    100.0% | 98.0%
    0.2d | 1.0d
    2026-10-11 17:08:39
    8.0 Kbit/s (M)




    
        
            longclaw (US)
        
    
    Yes
    Yes
    No
    —
    Y
    Yes
    
Running, Valid, V2Dir    
    0 bit/s (R) | 816.0 Kbit/s
    0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s
    100.0% | 98%
    0.2d | 8d
    0.2d | 11.1d
    N/A | 3.3d
    100.0% | 98.0%
    0.2d | 1.0d
    2026-10-11 17:08:39
    —




    
        
            maatuska (SE)
        
    
    Yes
    Yes
    No
    —
    N
    Yes
    
Running, Valid, V2Dir    
    0 bit/s (R) | 816.0 Kbit/s
    0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s
    100.0% | 98%
    0.2d | 8d
    0.2d | 10.5d
    N/A | 3.2d
    100.0% | 98.0%
    0.2d | 1.0d
    2026-10-11 17:08:39
    —




    
        
            moria1 (US)
        
    
    Yes
    Yes
    No
    —
    Y
    Yes
    
Running, Valid, V2Dir    
    8.0 Kbit/s (M) | 8.4 Mbit/s
    8.0 Kbit/s (M) | 208.0 Mbit/s OR 16.8 Mbit/s
    100.0% | 98%
    0.2d | 8d
    0.2d | 9251.3d
    N/A | 3.3d
    100.0% | 98.0%
    0.2d | 10.0d
    2026-10-11 17:08:39
    8.0 Kbit/s (M)




    
        
            tor26 (AT)
        
    
    Yes
    Yes
    No
    —
    Y
    Yes
    
Running, Valid, V2Dir    
    8.0 Kbit/s (M) | 816.0 Kbit/s
    8.0 Kbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s
    100.0% | 98%
    0.2d | 8d
    0.2d | 11.2d
    N/A | 3.3d
    100.0% | 98.0%
    0.2d | 1.0d
    2026-10-11 17:08:39
    8.0 Kbit/s (M)










— = not tested/available • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known • Bandwidth source: (M) bandwidth-scanner measurement, (R) relay-reported, (U) unmeasured, counted as 0





Bandwidth Values Explained:

Measured (M) = An authority's bandwidth-scanner measurement of your relay (Measured= in its vote). An authority that has one uses it for the Fast and Guard flags, and the consensus weight is the median of these measurements when 3 or more authorities have one.

Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (Bandwidth= in every vote). An authority without a measurement uses it for flags, unless it has measurements for enough other relays (ignoring-advertised-bws=1); then your relay counts as 0 (U). It sets the consensus weight only when fewer than 3 authorities measured the relay, capped at 20 KB/s (maxunmeasuredbw) while 3 or more authorities publish measurements.

Not published = The authority has no measurement of your relay in its vote and ignores relay-reported bandwidth, yet it voted Fast or its vote has no measurements at all: it judges your relay by a measurement kept from an earlier bandwidth file (0 if none), which its vote doesn't show.

Why different? A low measurement means the bandwidth scanners see your relay underperforming compared with other relays that report a similar speed. Votes list both values in kilobytes per second. Rules: Assigning flags in a vote, Computing a consensus.





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.