View Relay "badthread"

Fingerprint: 125560B129DDD64B937952662DC408FDD34B5B04 | Operator: badthread.org (1 relay) 🚫 Unauthorized | Family: 1 relay | tor@badthread.org url:badthread.org... | AS213230 | United States of America | OpenBSD

Health Status

Consensus
Not In Consensus (2/9 Directory Auths, need 5)
Flags
Running, Valid, Fast (3)
BW Verified
2/6 BW Auths Measured 7360 bit/s Median
Stability
Not Overloaded | UP 1d 5h 3m ago | UP 55% (1M)
Reachability
IPv4: 2/9 | v6: 0/7 (Directory Auths)
First Seen
2y 1mo 2d ago
BW Weight
0.00% of Network | 6 Mbit/s Observed By Relay
Version
0.4.8.21 Recommended
Issues Detected:
  • Not in consensus : Only 2/9 authorities voted for this relay (need 5)
    Suggestion: Verify your relay is reachable from multiple geographic locations. Check firewall rules allow incoming connections on your ORPort from all directory authority IP addresses.
  • IPv4 reachability issues : Only 2/9 authorities can reach this relay
    Suggestion: Authorities that cannot reach you: bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska. Check: 1) Firewall allows incoming TCP on ORPort, 2) No ISP-level blocking, 3) Tor is running and listening. Use 'nc -zv your-ip your-orport' from external hosts to test.
  • IPv6 not reachable : 0/7 authorities that test IPv6 can reach your IPv6 address
    Suggestion: Verify IPv6 is correctly configured: 1) Check ORPort binding includes IPv6 address, 2) Firewall allows IPv6 traffic, 3) IPv6 address is publicly routable. Test with: curl -6 http://ipv6.icanhazip.com/
  • 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.8 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 69.3% 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 69.3% 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.
  • Low bandwidth authority measurements : Only 2/6 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.

Connectivity and Location

Addresses
OR Address
badthread.org
5.161.215.230:420
Reachability (Directory Authorities)
IPv4
2/9
IPv6
0/7 (2 don't test)
Location
Country
United States of America United States of America
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS213230
AS Name
Hetzner Online GmbH (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 4 operators)

Flags and Eligibility

Current Flags (3): Running, Valid, Fast
Eligible Flags (0): Running: 2/9 | Valid: 2/9 | V2Dir: 2/9 | Fast: 2/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 Below (2/9 DA) 2/9 authorities reached relay ≥5/9 DA ORPort reachable
IPv6 Reachability Below (0/7 DA) 0/7 tested authorities reached relay ≥4/7 tested (majority) (≥4/7 DA)
Valid Descriptor Partial (2/9 DA) 2/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) 6.7 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: 9989.3d (1/9 DA above threshold)
Min/Max: 0.2d / 19978.4d (2/9 DA, Voting / Total Eligible)		 ≥17.9d - 58.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥293.7d
Uptime Below (0/9 DA) 1.2d (R) ≥3.3d - 3.4d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (2/9 DA) 2/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 ≥17.9d - 58.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥293.7d
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: 69.9% (0/9 DA above threshold)
Min/Max: 69.3% / 70.5% (2/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Below (2/9 DA) Median: 10.2d (2/9 DA above threshold)
Min/Max: 9.9d / 10.4d (2/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below (2/9 DA) 2/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 ≥17.9d - 58.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥293.7d
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: 69.9% (0/9 DA above threshold)
Min/Max: 69.3% / 70.5% (2/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Meets (2/9 DA) Median: 10.2d (2/9 DA above threshold)
Min/Max: 9.9d / 10.4d (2/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 6.7 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-29 12:45:07).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
6.73 Mbit/s
Advertised Bandwidth
6.73 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
185 TB (5 years)
1mo: 24 GB | 6mo: 3.9 TB | 1y: 24 TB | 5y: 185 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-29 12:45:07

Measured By
2/6 Bandwidth Authorities
Not measured by: bastet, gabelmoo, longclaw, maatuska
Median Measurement
7360.0 bit/s
Min / Max
1920 bit/s / 12.8 Kbit/s
Deviation
10.9 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0002% of network (9th pctl) | Guard: N/A | Middle: 0.0005% (12th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 1d 5h 3m ago
Overall Uptime (1M/6M/1Y/5Y)
55.7%/66.3%/67.3%/73.1%
Flag Uptime (1M/6M/1Y/5Y)
—/66.1%/67.1%/72.8%
Hibernating
No
Timestamps
First Seen
2y 1mo 2d ago (2024-02-25 18:00:00)
Last Seen
2h 45m 55s ago (2026-03-29 10:00:00)
Last Restarted
1d 5h 3m ago (2026-03-28 07:42:46)
Last Changed Address
2026-02-22 08:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-03-29 05:00 UTC

AROI Domain (?)
badthread.org
Operator Validation
Unvalidated
This Relay
Unvalidated
Error: DNS-RSA: TXT record not found at badthread.org
Contact
tor@badthread.org url:badthread.org proof:dns-rsa ciissversion:2
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
125560B129DDD64B937952662DC408FDD34B5B04 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

Platform
OpenBSD — Tor 0.4.8.21 on OpenBSD
Version
0.4.8.21 — 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, 29 Mar 2026 12:45:53 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-03-29 12: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 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) No — — — Y No — — — — — — — — — — — —
dannenberg (DE) No — — — N No — — — — — — — — — — — —
dizum (NL) No — — — N No — — — — — — — — — — — —
faravahar (US) No — — — N No — — — — — — — — — — — —
gabelmoo (DE) No — — — Y No — — — — — — — — — — — —
longclaw (US) No — — — Y No — — — — — — — — — — — —
maatuska (SE) No — — — Y No — — — — — — — — — — — —
moria1 (US) Yes Yes No — Y Yes — Running, Valid, Fast, Stable 6.7 Mbit/s | 8.4 Mbit/s 6.7 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 69.3% | 98% 9.9d | 8d 19978.4d | 293.7d 1.2d | 4.1d 69.3% | 98.0% 9.92d | 9.90d 2026-03-29 08:47:51 12.8 Kbit/s
tor26 (AT) Yes Yes No — Y Yes — Running, Valid, Fast 6.7 Mbit/s | 816.0 Kbit/s 6.7 Mbit/s | 264.0 Mbit/s OR 16.0 Mbit/s 70.5% | 98% 10.4d | 8d 0.2d | 58.7d 1.2d | 3.8d 70.5% | 98.0% 10.4d | 1.0d 2026-03-29 08:47:51 1920 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.