Tor Relays :: Chief

View Relay "Chief"

Fingerprint: `C01929F990071EBB4651609D21FD56176B96D554` | Family: 2 relays | dontcallmepls | AS58087 | Germany | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Fast, Exit (5)
DNS Health: Relay Unreachable (failed last 2 scans) (via exitdnshealth.1aeo.com)
BW Verified: 5/7 BW Auths Measured 80 Kbit/s Median
Stability: Overloaded | UP 1w 1d 17h ago | UP 98% (1M)

Reachability: IPv4: 9/9 (Directory Auths)
First Seen: 1w 1d 17h ago
BW Weight: 0.00% of Network | 98 Mbit/s Observed By Relay
Version: 0.4.9.9 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 7.0 days is below 8 days requirement (1.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.
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.
General Overload Active : Relay reported general overload at 2026-07-02 09:00 UTC. This indicates OOM killer invocation, onionskin queue saturation, or TCP port exhaustion.
Suggestion: Check CPU/memory with htop. Review logs for "out of memory" or "onionskins" warnings. Consider increasing MaxMemInQueues in torrc. Verify TCP ports available.

Connectivity and Location

Addresses

OR Address: 238.64.131.45.in-addr.arpa
45.131.64.238:443
Exit Address: 45.131.64.238

Reachability (Directory Authorities)

IPv4: 9/9

Location

Country: Germany
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS58087
AS Name: Florian Kolb (BGP.tools)
AS Rarity: Rare (score: 2/5, 0.83% consensus weight, 8 operators)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Exit

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)	98.2 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 (1/9 DA)	Median: 4.1d (1/9 DA above threshold) Min/Max: 0.6d / 8486.3d (9/9 DA, Voting / Total Eligible)	≥10.1d - 48.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥1364.1d
Stable	Uptime	Meets (9/9 DA)	8.7d (R)	≥4.3d - 5.2d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (8/9 DA)	8/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 (1/9 DA)	1/9 DA assigned Stable	≥10.1d - 48.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥1364.1d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Meets (7/9 DA)	Median: 98.7% (7/9 DA above threshold) Min/Max: 83.7% / 98.8% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (8/9 DA)	Median: 7.0d (0/9 DA above threshold) Min/Max: 5.2d / 7.1d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Meets (8/9 DA)	8/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 (1/9 DA)	1/9 DA assigned Stable	≥10.1d - 48.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥1364.1d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Meets (7/9 DA)	Median: 98.7% (7/9 DA above threshold) Min/Max: 83.7% / 98.8% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Below (0/9 DA) (need 1.0 more days)	Median: 7.0d (0/9 DA above threshold) Min/Max: 5.2d / 7.1d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	98.2 Mbit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.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-07-03 03:02:32).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 98.18 Mbit/s
Advertised Bandwidth: 98.18 Mbit/s
Rate Limit: 8.59 Gbit/s
Burst Limit: 8.59 Gbit/s
Total Data: 2.9 TB (1 month)

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-07-03 03:02:32

