View Relay "quantumflux"

Fingerprint: CC55B3F4340C97C0219E8ED2321D5B44DE3FA028 | Family: 1 relay | AS51852 | Switzerland | Linux

Health Status

Consensus
Not In Consensus (4/9 Directory Auths, need 5)
Flags
Running, Valid, V2Dir, Fast, Exit (5)
DNS Health
Healthy (19.4s, 57th percentile) (via exitdnshealth.1aeo.com)
BW Verified
2/6 BW Auths Measured 160 Kbit/s Median
Stability
Not Overloaded | DOWN 3h 15m 38s ago | UP 100% (1M)
Reachability
IPv4: 4/9 (Directory Auths)
First Seen
1w 11h 15m ago
BW Weight
0.00% of Network | 179 Mbit/s Observed By Relay
Version
0.4.9.7 Recommended
Issues Detected:
  • Not in consensus : Only 4/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 4/9 authorities can reach this relay
    Suggestion: Authorities that cannot reach you: bastet, faravahar, gabelmoo, longclaw, tor26. 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: 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 7.4 days is below 8 days requirement (0.6 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 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.
  • 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
hostedby.privatelayer.com
141.255.167.134:9001
Exit Address
141.255.167.134
Reachability (Directory Authorities)
IPv4
4/9
Location
Country
Switzerland Switzerland
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS51852
AS Name
Private Layer INC (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.13% consensus weight, 12 operators)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (0): Running: 4/9 | Valid: 4/9 | V2Dir: 4/9 | Fast: 4/9 | Stable: 3/9 | HSDir: 2/9 | Guard: 0/9 | Exit: 4/9
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Below (4/9 DA) 4/9 authorities reached relay ≥5/9 DA ORPort reachable
IPv6 Reachability Below (0/5 DA) 0/5 tested authorities reached relay ≥3/5 tested (majority) (≥3/5 DA)
Valid Descriptor Partial (4/9 DA) 4/9 authorities assigned Valid Not blacklisted + valid descriptor (≥5/9 DA)
V2Dir DirPort Available Meets (4/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 179.3 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 (0/9 DA) Median: 7.4d (0/9 DA above threshold)
Min/Max: 4.0d / 7.4d (4/9 DA, Voting / Total Eligible)		 ≥19.6d - 52.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥328.2d
Uptime Meets (9/9 DA) 7.5d (R) ≥6.5d - 6.6d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (4/9 DA) 4/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 (3/9 DA) 3/9 DA assigned Stable ≥19.6d - 52.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥328.2d
Prereq: V2Dir Below (4/9 DA) 4/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (3/9 DA) Median: 100.0% (3/9 DA above threshold)
Min/Max: 98.0% / 100.0% (4/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Below (3/9 DA) Median: 6.9d (0/9 DA above threshold)
Min/Max: 5.3d / 7.4d (4/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below (4/9 DA) 4/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 (3/9 DA) 3/9 DA assigned Stable ≥19.6d - 52.0d (varies) (≥5/9 DA)
[Stricter] moria1: ≥328.2d
Prereq: V2Dir Below (4/9 DA) 4/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (3/9 DA) Median: 100.0% (3/9 DA above threshold)
Min/Max: 98.0% / 100.0% (4/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 1.1 more days) Median: 6.9d (0/9 DA above threshold)
Min/Max: 5.3d / 7.4d (4/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 179.3 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-336.0 Mbit/s (≥5/9 DA)
Exit Exit Policy Partial (4/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-05-14 21:15:08).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
179.26 Mbit/s
Advertised Bandwidth
179.26 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
2.0 TB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-05-14 21:15:08

Measured By
2/6 Bandwidth Authorities
Not measured by: bastet, gabelmoo, longclaw, tor26
Median Measurement
160.0 Kbit/s
Min / Max
80.0 Kbit/s / 256.0 Kbit/s
Deviation
176.0 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (2th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
DOWN 3h 15m 38s ago
Overall Uptime (1M/6M/1Y/5Y)
100.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (100.0%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
1w 11h 15m ago (2026-05-07 10:00:00)
Last Seen
3h 15m 38s ago (2026-05-14 18:00:00)
Last Restarted
1w 11h 28m ago (2026-05-07 09:47:07)
Last Changed Address
2026-05-07 10:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-05-14 14:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
none
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
CC55B3F4340C97C0219E8ED2321D5B44DE3FA028 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

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

Exit Health & Policy

DNS Health
Status
Healthy (avg. 19.4s, 57th percentile)
Query Domain
107f0a0215154cbe8f2c186efb817875.cc55b3f4.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
4/4 instances succeeded
First Hop
LauchYT (DE) 6AEF55C91E55A769D41AFD34DEB49264572315AE
Exit Address Used
141.255.167.134
Per-Instance Results
Cross Validation Attempt 1: Success, 19.5s (cv1_w3)
Cross Validation Attempt 2: Success, 23.9s (cv2_w3)
Cross Validation Attempt 3: Success, 19.0s (cv3_w3)
Cross Validation Attempt 4: Success, 15.2s (cv4_w3)
Tested: 2026-05-14 07:13:50 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
reject: 
  25
  119
  135-139
  445
  465
  563
  587
  1214
  4661-4666
  6346-6429
  6699
  6881-6999
IPv6 Exit Policy Summary
None
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 141.255.167.134:*
reject *:25
reject *:119
reject *:135-139
reject *:445
reject *:465
reject *:563
reject *:587
reject *:1214
reject *:4661-4666
reject *:6346-6429
reject *:6699
reject *:6881-6999
accept *:*

Last fetch was at Thu, 14 May 2026 21:15:38 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-05-14 21:15: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 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 Yes — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 179.3 Mbit/s | 816.0 Kbit/s 179.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 7.4d | 8d 7.4d | 49.9d 7.5d | 6.6d 100.0% | 98.0% 7.4d | 1.0d 2026-05-14 19:21:51 80.0 Kbit/s
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 179.3 Mbit/s | 816.0 Kbit/s 179.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 98.0% | 98% 6.5d | 8d 4.0d | 19.6d 7.5d | 6.6d 98.0% | 98.0% 6.5d | 1.0d 2026-05-14 19:21:51 80.0 Kbit/s
faravahar (US) No — — — N No — — — — — — — — — — —
gabelmoo (DE) No — — — Y No — — — — — — — — — — —
longclaw (US) No — — — Y No — — — — — — — — — — —
maatuska (SE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 179.3 Mbit/s | 816.0 Kbit/s 179.3 Mbit/s | 336.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 7.4d | 8d 7.4d | 23.1d 7.5d | 6.6d 100.0% | 98.0% 7.4d | 1.0d 2026-05-14 19:21:51 256.0 Kbit/s
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, Exit 179.3 Mbit/s | 8.4 Mbit/s 179.3 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.3d | 8d 7.4d | 328.2d 7.5d | 6.6d 100.0% | 98.0% 5.3d | 9.9d 2026-05-14 19:21:51 240.0 Kbit/s
tor26 (AT) No — — — Y No — — — — — — — — — — —

— = 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.