View Relay "tdxchg"

Family: 1 relay | TOR Operator <[email protected]> | AS51167 | Germany | FreeBSD

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, V2Dir, Valid (3)
BW Verified
5/6 BW Auths Measured 280 bit/s Median
Stability
Overloaded | DOWN 3h 47m 29s ago | UP 75% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
18y 2mo 2w ago
BW Weight
0.00% of Network | 1 Mbit/s Observed By Relay
Version
0.4.8.10 Not Recommended
Issues Detected:
  • Guard: bandwidth below threshold : Observed bandwidth 0.2 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.
  • Guard: WFU below threshold : Weighted Fractional Uptime 91.0% 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.
  • 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: 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.
  • 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: WFU below threshold : WFU 91.0% 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.
  • 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.8.10 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.
  • Write Bandwidth Limit Hit : Write rate limit (2 Mbit/s) was hit 3,857 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 (2 Mbit/s) was hit 7,353 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=2 Mbit/s, Burst=2 Mbit/s. Limits hit: Write=3,857, Read=7,353.

Connectivity and Location

Addresses
OR Address
tdxchg.insc.de
207.180.192.66:9001
[2a02:c207:3002:8686::66]:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Germany Germany
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS51167
AS Name
Contabo GmbH (BGP.tools)

Flags and Eligibility

Current Flags (3): Running, V2Dir, Valid
Eligible Flags (4): Guard: 0/9 | Stable: 3/9 | Fast: 9/9 | HSDir: 2/9 | Running: 9/9 | V2Dir: 9/9 | Valid: 9/9 (need ≥5/9 for flag)
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Guard WFU Below 91.0% (DA) ≥98% (all authorities)
Time Known Meets 9.8 days (DA) ≥8 days (all authorities)
Bandwidth Below 1.7 Mbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s
Stable MTBF Below 10 days (DA) ≥26.6d - 45.4d (varies)
Uptime Meets 185.9d (R) ≥19.1d - 19.7d (varies)
Fast Speed Meets (≥100 KB/s) 1.7 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
HSDir WFU Below 91.0% (DA) ≥98.0%
Time Known Below 9.8 days (DA) ≥1.0d (most) / 9.9d (max)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-01-10 04:46:16).

Last fetch was at Sat, 10 Jan 2026 04:47:26 GMT.

Nickname
tdxchg
Fingerprint
0BA30A3D11B73F95D1447CC9B35BE5F0681D5A1C
AROI (?)
none
Contact
TOR Operator <[email protected]>
IPv4 Exit Policy Summary 
reject: 
  1-65535
IPv6 Exit Policy Summary 
none
Exit Policy 
reject *:*
Effective Family Member: 1 
0BA30A3D11B73F95D1447CC9B35BE5F0681D5A1C
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
1.67 Mbit/s | 1.64 Mbit/s| 1.64 Mbit/s| 2.46 Mbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.00% | N/A | N/A | N/A
OR Address
tdxchg.insc.de | 207.180.192.66:9001, [2a02:c207:3002:8686::66]:9001
Exit Address
none
Dir Address
none
Country
Germany Germany
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS51167 | Contabo GmbH (BGP.tools)
Flags: 3
Running Running V2Dir V2Dir Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
Match Overall Uptime (75.3%/71.3%/73.7%/74.0%)
Uptime (1M/6M/1Y/5Y)
75.3%/71.3%/73.7%/74.0%
Uptime / Downtime
DOWN 3h 47m 29s ago
Seen (First | Last)
18y 2mo 2w ago (2007-10-27 12:00:00) | 3h 55m 3s ago (2026-01-10 01:00:00)
Last Restarted
6mo 5d 21h ago (2025-07-08 07:29:05)
Last Changed Address or Port
2021-08-23 17:00:00
Hibernating
No
Platform (Short | Long)
FreeBSD | Tor 0.4.8.10 on FreeBSD
Version (Running | Recommended | Status)
0.4.8.10 | No | obsolete

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-01-10 04:46:16).

  • Consensus Status (need ≥5/9): In Consensus — 9/9 authorities voted.
  • Flag Eligibility (need ≥5/9 for flag): Guard: 0/9 | Stable: 3/9 | Fast: 9/9 | HSDir: 2/9 | Running: 9/9 | Valid: 9/9 | V2Dir: 9/9
  • Reachability: IPv4: 9/9 | IPv6: 6/0
  • Consensus Weight (Dir. Auth.): Median: 280 bit/s | Min: 88 bit/s | Max: 1632 bit/s [Warning] High deviation
  • Identified Issues:
    • Guard: bandwidth below threshold: Observed bandwidth 0.2 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.
    • Guard: WFU below threshold: Weighted Fractional Uptime 91.0% 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.
    • 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: 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.
    • 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: WFU below threshold: WFU 91.0% 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.
    • 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.8.10 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.
    • Write Bandwidth Limit Hit: Write rate limit (2 Mbit/s) was hit 3,857 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 (2 Mbit/s) was hit 7,353 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=2 Mbit/s, Burst=2 Mbit/s. Limits hit: Write=3,857, Read=7,353.

