View Relay "4715"

Fingerprint: FEDA854291A94B8CA5BB6920AE100346EBC4E522 | Operator: middelstaedt.com v2 (16 relays) ⚠ Misconfigured | Family: 1 relay | email:tor [] middelstaedt dot com... | AS53667 | Luxembourg | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
2/7 BW Auths Measured
Stability
Not Overloaded | UP 4h 24m 50s ago
Reachability
IPv4: 9/9 (Directory Auths)
BW Weight
0 Kbit/s Observed By Relay
Version
0.4.9.11 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: 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: Time Known below threshold : Time Known 0.1 days is below 8 days requirement (7.9 more days needed)
    Suggestion: Time Known tracks how long authorities have observed your relay. This resets if: 1) Identity key changes, 2) Long downtime makes authorities forget you. Just keep running stably.
  • 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 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.
  • 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: Time Known below threshold : Time Known 2.5 hours below 25 hours (dir-spec default)
    Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
  • Low bandwidth authority measurements : Only 2/7 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
    Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.
  • 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.

Addresses
OR Address
tor-exit-readme.middelstaedt.com
104.244.73.136:9001
[2605:6400:30:edc3::34]:9001
Exit Address
104.244.73.136
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Luxembourg Luxembourg
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS53667
AS Name
FranTech Solutions (BGP.tools)
AS Rarity
Emerging (score: 1/5, 1.75% consensus weight, 64 operators)

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 0/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 9/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
IPv6 Reachability Meets (6/6 DA) 6/6 tested authorities reached relay ≥4/6 tested (majority) (≥4/6 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 Below (0/9 DA) 0 bit/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.1d (1/9 DA above threshold)
Min/Max: 0.0d / 20731.0d (9/9 DA, Voting / Total Eligible)
≥4.4d - 12.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7483.2d
Uptime Below (0/9 DA) 0.2d (R) ≥4.7d - 4.7d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (0/9 DA) 0/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.4d - 12.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7483.2d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (7/9 DA) Majority: 100.0% (7/9 DA)
Min/Med/Max: 0.0% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Below (0/9 DA) Median: 0.1d (0/9 DA above threshold)
Min/Max: 0.0d / 0.1d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Below (0/9 DA) 0/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.4d - 12.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7483.2d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (7/9 DA) Majority: 100.0% (7/9 DA)
Min/Med/Max: 0.0% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 7.9 more days) Median: 0.1d (0/9 DA above threshold)
Min/Max: 0.0d / 0.1d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 0 bit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.0 Mbit/s (≥5/9 DA)
Exit Exit Policy Meets (9/9 DA) Port 80: Yes | Port 443: Yes (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-10-05 01:45:09).

Capacity (Relay Reported)
Observed Bandwidth
0.00 Kbit/s
Advertised Bandwidth
Unknown
Rate Limit
1.05 Gbit/s
Burst Limit
1.05 Gbit/s
Total Data
N/A
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-05 01:45:09

Measured By
2/7 Bandwidth Authorities
Not measured by: bastet, dannenberg, faravahar, gabelmoo, longclaw
Median Measurement
0 bit/s
Min / Max
0 bit/s / 8 bit/s
Network Participation: Consensus Weight: N/A | Guard: N/A | Middle: N/A | Exit: N/A

Uptime Metrics
Current Status
UP 4h 24m 50s ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
N/A
Hibernating
No
Timestamps
First Seen
3h 45m 45s ago (2026-10-04 23:00:00)
Last Seen
1h 45m 45s ago (2026-10-05 01:00:00)
Last Restarted
4h 24m 50s ago (2026-10-04 22:20:55)
Last Changed Address
2026-10-04 23:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator Identity

Source: AROI Validation API — 2026-10-04 16:00 UTC

AROI Domain (?)
middelstaedt.com
Operator Validation
Unvalidated
This Relay
Unvalidated
Error: Not yet processed by validator (relay may be new)
Contact
email:tor [] middelstaedt dot com url:https://middelstaedt.com proof:uri-rsa abuse:abuse [] middelstaedt dot com pgp:A0D46E5E01288C9743B28774C74E950EBE2B8E0D dnslocation:local ciissversion:2

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

DNS Health
Status
Not Tested
IPv4 Exit Policy Summary
reject: 
  25
  110
  135
  137-139
  143
  445
  465
  587
  993
  995
  3389
IPv6 Exit Policy Summary
reject: 
  25
  110
  135
  137-139
  143
  445
  465
  587
  993
  995
  3389
Full Exit Policy
reject 0.0.0.0/8:*
reject 169.254.0.0/16:*
reject 127.0.0.0/8:*
reject 192.168.0.0/16:*
reject 10.0.0.0/8:*
reject 172.16.0.0/12:*
reject 104.244.73.136:*
reject *:25
reject *:465
reject *:587
reject *:110
reject *:143
reject *:993
reject *:995
reject *:3389
reject *:135
reject *:137-139
reject *:445
accept *:*

Last fetch was at Mon, 05 Oct 2026 02:45:42 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-10-05 01:45:09).

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 Yes — Y Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 192.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 12.3d 0.2d | 4.7d 100.0% | 98.0% 0.1d | 1.0d 2026-10-04 22:21:18 —
dannenberg (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 4.4d 0.2d | 4.7d 100.0% | 98.0% 0.1d | 1.0d 2026-10-04 22:21:18 —
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 12.2d 0.2d | 4.7d 100.0% | 98.0% 0.1d | 1.0d 2026-10-04 22:21:18 —
faravahar (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 13.6d 0.2d | 4.7d 100.0% | 98.0% 0.1d | 1.0d 2026-10-04 22:21:18 —
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 280.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 12.3d 0.2d | 4.7d 100.0% | 98.0% 0.1d | 1.0d 2026-10-04 22:21:18 —
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 12.7d 0.2d | 4.7d 100.0% | 98.0% 0.1d | 1.0d 2026-10-04 22:21:18 —
maatuska (SE) Yes Yes Yes — N Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.1d | 8d 0.1d | 11.8d 0.2d | 4.7d 100.0% | 98.0% 0.1d | 1.0d 2026-10-04 22:21:18 —
moria1 (US) Yes Yes Yes — Y Yes Valid, V2Dir, Stable, Exit 0 bit/s | 8.4 Mbit/s 0 bit/s | 208.0 Mbit/s OR 16.0 Mbit/s 85.3% | 98% 0.1d | 8d 20731.0d | 7483.2d 0.2d | 4.7d 85.3% | 98.0% 0.1d | 9.8d 2026-10-04 22:21:18 8 bit/s
tor26 (AT) Yes Yes Yes — Y Yes Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 264.0 Mbit/s OR 16.0 Mbit/s 0.0% | 98% 0.0d | 8d 0.0d | 12.6d 0.2d | 4.7d 0.0% | 98.0% 0.0d | 1.0d 2026-10-04 22:21:18 8 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.