Tor Relays :: tor04

View Relay "tor04"

Fingerprint: `A189A9D71CF57EA6280555CFA330D2BF1654C14E` | Family: 4 relays | someone < tor27 AT nurfuerspam DOT de > | AS8560 | Spain | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, Fast (3)
BW Verified: 6/6 BW Auths Measured 128 Kbit/s Median
Stability: Not Overloaded | UP 2d 21h 15m ago | UP 98% (1M)

Reachability: IPv4: 9/9 (Directory Auths)
First Seen: 4mo 3w 5d ago
BW Weight: 0.01% of Network | 137 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).
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: requires V2Dir (tunnelled-dir-server) : HSDir requires the relay to support tunnelled directory requests (V2Dir flag). This relay is missing V2Dir — the descriptor likely does not include tunnelled-dir-server, usually because DirCache 0 is set in torrc.
Suggestion: Remove DirCache 0 from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includes tunnelled-dir-server. You can check with: grep tunnelled-dir-server /var/lib/tor/cached-descriptors
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: 93.93.115.219:443

Reachability (Directory Authorities)

IPv4: 9/9

Location

Country: Spain
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS8560
AS Name: IONOS SE (BGP.tools)
AS Rarity: Emerging (score: 1/5, 3.87% consensus weight, 166 operators)

Flags and Eligibility

Current Flags (3): Running, Valid, Fast

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	Below (0/9 DA)	No DirPort, no tunnelled-dir-server (R)	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast	Speed	Meets (9/9 DA)	137.4 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.4d (1/9 DA above threshold) Min/Max: 3.4d / 13113.8d (9/9 DA, Voting / Total Eligible)	≥19.5d - 51.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥328.1d
Stable	Uptime	Below (0/9 DA)	2.9d (R)	≥6.4d - 6.4d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (9/9 DA)	9/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	≥19.5d - 51.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥328.1d
	Prereq: V2Dir	Below (0/9 DA)	0/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Meets (5/9 DA)	Median: 98.1% (5/9 DA above threshold) Min/Max: 96.8% / 98.4% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (8/9 DA)	Median: 12.3d (9/9 DA above threshold) Min/Max: 9.8d / 12.6d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.9d
Guard	Prereq: Fast	Meets (9/9 DA)	9/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	≥19.5d - 51.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥328.1d
	Prereq: V2Dir	Below (0/9 DA)	0/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Meets (5/9 DA)	Median: 98.1% (5/9 DA above threshold) Min/Max: 96.8% / 98.4% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 12.3d (9/9 DA above threshold) Min/Max: 9.8d / 12.6d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	137.4 Mbit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-336.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-05-14 18:15:08).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 137.42 Mbit/s
Advertised Bandwidth: 137.42 Mbit/s
Rate Limit: 163.84 Mbit/s
Burst Limit: 204.80 Mbit/s
Total Data: 51 TB (6 months)
1mo: 15 TB | 6mo: 51 TB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-05-14 18:15:08

