Tor Relays :: myexitrelayD

View Relay "myexitrelayD"

Family: 1 relay | email:BilboHira88[]proton.me... | AS52048 | Latvia | Linux

Health Status

Consensus: Not In Consensus (3/9 Directory Auths, need 5)
Flags: Fast, Running, Stable, Valid (4)
BW Verified: 1/6 BW Auths Measured 25 Kbit/s Median
Stability: Not Overloaded | DOWN 2d 9h 47m ago | UP 100% (1M)

Reachability: IPv4: 3/9 (Directory Auths)
First Seen: 1w 13h 54m ago
BW Weight: 0.00% of Network | 31 Mbit/s Observed By Relay
Version: 0.4.8.21 Recommended

Issues Detected:

Not in consensus : Only 3/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 3/9 authorities can reach this relay
Suggestion: Authorities that cannot reach you: bastet, faravahar, gabelmoo, longclaw, maatuska, moria1. 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.
Guard: Time Known below threshold : Time Known 7.5 days is below 8 days requirement (0.5 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.
Low bandwidth authority measurements : Only 1/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: 185.28.47.28:9001

Reachability (Directory Authorities)

IPv4: 3/9

Location

Country: Latvia
Interactive Map: View on Interactive Map

Autonomous System

AS Number: AS52048
AS Name: SIA RixHost (BGP.tools)

Flags and Eligibility

Current Flags (4): Stable, Fast, Running, Valid

Eligibility Flag Vote Details

Flag	Metric	Status	Relay Value	Threshold Required
Guard	WFU	Meets	100.0% (DA)	≥98% (all authorities)
	Time Known	Below (need 0.5 more days)	7.5 days (DA)	≥8 days (all authorities)
	Bandwidth	Meets (≥2 MB/s)	31.5 Mbit/s (R)	≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s
Stable	MTBF	Below	8 days (DA)	≥26.6d - 45.4d (varies)
Stable	Uptime	Below	7.6d (R)	≥19.1d - 19.7d (varies)
Fast	Speed	Meets (≥100 KB/s)	31.5 Mbit/s (R)	≥800.0 Kbit/s (guarantee) OR top 7/8
HSDir	WFU	Meets	100.0% (DA)	≥98.0%
HSDir	Time Known	Below	7.5 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

myexitrelayD

Fingerprint

52C14B1DF62601763B152B8B94E372A467D44F43

AROI (?)

none

Contact

email:BilboHira88[]proton.me pgp:572182EB80795CA44254ED9BC74AE2C661E6AA00

IPv4 Exit Policy Summary

accept: 
  80
  443

IPv6 Exit Policy Summary

none

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.28.47.28:*
accept *:80
accept *:443
reject *:*

Effective Family Member: 1

52C14B1DF62601763B152B8B94E372A467D44F43

Alleged Family Members: 0

none

Indirect Family Members: 0

none

Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit): 31.54 Mbit/s | 25.17 Mbit/s| 25.17 Mbit/s| 50.33 Mbit/s Measured
Network Participation (Consensus Weight | Guard | Middle | Exit): 0.00% | N/A | N/A | N/A
OR Address: 185.28.47.28:9001
Exit Address: none
Dir Address: none
Country: Latvia
Interactive Map: View on Interactive Map
Autonomous System (AS Number | AS Name): AS52048 | SIA RixHost (BGP.tools)
Flags: 4: Fast Running Stable Valid
Flag Uptime (1M/6M/1Y/5Y): 0.0%/—/—/—
Uptime (1M/6M/1Y/5Y): 100.0%/0.0%/0.0%/0.0%
Uptime / Downtime: DOWN 2d 9h 47m ago
Seen (First | Last): 1w 13h 54m ago (2026-01-02 15:00:00) | 2d 9h 54m ago (2026-01-07 19:00:00)
Last Restarted: 1w 14h 14m ago (2026-01-02 14:40:20)
Last Changed Address or Port: 2026-01-02 15:00:00
Hibernating: No
Platform (Short | Long): Linux | Tor 0.4.8.21 on Linux
Version (Running | Recommended | Status): 0.4.8.21 | Yes | recommended

