View Relay "Unnamed"

Fingerprint: 8196C312C59914FC0111BA7800C194271148F1BD | Family: 1 relay | laure.accardi.ikf@inbox.lv | AS14956 | Singapore | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, Fast, MiddleOnly, BadExit (5)
BW Verified
5/7 BW Auths Measured 3520 bit/s Median
Stability
Not Overloaded | UP 2d 1h 4m ago
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
3d 18h 6m ago
BW Weight
0.00% of Network | 11 Mbit/s Observed By Relay
Version
0.4.9.14 Recommended
Issues Detected:
  • 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 12 Mbit/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 96.7% 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.
  • Guard: Time Known below threshold : Time Known 3.4 days is below 8 days requirement (4.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.
  • 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 96.7% 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.
  • BadExit flag assigned : This relay has been flagged as a bad exit by directory authorities. BadExit means authorities detected malicious behavior (traffic modification, SSL stripping, etc.).
    Suggestion: Contact bad-relays@lists.torproject.org to understand and resolve this issue.
  • MiddleOnly restriction active : This relay has been restricted to middle position only by directory authorities. MiddleOnly removes Guard, Exit, HSDir, and V2Dir flags, and adds BadExit. This significantly limits the relay's role in the network.
    Suggestion: This may indicate suspicious behavior patterns, Sybil risk indicators, or policy violations. Contact bad-relays@lists.torproject.org for more information.

Connectivity and Location

Addresses
OR Address
172.86.80.83:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Singapore Singapore
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS14956
AS Name
RouterHosting LLC (BGP.tools)
AS Rarity
Epic (score: 3/5, 0.09% consensus weight, 8 operators)

Flags and Eligibility

Current Flags (5): Running, Valid, Fast, MiddleOnly, BadExit
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 5/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 0/9
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Meets (9/9 DA) 9/9 authorities reached relay ≥5/9 DA ORPort reachable
Valid Descriptor Meets (9/9 DA) 9/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) 11.6 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: 3.7d (0/9 DA above threshold)
Min/Max: 1.7d / 3.7d (9/9 DA, Voting / Total Eligible)		 ≥4.9d - 7.8d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10630.3d
Uptime Below (0/9 DA) 2.0d (R) ≥6.2d - 6.5d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (5/9 DA) 5/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 (0/9 DA) 0/9 DA assigned Stable ≥4.9d - 7.8d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10630.3d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Majority: 100.0% (8/9 DA)
Min/Med/Max: 96.7% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 3.7d (0/9 DA above threshold)
Min/Max: 3.1d / 3.7d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.7d
Guard Prereq: Fast Meets (5/9 DA) 5/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 (0/9 DA) 0/9 DA assigned Stable ≥4.9d - 7.8d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10630.3d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Majority: 100.0% (8/9 DA)
Min/Med/Max: 96.7% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 4.3 more days) Median: 3.7d (0/9 DA above threshold)
Min/Max: 3.1d / 3.7d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 11.6 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-320.0 Mbit/s (≥5/9 DA)
Exit Exit Policy Partial (0/9 DA) (only port 80) Port 80: Yes | Port 443: Yes (R) Allows ≥1 /8 on ports 80 AND 443 (≥5/9 DA)
MiddleOnly Restriction (by DA) Flagged (9/9 DA) 9/9 authorities assigned MiddleOnly Suspicious behavior, Sybil risk, or policy violation
BadExit Restriction (by DA) Flagged (5/9 DA) 5/9 authorities assigned BadExit Exit traffic manipulation, SSL stripping, or policy violation

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-10-23 12:01:17).

Bandwidth Metrics

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

