View Relay "Unnamed"

Fingerprint: 6544135F0A477E1F71FD4747FE6F2BC18850C0C5 | Family: 2 relays | anonymous@localhost.localdomain | AS3320 | Germany | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast (4)
BW Verified
5/7 BW Auths Measured 3840 bit/s Median
Stability
Overloaded | UP 1d 16h 54m ago | UP 99% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
3w 1d 16h ago
BW Weight
0.00% of Network | 7 Mbit/s Observed By Relay
Version
0.4.9.11 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: bandwidth below threshold : Observed bandwidth 0.9 MB/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.
  • 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.
  • 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.
  • Write Bandwidth Limit Hit : Write rate limit (7 Mbit/s) was hit 27 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 (7 Mbit/s) was hit 65 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=7 Mbit/s, Burst=7 Mbit/s. Limits hit: Write=27, Read=65.

Connectivity and Location

Addresses
OR Address
p5dc59b9d.dip0.t-ipconnect.de
93.197.155.157:61442
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS3320
AS Name
Deutsche Telekom AG (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.22% consensus weight, 56 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 8/9 | Stable: 2/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 Meets (9/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 7.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 Below (1/9 DA) Median: 4.8d (1/9 DA above threshold)
Min/Max: 3.1d / 11972.4d (9/9 DA, Voting / Total Eligible)		 ≥10.1d - 48.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥1364.1d
Uptime Below (0/9 DA) 1.7d (R) ≥4.3d - 5.2d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (8/9 DA) 8/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 (2/9 DA) 2/9 DA assigned Stable ≥10.1d - 48.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥1364.1d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Median: 99.2% (8/9 DA above threshold)
Min/Max: 89.9% / 99.6% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 11.6d (9/9 DA above threshold)
Min/Max: 8.8d / 11.6d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Meets (8/9 DA) 8/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 (2/9 DA) 2/9 DA assigned Stable ≥10.1d - 48.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥1364.1d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Median: 99.2% (8/9 DA above threshold)
Min/Max: 89.9% / 99.6% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 11.6d (9/9 DA above threshold)
Min/Max: 8.8d / 11.6d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 7.1 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.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-03 03:02:32).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
7.06 Mbit/s
Advertised Bandwidth
6.55 Mbit/s
Rate Limit
6.55 Mbit/s
Burst Limit
7.37 Mbit/s
Total Data
509 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-07-03 03:02:32

Measured By
5/7 Bandwidth Authorities
Not measured by: bastet, dannenberg
Median Measurement
3840 bit/s
Min / Max
2640 bit/s / 6552 bit/s
Deviation
3912 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0002% of network (12th pctl) | Guard: N/A | Middle: 0.0007% (13th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 1d 16h 54m ago
Overall Uptime (1M/6M/1Y/5Y)
99.4%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (99.4%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
3w 1d 16h ago (2026-06-10 11:00:00)
Last Seen
2h 11m 26s ago (2026-07-03 01:00:00)
Last Restarted
1d 16h 54m ago (2026-07-01 10:16:41)
Last Changed Address
2026-06-30 01:00:00
[Warning] OVERLOADED — Rate limits hit W:27 R:65 (limit: 7 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
6.55 Mbit/s
Burst Limit
7.37 Mbit/s
Write Limit Hit
27 times
Read Limit Hit
65 times
Last Reported
5 hours ago
Recommendations
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-07-02 19:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
anonymous@localhost.localdomain
Family Configuration
Family Support
MyFamily Only (2) — Legacy only. Consider migrating to Happy Families. | View Full Family (2)
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Members: 2 
6544135F0A477E1F71FD4747FE6F2BC18850C0C5 (this relay)
9E35951EF13C574E7819A4127B61036930795455
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 — 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 Fri, 03 Jul 2026 03:11:23 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-07-03 03:02:32).

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 7.1 Mbit/s | 816.0 Kbit/s 7.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.0% | 98% 11.6d | 8d 4.8d | 48.4d 1.7d | 5.1d 99.0% | 98.0% 11.6d | 1.0d 2026-07-02 22:16:48 6552 bit/s
dannenberg (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 7.1 Mbit/s | 816.0 Kbit/s 7.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.2% | 98% 11.4d | 8d 4.8d | 10.1d 1.7d | 5.2d 99.2% | 98.0% 11.4d | 1.0d 2026-07-02 22:16:48 6552 bit/s
dizum (NL) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 7.1 Mbit/s | 816.0 Kbit/s 7.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.5% | 98% 11.6d | 8d 4.8d | 25.9d 1.7d | 5.2d 99.5% | 98.0% 11.6d | 1.0d 2026-07-02 22:16:48 6552 bit/s
faravahar (US) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 7.1 Mbit/s | 816.0 Kbit/s 7.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 89.9% | 98% 11.5d | 8d 3.1d | 28.4d 1.7d | 5.2d 89.9% | 98.0% 11.5d | 1.0d 2026-07-02 22:16:48 6552 bit/s
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable 7.1 Mbit/s | 816.0 Kbit/s 7.1 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 99.6% | 98% 11.4d | 8d 6.1d | 60.1d 1.7d | 4.3d 99.6% | 98.0% 11.4d | 1.0d 2026-06-29 15:03:56 3200 bit/s
longclaw (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 7.1 Mbit/s | 816.0 Kbit/s 7.1 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 99.0% | 98% 11.6d | 8d 4.8d | 57.2d 1.7d | 5.4d 99.0% | 98.0% 11.6d | 1.0d 2026-07-02 22:16:48 3440 bit/s
maatuska (SE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 7.1 Mbit/s | 816.0 Kbit/s 7.1 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 99.2% | 98% 11.6d | 8d 4.8d | 30.6d 1.7d | 5.3d 99.2% | 98.0% 11.6d | 1.0d 2026-07-02 22:16:48 2640 bit/s
moria1 (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Stable 7.1 Mbit/s | 8.4 Mbit/s 7.1 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 99.0% | 98% 8.8d | 8d 11972.4d | 1364.1d 1.7d | 5.4d 99.0% | 98.0% 8.8d | 9.8d 2026-07-02 22:16:48 3840 bit/s
tor26 (AT) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 7.1 Mbit/s | 816.0 Kbit/s 7.1 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 99.6% | 98% 11.6d | 8d 4.8d | 53.1d 1.7d | 5.4d 99.6% | 98.0% 11.6d | 1.0d 2026-07-02 22:16:48 3680 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.