Tor Relays :: QbiXES1

View Relay "QbiXES1"

Fingerprint: `A5584BD5977882DB14D5A9C000D8E8AE1F17A8B2` | Family: 6 relays | tor@qbix.mozmail.com | AS8560 | Spain | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid, V2Dir, Fast, Stable, HSDir, Guard (7)
BW Verified: 6/7 BW Auths Measured 104 Kbit/s Median
Stability: Overloaded | UP 6d 18h 19m ago | UP 99% (1M)

Reachability: IPv4: 9/9 | v6: 8/8 (Directory Auths)
First Seen: 3mo 2w 4d ago
BW Weight: 0.01% of Network | 130 Mbit/s Observed By Relay
Version: 0.4.9.8 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.
General Overload Active : Relay reported general overload at 2026-06-14 17:00 UTC. This indicates OOM killer invocation, onionskin queue saturation, or TCP port exhaustion.
Suggestion: Check CPU/memory with htop. Review logs for "out of memory" or "onionskins" warnings. Consider increasing MaxMemInQueues in torrc. Verify TCP ports available.

Connectivity and Location

Addresses

OR Address: ip212-227-104-91.pbiaas.com
212.227.104.91:443
[2001:ba0:298:7c00::1]:443

Reachability (Directory Authorities)

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

Location

Country: Spain
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS8560
AS Name: IONOS SE (BGP.tools)
AS Rarity: Common (score: 0/5, 4.06% consensus weight, 163 operators)

Flags and Eligibility

Current Flags (7): Running, Valid, V2Dir, Fast, Stable, HSDir, 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)	130.9 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: 17.3d (1/9 DA above threshold) Min/Max: 15.2d / 3976.0d (9/9 DA, Voting / Total Eligible)	≥30.6d - 54.6d (varies) (≥5/9 DA) [Stricter] moria1: ≥297.5d
Stable	Uptime	Below (0/9 DA)	6.8d (R)	≥8.6d - 8.9d (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	≥30.6d - 54.6d (varies) (≥5/9 DA) [Stricter] moria1: ≥297.5d
	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.9% (9/9 DA above threshold) Min/Max: 99.9% / 99.9% (9/9 DA, Voting / Total Eligible)	≥98.0% (≥5/9 DA)
	Time Known	Meets (8/9 DA)	Median: 21.6d (9/9 DA above threshold) Min/Max: 9.7d / 21.8d (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	≥30.6d - 54.6d (varies) (≥5/9 DA) [Stricter] moria1: ≥297.5d
	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.9% (9/9 DA above threshold) Min/Max: 99.9% / 99.9% (9/9 DA, Voting / Total Eligible)	≥98% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 21.6d (9/9 DA above threshold) Min/Max: 9.7d / 21.8d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Meets (9/9 DA)	130.9 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-06-15 11:15:07).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 130.90 Mbit/s
Advertised Bandwidth: 130.90 Mbit/s
Rate Limit: 8.59 Gbit/s
Burst Limit: 8.59 Gbit/s
Total Data: 32 TB (6 months)
1mo: 10 TB | 6mo: 32 TB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-06-15 11:15:07

Measured By: 6/7 Bandwidth Authorities
Not measured by: dannenberg
Median Measurement: 104.0 Kbit/s
Min / Max: 80.0 Kbit/s / 200.0 Kbit/s
Deviation: 120.0 Kbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0074% of network (57th pctl) | Guard: 0.0125% (50th pctl) | Middle: 0.0096% (62th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics

Current Status: UP 6d 18h 19m ago
Overall Uptime (1M/6M/1Y/5Y): 99.7%/99.5%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y): 94.0%/72.2%/—/—
Hibernating: No

Timestamps

First Seen: 3mo 2w 4d ago (2026-02-26 18:00:00)
Last Seen: 1h 16m 5s ago (2026-06-15 11:00:00)
Last Restarted: 6d 18h 19m ago (2026-06-08 17:56:28)
Last Changed Address: 2026-04-06 23:00:00

[Warning] OVERLOADED — General overload at 2026-06-14 17:00 UTC

General Overload (from /details)

Status: Reported
When: 2026-06-14 17:00 UTC (19 hours ago)

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)

No rate limit data from /bandwidth endpoint.

Recommendations