Measured By: 6/6 Bandwidth Authorities
Median Measurement: 128.0 Kbit/s
Min / Max: 80.0 Kbit/s / 176.0 Kbit/s
Deviation: 96.0 Kbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0089% of network (62th pctl) | Guard: N/A | Middle: 0.0268% (86th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: UP 2d 21h 15m ago
Overall Uptime (1M/6M/1Y/5Y): 98.3%/98.8%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (98.3%/98.8%/0.0%/0.0%)
Hibernating: No

Timestamps

First Seen: 4mo 3w 5d ago (2025-12-19 06:00:00)
Last Seen: 1h 15m 53s ago (2026-05-14 18:00:00)
Last Restarted: 2d 21h 15m ago (2026-05-11 21:59:59)
Last Changed Address: 2026-04-06 23:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-05-14 11:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: someone < tor27 AT nurfuerspam DOT de >

Family Configuration

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

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Members: 4

1D280C19E9068921D82DB4471C48CB97E4CF9A93
710C9BF5192D99365DB3CD2DC870963C8B53F274
972E70F4124822F5DAB9C58FF6D53295DF3C01D7
A189A9D71CF57EA6280555CFA330D2BF1654C14E (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 Thu, 14 May 2026 19:15:52 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-05-14 18: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	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, Fast	137.4 Mbit/s \| 816.0 Kbit/s	137.4 Mbit/s \| 224.0 Mbit/s OR 16.0 Mbit/s	98.2% \| 98%	12.3d \| 8d	4.4d \| 50.8d	2.9d \| 6.4d	98.2% \| 98.0%	12.3d \| 1.0d	2026-05-14 05:20:10	120.0 Kbit/s
dannenberg (DE)	Yes	Yes	No	—	N	Yes	Running, Valid, Fast	137.4 Mbit/s \| 816.0 Kbit/s	137.4 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	98.2% \| 98%	12.6d \| 8d	4.6d \| 49.7d	2.9d \| 6.4d	98.2% \| 98.0%	12.6d \| 1.0d	2026-05-14 05:20:10	80.0 Kbit/s
dizum (NL)	Yes	Yes	No	—	N	Yes	Running, Valid, Fast	137.4 Mbit/s \| 816.0 Kbit/s	137.4 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	96.8% \| 98%	11.7d \| 8d	3.4d \| 19.5d	2.9d \| 6.4d	96.8% \| 98.0%	11.7d \| 1.0d	2026-05-14 05:20:10	80.0 Kbit/s
faravahar (US)	Yes	Yes	No	—	N	Yes	Running, Valid, Fast	137.4 Mbit/s \| 816.0 Kbit/s	137.4 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	98.3% \| 98%	12.6d \| 8d	4.6d \| 51.5d	2.9d \| 6.4d	98.3% \| 98.0%	12.6d \| 1.0d	2026-05-14 05:20:10	80.0 Kbit/s
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, Fast	137.4 Mbit/s \| 816.0 Kbit/s	137.4 Mbit/s \| 320.0 Mbit/s OR 16.0 Mbit/s	98.0% \| 98%	12.3d \| 8d	4.4d \| 51.9d	2.9d \| 6.4d	98.0% \| 98.0%	12.3d \| 1.0d	2026-05-14 05:20:10	176.0 Kbit/s
longclaw (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, Fast	137.4 Mbit/s \| 816.0 Kbit/s	137.4 Mbit/s \| 248.0 Mbit/s OR 16.0 Mbit/s	98.1% \| 98%	12.6d \| 8d	4.6d \| 58.4d	2.9d \| 6.4d	98.1% \| 98.0%	12.6d \| 1.0d	2026-05-14 05:20:10	152.0 Kbit/s
maatuska (SE)	Yes	Yes	No	—	Y	Yes	Running, Valid, Fast	137.4 Mbit/s \| 816.0 Kbit/s	137.4 Mbit/s \| 336.0 Mbit/s OR 16.0 Mbit/s	97.3% \| 98%	12.4d \| 8d	4.2d \| 23.0d	2.9d \| 6.4d	97.3% \| 98.0%	12.4d \| 1.0d	2026-05-14 05:20:10	128.0 Kbit/s
moria1 (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, Fast, Stable	137.4 Mbit/s \| 8.4 Mbit/s	137.4 Mbit/s \| 232.0 Mbit/s OR 16.0 Mbit/s	97.5% \| 98%	9.8d \| 8d	13113.8d \| 328.1d	2.9d \| 6.4d	97.5% \| 98.0%	9.8d \| 9.9d	2026-05-14 05:20:10	136.0 Kbit/s
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Running, Valid, Fast	137.4 Mbit/s \| 816.0 Kbit/s	137.4 Mbit/s \| 304.0 Mbit/s OR 16.0 Mbit/s	98.4% \| 98%	12.2d \| 8d	4.4d \| 54.6d	2.9d \| 6.5d	98.4% \| 98.0%	12.2d \| 1.0d	2026-05-14 05:20:10	160.0 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.