Source: CollecTor — fetched 2026-10-23 12:01:17

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Median Measurement
3520 bit/s
Min / Max
8 bit/s / 11.6 Kbit/s
Deviation
11.5 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0001% of network (8th pctl) | Guard: N/A | Middle: 0.0004% (10th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 2d 1h 4m 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
3d 18h 6m ago (2026-10-19 19:00:00)
Last Seen
2h 6m 24s ago (2026-10-23 11:00:00)
Last Restarted
2d 1h 4m ago (2026-10-21 12:02:16)
Last Changed Address
2026-10-19 19:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-10-23 04:00 UTC

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

Software and Version

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

Exit Health & Policy

DNS Health
Not an exit relay — DNS health testing does not apply.
IPv4 Exit Policy Summary
accept: 
  22
  53
  80
  443
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 172.86.80.83:*
accept *:22
accept *:53
accept *:80
accept *:443
reject *:*

Last fetch was at Fri, 23 Oct 2026 13:06:07 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-10-23 12:01:17).

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) Yes Yes No Yes Y Yes Running, Valid, MiddleOnly 11.6 Mbit/s | 816.0 Kbit/s 11.6 Mbit/s | 192.0 Mbit/s OR 16.0 Mbit/s 96.7% | 98% 3.4d | 8d 1.7d | 4.9d 2.0d | 6.5d 96.7% | 98.0% 3.4d | 1.0d 2026-10-23 00:02:30 8 bit/s
dannenberg (DE) Yes Yes No Yes Y Yes Running, Valid, Fast, MiddleOnly 11.6 Mbit/s | 816.0 Kbit/s 11.6 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.7d | 8d 3.7d | 5.8d 2.0d | 6.6d 100.0% | 98.0% 3.7d | 1.0d 2026-10-23 00:02:30 2800 bit/s
dizum (NL) Yes Yes No Yes N Yes Running, Valid, Fast, MiddleOnly 11.6 Mbit/s | 816.0 Kbit/s 11.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.7d | 8d 3.7d | 7.7d 2.0d | 6.5d 100.0% | 98.0% 3.7d | 1.0d 2026-10-23 00:02:30 11.6 Kbit/s
faravahar (US) Yes Yes No Yes Y Yes Running, Valid, MiddleOnly, BadExit 11.6 Mbit/s | 816.0 Kbit/s 11.6 Mbit/s | 320.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.7d | 8d 3.7d | 8.0d 2.0d | 6.7d 100.0% | 98.0% 3.7d | 1.0d 2026-10-23 00:02:30 11.6 Kbit/s
gabelmoo (DE) Yes Yes No Yes Y Yes Running, Valid, MiddleOnly, BadExit 11.6 Mbit/s | 816.0 Kbit/s 11.6 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.7d | 8d 3.7d | 7.8d 2.0d | 6.5d 100.0% | 98.0% 3.7d | 1.0d 2026-10-23 00:02:30 8 bit/s
longclaw (US) Yes Yes No Yes Y Yes Running, Valid, Fast, MiddleOnly, BadExit 11.6 Mbit/s | 816.0 Kbit/s 11.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.7d | 8d 3.7d | 7.9d 2.0d | 6.4d 100.0% | 98.0% 3.7d | 1.0d 2026-10-23 00:02:30 11.6 Kbit/s
maatuska (SE) Yes Yes No Yes N Yes Running, Valid, Fast, MiddleOnly 11.6 Mbit/s | 816.0 Kbit/s 11.6 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.7d | 8d 3.7d | 7.7d 2.0d | 6.4d 100.0% | 98.0% 3.7d | 1.0d 2026-10-23 00:02:30 11.6 Kbit/s
moria1 (US) Yes Yes No Yes Y Yes Running, Valid, MiddleOnly, BadExit 11.6 Mbit/s | 8.4 Mbit/s 11.6 Mbit/s | 200.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.1d | 8d 3.7d | 10630.3d 2.0d | 6.2d 100.0% | 98.0% 3.1d | 9.7d 2026-10-23 00:02:30 2160 bit/s
tor26 (AT) Yes Yes No Yes Y Yes Running, Valid, Fast, MiddleOnly, BadExit 11.6 Mbit/s | 816.0 Kbit/s 11.6 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.7d | 8d 3.7d | 7.9d 2.0d | 6.7d 100.0% | 98.0% 3.7d | 1.0d 2026-10-23 00:02:30 3520 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.