View Relay "phoenix"

Operator: applied-privacy.net (105 relays) ✓ Validated | Family: 1 relay | email:[email protected]... | AS12989 | Netherlands | Linux

Consensus
Not In Consensus (2/9 Directory Auths, need 5)
BW Verified
0/6 BW Auths Measured 80 Kbit/s Median
Stability
Not Overloaded | DOWN 4d 6h 47m ago | UP 100% (1M)
Reachability
IPv4: 2/9 | v6: 0/7 (Directory Auths)
First Seen
1mo 1w 12h ago
BW Weight
0.00% of Network | 94 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, faravahar, gabelmoo, longclaw, maatuska, moria1, 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.
  • 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/
  • Low bandwidth authority measurements : Only 0/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.

Addresses
OR Address
86.54.28.107:9001
Reachability (Directory Authorities)
IPv4
2/9
IPv6
0/7 (2 don't test)
Location
Country
Netherlands Netherlands
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS12989
AS Name
Black HOST Ltd (BGP.tools)

Current Flags (7): Guard, Stable, Fast, HSDir, Running, V2Dir, Valid
Eligible Flags (1): Guard: 2/9 | Stable: 1/9 | Fast: 9/9 | HSDir: 2/9 | Running: 2/9 | V2Dir: 2/9 | Valid: 2/9 (need ≥5/9 for flag)
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Guard WFU Meets 100.0% (DA) ≥98% (all authorities)
Time Known Meets 36.7 days (DA) ≥8 days (all authorities)
Bandwidth Meets (≥2 MB/s) 94.1 Mbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s
Stable MTBF Below 37 days (DA) ≥26.6d - 45.4d (varies)
Uptime Meets 37.6d (R) ≥19.1d - 19.7d (varies)
Fast Speed Meets (≥100 KB/s) 94.1 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
HSDir WFU Meets 100.0% (DA) ≥98.0%
Time Known Meets 36.7 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.

94.09 Mbit/s | 94.09 Mbit/s| 8.59 Gbit/s| 10.74 Gbit/s  Not Measured
0.00% | N/A | N/A | N/A
86.54.28.107:9001
none
none
Netherlands Netherlands
View on Interactive Map
AS12989 | Black HOST Ltd (BGP.tools)
Fast Fast Guard Guard HSDir HSDir Running Running Stable Stable V2Dir V2Dir Valid Valid
82.1%/—/—/—
100.0%/100.0%/0.0%/0.0%
DOWN 4d 6h 47m ago
1mo 1w 12h ago (2025-12-03 16:00:00) | 4d 6h 54m ago (2026-01-05 22:00:00)
1mo 1w 13h ago (2025-12-03 15:17:34)
2025-12-03 16:00:00
No
Linux | Tor 0.4.8.21 on Linux
0.4.8.21 | Yes | recommended

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

  • Consensus Status (need ≥5/9): Not In Consensus — 2/9 authorities voted.
  • Flag Eligibility (need ≥5/9 for flag): Guard: 2/9 | Stable: 1/9 | Fast: 9/9 | HSDir: 2/9 | Running: 2/9 | Valid: 2/9 | V2Dir: 2/9
  • Reachability: IPv4: 2/9
  • Consensus Weight (Dir. Auth.): Median: 80.0 Kbit/s | Min: 80.0 Kbit/s | Max: 80.0 Kbit/s
  • Identified Issues:
    • 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, faravahar, gabelmoo, longclaw, maatuska, moria1, 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.
    • 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/
    • Low bandwidth authority measurements: Only 0/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.

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

Metric Dir Auth Measured Dir Auth Threshold Status
In Consensus (Dir. Auth.) 2/9 authorities ≥5/9 (majority) NOT IN CONSENSUS
Running (IPv4 Reachable) 2/9 authorities reached this relay ≥5/9 (majority) NOT RUNNING
Valid 2/9 (Running + Valid Descriptor) ≥5/9 (majority) NOT VALID
Consensus Weight (Dir. Auth.) 80.0 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) 36.7 days ≥8 days (all authorities) MEETS
Guard BW (Relay Reported) 94.1 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported) 37.6d ≥19.1d - 19.7d (typical) MEETS - all authorities
Stable MTBF (Dir. Auth., mtbf) 37 days ≥26.6d - 45.4d (typical)
[Stricter] moria1: ≥376.2d
BELOW - 1/9
Fast Speed (Relay Reported) 94.1 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 - 2/9
HSDir TK (Dir. Auth., tk) 36.7 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d
BELOW - 2/9

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 Fast, Guard, HSDir, Running, Stable, V2Dir, Valid 94.1 Mbit/s | 816.0 Kbit/s 94.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 36.7d | 8d 36.7d | 35.7d 37.6d | 20.2d 100.0% | 98.0% 36.7d | 1.0d 2026-01-10 01:40:51 80.0 Kbit/s
dizum (NL) Yes Yes N Yes Fast, Guard, HSDir, Running, Stable, V2Dir, Valid 94.1 Mbit/s | 816.0 Kbit/s 94.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 27.8d | 8d 26.2d | 26.6d 37.6d | 20.4d 100.0% | 98.0% 27.8d | 1.0d 2026-01-10 01:40:51 80.0 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) 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). 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.