View Relay "Torsniff89d8f7"

Fingerprint: 364DEB626E9462F9508F18CB2BFD8F08CA53DC77 | Family: 1 relay | AS14956 | United States of America | Platform: unknown

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Exit (4)
DNS Health
Not Tested (via exitdnshealth.1aeo.com)
BW Verified
0/7 BW Auths Measured
Stability
Incomplete | Unknown
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
2h 15m 23s ago
BW Weight
0 Kbit/s Observed By Relay
Version
0.4.9.11 Not Recommended
Issues Detected:
  • Not getting the Fast flag : Only 0/9 authorities vote Fast (5 needed). dizum, longclaw and maatuska used the relay-reported unknown, below the Fast threshold (816.0 Kbit/s). bastet, dannenberg, gabelmoo, moria1 and tor26 counted this relay as 0 (no measurement, relay-reported bandwidth ignored). faravahar judged it by bandwidth not shown in the votes.
    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 – 296.0 Mbit/s). dizum, longclaw and maatuska used the relay-reported unknown. bastet, dannenberg, gabelmoo, moria1 and tor26 counted this relay as 0 (no measurement, relay-reported bandwidth ignored).
    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 : 0/9 authorities meet guard-tk (≥8 days; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 have no time-known history (925 seconds–942 seconds).
    Suggestion: Time Known stays near zero until an authority has observed the relay. Keep it running with the same identity key so those authorities accumulate history.
  • Not eligible for Stable flag : 0/9 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 do not.
    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.
  • Low bandwidth authority measurements : Only 0/7 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.
  • Tor version not recommended : Running Tor version 0.4.9.11 which is not on the recommended list.
    Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases.

Connectivity and Location

Addresses
OR Address
167.88.175.160: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
AS14956
AS Name
RouterHosting LLC (BGP.tools)
AS Rarity
Epic (score: 3/5, 0.09% consensus weight, 8 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 0/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 9/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) 0 bit/s (3 DA relay-reported)
0 bit/s (5 DA unmeasured, counted as 0)
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.0d (0/9 DA above threshold)
Min/Max: 0.0d / 0.0d (9/9 DA, Voting / Total Eligible)		 ≥4.8d - 7.8d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10681.9d
Uptime Below (0/9 DA) N/A (R) ≥6.2d - 6.4d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (0/9 DA) 0/9 DA assigned Fast
0 bit/s (3 DA relay-reported)
0 bit/s (5 DA unmeasured, counted as 0)
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.8d - 7.8d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10681.9d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Below (0/9 DA) N/A (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.8d Time Known
Guard Prereq: Fast Below (0/9 DA) 0/9 DA assigned Fast
0 bit/s (3 DA relay-reported)
0 bit/s (5 DA unmeasured, counted as 0)
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.8d - 7.8d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10681.9d
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 above threshold) ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) Median: 0.0d (0/9 DA above threshold)
Min/Max: 0.0d / 0.0d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 0 bit/s (3 DA relay-reported)
0 bit/s (5 DA unmeasured, counted as 0)
faravahar: not published		 ≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-296.0 Mbit/s) (≥5/9 DA)
Exit Exit Policy Meets (9/9 DA) Port 80: Yes | Port 443: Yes (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-23 15:15:07).

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-23 15:15:07

Measured By
0/7 Bandwidth Authorities
Not measured by: bastet, dannenberg, faravahar, gabelmoo, longclaw, moria1, tor26
Consensus Weight
0 bit/s (Unmeasured)
Measured Min / Max
N/A / N/A
Network Participation: Consensus Weight: N/A | Guard: N/A | Middle: N/A | 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
2h 15m 23s ago (2026-10-23 14:00:00)
Last Seen
1h 15m 23s ago (2026-10-23 15:00:00)
Last Restarted
Unknown
Last Changed Address
2026-10-23 14:00:00
Overload status: Incomplete — not every signal could be evaluated. (Invalid overload data; No bandwidth record available for this relay)

Evaluated 2026-10-23 16:15 UTC. /details snapshot 2026-10-23 15:00:00 UTC (cached 22s ago). /bandwidth snapshot 2026-10-23 13:00:00 UTC (cached 2h ago).

General Overload (from /details)
Status
Invalid overload data
File Descriptor Exhaustion (from /bandwidth)
Status
No bandwidth record available for this relay
Rate Limits (from /bandwidth)
Status
No bandwidth record available for this relay
Rate Limit
—
Burst Limit
—
Write counter
—
Read counter
—
About these reports and MetricsPort

Allium’s eligibility windows are applied to the reported timestamps: 72 hours for general overload and file-descriptor exhaustion, 24 hours for a rate-limit hit. A report at the cutoff is historical. An older report can remain visible after Onionoo or Allium’s cache still has it. The cutoff does not prove the relay recovered at that moment. Allium caches the bandwidth document for 12 hours by default. The snapshot time is when Onionoo published that document. It is not the relay’s event time, and it is not necessarily the extra-info publication time. Cache age is how old Allium’s copy is.

