View Relay "taquered"

Fingerprint: 87A2FD7406192120934CD1CD0FB54A50518A039F | Family: 2 relays | chetb9@gmail.com | AS56322 | Hungary | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, Fast (3)
BW Verified
5/6 BW Auths Measured 80 Kbit/s Median
Stability
Not Overloaded | UP 1d 20h 46m ago | UP 96% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
1y 1mo 2w ago
BW Weight
0.01% of Network | 88 Mbit/s Observed By Relay
Version
0.4.9.5 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 96.1% 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: 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
  • HSDir: WFU below threshold : WFU 96.1% 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.

Connectivity and Location

Addresses
OR Address
76477695-stellar.serverastra.com
91.219.237.218:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Hungary Hungary
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS56322
AS Name
ServerAstra Kft. (BGP.tools)
AS Rarity
Epic (score: 3/5, 0.06% consensus weight, 8 operators)

Flags and Eligibility

Current Flags (3): Running, Valid, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 0/9
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) 89.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: 4.3d (1/9 DA above threshold)
Min/Max: 2.5d / 13170.4d (9/9 DA, Voting / Total Eligible)		 ≥11.3d - 53.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥366.1d
Uptime Below (0/9 DA) 1.9d (R) ≥9.8d - 12.7d (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 ≥11.3d - 53.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥366.1d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 96.2% (0/9 DA above threshold)
Min/Max: 95.3% / 96.7% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 12.4d (9/9 DA above threshold)
Min/Max: 9.8d / 12.4d (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 ≥11.3d - 53.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥366.1d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 96.2% (0/9 DA above threshold)
Min/Max: 95.3% / 96.7% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 12.4d (9/9 DA above threshold)
Min/Max: 9.8d / 12.4d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 89.0 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-15 20:45:07).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
88.95 Mbit/s
Advertised Bandwidth
88.95 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
141 TB (5 years)
1mo: 8.1 TB | 6mo: 56 TB | 1y: 127 TB | 5y: 141 TB
Measurement (Directory Authority Verified)

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

Measured By
5/6 Bandwidth Authorities
Not measured by: longclaw
Median Measurement
80.0 Kbit/s
Min / Max
69.6 Kbit/s / 104.0 Kbit/s
Network Participation: Consensus Weight: 0.0061% of network (53th pctl) | Guard: N/A | Middle: 0.0183% (80th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 1d 20h 46m ago
Overall Uptime (1M/6M/1Y/5Y)
96.4%/94.8%/94.0%/94.3%
Flag Uptime (1M/6M/1Y/5Y)
—/—/—/94.9%
Hibernating
No
Timestamps
First Seen
1y 1mo 2w ago (2025-01-28 23:00:00)
Last Seen
1h 46m 38s ago (2026-03-15 19:00:00)
Last Restarted
1d 20h 46m ago (2026-03-14 00:00:00)
Last Changed Address
2025-01-28 23:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-03-15 13:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
chetb9@gmail.com
Family Configuration
Family Support
Happy Families (2) — Has family-cert in server descriptor (guide) | View Full Family (2)
Happy Families (family-cert)
Effective Members: 2 
1576CBC7EBE6C26F5E048E1F28F9D56C90F9C36C
87A2FD7406192120934CD1CD0FB54A50518A039F (this relay)
MyFamily (legacy declarations) — none

Software and Version

Platform
Linux — Tor 0.4.9.5 on Linux
Version
0.4.9.5 — 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
IPv6 Exit Policy Summary
None
Full Exit Policy
reject *:*

Last fetch was at Sun, 15 Mar 2026 20:46:37 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-15 20: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 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 89.0 Mbit/s | 816.0 Kbit/s 89.0 Mbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 96.1% | 98% 12.2d | 8d 3.3d | 57.0d 1.9d | 11.9d 96.1% | 98.0% 12.2d | 1.0d 2026-03-15 12:01:15 69.6 Kbit/s
dannenberg (DE) Yes Yes No — N Yes Running, Valid, Fast 89.0 Mbit/s | 816.0 Kbit/s 89.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 96.5% | 98% 12.4d | 8d 4.3d | 11.3d 1.9d | 12.7d 96.5% | 98.0% 12.4d | 1.0d 2026-03-15 12:01:15 80.0 Kbit/s
dizum (NL) Yes Yes No — N Yes Running, Valid, Fast 89.0 Mbit/s | 816.0 Kbit/s 89.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 96.2% | 98% 12.4d | 8d 4.3d | 43.2d 1.9d | 9.8d 96.2% | 98.0% 12.4d | 1.0d 2026-03-15 12:01:15 80.0 Kbit/s
faravahar (US) Yes Yes No — N Yes Running, Valid, Fast 89.0 Mbit/s | 816.0 Kbit/s 89.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 96.1% | 98% 12.0d | 8d 3.3d | 53.3d 1.9d | 12.8d 96.1% | 98.0% 12.0d | 1.0d 2026-03-15 12:01:15 80.0 Kbit/s
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, Fast 89.0 Mbit/s | 816.0 Kbit/s 89.0 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 96.7% | 98% 12.4d | 8d 4.3d | 58.4d 1.9d | 12.7d 96.7% | 98.0% 12.4d | 1.0d 2026-03-15 12:01:15 96.0 Kbit/s
longclaw (US) Yes Yes No — Y Yes Running, Valid, Fast 89.0 Mbit/s | 816.0 Kbit/s 89.0 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 95.8% | 98% 10.7d | 8d 2.5d | 61.1d 1.9d | 12.8d 95.8% | 98.0% 10.7d | 1.0d 2026-03-15 12:01:15 80.0 Kbit/s
maatuska (SE) Yes Yes No — Y Yes Running, Valid, Fast 89.0 Mbit/s | 816.0 Kbit/s 89.0 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 96.3% | 98% 12.4d | 8d 4.3d | 40.8d 1.9d | 12.7d 96.3% | 98.0% 12.4d | 1.0d 2026-03-15 12:01:15 96.0 Kbit/s
moria1 (US) Yes Yes No — Y Yes Running, Valid, Fast, Stable 89.0 Mbit/s | 8.4 Mbit/s 89.0 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 95.3% | 98% 9.8d | 8d 13170.4d | 366.1d 1.9d | 15.4d 95.3% | 98.0% 9.8d | 9.9d 2026-03-15 12:01:15 104.0 Kbit/s
tor26 (AT) Yes Yes No — Y Yes Running, Valid, Fast 89.0 Mbit/s | 816.0 Kbit/s 89.0 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 96.5% | 98% 12.4d | 8d 4.3d | 53.9d 1.9d | 12.8d 96.5% | 98.0% 12.4d | 1.0d 2026-03-15 12:01:15 96.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.