Tor Relays :: 4c4f56loss

View Relay "4c4f56loss"

Fingerprint: `511B997BCD6E8F2EC5AB745B946CB7CBABD98E86` | Family: 1 relay | 4c4f56loss <torproject@4c4f56loss.net> | AS58212 | Germany | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Fast, Stable, Guard (6)
BW Verified: 5/6 BW Auths Measured 488 Kbit/s Median
Stability: Not Overloaded | UP 2d 19h 53m ago | UP 96% (1M)

Reachability: IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen: 2mo 1w 20h ago
BW Weight: 0.05% of Network | 416 Mbit/s Observed By Relay
Version: 0.4.9.6 Recommended

Issues Detected:

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: 4c4f56loss.net
45.145.43.232:9001
[2a0d:5940:94:11::]:9001

Reachability (Directory Authorities)

IPv4: 9/9
IPv6: 8/8 (1 don't test)

Location

Country: Germany
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS58212
AS Name: dataforest GmbH (BGP.tools)
AS Rarity: Epic (score: 3/5, 0.35% consensus weight, 7 operators)

Flags and Eligibility

Current Flags (6): Running, Valid, V2Dir, Fast, Stable, Guard

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
Running	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	Meets (9/9 DA)	416.8 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: 20.4d (1/9 DA above threshold) Min/Max: 5.0d / 2937.3d (9/9 DA, Voting / Total Eligible)	≥18.0d - 58.7d (varies) (≥5/9 DA)
Stable	Uptime	Below (0/9 DA)	2.8d (R)	≥3.5d - 3.5d (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	Meets (9/9 DA)	9/9 DA assigned Stable	≥18.0d - 58.7d (varies) (≥5/9 DA)
	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)	Median: 99.1% (9/9 DA above threshold) Min/Max: 98.1% / 99.2% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 23.0d (9/9 DA above threshold) Min/Max: 9.9d / 25.0d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d
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	Meets (9/9 DA)	9/9 DA assigned Stable	≥18.0d - 58.7d (varies) (≥5/9 DA)
	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)	Median: 99.1% (9/9 DA above threshold) Min/Max: 98.1% / 99.2% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 23.0d (9/9 DA above threshold) Min/Max: 9.9d / 25.0d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	416.8 Mbit/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-29 15:45:07).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 416.82 Mbit/s
Advertised Bandwidth: 416.82 Mbit/s
Rate Limit: 1000.00 Mbit/s
Burst Limit: 1.20 Gbit/s
Total Data: 231 TB (6 months)
1mo: 143 TB | 6mo: 231 TB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-29 15:45:07

Measured By: 5/6 Bandwidth Authorities
Not measured by: bastet
Median Measurement: 488.0 Kbit/s
Min / Max: 80.0 Kbit/s / 960.0 Kbit/s
Deviation: 880.0 Kbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0482% of network (99th pctl) | Guard: 0.0856% (99th pctl) | Middle: 0.0591% (98th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: UP 2d 19h 53m ago
Overall Uptime (1M/6M/1Y/5Y): 96.3%/98.4%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y): 69.1%/81.1%/—/—
Hibernating: No

Timestamps

First Seen: 2mo 1w 20h ago (2026-01-20 20:00:00)
Last Seen: 1h 46m 34s ago (2026-03-29 15:00:00)
Last Restarted: 2d 19h 53m ago (2026-03-26 20:52:58)
Last Changed Address: 2026-01-20 20:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-03-29 08:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: 4c4f56loss <torproject@4c4f56loss.net>

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

511B997BCD6E8F2EC5AB745B946CB7CBABD98E86 (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.9.6 on Linux
Version: 0.4.9.6 — 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 Sun, 29 Mar 2026 16:46:34 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-29 15:45:07).

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, Fast, Stable, Guard	416.8 Mbit/s \| 816.0 Kbit/s	416.8 Mbit/s \| 200.0 Mbit/s OR 16.0 Mbit/s	99.1% \| 98%	23.0d \| 8d	19.5d \| 63.5d	2.8d \| 3.5d	99.1% \| 98.0%	23.0d \| 1.0d	2026-03-29 02:53:09	80.0 Kbit/s
dannenberg (DE)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	416.8 Mbit/s \| 816.0 Kbit/s	416.8 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	98.3% \| 98%	15.9d \| 8d	5.0d \| 18.0d	2.8d \| 3.5d	98.3% \| 98.0%	15.9d \| 1.0d	2026-03-29 02:53:09	80.0 Kbit/s
dizum (NL)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	416.8 Mbit/s \| 816.0 Kbit/s	416.8 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	99.2% \| 98%	24.0d \| 8d	20.4d \| 42.7d	2.8d \| 3.5d	99.2% \| 98.0%	24.0d \| 1.0d	2026-03-29 02:53:09	80.0 Kbit/s
faravahar (US)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	416.8 Mbit/s \| 816.0 Kbit/s	416.8 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	99.2% \| 98%	25.0d \| 8d	21.2d \| 56.6d	2.8d \| 3.5d	99.2% \| 98.0%	25.0d \| 1.0d	2026-03-29 02:53:09	80.0 Kbit/s
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	416.8 Mbit/s \| 816.0 Kbit/s	416.8 Mbit/s \| 280.0 Mbit/s OR 16.0 Mbit/s	99.1% \| 98%	23.0d \| 8d	19.5d \| 61.8d	2.8d \| 3.5d	99.1% \| 98.0%	23.0d \| 1.0d	2026-03-29 02:53:09	960.0 Kbit/s
longclaw (US)	Yes	Yes	No	—	Y	Yes	—	Running, Valid, V2Dir, Fast, Stable, Guard	416.8 Mbit/s \| 816.0 Kbit/s	416.8 Mbit/s \| 232.0 Mbit/s OR 16.0 Mbit/s	99.2% \| 98%	24.6d \| 8d	21.0d \| 62.8d	2.8d \| 3.5d	99.2% \| 98.0%	24.6d \| 1.0d	2026-03-29 02:53:09	504.0 Kbit/s
maatuska (SE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	416.8 Mbit/s \| 816.0 Kbit/s	416.8 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	99.2% \| 98%	24.9d \| 8d	21.2d \| 50.8d	2.8d \| 3.5d	99.2% \| 98.0%	24.9d \| 1.0d	2026-03-29 02:53:09	720.0 Kbit/s
moria1 (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	416.8 Mbit/s \| 8.4 Mbit/s	416.8 Mbit/s \| 216.0 Mbit/s OR 16.0 Mbit/s	98.1% \| 98%	9.9d \| 8d	2937.3d \| 291.2d	2.8d \| 4.2d	98.1% \| 98.0%	9.9d \| 9.8d	2026-03-29 02:53:09	488.0 Kbit/s
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	416.8 Mbit/s \| 816.0 Kbit/s	416.8 Mbit/s \| 264.0 Mbit/s OR 16.0 Mbit/s	99.1% \| 98%	23.0d \| 8d	19.5d \| 58.7d	2.8d \| 3.8d	99.1% \| 98.0%	23.0d \| 1.0d	2026-03-29 02:53:09	880.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.