MetricsPort counters are cumulative. Compare samples, and account for process restarts. A nonzero total alone does not show ongoing activity. Gauges describe current values. An unavailable metric is unknown, not zero. Allium does not have this relay’s MetricsPort readings and does not invent them.

The port below is an example for an endpoint you have already configured. MetricsPort must be enabled with restricted access and must not be exposed publicly. Setup stays in the Tor overload troubleshooting guide. 

curl http://127.0.0.1:9035/metrics

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-10-23 08: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 
364DEB626E9462F9508F18CB2BFD8F08CA53DC77 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

Platform
Unknown
Version
0.4.9.11 — Not Recommended
Version Status
Obsolete — Update urgently. See torproject.org/download

Exit Health & Policy

DNS Health
Status
Not Tested
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
reject: 
  119
  135-139
  445
  1214
  4661-4666
  6346-6429
  6699
  6881-6999
IPv6 Exit Policy Summary
None
Full Exit Policy

    







Last fetch was at Fri, 23 Oct 2026 16:15:22 GMT.










Consensus Evaluation






Data from Tor CollecTor (authority votes, fetched 2026-10-23 15:15: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 (BW|T)
    Guard BW (BW|Threshold)
    Guard WFU (M|T)
    Guard TK (M|T)
    Stable MTBF (M|T)
    Stable Uptime (Relay|T)
    Desc Published
    Cons Wt (Authority)






    
        
            bastet (US)
        
    
    Yes
    Yes
    Yes
    —
    Y
    Yes
    
Running, Valid, V2Dir, Exit    
    0 bit/s (U) | 816.0 Kbit/s
    0 bit/s (U) | 192.0 Mbit/s OR 16.8 Mbit/s
    100.0% | 98%
    0.0d | 8d
    0.0d | 4.8d
    N/A | 6.4d
    2026-10-23 13:34:36
    —




    
        
            dannenberg (DE)
        
    
    Yes
    Yes
    Yes
    —
    Y
    Yes
    
Running, Valid, V2Dir, Exit    
    0 bit/s (U) | 816.0 Kbit/s
    0 bit/s (U) | 296.0 Mbit/s OR 16.8 Mbit/s
    100.0% | 98%
    0.0d | 8d
    0.0d | 5.8d
    N/A | 6.5d
    2026-10-23 13:34:36
    —




    
        
            dizum (NL)
        
    
    Yes
    Yes
    Yes
    —
    N
    Yes
    
Running, Valid, V2Dir, Exit    
    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.0d | 8d
    0.0d | 7.6d
    N/A | 6.4d
    2026-10-23 13:34:36
    —




    
        
            faravahar (US)
        
    
    Yes
    Yes
    Yes
    —
    Y
    Yes
    
Running, Valid, V2Dir, Exit    
    not published | 816.0 Kbit/s
    not published | 280.0 Mbit/s OR 16.8 Mbit/s
    100.0% | 98%
    0.0d | 8d
    0.0d | 8.1d
    N/A | 6.8d
    2026-10-23 13:34:36
    —




    
        
            gabelmoo (DE)
        
    
    Yes
    Yes
    Yes
    —
    Y
    Yes
    
Running, Valid, V2Dir, Exit    
    0 bit/s (U) | 816.0 Kbit/s
    0 bit/s (U) | 264.0 Mbit/s OR 16.8 Mbit/s
    100.0% | 98%
    0.0d | 8d
    0.0d | 7.8d
    N/A | 6.5d
    2026-10-23 13:34:36
    —




    
        
            longclaw (US)
        
    
    Yes
    Yes
    Yes
    —
    Y
    Yes
    
Running, Valid, V2Dir, Exit    
    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.0d | 8d
    0.0d | 7.9d
    N/A | 6.4d
    2026-10-23 13:34:36
    —




    
        
            maatuska (SE)
        
    
    Yes
    Yes
    Yes
    —
    N
    Yes
    
Running, Valid, V2Dir, Exit    
    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.0d | 8d
    0.0d | 7.7d
    N/A | 6.4d
    2026-10-23 13:34:36
    —




    
        
            moria1 (US)
        
    
    Yes
    Yes
    Yes
    —
    Y
    Yes
    
Running, Valid, V2Dir, Exit    
    0 bit/s (U) | 8.4 Mbit/s
    0 bit/s (U) | 200.0 Mbit/s OR 16.8 Mbit/s
    100.0% | 98%
    0.0d | 8d
    0.0d | 10681.9d
    N/A | 6.2d
    2026-10-23 13:34:36
    —




    
        
            tor26 (AT)
        
    
    Yes
    Yes
    Yes
    —
    Y
    Yes
    
Running, Valid, V2Dir, Exit    
    0 bit/s (U) | 816.0 Kbit/s
    0 bit/s (U) | 272.0 Mbit/s OR 16.8 Mbit/s
    100.0% | 98%
    0.0d | 8d
    0.0d | 7.9d
    N/A | 6.7d
    2026-10-23 13:34:36
    —










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