Tor Relays :: B6pNt

View Relay "B6pNt"

Fingerprint: `2B46E1CE0C24516BFF85A6063ACE637570607AE6` | Family: 1 relay | your@e-mail | AS3320 | Germany | Linux

Health Status

Consensus: In Consensus (7/7 Directory Auths)
Flags: Running, Valid, V2Dir, Fast (4)
BW Verified: 5/6 BW Auths Measured 40 Kbit/s Median
Stability: Not Overloaded | UP 4d 5h 5m ago | UP 92% (1M)

Reachability: IPv4: 7/7 (Directory Auths)
First Seen: 1mo 2w 6d ago
BW Weight: 0.00% of Network | 37 Mbit/s Observed By Relay
Version: 0.4.9.8 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: WFU below threshold : Weighted Fractional Uptime 97.5% is below 98% requirement
Suggestion: WFU measures recent uptime (recent downtime weighs more heavily). To improve: 1) Minimize restarts, 2) Use systemd with Restart=always, 3) Monitor for OOM kills, 4) Schedule updates during low-traffic periods.
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.
HSDir: WFU below threshold : WFU 97.5% below 98% required for HSDir
Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency.

Connectivity and Location

Addresses

OR Address: p4fd26a4d.dip0.t-ipconnect.de
79.210.106.77:443

Reachability (Directory Authorities)

IPv4: 7/7

Location

Country: Germany
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS3320
AS Name: Deutsche Telekom AG (BGP.tools)
AS Rarity: Rare (score: 2/5, 0.20% consensus weight, 53 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Fast

Eligibility Flag Vote Details

Flag	Metric	Status	Relay Value	Threshold Required
Running	IPv4 Reachability	Meets (7/7 DA)	7/7 authorities reached relay	≥4/7 DA ORPort reachable
Valid	Descriptor	Meets (7/7 DA)	7/7 authorities assigned Valid	Not blacklisted + valid descriptor (≥4/7 DA)
V2Dir	DirPort Available	Meets (7/7 DA)	Tunnelled: Yes (no DirPort) (R)	Tunnelled directory via ORPort or DirPort (≥4/7 DA)
Fast	Speed	Meets (7/7 DA)	37.6 Mbit/s (R)	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA) [Stricter] moria1: ≥8.4 Mbit/s
Stable	MTBF	Below (1/7 DA)	Median: 5.0d (1/7 DA above threshold) Min/Max: 4.3d / 12812.2d (7/7 DA, Voting / Total Eligible)	≥9.6d - 20.1d (varies) (≥4/7 DA) [Stricter] moria1: ≥7734.1d
Stable	Uptime	Partial (5/7 DA)	4.2d (R)	≥4.0d - 4.0d (varies) (≥4/7 DA)
HSDir	Prereq: Fast	Meets (7/7 DA)	7/7 DA assigned Fast	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Below (1/7 DA)	1/7 DA assigned Stable	≥9.6d - 20.1d (varies) (≥4/7 DA) [Stricter] moria1: ≥7734.1d
	Prereq: V2Dir	Meets (7/7 DA)	7/7 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥4/7 DA)
	WFU	Below (0/7 DA)	Median: 97.4% (0/7 DA above threshold) Min/Max: 95.0% / 97.5% (7/7 DA, Voting / Total Eligible)	≥98.0% (≥4/7 DA)
	Time Known	Meets (6/7 DA)	Median: 13.1d (7/7 DA above threshold) Min/Max: 9.8d / 13.4d (7/7 DA, Voting / Total Eligible)	≥1.0d (most) (≥4/7 DA) [Stricter] moria1: ≥9.9d
Guard	Prereq: Fast	Meets (7/7 DA)	7/7 DA assigned Fast	≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA) [Stricter] moria1: ≥8.4 Mbit/s
	Prereq: Stable	Below (1/7 DA)	1/7 DA assigned Stable	≥9.6d - 20.1d (varies) (≥4/7 DA) [Stricter] moria1: ≥7734.1d
	Prereq: V2Dir	Meets (7/7 DA)	7/7 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥4/7 DA)
	WFU	Below (0/7 DA)	Median: 97.4% (0/7 DA above threshold) Min/Max: 95.0% / 97.5% (7/7 DA, Voting / Total Eligible)	≥98% (≥4/7 DA)
	Time Known	Meets (7/7 DA)	Median: 13.1d (7/7 DA above threshold) Min/Max: 9.8d / 13.4d (7/7 DA, Voting / Total Eligible)	≥8 days (≥4/7 DA)
	Bandwidth	Meets (7/7 DA)	37.6 Mbit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-288.0 Mbit/s (≥4/7 DA)
