View Relay "YourDataMyProblem"

Fingerprint: 39717519CEE39FB7E5EF12B0F7FB3F1ED14C58E9 | Family: 2 relays | 2mp@pulledtheirlife.support | AS58087 | Germany | Linux

Health Status

Consensus
In Consensus (7/8 Directory Auths)
Flags
Running, Valid, V2Dir, Exit (4)
DNS Health
Not Tested (via exitdnshealth.1aeo.com)
BW Verified
3/5 BW Auths Measured
Stability
Not Overloaded | UP 14h 3m 48s ago
Reachability
IPv4: 7/9 | v6: 6/8 (Directory Auths)
First Seen
15h 46m 3s ago
BW Weight
0.00% of Network | 0 Kbit/s Observed By Relay
Version
0.4.9.6 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.6 days is below 8 days requirement (7.4 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 14.3 hours below 25 hours (dir-spec default)
    Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
Notes:
  • Partial IPv4 reachability: 7/9 authorities can reach this relay

Connectivity and Location

Addresses
OR Address
118.64.131.45.in-addr.arpa
45.131.64.118:9001
[2a0e:97c0:3e3:b68::1]:9001
Exit Address
45.131.64.118
Reachability (Directory Authorities)
IPv4
7/9
IPv6
6/8 (1 don't test)
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS58087
AS Name
Florian Kolb (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.68% consensus weight, 8 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (4): Running: 7/8 | Valid: 7/8 | V2Dir: 7/8 | Fast: 0/8 | Stable: 0/8 | HSDir: 0/8 | Guard: 0/8 | Exit: 7/8
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (7/8 DA) 7/8 authorities reached relay ≥5/8 DA ORPort reachable
IPv6 Reachability Meets (6/7 DA) 6/7 tested authorities reached relay ≥4/7 tested (majority) (≥4/7 DA)
Valid Descriptor Meets (7/8 DA) 7/8 authorities assigned Valid Not blacklisted + valid descriptor (≥5/8 DA)
V2Dir DirPort Available Meets (7/8 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/8 DA)
Fast Speed Below (0/8 DA) 0 bit/s (R) ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Below (0/8 DA) Median: 0.6d (0/8 DA above threshold)
Min/Max: 0.6d / 0.6d (7/8 DA, Voting / Total Eligible)		 ≥16.8d - 56.5d (varies) (≥5/8 DA)
[Stricter] moria1: ≥311.9d
Uptime Below (0/8 DA) 0.6d (R) ≥8.8d - 8.8d (varies) (≥5/8 DA)
HSDir Prereq: Fast Below (0/8 DA) 0/8 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (0/8 DA) 0/8 DA assigned Stable ≥16.8d - 56.5d (varies) (≥5/8 DA)
[Stricter] moria1: ≥311.9d
Prereq: V2Dir Meets (7/8 DA) 7/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Meets (7/8 DA) Majority: 100.0% (7/8 DA) ≥98.0% (≥5/8 DA)
Time Known Below (0/8 DA) Median: 0.6d (0/8 DA above threshold)
Min/Max: 0.6d / 0.6d (7/8 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/8 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below (0/8 DA) 0/8 DA assigned Fast ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/8 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Below (0/8 DA) 0/8 DA assigned Stable ≥16.8d - 56.5d (varies) (≥5/8 DA)
[Stricter] moria1: ≥311.9d
Prereq: V2Dir Meets (7/8 DA) 7/8 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/8 DA)
WFU Meets (7/8 DA) Majority: 100.0% (7/8 DA) ≥98% (≥5/8 DA)
Time Known Below (0/8 DA) (need 7.4 more days) Median: 0.6d (0/8 DA above threshold)
Min/Max: 0.6d / 0.6d (7/8 DA, Voting / Total Eligible)		 ≥8 days (≥5/8 DA)
Bandwidth Below (0/8 DA) 0 bit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-336.0 Mbit/s (≥5/8 DA)
Exit Exit Policy Meets (7/8 DA) Port 80: Yes | Port 443: Yes (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/8 DA)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-05-01 03:45:08).

Bandwidth Metrics

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

Source: CollecTor — fetched 2026-05-01 03:45:08

Measured By
3/5 Bandwidth Authorities
Not measured by: gabelmoo, moria1
Median Measurement
0 bit/s
Min / Max
0 bit/s / 8 bit/s
Network Participation: Consensus Weight: 0.0000% of network (0th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0000% (0th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 14h 3m 48s ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
15h 46m 3s ago (2026-04-30 13:00:00)
Last Seen
1h 46m 3s ago (2026-05-01 03:00:00)
Last Restarted
14h 3m 48s ago (2026-04-30 14:42:15)
Last Changed Address
2026-04-30 13:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-04-30 20:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
2mp@pulledtheirlife.support
Family Configuration
Family Support
MyFamily Only (2) — Legacy only. Consider migrating to Happy Families. | View Full Family (2)
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Members: 2 
39717519CEE39FB7E5EF12B0F7FB3F1ED14C58E9 (this relay)
9A5805E6B43138867DBC5AFD3040107B45E00D9F
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

Platform
Linux — Tor 0.4.9.6 on Linux
Version
0.4.9.6 — Recommended
Version Status
Recommended

Exit Health & Policy

DNS Health
Status
Not Tested
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  43
  53
  79-81
  88
  110
  143
  194
  220
  389
  443
  531
  543-544
  563
  636
  749
  873
  989-995
  1194
  1723
  2083
  2086-2087
  4321
  5222-5223
  5228
  5900
  5984
  6660-6669
  6679
  6697
  6984
  8008
  8080
  8332-8333
  8443
  8888
  11371
IPv6 Exit Policy Summary
accept: 
  43
  53
  79-81
  88
  110
  143
  194
  220
  389
  443
  531
  543-544
  563
  636
  749
  873
  989-995
  1194
  1723
  2083
  2086-2087
  4321
  5222-5223
  5228
  5900
  5984
  6660-6669
  6679
  6697
  6984
  8008
  8080
  8332-8333
  8443
  8888
  11371
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 45.131.64.118:*
reject 109.71.252.88:*
accept *:43
accept *:53
accept *:79-81
accept *:88
accept *:110
accept *:143
accept *:194
accept *:220
accept *:389
accept *:443
accept *:531
accept *:543-544
accept *:563
accept *:636
accept *:749
accept *:873
accept *:989-995
accept *:1194
accept *:1723
accept *:2083
accept *:2086-2087
accept *:4321
accept *:5222-5223
accept *:5228
accept *:5900
accept *:5984
accept *:6660-6669
accept *:6679
accept *:6697
accept *:6984
accept *:8008
accept *:8080
accept *:8332-8333
accept *:8443
accept *:8888
accept *:11371
reject *:*

Last fetch was at Fri, 01 May 2026 04:46:01 GMT.

Consensus Evaluation

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

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 — — — N No — — — — — — — — — — — —
dannenberg (DE) Yes Yes Yes — N Yes 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.6d | 8d 0.6d | 47.4d 0.6d | 8.8d 100.0% | 98.0% 0.6d | 1.0d 2026-04-30 14:52:30 —
dizum (NL) No — — — N No — — — — — — — — — — — —
faravahar (US) Yes Yes Yes — N Yes 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.6d | 8d 0.6d | 56.7d 0.6d | 8.8d 100.0% | 98.0% 0.6d | 1.0d 2026-04-30 14:52:30 —
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.6d | 8d 0.6d | 55.6d 0.6d | 8.8d 100.0% | 98.0% 0.6d | 1.0d 2026-04-30 14:52:30 —
longclaw (US) Yes Yes Yes — Y Yes — Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 248.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.6d | 8d 0.6d | 63.3d 0.6d | 8.8d 100.0% | 98.0% 0.6d | 1.0d 2026-04-30 14:52:30 8 bit/s
maatuska (SE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 336.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.6d | 8d 0.6d | 16.8d 0.6d | 8.8d 100.0% | 98.0% 0.6d | 1.0d 2026-04-30 14:52:30 8 bit/s
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 8.4 Mbit/s 0 bit/s | 224.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.6d | 8d 0.6d | 311.9d 0.6d | 9.9d 100.0% | 98.0% 0.6d | 9.9d 2026-04-30 14:52:30 —
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.6d | 8d 0.6d | 56.5d 0.6d | 8.9d 100.0% | 98.0% 0.6d | 1.0d 2026-04-30 14:52:30 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.