Summary: Your Relay vs Consensus

Green = meets threshold, Red = below threshold, Yellow = partial.

Metric Dir Auth Measured Dir Auth Threshold Status
In Consensus (Dir. Auth.) 9/9 authorities ≥5/9 (majority) IN CONSENSUS
Running (IPv4 Reachable) 9/9 authorities reached this relay ≥5/9 (majority) RUNNING
Valid 9/9 (Running + Valid Descriptor) ≥5/9 (majority) VALID
Consensus Weight (Dir. Auth.) 280 bit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 91.0% ≥98% (all authorities) BELOW - cannot get Guard
Guard TK (Dir. Auth., tk) 9.8 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 1.7 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s BELOW - need ≥2 MB/s
Stable Uptime (Relay Reported) 185.9d ≥19.1d - 19.7d (typical) MEETS - all authorities
Stable MTBF (Dir. Auth., mtbf) 10 days ≥26.6d - 45.4d (typical)
[Stricter] moria1: ≥376.2d 		BELOW - 3/9
Fast Speed (Relay Reported) 1.7 Mbit/s ≥800.0 Kbit/s (guarantee) OR ≥816.0 Kbit/s (typical)
[Stricter] moria1: ≥8.4 Mbit/s 		MEETS - ≥100 KB/s guarantee
HSDir WFU (Dir. Auth., wfu) 91.0% ≥98.0% (from all auths) BELOW - 2/9
HSDir TK (Dir. Auth., tk) 9.8 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d 		BELOW - 2/9
IPv6 Reachable (Dir. Auth.) 6/6 tested ≥4/6 (majority) REACHABLE

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 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 Y Yes Yes Running, V2Dir, Valid 1.7 Mbit/s | 816.0 Kbit/s 1.7 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 91.0% | 98% 9.8d | 8d 0.1d | 47.0d 185.9d | 19.7d 91.0% | 98.0% 9.8d | 1.0d 2026-01-10 02:14:47 280 bit/s
dannenberg (DE) Yes Yes N Yes — Fast, V2Dir, Valid 1.7 Mbit/s | 816.0 Kbit/s 1.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 88.7% | 98% 9.6d | 8d 0.1d | 35.7d 185.9d | 20.2d 88.7% | 98.0% 9.6d | 1.0d 2026-01-10 02:14:47 1632 bit/s
dizum (NL) Yes Yes N Yes — Fast, HSDir, Running, Stable, V2Dir, Valid 1.7 Mbit/s | 816.0 Kbit/s 1.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 34.1d | 8d 32.2d | 26.6d 185.9d | 20.4d 100.0% | 98.0% 34.1d | 1.0d 2026-01-10 02:14:47 1632 bit/s
faravahar (US) Yes Yes N Yes Yes Fast, Running, V2Dir, Valid 1.7 Mbit/s | 816.0 Kbit/s 1.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 92.2% | 98% 9.6d | 8d 0.1d | 41.9d 185.9d | 19.1d 92.2% | 98.0% 9.6d | 1.0d 2026-01-10 02:14:47 1632 bit/s
gabelmoo (DE) Yes Yes Y Yes Yes Running, V2Dir, Valid 1.7 Mbit/s | 816.0 Kbit/s 1.7 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 91.8% | 98% 9.8d | 8d 0.1d | 45.4d 185.9d | 19.6d 91.8% | 98.0% 9.8d | 1.0d 2026-01-10 02:14:47 88 bit/s
longclaw (US) Yes Yes Y Yes — Fast, HSDir, Running, Stable, V2Dir, Valid 1.7 Mbit/s | 816.0 Kbit/s 1.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 184.9d | 8d 184.9d | 48.7d 185.9d | 19.5d 100.0% | 98.0% 184.9d | 1.0d 2026-01-10 02:14:47 1632 bit/s
maatuska (SE) Yes Yes Y Yes Yes Running, V2Dir, Valid 1.7 Mbit/s | 816.0 Kbit/s 1.7 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 90.1% | 98% 9.9d | 8d 0.1d | 42.3d 185.9d | 19.4d 90.1% | 98.0% 9.9d | 1.0d 2026-01-10 02:14:47 112 bit/s
moria1 (US) Yes Yes Y Yes Yes Running, Stable, V2Dir, Valid 1.7 Mbit/s | 8.4 Mbit/s 1.7 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 91.2% | 98% 9.8d | 8d 20279.9d | 376.2d 185.9d | 20.4d 91.2% | 98.0% 9.8d | 9.9d 2026-01-10 02:14:47 272 bit/s
tor26 (AT) Yes Yes Y Yes Yes Running, V2Dir, Valid 1.7 Mbit/s | 816.0 Kbit/s 1.7 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 91.5% | 98% 9.6d | 8d 0.1d | 51.8d 185.9d | 19.7d 91.5% | 98.0% 9.6d | 1.0d 2026-01-10 02:14:47 96 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). This is your relay's self-reported uptime from its 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.