Tor Relays :: mmsx76xsaa

View Relay "mmsx76xsaa"

Fingerprint: `A1141ADC0B4872E77E80D031E3B12EB5A4B249ED` | Family: 1 relay | AS39378 | Germany | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Stable (4)
BW Verified: 7/8 BW Auths Measured 280 bit/s Median
Stability: Overloaded | UP 1mo 2w 1d ago | UP 100% (1M)

Reachability: IPv4: 9/9 (Directory Auths)
First Seen: 1y 3w 4d ago
BW Weight: 0.00% of Network | 2 Mbit/s Observed By Relay
Version: 0.4.8.10 Not 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: bandwidth below threshold : Observed bandwidth 2 Mbit/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
Suggestion: Guard requires ≥2 MB/s bandwidth OR being in top 25% of network. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx or ARM.
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.
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.
Tor version not recommended : Running Tor version 0.4.8.10 which is not on the recommended list.
Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases.
Write Bandwidth Limit Hit : Write rate limit (2 Mbit/s) was hit 488 times. Relay is throttling outbound traffic.
Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more upload capacity.
Read Bandwidth Limit Hit : Read rate limit (2 Mbit/s) was hit 1,161 times. Relay is throttling inbound traffic.
Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more download capacity.

Notes:

Rate Limit Configuration: Configured limits: Rate=2 Mbit/s, Burst=256 KB. Limits hit: Write=488, Read=1,161.

Connectivity and Location

Addresses

OR Address: 185.212.44.101:443

Reachability (Directory Authorities)

IPv4: 9/9

Location

Country: Germany
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS39378
AS Name: servinga GmbH (BGP.tools)
AS Rarity: Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Flags and Eligibility

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

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)	2.1 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	Partial (7/9 DA)	Median: 134.8d (8/9 DA above threshold) Min/Max: 5.3d / 389.9d (9/9 DA, Voting / Total Eligible)	≥7.6d - 11.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥9239.4d
Stable	Uptime	Meets (9/9 DA)	45.4d (R)	≥7.4d - 7.4d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Below (2/9 DA)	2/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	≥7.6d - 11.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥9239.4d
	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: 100.0% (9/9 DA above threshold) Min/Max: 99.3% / 100.0% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 95.8d (9/9 DA above threshold) Min/Max: 9.9d / 389.5d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Below (2/9 DA)	2/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	≥7.6d - 11.8d (varies) (≥5/9 DA) [Stricter] moria1: ≥9239.4d
	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: 100.0% (9/9 DA above threshold) Min/Max: 99.3% / 100.0% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 95.8d (9/9 DA above threshold) Min/Max: 9.9d / 389.5d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Below (0/9 DA)	2.1 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-07-25 16:15:10).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 2.12 Mbit/s
Advertised Bandwidth: 2.05 Mbit/s
Rate Limit: 2.05 Mbit/s
Burst Limit: 2.05 Mbit/s
Total Data: 301 GB (5 years)
1mo: 17 GB | 6mo: 96 GB | 1y: 290 GB | 5y: 301 GB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-07-25 16:15:10

Measured By: 7/8 Bandwidth Authorities
Not measured by: bastet
Median Measurement: 280 bit/s
Min / Max: 232 bit/s / 2048 bit/s
Deviation: 1816 bit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0000% of network (3th pctl) | Guard: N/A | Middle: 0.0000% (3th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: UP 1mo 2w 1d ago
Overall Uptime (1M/6M/1Y/5Y): 100.0%/100.0%/100.0%/100.0%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (100.0%/100.0%/100.0%/100.0%)
Hibernating: No

Timestamps

First Seen: 1y 3w 4d ago (2025-06-30 15:00:00)
Last Seen: 2h 16m 43s ago (2026-07-25 15:00:00)
Last Restarted: 1mo 2w 1d ago (2026-06-10 06:55:20)
Last Changed Address: 2026-04-06 23:00:00

[Warning] OVERLOADED — Rate limits hit W:488 R:1161 (limit: 2 Mbit/s)

General Overload (from /details)

Status: Not Reported

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)

Rate Limit: 2.05 Mbit/s
Burst Limit: 256 KB
Write Limit Hit: 488 times
Read Limit Hit: 1,161 times
Last Reported: 12 hours ago

Recommendations

Consider increasing RelayBandwidthRate
Check if ISP is throttling traffic

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-07-25 09:00 UTC

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

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

A1141ADC0B4872E77E80D031E3B12EB5A4B249ED (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.8.10 on Linux
Version: 0.4.8.10 — Not Recommended
Version Status: Obsolete — Update urgently. See torproject.org/download

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 Sat, 25 Jul 2026 17:16:39 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-07-25 16:15: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, Stable, HSDir	2.1 Mbit/s \| 816.0 Kbit/s	2.1 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	389.2d \| 8d	389.2d \| 15.7d	45.4d \| 7.4d	100.0% \| 98.0%	389.2d \| 1.0d	2026-07-25 05:57:33	2048 bit/s
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Stable	2.1 Mbit/s \| 816.0 Kbit/s	2.1 Mbit/s \| 272.0 Mbit/s OR 16.0 Mbit/s	99.3% \| 98%	24.7d \| 8d	5.3d \| 7.6d	45.4d \| 7.4d	99.3% \| 98.0%	24.7d \| 1.0d	2026-07-25 05:57:33	248 bit/s
dizum (NL)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir	2.1 Mbit/s \| 816.0 Kbit/s	2.1 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	74.7d \| 8d	74.7d \| 10.9d	45.4d \| 7.4d	100.0% \| 98.0%	74.7d \| 1.0d	2026-07-25 05:57:33	2048 bit/s
faravahar (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Stable	2.1 Mbit/s \| 816.0 Kbit/s	2.1 Mbit/s \| 296.0 Mbit/s OR 16.0 Mbit/s	99.8% \| 98%	54.1d \| 8d	49.8d \| 11.3d	45.4d \| 7.4d	99.8% \| 98.0%	54.1d \| 1.0d	2026-07-25 05:57:33	280 bit/s
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Stable	2.1 Mbit/s \| 816.0 Kbit/s	2.1 Mbit/s \| 288.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	215.5d \| 6d	134.8d \| 11.3d	45.4d \| 7.4d	100.0% \| 98.0%	215.5d \| 1.0d	2026-07-25 05:57:33	232 bit/s
longclaw (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Stable	2.1 Mbit/s \| 816.0 Kbit/s	2.1 Mbit/s \| 240.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	373.6d \| 8d	373.6d \| 22.8d	45.4d \| 7.5d	100.0% \| 98.0%	373.6d \| 1.0d	2026-07-25 05:57:33	384 bit/s
maatuska (SE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Stable	2.1 Mbit/s \| 816.0 Kbit/s	2.1 Mbit/s \| 288.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	95.8d \| 8d	95.8d \| 11.8d	45.4d \| 7.5d	100.0% \| 98.0%	95.8d \| 1.0d	2026-07-25 05:57:33	264 bit/s
moria1 (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Stable	2.1 Mbit/s \| 8.4 Mbit/s	2.1 Mbit/s \| 216.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	9.9d \| 8d	389.9d \| 9239.4d	45.4d \| 7.5d	100.0% \| 98.0%	9.9d \| 9.8d	2026-07-25 05:57:33	576 bit/s
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Stable	2.1 Mbit/s \| 816.0 Kbit/s	2.1 Mbit/s \| 272.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	389.5d \| 8d	389.5d \| 15.6d	45.4d \| 7.4d	100.0% \| 98.0%	389.5d \| 1.0d	2026-07-25 05:57:33	272 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.