Check CPU/memory: htop
Review MaxMemInQueues in torrc

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-06-15 04:00 UTC

AROI Domain (?): Not specified
Operator Validation: Unvalidated
This Relay: N/A (no AROI configured)
Contact: tor@qbix.mozmail.com

Family Configuration

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

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Members: 6

2964F0573648FD5E4AE1408005032352CA927C22
8D6D97F83E31D7D24602777B2607CAF2C91EFE0B
A5584BD5977882DB14D5A9C000D8E8AE1F17A8B2 (this relay)
E1F70F60315AD99A3991DE31CA654B6144A7F433
EA0E0122248B42B8A010ED413414122E4A9D931F
EA5BEB92B2CBDD305DEA04A4B99FD21368B18D75

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 Mon, 15 Jun 2026 12:16:04 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-06-15 11:15: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, HSDir, Guard	130.9 Mbit/s \| 816.0 Kbit/s	130.9 Mbit/s \| 248.0 Mbit/s OR 16.0 Mbit/s	99.9% \| 98%	21.8d \| 8d	17.3d \| 57.3d	6.8d \| 9.6d	99.9% \| 98.0%	21.8d \| 1.0d	2026-06-14 17:58:04	200.0 Kbit/s
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	130.9 Mbit/s \| 816.0 Kbit/s	130.9 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	99.9% \| 98%	21.8d \| 8d	17.5d \| 30.6d	6.8d \| 8.6d	99.9% \| 98.0%	21.8d \| 1.0d	2026-06-14 17:58:04	80.0 Kbit/s
dizum (NL)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	130.9 Mbit/s \| 816.0 Kbit/s	130.9 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	99.9% \| 98%	19.4d \| 8d	15.2d \| 34.3d	6.8d \| 8.8d	99.9% \| 98.0%	19.4d \| 1.0d	2026-06-14 17:58:04	80.0 Kbit/s
faravahar (US)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	130.9 Mbit/s \| 816.0 Kbit/s	130.9 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	99.9% \| 98%	21.7d \| 8d	16.6d \| 52.5d	6.8d \| 8.8d	99.9% \| 98.0%	21.7d \| 1.0d	2026-06-14 17:58:04	80.0 Kbit/s
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	130.9 Mbit/s \| 816.0 Kbit/s	130.9 Mbit/s \| 304.0 Mbit/s OR 16.0 Mbit/s	99.9% \| 98%	21.8d \| 8d	17.5d \| 54.9d	6.8d \| 9.0d	99.9% \| 98.0%	21.8d \| 1.0d	2026-06-14 17:58:04	104.0 Kbit/s
longclaw (US)	Yes	Yes	No	—	Y	Yes	—	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	130.9 Mbit/s \| 816.0 Kbit/s	130.9 Mbit/s \| 240.0 Mbit/s OR 16.0 Mbit/s	99.9% \| 98%	20.9d \| 8d	16.5d \| 60.3d	6.8d \| 8.9d	99.9% \| 98.0%	20.9d \| 1.0d	2026-06-14 17:58:04	120.0 Kbit/s
maatuska (SE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	130.9 Mbit/s \| 816.0 Kbit/s	130.9 Mbit/s \| 320.0 Mbit/s OR 16.0 Mbit/s	99.9% \| 98%	21.6d \| 8d	17.5d \| 31.1d	6.8d \| 8.8d	99.9% \| 98.0%	21.6d \| 1.0d	2026-06-14 17:58:04	104.0 Kbit/s
moria1 (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, Guard	130.9 Mbit/s \| 8.4 Mbit/s	130.9 Mbit/s \| 240.0 Mbit/s OR 16.0 Mbit/s	99.9% \| 98%	9.7d \| 8d	3976.0d \| 297.5d	6.8d \| 9.0d	99.9% \| 98.0%	9.7d \| 9.8d	2026-06-14 17:58:04	136.0 Kbit/s
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, V2Dir, Fast, Stable, HSDir, Guard	130.9 Mbit/s \| 816.0 Kbit/s	130.9 Mbit/s \| 304.0 Mbit/s OR 16.0 Mbit/s	99.9% \| 98%	21.5d \| 8d	16.7d \| 54.6d	6.8d \| 9.0d	99.9% \| 98.0%	21.5d \| 1.0d	2026-06-14 17:58:04	120.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.