View Relay "Tofoten"

Family: 1 relay | email:tildy[]cock.li... | AS36352 | United States of America | OpenBSD

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Exit, Running, Valid (3)
BW Verified
5/6 BW Auths Measured 8 bit/s Median
Stability
Not Overloaded | UP 13h 57m 46s ago
Reachability
IPv4: 9/9 | v6: 7/7 (Directory Auths)
First Seen
1d 11h 55m ago
BW Weight
0.00% of Network | 15 Mbit/s Observed By Relay
Version
0.4.8.21 Recommended
Issues Detected:
  • Guard: bandwidth below threshold : Observed bandwidth 2.0 MB/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
    Suggestion: Guard requires ≥2 MB/s bandwidth OR being in top 25% of network. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx or ARM.
  • Guard: Time Known below threshold : Time Known 1.5 days is below 8 days requirement (6.5 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.
  • 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: requires Fast flag : Guard flag requires having the Fast flag first
    Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • 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.
  • 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
216.144.230.176:9001
[2001:470:7:be::2]:9001
Exit Address
216.144.230.176
Reachability (Directory Authorities)
IPv4
9/9
IPv6
7/7 (2 don't test)
Location
Country
United States of America United States of America
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS36352
AS Name
HostPapa (BGP.tools)

Flags and Eligibility

Current Flags (3): Exit, Running, Valid
Eligible Flags (5): Guard: 0/9 | Stable: 0/9 | Fast: 9/9 | HSDir: 8/9 | Running: 9/9 | V2Dir: 9/9 | Valid: 9/9 (need ≥5/9 for flag)
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Guard WFU Meets 100.0% (DA) ≥98% (all authorities)
Time Known Below (need 6.5 more days) 1.5 days (DA) ≥8 days (all authorities)
Bandwidth Below 15.9 Mbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s
Stable MTBF Below 1 days (DA) ≥26.6d - 45.4d (varies)
Uptime Below 0.6d (R) ≥19.1d - 19.7d (varies)
Fast Speed Meets (≥100 KB/s) 15.9 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
HSDir WFU Meets 100.0% (DA) ≥98.0%
Time Known Below 1.5 days (DA) ≥1.0d (most) / 9.9d (max)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-01-10 04:46:16).

Last fetch was at Sat, 10 Jan 2026 04:47:26 GMT.

Nickname
Tofoten
Fingerprint
58B37D7F045E388E14F002D5EF7D5FF514A49F8B
AROI (?)
none
Contact
email:tildy[]cock.li xmr:89CB87iKkAn9rPFK7x534CQsbshZ7y4sHZKyie9hJXasZj9PET3KvahMjzo81shDHPSvFWrKbsyKo2i7hzTDHX8cLtwNZ5Y
IPv4 Exit Policy Summary 
accept: 
  20-21
  43
  53
  79-81
  88
  110
  143
  194
  220
  389
  443
  464-465
  531
  543-544
  554
  563
  587
  636
  706
  749
  853
  873
  902-904
  981
  989-995
  1194
  1220
  1293
  1500
  1533
  1677
  1723
  1755
  1863
  2082-2083
  2086-2087
  2095-2096
  2102-2104
  3128
  3389
  3690
  4321
  4643
  5050
  5190
  5222-5223
  5228
  5900
  6660-6669
  6679
  6697
  8000
  8008
  8074
  8080
  8082
  8087-8088
  8232-8233
  8332-8333
  8443
  8888
  9418
  9999-10000
  11371
  19294
  19638
  50002
  64738
IPv6 Exit Policy Summary 
accept: 
  20-21
  43
  53
  79-81
  88
  110
  143
  194
  220
  389
  443
  464-465
  531
  543-544
  554
  563
  587
  636
  706
  749
  853
  873
  902-904
  981
  989-995
  1194
  1220
  1293
  1500
  1533
  1677
  1723
  1755
  1863
  2082-2083
  2086-2087
  2095-2096
  2102-2104
  3128
  3389
  3690
  4321
  4643
  5050
  5190
  5222-5223
  5228
  5900
  6660-6669
  6679
  6697
  8000
  8008
  8074
  8080
  8082
  8087-8088
  8232-8233
  8332-8333
  8443
  8888
  9418
  9999-10000
  11371
  19294
  19638
  50002
  64738
Exit Policy 
reject 0.0.0.0/8:*
reject 169.254.0.0/16:*
reject 127.0.0.0/8:*
reject 192.168.0.0/16:*
reject 10.0.0.0/8:*
reject 172.16.0.0/12:*
reject 216.144.230.176:*
accept *:20-21
accept *:43
accept *:53
accept *:79
accept *:80-81
accept *:88
accept *:110
accept *:143
accept *:194
accept *:220
accept *:389
accept *:443
accept *:464
accept *:465
accept *:531
accept *:543-544
accept *:554
accept *:563
accept *:587
accept *:636
accept *:706
accept *:749
accept *:853
accept *:873
accept *:902-904
accept *:981
accept *:989-990
accept *:991
accept *:992
accept *:993
accept *:994
accept *:995
accept *:1194
accept *:1220
accept *:1293
accept *:1500
accept *:1533
accept *:1677
accept *:1723
accept *:1755
accept *:1863
accept *:2082
accept *:2083
accept *:2086-2087
accept *:2095-2096
accept *:2102-2104
accept *:3128
accept *:3389
accept *:3690
accept *:4321
accept *:4643
accept *:5050
accept *:5190
accept *:5222-5223
accept *:5228
accept *:5900
accept *:6660-6669
accept *:6679
accept *:6697
accept *:8000
accept *:8008
accept *:8074
accept *:8080
accept *:8082
accept *:8087-8088
accept *:8232-8233
accept *:8332-8333
accept *:8443
accept *:8888
accept *:9418
accept *:9999
accept *:10000
accept *:11371
accept *:19294
accept *:19638
accept *:50002
accept *:64738
reject *:*
Effective Family Member: 1 
58B37D7F045E388E14F002D5EF7D5FF514A49F8B
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
15.93 Mbit/s | 15.93 Mbit/s| 8.59 Gbit/s| 8.59 Gbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.00% | N/A | N/A | 0.00%
OR Address
216.144.230.176:9001, [2001:470:7:be::2]:9001
Exit Address
none
Dir Address
none
Country
United States of America United States of America
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS36352 | HostPapa (BGP.tools)
Flags: 3
Exit Exit Running Running Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
Match Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Uptime / Downtime
UP 13h 57m 46s ago
Seen (First | Last)
1d 11h 55m ago (2026-01-08 17:00:00) | 1h 55m ago (2026-01-10 03:00:00)
Last Restarted
14h 5m 17s ago (2026-01-09 14:49:43)
Last Changed Address or Port
2026-01-08 17:00:00
Hibernating
No
Platform (Short | Long)
OpenBSD | Tor 0.4.8.21 on OpenBSD
Version (Running | Recommended | Status)
0.4.8.21 | Yes | recommended

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-01-10 04:46:16).

  • Consensus Status (need ≥5/9): In Consensus — 9/9 authorities voted.
  • Flag Eligibility (need ≥5/9 for flag): Guard: 0/9 | Stable: 0/9 | Fast: 9/9 | HSDir: 8/9 | Running: 9/9 | Valid: 9/9 | V2Dir: 9/9
  • Reachability: IPv4: 9/9 | IPv6: 7/7 (2 don't test)
  • Consensus Weight (Dir. Auth.): Median: 8 bit/s | Min: 0 bit/s | Max: 15.9 Kbit/s [Warning] High deviation
  • Identified Issues:
    • Guard: bandwidth below threshold: Observed bandwidth 2.0 MB/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
      • Suggestion: Guard requires ≥2 MB/s bandwidth OR being in top 25% of network. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx or ARM.
    • Guard: Time Known below threshold: Time Known 1.5 days is below 8 days requirement (6.5 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.
    • 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: requires Fast flag: Guard flag requires having the Fast flag first
      • Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
    • 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.
    • 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.

Summary: Your Relay vs Consensus

Green = meets threshold, Red = below threshold, Yellow = partial.

Metric Dir Auth Measured Dir Auth Threshold Status
In Consensus (Dir. Auth.) 9/9 authorities ≥5/9 (majority) IN CONSENSUS
Running (IPv4 Reachable) 9/9 authorities reached this relay ≥5/9 (majority) RUNNING
Valid 9/9 (Running + Valid Descriptor) ≥5/9 (majority) VALID
Consensus Weight (Dir. Auth.) 8 bit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 100.0% ≥98% (all authorities) MEETS
Guard TK (Dir. Auth., tk) 1.5 days ≥8 days (all authorities) BELOW - need 6.5 more days
Guard BW (Relay Reported) 15.9 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported) 0.6d ≥19.1d - 19.7d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 1 days ≥26.6d - 45.4d (typical)
[Stricter] moria1: ≥376.2d 		BELOW - 0/9
Fast Speed (Relay Reported) 15.9 Mbit/s ≥800.0 Kbit/s (guarantee) OR ≥816.0 Kbit/s (typical)
[Stricter] moria1: ≥8.4 Mbit/s 		MEETS - ≥100 KB/s guarantee
HSDir WFU (Dir. Auth., wfu) 100.0% ≥98.0% (from all auths) PARTIAL - 8/9
HSDir TK (Dir. Auth., tk) 1.5 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d 		PARTIAL - 8/9
IPv6 Reachable (Dir. Auth.) 7/7 tested ≥4/7 (majority) REACHABLE

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 BW Scan (Authority) v4 v6 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 Y Yes Yes Exit, Running, Valid 15.9 Mbit/s | 816.0 Kbit/s 15.9 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.5d | 8d 1.5d | 47.0d 0.6d | 19.7d 100.0% | 98.0% 1.5d | 1.0d 2026-01-09 15:42:47 8 bit/s
dannenberg (DE) Yes Yes N Yes Yes Exit, Running, Valid 15.9 Mbit/s | 816.0 Kbit/s 15.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.5d | 8d 1.5d | 35.7d 0.6d | 20.2d 100.0% | 98.0% 1.5d | 1.0d 2026-01-09 14:43:59 —
dizum (NL) Yes Yes N Yes — Exit, Fast, Running, Valid 15.9 Mbit/s | 816.0 Kbit/s 15.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.5d | 8d 1.5d | 26.6d 0.6d | 20.4d 100.0% | 98.0% 1.5d | 1.0d 2026-01-09 15:42:47 15.9 Kbit/s
faravahar (US) Yes Yes N Yes Yes Exit, Fast, Running, Valid 15.9 Mbit/s | 816.0 Kbit/s 15.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.5d | 8d 1.5d | 41.9d 0.6d | 19.1d 100.0% | 98.0% 1.5d | 1.0d 2026-01-09 15:42:47 15.9 Kbit/s
gabelmoo (DE) Yes Yes Y Yes Yes Exit, Running, Valid 15.9 Mbit/s | 816.0 Kbit/s 15.9 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.5d | 8d 1.5d | 45.4d 0.6d | 19.6d 100.0% | 98.0% 1.5d | 1.0d 2026-01-09 15:42:47 8 bit/s
longclaw (US) Yes Yes Y Yes — Exit, Fast, Running, Valid 15.9 Mbit/s | 816.0 Kbit/s 15.9 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.5d | 8d 1.5d | 48.7d 0.6d | 19.5d 100.0% | 98.0% 1.5d | 1.0d 2026-01-09 15:42:47 15.9 Kbit/s
maatuska (SE) Yes Yes Y Yes Yes Exit, Fast, Running, Valid 15.9 Mbit/s | 816.0 Kbit/s 15.9 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.5d | 8d 1.5d | 42.3d 0.6d | 19.4d 100.0% | 98.0% 1.5d | 1.0d 2026-01-09 15:42:47 4880 bit/s
moria1 (US) Yes Yes Y Yes Yes Exit, Running, Valid 15.9 Mbit/s | 8.4 Mbit/s 15.9 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.4d | 8d 1.5d | 376.2d 0.6d | 20.4d 100.0% | 98.0% 1.4d | 9.9d 2026-01-09 15:42:47 8 bit/s
tor26 (AT) Yes Yes Y Yes Yes Exit, Running, Valid 15.9 Mbit/s | 816.0 Kbit/s 15.9 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.5d | 8d 1.5d | 51.8d 0.6d | 19.7d 100.0% | 98.0% 1.5d | 1.0d 2026-01-09 15:42:47 8 bit/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). This is your relay's self-reported uptime from its 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.