Consensus Evaluation

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

Consensus Status (need ≥5/9): Not In Consensus — 3/9 authorities voted.
Flag Eligibility (need ≥5/9 for flag): Guard: 0/9 | Stable: 0/9 | Fast: 9/9 | HSDir: 3/9 | Running: 3/9 | Valid: 3/9 | V2Dir: 3/9
Reachability: IPv4: 3/9
Consensus Weight (Dir. Auth.): Median: 25.2 Kbit/s | Min: 15.2 Kbit/s | Max: 25.2 Kbit/s
Identified Issues:
- Not in consensus: Only 3/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 3/9 authorities can reach this relay
  - Suggestion: Authorities that cannot reach you: bastet, faravahar, gabelmoo, longclaw, maatuska, moria1. 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.
- Guard: Time Known below threshold: Time Known 7.5 days is below 8 days requirement (0.5 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.
- Low bandwidth authority measurements: Only 1/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.

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.)	3/9 authorities	≥5/9 (majority)	NOT IN CONSENSUS
Running (IPv4 Reachable)	3/9 authorities reached this relay	≥5/9 (majority)	NOT RUNNING
Valid	3/9 (Running + Valid Descriptor)	≥5/9 (majority)	NOT VALID
Consensus Weight (Dir. Auth.)	25.2 Kbit/s (median)	N/A (no threshold, used for path selection)	—
Guard WFU (Dir. Auth., guard-wfu)	100.0%	≥98% (all authorities)	MEETS
Guard TK (Dir. Auth., tk)	7.5 days	≥8 days (all authorities)	BELOW - need 0.5 more days
Guard BW (Relay Reported)	31.5 Mbit/s	≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s	MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported)	7.6d	≥19.1d - 19.7d (typical)	BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf)	8 days	≥26.6d - 45.4d (typical) [Stricter] moria1: ≥376.2d	BELOW - 0/9
Fast Speed (Relay Reported)	31.5 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)	100.0%	≥98.0% (from all auths)	BELOW - 3/9
HSDir TK (Dir. Auth., tk)	7.5 days	≥1.0d (8/9 auths) [Stricter] moria1: ≥9.9d	BELOW - 3/9

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	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)	Yes	Yes	N	Yes	Exit, Fast, HSDir, Running, Stable, V2Dir, Valid	31.5 Mbit/s \| 816.0 Kbit/s	31.5 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	7.5d \| 8d	7.5d \| 35.7d	7.6d \| 20.2d	100.0% \| 98.0%	7.5d \| 1.0d	2026-01-09 23:59:42	25.2 Kbit/s
dizum (NL)	Yes	Yes	N	Yes	Exit, Fast, HSDir, Running, Stable, V2Dir, Valid	31.5 Mbit/s \| 816.0 Kbit/s	31.5 Mbit/s \| 80.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	7.5d \| 8d	7.5d \| 26.6d	7.6d \| 20.4d	100.0% \| 98.0%	7.5d \| 1.0d	2026-01-10 03:01:42	25.2 Kbit/s
faravahar (US)	No	—	N	No	—	—	—	—	—	—	—	—	—	—	—
gabelmoo (DE)	No	—	Y	No	—	—	—	—	—	—	—	—	—	—	—
longclaw (US)	No	—	Y	No	—	—	—	—	—	—	—	—	—	—	—
maatuska (SE)	No	—	Y	No	—	—	—	—	—	—	—	—	—	—	—
moria1 (US)	No	—	Y	No	—	—	—	—	—	—	—	—	—	—	—
tor26 (AT)	Yes	Yes	Y	Yes	Exit, Fast, HSDir, Running, Stable, V2Dir, Valid	31.5 Mbit/s \| 816.0 Kbit/s	31.5 Mbit/s \| 272.0 Mbit/s OR 16.0 Mbit/s	100.0% \| 98%	7.5d \| 8d	7.5d \| 51.8d	7.6d \| 19.7d	100.0% \| 98.0%	7.5d \| 1.0d	2026-01-10 03:01:42	15.2 Kbit/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.