View Relay "4723"
Fingerprint: 3597A3F60A4AFE44A3DDE8B5219F9F85D9B441A2 |
Operator: middelstaedt.com v2
(13 relays)
⚠ Misconfigured
|
Family: 13 relays
|
email:tor [] middelstaedt dot com... |
AS56655
|
Norway
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- DNS Health
- DNS Lookup Failed (failed last 15 scans) (via exitdnshealth.1aeo.com)
- BW Verified
- 5/7 BW Auths Measured 280 Mbit/s Median
- Stability
- Not Overloaded | UP 3d 17h 7m ago | UP 99% (1M)
- Reachability
- IPv4: 9/9 | v6: 6/8(Directory Auths)
- BW Weight
- 0.02% of Network | 169 Mbit/s Observed By Relay
- Version
- 0.4.9.14 Not Recommended
Issues Detected:
-
HSDir: uptime below 96 hours
: Only 0/9 authorities voted HSDir, though this relay has Fast, Stable and V2Dir
Suggestion: HSDir needs 96 hours of uptime as each authority sees it (MinUptimeHidServDirectoryV2): the time since your relay restarted, or since that authority last failed to reach it if that is shorter. Keep the relay running and reachable. -
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.14 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.
Notes:
- Guard: WFU near threshold: Weighted Fractional Uptime is just above the Guard bar at dizum (98.2%, need ≥97.86%). Recent downtime weighs more than older downtime. Avoid restarts while it is this close; a short outage can drop the Guard flag.
Suggestion: Recent downtime weighs more than older downtime. Minimize restarts, use systemd Restart=always, and watch for OOM kills until each authority has more room above its own guard-wfu.
Addresses
- OR Address
-
tor-exit-info.middelstaedt.com
185.243.218.229:9004
[2a03:94e0:ffff:185:243:218:0:229]:9004
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- 6/8 (1 don't test)
Location
- Country
-
Norway
- Interactive Map
- View in RouteFluxMap
Eligible Flags (7):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 8/9 | HSDir: 0/9 | Guard: 7/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/8 DA) | 6/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) | 136.0 Mbit/s – 336.0 Mbit/s (5 DA measured) 80.0 Mbit/s (4 DA relay-reported) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Stable | MTBF | Partial (6/9 DA) | Median: 7.9d (3/9 DA above threshold) Min/Max: 0.0d / 20752.0d (9/9 DA, Voting / Total Eligible) |
≥2.4d - 9.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥7616.8d |
| Uptime | Below (0/9 DA) | 3.7d (R) | ≥5.2d - 5.5d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 136.0 Mbit/s – 336.0 Mbit/s (5 DA measured) 80.0 Mbit/s (4 DA relay-reported) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Meets (8/9 DA) | 8/9 DA assigned Stable | ≥2.4d - 9.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥7616.8d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Below (0/9 DA) | 3.7d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known |
|
| Guard | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 136.0 Mbit/s – 336.0 Mbit/s (5 DA measured) 80.0 Mbit/s (4 DA relay-reported) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Meets (8/9 DA) | 8/9 DA assigned Stable | ≥2.4d - 9.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥7616.8d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Partial (7/9 DA) | Median: 99.4% (7/9 DA above threshold) Min/Max: 0.0% / 99.8% (9/9 DA, Voting / Total Eligible) |
≥98%; dizum: ≥97.86% (≥5/9 DA) | |
| Time Known | Partial (8/9 DA) | Median: 16.4d (8/9 DA above threshold) Min/Max: 0.0d / 18.8d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Meets (9/9 DA) | 136.0 Mbit/s – 336.0 Mbit/s (5 DA measured) 80.0 Mbit/s (4 DA relay-reported) |
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-272.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-11-04 17:15:06).
Capacity (Relay Reported)
- Observed Bandwidth
- 169.77 Mbit/s
- Advertised Bandwidth
- 169.77 Mbit/s
- Rate Limit
- 8.59 Gbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
-
1.2 PB
(5 years)
1mo: 30 TB | 6mo: 232 TB | 1y: 447 TB | 5y: 1.2 PB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-04 17:15:06
- Measured By
-
5/7
Bandwidth Authorities
Not measured by: faravahar, longclaw - Consensus Weight
- 280.0 Mbit/s (median of 5 measurements)
- Measured Min / Max
- 136.0 Mbit/s / 336.0 Mbit/s
- Deviation
- 200.0 Mbit/s [Warning] High variation
Network Participation:
Consensus Weight:
0.0189% of network
(81th pctl)
|
Guard:
N/A |
Middle:
N/A |
Exit:
0.0588% (80th pctl)
History
Uptime Metrics
- Current Status
- UP 3d 17h 7m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 99.3%/99.7%/99.8%/99.6%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (99.3%/99.7%/99.8%/99.6%)
- Hibernating
- No
Timestamps
- First Seen
- 2y 10mo 1w ago (2024-01-01 00:00:00)
- Last Seen
- 2h 15m 39s ago (2026-11-04 15:00:00)
- Last Restarted
- 3d 17h 7m ago (2026-11-01 00:08:39)
- Last Changed Address
- 2026-04-06 23:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
Evaluated 2026-11-04 17:15 UTC. /details snapshot 2026-11-04 15:00:00 UTC (cached 33s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 9h 30m ago).
General Overload (from /details)
- Status
- No general overload report in available data
File Descriptor Exhaustion (from /bandwidth)
- Status
- No file-descriptor exhaustion report in available data
Rate Limits (from /bandwidth)
- Status
- No rate-limit report in available data
- Rate Limit
- —
- Burst Limit
- —
- Write counter
- —
- Read counter
- —
About these reports and MetricsPort
Allium’s eligibility windows are applied to the reported timestamps: 72 hours for general overload and file-descriptor exhaustion, 24 hours for a rate-limit hit. A report at the cutoff is historical. An older report can remain visible after Onionoo or Allium’s cache still has it. The cutoff does not prove the relay recovered at that moment. Allium caches the bandwidth document for 12 hours by default. The snapshot time is when Onionoo published that document. It is not the relay’s event time, and it is not necessarily the extra-info publication time. Cache age is how old Allium’s copy is.
MetricsPort counters are cumulative. Compare samples, and account for process restarts. A nonzero total alone does not show ongoing activity. Gauges describe current values. An unavailable metric is unknown, not zero. Allium does not have this relay’s MetricsPort readings and does not invent them.
The port below is an example for an endpoint you have already configured. MetricsPort must be enabled with restricted access and must not be exposed publicly. Setup stays in the Tor overload troubleshooting guide.
curl http://127.0.0.1:9035/metrics
History
Operator Identity
Source: AROI Validation API — 2026-11-04 08:00 UTC
- AROI Domain (?)
- middelstaedt.com
- Operator Validation
- Unvalidated
- This Relay
-
Unvalidated
Error: URI-RSA: HTTP error connection timed out after 5s for URL: https://middelstaedt.com/.well-known/tor-relay/rsa-fingerprint.txt - Contact
- email:tor [] middelstaedt dot com url:https://middelstaedt.com proof:uri-rsa abuse:abuse [] middelstaedt dot com pgp:A0D46E5E01288C9743B28774C74E950EBE2B8E0D dnslocation:local ciissversion:2
Family Configuration
- Family Support
- MyFamily Only (13) — Legacy only. Consider migrating to Happy Families. | View Full Family (13)
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Members: 13
1771F9D32775A95BCB9A0D078E509A5624438B76 18F4F0F749B0A48F51F0C56233A7F00C7BCEB4D8 3597A3F60A4AFE44A3DDE8B5219F9F85D9B441A2 (this relay) 4F270462A8BF960102EBE193BC0DF6432F49832F 566F698A2C234802F82BC76D8FA82E60BAA68015 8377F64D31B1B551AA3D8F7D4482192CA3292FED 8DBC6F2F474FE4959B7B33FF680733F324D385EA 8E1CB2E2467989A9369284E09669AD0FD691075E 9B8E44116F2AE302B8EDDB6C3E56F6559BE80936 E0AE4772051D74DE4DC1A525D9670BC12ED2EDAF EDFFE7DF9BA80ED6719B79A86EB9E3E9F875616F FADD9A15FFC9DE65A00E6A37BCC377A2B102203A FC775F7C3B031F8BD21AD814C2F168D402664E4B
- Alleged Members: 6
-
(they don't list you back)
0645197737A373E6EFF2B9F47913DF06FA3B5310 (not in the network) 23CC9B711B8FF93403C95E8643F0A85FFE1DFB3C (not in the network) 322967A70161145738F6CEB4F5165FDADF9EB27C (not in the network) 64DF2CA9276871CEE3638F1CD1310EBAA0A6E16C (not in the network) FA7B76686DAFB850A58072320907E282562BDD66 (not in the network) FA9F92CB28E2285A589643DDA31448361076D0C7 (not in the network)
- Indirect Members: 0
- none
- Platform
- Linux — Tor 0.4.9.14 on Linux
- Version
- 0.4.9.14 — Not Recommended
- Version Status
- Obsolete — Update urgently. See torproject.org/download
DNS Health
- Status
- DNS Lookup Failed (failed last 15 scans)
- Error
DNS Error: SOCKS 4 - Domain not found (NXDOMAIN)- Query Domain
f2ccbf0a0c374534b2dc2a77345ab063.3597a3f6.tor.exit.validator.1aeo.com- DNS Result
-
No Response (expected
64.65.4.1) - Upstream Resolver
-
Not enough data
Local /24 100% (~11 estimated queries) - Cross-Validation
- 0/4 instances succeeded
- First Hop
- MrTorRelay1 (US) 22D35F89DFEC859351B7F221773A3E25FA0FB14F
- Exit Address Used
185.243.218.229- Per-Instance Results
-
Cross Validation Attempt 1: DNS Fail, 19.7s (cv1_w1) Cross Validation Attempt 2: DNS Fail, 24.8s (cv2_w1) Cross Validation Attempt 3: DNS Fail, 16.7s (cv3_w1) Cross Validation Attempt 4: DNS Fail, 8.6s (cv4_w1)
Tested: 2026-11-03 20:05:40 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 20-21 43 53 80-81 443 853 989-990 1194 64738
IPv6 Exit Policy Summary
accept: 20-21 43 53 80-81 443 853 989-990 1194 64738
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 185.243.218.229:* accept *:20-21 accept *:43 accept *:53 accept *:80-81 accept *:443 accept *:853 accept *:989-990 accept *:1194 accept *:64738 reject *:*
Last fetch was at Wed, 04 Nov 2026 17:15:39 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-04 17:15:06).
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 (BW|T) | Guard BW (BW|Threshold) | Guard WFU (M|T) | Guard TK (M|T) | Stable MTBF (M|T) | Stable Uptime (Relay|T) | Desc Published | Cons Wt (Authority) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bastet (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, Guard, Exit | 224.0 Mbit/s (M) | 816.0 Kbit/s | 224.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 99.4% | 98% | 16.6d | 8d | 6.0d | 8.4d | 3.7d | 5.2d | 2026-11-03 23:08:41 | 224.0 Mbit/s (M) |
| dannenberg (DE) | Yes | Yes | Yes | — | Y | Yes | Yes | Valid, V2Dir, Fast, Stable, Guard, Exit | 336.0 Mbit/s (M) | 816.0 Kbit/s | 336.0 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s | 99.8% | 98% | 18.4d | 8d | 9.8d | 9.4d | 3.7d | 5.5d | 2026-11-03 23:08:41 | 336.0 Mbit/s (M) |
| dizum (NL) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, Guard, Exit | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 98.2% | 98% | 16.4d | 8d | 8.4d | 6.8d | 3.7d | 5.5d | 2026-11-03 23:08:41 | 80.0 Mbit/s (R) |
| faravahar (US) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, Guard, Exit | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.6% | 98% | 16.2d | 8d | 7.9d | 6.5d | 3.7d | 5.5d | 2026-11-03 23:08:41 | 80.0 Mbit/s (R) |
| gabelmoo (DE) | Yes | Yes | Yes | — | Y | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, Guard, Exit | 328.0 Mbit/s (M) | 816.0 Kbit/s | 328.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s | 99.5% | 98% | 16.4d | 8d | 7.6d | 10.8d | 3.7d | 5.5d | 2026-11-03 23:08:41 | 328.0 Mbit/s (M) |
| longclaw (US) | Yes | Yes | Yes | — | Y | Yes | N/T | Running, Valid, V2Dir, Fast, Stable, Guard, Exit | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.7% | 98% | 18.8d | 8d | 12.8d | 10.9d | 3.7d | 5.3d | 2026-11-03 23:08:41 | 80.0 Mbit/s (R) |
| maatuska (SE) | Yes | Yes | Yes | — | N | Yes | Yes | Running, Valid, V2Dir, Fast, Stable, Guard, Exit | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 98.9% | 98% | 15.7d | 8d | 3.3d | 2.4d | 3.7d | 5.5d | 2026-11-03 23:08:41 | 80.0 Mbit/s (R) |
| moria1 (US) | Yes | Yes | Yes | — | Y | Yes | No | Valid, V2Dir, Fast, Stable, Exit | 136.0 Mbit/s (M) | 8.4 Mbit/s | 136.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 82.1% | 98% | 9.8d | 8d | 20752.0d | 7616.8d | 3.7d | 5.5d | 2026-11-03 23:08:41 | 136.0 Mbit/s (M) |
| tor26 (AT) | Yes | Yes | Yes | — | Y | Yes | No | Valid, V2Dir, Fast, Exit | 280.0 Mbit/s (M) | 816.0 Kbit/s | 280.0 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s | 0.0% | 98% | 0.0d | 8d | 0.0d | 10.7d | 3.7d | 5.5d | 2026-11-03 23:08:41 | 280.0 Mbit/s (M) |
N/T = this authority does not test IPv6 • — = not in this vote • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known • Bandwidth source: (M) bandwidth-scanner measurement, (R) relay-reported, (U) unmeasured, counted as 0
Bandwidth Values Explained:
Measured (M) = An authority's bandwidth-scanner measurement of your relay (
Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (
Not published = The authority has no measurement of your relay in its vote and ignores relay-reported bandwidth, yet it voted Fast or its vote has no measurements at all: it judges your relay by a measurement kept from an earlier bandwidth file (0 if none), which its vote doesn't show.
Why different? A low measurement means the bandwidth scanners see your relay underperforming compared with other relays that report a similar speed. Votes list both values in kilobytes per second. Rules: Assigning flags in a vote, Computing a consensus.
Measured (M) = An authority's bandwidth-scanner measurement of your relay (
Measured= in its vote). An authority that has one uses it for the Fast and Guard flags, and the consensus weight is the median of these measurements when 3 or more authorities have one.Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (
Bandwidth= in every vote). An authority without a measurement uses it for flags, unless it has measurements for enough other relays (ignoring-advertised-bws=1); then your relay counts as 0 (U). It sets the consensus weight only when fewer than 3 authorities measured the relay, capped at 20 KB/s (maxunmeasuredbw) while 3 or more authorities publish measurements.Not published = The authority has no measurement of your relay in its vote and ignores relay-reported bandwidth, yet it voted Fast or its vote has no measurements at all: it judges your relay by a measurement kept from an earlier bandwidth file (0 if none), which its vote doesn't show.
Why different? A low measurement means the bandwidth scanners see your relay underperforming compared with other relays that report a similar speed. Votes list both values in kilobytes per second. Rules: Assigning flags in a vote, Computing a consensus.
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.
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.