Measured By: 5/7 Bandwidth Authorities
Not measured by: bastet, dannenberg
Median Measurement: 80.0 Kbit/s
Min / Max: 8 bit/s / 168.0 Kbit/s
Deviation: 168.0 Kbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0047% of network (48th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0149% (30th pctl)

Uptime and Stability

Uptime Metrics

Current Status: UP 1w 1d 17h ago
Overall Uptime (1M/6M/1Y/5Y): 98.6%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (98.6%/0.0%/0.0%/0.0%)
Hibernating: No

Timestamps

First Seen: 1w 1d 17h ago (2026-06-24 10:00:00)
Last Seen: 2h 11m 25s ago (2026-07-03 01:00:00)
Last Restarted: 1w 1d 17h ago (2026-06-24 09:44:48)
Last Changed Address: 2026-06-24 10:00:00

[Warning] OVERLOADED — General overload at 2026-07-02 09:00 UTC

General Overload (from /details)

Status: Reported
When: 2026-07-02 09:00 UTC (18 hours ago)

OOM killer, onionskin queue saturation, or TCP port exhaustion. Flag remains 72h after last event (Tor spec 328).

File Descriptor Exhaustion (from /bandwidth)

Status: Not Reported

Rate Limits (from /bandwidth)

No rate limit data from /bandwidth endpoint.

Recommendations

Check CPU/memory: htop
Review MaxMemInQueues in torrc

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-07-02 19:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: dontcallmepls

Family Configuration

Family Support: MyFamily Only (2) — Legacy only. Consider migrating to Happy Families. | View Full Family (2)

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Members: 2

C01929F990071EBB4651609D21FD56176B96D554 (this relay)
D43032BFC3A3BB91FE7B4382C151A7350BA6E389

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.9.9 on Linux
Version: 0.4.9.9 — Recommended
Version Status: Recommended

Exit Health & Policy

DNS Health

Status: Relay Unreachable (failed last 2 scans)
Error: Tor Circuit Error: Circuit was closed
First Hop: prsv (GB) FB95298614940C14003223251B312A68CF3B76E1
Exit Address Used: 45.131.64.238

Tested: 2026-07-02 19:15:50 UTC

Source: exitdnshealth.1aeo.com

IPv4 Exit Policy Summary

accept: 
  53
  80
  443

Full 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 45.131.64.238:*
accept *:53
accept *:80
accept *:443
reject *:*

Last fetch was at Fri, 03 Jul 2026 03:11:23 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-07-03 03:02:32).

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	Yes	—	Y	Yes	Running, Valid, V2Dir, Fast, Exit	98.2 Mbit/s \| 816.0 Kbit/s	98.2 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	98.7% \| 98%	7.0d \| 8d	4.1d \| 48.4d	8.7d \| 5.1d	98.7% \| 98.0%	7.0d \| 1.0d	2026-07-02 12:18:53	80.0 Kbit/s
dannenberg (DE)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, V2Dir, Fast, Exit	98.2 Mbit/s \| 816.0 Kbit/s	98.2 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	93.1% \| 98%	6.0d \| 8d	0.6d \| 10.1d	8.7d \| 5.2d	93.1% \| 98.0%	6.0d \| 1.0d	2026-07-02 12:18:53	80.0 Kbit/s
dizum (NL)	Yes	Yes	Yes	—	N	Yes	Running, Valid, V2Dir, Fast, Exit	98.2 Mbit/s \| 816.0 Kbit/s	98.2 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	98.7% \| 98%	7.1d \| 8d	4.1d \| 25.9d	8.7d \| 5.2d	98.7% \| 98.0%	7.1d \| 1.0d	2026-07-02 12:18:53	80.0 Kbit/s
faravahar (US)	Yes	Yes	Yes	—	N	Yes	Running, Valid, V2Dir, Fast, Exit	98.2 Mbit/s \| 816.0 Kbit/s	98.2 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	83.7% \| 98%	6.9d \| 8d	2.2d \| 28.4d	8.7d \| 5.2d	83.7% \| 98.0%	6.9d \| 1.0d	2026-07-02 12:18:53	80.0 Kbit/s
gabelmoo (DE)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, V2Dir, Fast, Exit	98.2 Mbit/s \| 816.0 Kbit/s	98.2 Mbit/s \| 312.0 Mbit/s OR 16.0 Mbit/s	98.8% \| 98%	5.2d \| 8d	2.7d \| 60.1d	8.7d \| 4.3d	98.8% \| 98.0%	5.2d \| 1.0d	2026-06-29 11:13:38	88.0 Kbit/s
longclaw (US)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, V2Dir, Fast, Exit	98.2 Mbit/s \| 816.0 Kbit/s	98.2 Mbit/s \| 240.0 Mbit/s OR 16.0 Mbit/s	98.7% \| 98%	7.1d \| 8d	4.1d \| 57.2d	8.7d \| 5.4d	98.7% \| 98.0%	7.1d \| 1.0d	2026-07-02 12:18:53	168.0 Kbit/s
maatuska (SE)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, V2Dir, Fast, Exit	98.2 Mbit/s \| 816.0 Kbit/s	98.2 Mbit/s \| 304.0 Mbit/s OR 16.0 Mbit/s	98.7% \| 98%	7.1d \| 8d	4.1d \| 30.6d	8.7d \| 5.3d	98.7% \| 98.0%	7.1d \| 1.0d	2026-07-02 12:18:53	160.0 Kbit/s
moria1 (US)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable, Exit	98.2 Mbit/s \| 8.4 Mbit/s	98.2 Mbit/s \| 248.0 Mbit/s OR 16.0 Mbit/s	98.4% \| 98%	5.7d \| 8d	8486.3d \| 1364.1d	8.7d \| 5.4d	98.4% \| 98.0%	5.7d \| 9.8d	2026-07-02 12:18:53	68.8 Kbit/s
tor26 (AT)	Yes	Yes	Yes	—	Y	Yes	Running, Valid, V2Dir, Exit	98.2 Mbit/s \| 816.0 Kbit/s	98.2 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	98.7% \| 98%	7.1d \| 8d	4.1d \| 53.1d	8.7d \| 5.4d	98.7% \| 98.0%	7.1d \| 1.0d	2026-07-02 12:18:53	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). 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.