Exit	Exit Policy	Below (0/7 DA)	Port 80: No \| Port 443: No (R)	Allows ≥1 /8 on ports 80 AND 443 (≥4/7 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-07-14 05:45:10).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 37.62 Mbit/s
Advertised Bandwidth: 37.62 Mbit/s
Rate Limit: 8.59 Gbit/s
Burst Limit: 8.59 Gbit/s
Total Data: 11 TB (6 months)
1mo: 6.6 TB | 6mo: 11 TB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-07-14 05:45:10

Measured By: 5/6 Bandwidth Authorities
Not measured by: bastet
Median Measurement: 40.0 Kbit/s
Min / Max: 31.2 Kbit/s / 44.0 Kbit/s

Network Participation: Consensus Weight: 0.0024% of network (38th pctl) | Guard: N/A | Middle: 0.0073% (60th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: UP 4d 5h 5m ago
Overall Uptime (1M/6M/1Y/5Y): 92.2%/95.4%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y): —/95.2%/—/—
Hibernating: No

Timestamps

First Seen: 1mo 2w 6d ago (2026-05-24 17:00:00)
Last Seen: 1h 45m 41s ago (2026-07-14 04:00:00)
Last Restarted: 4d 5h 5m ago (2026-07-10 00:40:07)
Last Changed Address: 2026-07-10 01:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-07-13 22:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: your@e-mail

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

2B46E1CE0C24516BFF85A6063ACE637570607AE6 (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.9.8 on Linux
Version: 0.4.9.8 — 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

Full Exit Policy

reject *:*

Last fetch was at Tue, 14 Jul 2026 05:45:40 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-07-14 05:45:10).

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	No	—	Y	Yes	Running, Valid, V2Dir, Fast	37.6 Mbit/s \| 816.0 Kbit/s	37.6 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	97.5% \| 98%	13.4d \| 8d	5.0d \| 29.6d	4.2d \| 4.3d	97.5% \| 98.0%	13.4d \| 1.0d	2026-07-13 18:41:29	37.6 Kbit/s
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	37.6 Mbit/s \| 816.0 Kbit/s	37.6 Mbit/s \| 256.0 Mbit/s OR 16.0 Mbit/s	97.4% \| 98%	13.1d \| 8d	5.0d \| 9.6d	4.2d \| 4.0d	97.4% \| 98.0%	13.1d \| 1.0d	2026-07-13 18:41:29	40.0 Kbit/s
dizum (NL)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast	37.6 Mbit/s \| 816.0 Kbit/s	37.6 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	97.4% \| 98%	13.3d \| 8d	4.9d \| 18.7d	4.2d \| 4.0d	97.4% \| 98.0%	13.3d \| 1.0d	2026-07-13 18:41:29	37.6 Kbit/s
faravahar (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	37.6 Mbit/s \| 816.0 Kbit/s	37.6 Mbit/s \| 288.0 Mbit/s OR 16.0 Mbit/s	95.0% \| 98%	12.9d \| 8d	4.3d \| 16.2d	4.2d \| 4.0d	95.0% \| 98.0%	12.9d \| 1.0d	2026-07-13 18:41:29	44.0 Kbit/s
maatuska (SE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	37.6 Mbit/s \| 816.0 Kbit/s	37.6 Mbit/s \| 280.0 Mbit/s OR 16.0 Mbit/s	97.5% \| 98%	13.4d \| 8d	5.0d \| 20.1d	4.2d \| 4.0d	97.5% \| 98.0%	13.4d \| 1.0d	2026-07-13 18:41:29	40.0 Kbit/s
moria1 (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast, Stable	37.6 Mbit/s \| 8.4 Mbit/s	37.6 Mbit/s \| 232.0 Mbit/s OR 16.0 Mbit/s	96.8% \| 98%	9.8d \| 8d	12812.2d \| 7734.1d	4.2d \| 4.2d	96.8% \| 98.0%	9.8d \| 9.9d	2026-07-13 18:41:29	31.2 Kbit/s
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	37.6 Mbit/s \| 816.0 Kbit/s	37.6 Mbit/s \| 280.0 Mbit/s OR 16.0 Mbit/s	97.5% \| 98%	13.1d \| 8d	5.0d \| 29.1d	4.2d \| 4.0d	97.5% \| 98.0%	13.1d \| 1.0d	2026-07-13 18:41:29	42.4 Kbit/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.