View Relay "TacosAlPastor"

Fingerprint: `359D274F053F63D15E216FCB05411EB88DCAEC6F` | Family: 1 relay | <goetia at riseup.net> | AS8151 | Mexico | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Fast (4)
BW Verified: 4/7 BW Auths Measured 41 Kbit/s Median
Stability: Overloaded | UP 5d 22h 38m ago | UP 61% (1M)

Reachability: IPv4: 9/9 (Directory Auths)
First Seen: 6d 6h 45m ago
BW Weight: 0.00% of Network | 41 Mbit/s Observed By Relay
Version: 0.4.9.11 Not 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 27.4% 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 27.4% 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.
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.9.11 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.
File Descriptor Exhaustion : Relay ran out of file descriptors at 2026-09-28 18:00 UTC. This severely impacts connections and performance.
Suggestion: Increase file descriptor limits: For systemd: add "LimitNOFILE=65535" to [Service] section. For shell: ulimit -n 65535. Persistent: edit /etc/security/limits.conf.

Connectivity and Location

Addresses

OR Address: 201.103.81.193:9000

Reachability (Directory Authorities)

IPv4: 9/9

Location

Country: Mexico
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS8151
AS Name: Unknown
AS Rarity: Legendary (score: 4/5, <0.05% consensus weight, 5 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 (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)	41.0 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: 0.2d (1/9 DA above threshold) Min/Max: 0.2d / 19778.0d (9/9 DA, Voting / Total Eligible)	≥4.1d - 11.9d (varies) (≥5/9 DA) [Stricter] moria1: ≥8259.0d
Stable	Uptime	Below (0/9 DA)	5.9d (R)	≥6.1d - 6.1d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (5/9 DA)	5/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	≥4.1d - 11.9d (varies) (≥5/9 DA) [Stricter] moria1: ≥8259.0d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Below (0/9 DA)	Median: 27.4% (0/9 DA above threshold) Min/Max: 26.7% / 35.9% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (8/9 DA)	Median: 13.5d (9/9 DA above threshold) Min/Max: 9.5d / 14.1d (9/9 DA, Voting / Total Eligible)	≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d
Guard	Prereq: Fast	Meets (5/9 DA)	5/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	≥4.1d - 11.9d (varies) (≥5/9 DA) [Stricter] moria1: ≥8259.0d
	Prereq: V2Dir	Meets (9/9 DA)	9/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Below (0/9 DA)	Median: 27.4% (0/9 DA above threshold) Min/Max: 26.7% / 35.9% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 13.5d (9/9 DA above threshold) Min/Max: 9.5d / 14.1d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	41.0 Mbit/s (R)	≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-320.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-09-30 02:45:09).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 41.01 Mbit/s
Advertised Bandwidth: 40.96 Mbit/s
Rate Limit: 40.96 Mbit/s
Burst Limit: 81.92 Mbit/s
Total Data: 70 GB (1 month)

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-09-30 02:45:09

Measured By: 4/7 Bandwidth Authorities
Not measured by: dannenberg, faravahar, longclaw
Median Measurement: 41.0 Kbit/s
Min / Max: 8 bit/s / 56.8 Kbit/s
Deviation: 56.8 Kbit/s [Warning] High variation

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

Uptime and Stability

Uptime Metrics

Current Status: UP 5d 22h 38m ago
Overall Uptime (1M/6M/1Y/5Y): 61.4%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y): 34.9%/—/—/—
Hibernating: No

Timestamps

First Seen: 6d 6h 45m ago (2026-09-23 21:00:00)
Last Seen: 1h 45m 41s ago (2026-09-30 02:00:00)
Last Restarted: 5d 22h 38m ago (2026-09-24 05:06:46)
Last Changed Address: 2026-09-24 06:00:00

[Warning] OVERLOADED — FD exhaustion (last: 2026-09-28)

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: Reported — 2026-09-28 18:00 UTC (1 days ago)

Rate Limits (from /bandwidth)

