View Relay "server15r1"

Fingerprint: B2F905D392FCF64CC74ED4A4BB154E44FF22D3DA | Family: 30 relays | Steve <tor@digital-world.dev> | AS24940 | Germany | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir (3)
BW Verified
1/6 BW Auths Measured
Stability
Not Overloaded | UP 5h 48m 28s ago
Reachability
IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen
5h 15m 38s ago
BW Weight
0 Kbit/s Observed By Relay
Version
0.4.8.22 Recommended
Issues Detected:
  • 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.
  • 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 0.1 days is below 8 days requirement (7.9 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: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • 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.3 hours below 25 hours (dir-spec default)
    Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
  • 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.

Connectivity and Location

Addresses
OR Address
88.99.141.175:9001
[2a01:4f8:10a:25d3::2]:9001
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS24940
AS Name
Hetzner Online GmbH (BGP.tools)
AS Rarity
Common (score: 0/5, 7.79% consensus weight, 266 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
IPv6 Reachability Meets (8/8 DA) 8/8 tested authorities reached relay ≥5/8 tested (majority) (≥5/8 DA)
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 (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: 0.1d (0/9 DA above threshold)
Min/Max: 0.1d / 0.1d (9/9 DA, Voting / Total Eligible)		 ≥11.6d - 56.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥358.7d
Uptime Below (0/9 DA) 0.2d (R) ≥9.7d - 12.6d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (0/9 DA) 0/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.6d - 56.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥358.7d
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.1d (0/9 DA above threshold)
Min/Max: 0.1d / 0.1d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Below (0/9 DA) 0/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.6d - 56.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥358.7d
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.9 more days) Median: 0.1d (0/9 DA above threshold)
Min/Max: 0.1d / 0.1d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 0 bit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-296.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-16 16:15:08).

Bandwidth Metrics

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

Source: CollecTor — fetched 2026-03-16 16:15:08

Measured By
1/6 Bandwidth Authorities
Not measured by: bastet, gabelmoo, longclaw, maatuska, tor26
Median Measurement
0 bit/s
Min / Max
0 bit/s / 8 bit/s
Network Participation: Consensus Weight: N/A | Guard: N/A | Middle: N/A | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 5h 48m 28s ago
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
5h 15m 38s ago (2026-03-16 11:00:00)
Last Seen
1h 15m 38s ago (2026-03-16 15:00:00)
Last Restarted
5h 48m 28s ago (2026-03-16 10:27:10)
Last Changed Address
2026-03-16 11:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

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

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
Steve <tor@digital-world.dev>
Family Configuration
Family Support
MyFamily Only (30) — Legacy only. Consider migrating to Happy Families. | View Full Family (30)
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Members: 30 
0223CCD5BC73880B2188051AF53D3C9BB074855E
04EE6DE377E96D6BF8D7F4E5414BEED4264655AD
0F7FDD96A0F8ABCC7161917E31ED8867481EFD3F
155FE229CC2952D8966E78080843BC542045DFE7
231ABED83DFEE96789327C3E596853E0BED84FC0
2A3887CD9EFFE39AE27C4995E5E14E21D2750258
358C3281B8CF4EB4CA60844A4F20E12624086049
4701DF3BFE55A6A4EC96BCA5F02EE82D842C8FC1
516CC3D3010A2EEAB57D7F4B90C95D7C5E7C88FF
5AA3C97A17378686CEED654746A6690D6C093009
5B0BE83C4C37693629FD3562C3055A22C7EC7B1A
6B7681A85E0BC1EDA711180ABB1A1F07B5CAEA2B
6EC602986B79CDEB4B4D847AE80ADE66F1BF18FC
76F84181CC6445B543B0544191F5AA88A8B1E8B8
7A7AB320B1341C8B8571BC2C22860142181BA568
8504F2C56B4EE2E66B7E9F3D2A605BA4B836D700
98C04EFD509DB1F54BF9427CE500FBE85A144E4D
98DEEF226D351CE4A991448BDA56E52E6D9E4F46
9F482CAD6DA431390DC60E4782A5F41AE79C96B7
B2F905D392FCF64CC74ED4A4BB154E44FF22D3DA (this relay)
C0D2445522239292C242C25F9DD4877C01183FFA
C9B8800E3090CA3CB78C5C6B1C715CFBE5216AA0
CAB61B21C52FF00986ACC8B3ECFCBF650D15FCE8
D0D54F261890BA250A500B2011D90363C117CCFF
D15EAC7EA58B93CD7DB085AE7B485DD983386F6E
DD8ACDD2F3A522BB22B1CE09710226C1D736EB69
E125331BD0A6B39F73533DB64A5A02D34DD56BDC
E670DC8C0A3E50DBDCADA8127CB01BAF0192C5FD
F94AFB35732365E838AD42C6547F739A5269A622
FA23DBEA7DBDAD049090A93F6940AF40551968ED
Alleged Members: 38
(they don't list you back) 
047F38B174DCA73336CA88C6388BF112A68A3F8D
0DF8CBBE4791F1B2FE82318547383146164EEEDE
174DBF57A13A8511B10C44ED0FD59208EEC5188B
1AAA1F784BA60D981972964F38C4A934D9EA311C
1B26115FBB0CE2529D4223E9E1684F53E7E9B45A
2333F12F6D231773E5DE83B21D44CDF4FF6E28D6
39202205C5F9746A08883A0B5F7CEC90D2E2C53D
3A4DDEC168343E0DC8C280151743A1DD86586458
41F33EED35AC0008C7F878D71D21CDF20706232D
4613E4A8FEC437F311392A7B6E6B63423AC736D7
46FBC5392FB0164F7360CC38257AE2FF2BC81BCD
489DEA68982C1D17DA5B4E664F7E5DECCBEA4652
4B87843788021131378099C34FEC5DA5436E9701
4EEC481907177B7396F8BC0EDB027250D6D6B7A6
502EA81442C3F467B91830676B07D090EE2A2298
510CA4FD386A5206B985D9AD56C4ADA401C3AB3B
51F6015939F70F09BF04F99CE9A5BB3F620E9309
538430B59B5DADB73E835AA1E14D1CDE7A34E779
53FB300C316145943CF1128695C0EFA87E590667
66E02598C983E16E56B986B0D8C9F5239C14269B
68088E47413665C874E3B609E8B948CABEF1E192
7785847B13EB685FB55C3A02604CEDAD91C1904A
8129D60E0A19733F3E9BC5D10DD529D32674280A
8974F49153E6DEA1CC83F5AEEFACBA07CA1854A8
8BDB3353C817616270425C785284D1F58D710CF8
A1DC43B6A91D31C4AD88A5679154EC5FCC44323F
A32D464B26856F2B3D97EF05DC923F6221EAB087
AB170E385FD0E8B1E08E6A9EF0EC74E3F85C324C
B1F1AC6780B3C8126D972C482EE1F1EEAB36B41A
BEE6ACF9E016BECE7452D37B310D5611872D5211
C010E1F23A1F976006E528766F9236E86CA0A7C0
C633E48EBE3981B5F974A3BCDF58F6AC03144907
D119CF335C0429771C7BD5018C27CC45ADEB4706
D94CFF07685EF8B447D436347A581EFA4F07B231
EAF39FC696C4FE56EC0919119F753ADEF1CFE9D1
EDECF31425E9C090F8961EF3477B94E8158AA211
EE1942F92CBB783D5FCEDF33FEB6BC3BCBE9F346
F40423693C5019A891C3FB00528CAADFEBEA8B76
Indirect Members: 0
none

Software and Version

Platform
Linux — Tor 0.4.8.22 on Linux
Version
0.4.8.22 — 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
reject *:*

Last fetch was at Mon, 16 Mar 2026 16:15:38 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-16 16:15:08).

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 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 No — Y Yes Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 208.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 57.8d 0.2d | 11.8d 100.0% | 98.0% 0.1d | 1.0d 2026-03-16 11:13:18 —
dannenberg (DE) Yes Yes No — N Yes Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 11.6d 0.2d | 12.6d 100.0% | 98.0% 0.1d | 1.0d 2026-03-16 11:13:18 —
dizum (NL) Yes Yes No — N Yes Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 43.4d 0.2d | 9.7d 100.0% | 98.0% 0.1d | 1.0d 2026-03-16 11:13:18 —
faravahar (US) Yes Yes No — N Yes Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 53.9d 0.2d | 12.6d 100.0% | 98.0% 0.1d | 1.0d 2026-03-16 11:13:18 —
gabelmoo (DE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 280.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 58.7d 0.2d | 12.6d 100.0% | 98.0% 0.1d | 1.0d 2026-03-16 11:13:18 —
longclaw (US) Yes Yes No — Y Yes — Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 61.9d 0.2d | 12.6d 100.0% | 98.0% 0.1d | 1.0d 2026-03-16 11:13:18 —
maatuska (SE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 41.5d 0.2d | 12.6d 100.0% | 98.0% 0.1d | 1.0d 2026-03-16 11:13:18 —
moria1 (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir 0 bit/s | 8.4 Mbit/s 0 bit/s | 224.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 358.7d 0.2d | 15.4d 100.0% | 98.0% 0.1d | 9.8d 2026-03-16 11:13:18 8 bit/s
tor26 (AT) Yes Yes No — Y Yes Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 272.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 56.0d 0.2d | 13.5d 100.0% | 98.0% 0.1d | 1.0d 2026-03-16 11:13:18 —

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