No rate limit data from /bandwidth endpoint.

Recommendations

Increase FD limit: ulimit -n 65535
systemd: LimitNOFILE=65535 in [Service]

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-09-29 19:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: <goetia at riseup.net>

Family Configuration

Family Support: None — No family membership configured

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Member: 1

359D274F053F63D15E216FCB05411EB88DCAEC6F (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.9.11 on Linux
Version: 0.4.9.11 — 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 Wed, 30 Sep 2026 03:45:39 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-09-30 02:45:09).

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	41.0 Mbit/s \| 816.0 Kbit/s	41.0 Mbit/s \| 192.0 Mbit/s OR 16.0 Mbit/s	27.4% \| 98%	13.5d \| 8d	0.2d \| 11.7d	5.9d \| 6.1d	27.4% \| 98.0%	13.5d \| 1.0d	2026-09-29 12:39:43	56.8 Kbit/s
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir	41.0 Mbit/s \| 816.0 Kbit/s	41.0 Mbit/s \| 272.0 Mbit/s OR 16.0 Mbit/s	27.1% \| 98%	13.3d \| 8d	0.2d \| 4.1d	5.9d \| 6.1d	27.1% \| 98.0%	13.3d \| 1.0d	2026-09-29 12:39:43	41.0 Kbit/s
dizum (NL)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast	41.0 Mbit/s \| 816.0 Kbit/s	41.0 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	27.7% \| 98%	13.5d \| 8d	0.2d \| 11.7d	5.9d \| 6.1d	27.7% \| 98.0%	13.5d \| 1.0d	2026-09-29 12:39:43	41.0 Kbit/s
faravahar (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir	41.0 Mbit/s \| 816.0 Kbit/s	41.0 Mbit/s \| 320.0 Mbit/s OR 16.0 Mbit/s	29.4% \| 98%	14.1d \| 8d	0.2d \| 12.5d	5.9d \| 6.3d	29.4% \| 98.0%	14.1d \| 1.0d	2026-09-29 12:39:43	41.0 Kbit/s
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir	41.0 Mbit/s \| 816.0 Kbit/s	41.0 Mbit/s \| 256.0 Mbit/s OR 16.0 Mbit/s	27.2% \| 98%	13.5d \| 8d	0.2d \| 11.9d	5.9d \| 6.1d	27.2% \| 98.0%	13.5d \| 1.0d	2026-09-29 12:39:43	8 bit/s
longclaw (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	41.0 Mbit/s \| 816.0 Kbit/s	41.0 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	29.0% \| 98%	14.0d \| 8d	0.2d \| 12.5d	5.9d \| 6.1d	29.0% \| 98.0%	14.0d \| 1.0d	2026-09-29 12:39:43	41.0 Kbit/s
maatuska (SE)	Yes	Yes	No	—	N	Yes	Running, Valid, V2Dir, Fast	41.0 Mbit/s \| 816.0 Kbit/s	41.0 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	27.2% \| 98%	13.5d \| 8d	0.2d \| 11.2d	5.9d \| 6.1d	27.2% \| 98.0%	13.5d \| 1.0d	2026-09-29 12:39:43	41.0 Kbit/s
moria1 (US)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Stable	41.0 Mbit/s \| 8.4 Mbit/s	41.0 Mbit/s \| 208.0 Mbit/s OR 16.0 Mbit/s	35.9% \| 98%	9.5d \| 8d	19778.0d \| 8259.0d	5.9d \| 6.1d	35.9% \| 98.0%	9.5d \| 9.8d	2026-09-29 12:39:43	8 bit/s
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Running, Valid, V2Dir, Fast	41.0 Mbit/s \| 816.0 Kbit/s	41.0 Mbit/s \| 256.0 Mbit/s OR 16.0 Mbit/s	26.7% \| 98%	14.0d \| 8d	0.2d \| 12.1d	5.9d \| 6.1d	26.7% \| 98.0%	14.0d \| 1.0d	2026-09-29 12:39:43	1360 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.