View Relay "PremiumTorExit"

Fingerprint: 9366185B4ECB1CC3634F475D20FDDFE7A302BAF2 | Family: 1 relay | AS200651 | Romania | Linux

Consensus
Not In Consensus (1/9 Directory Auths, need 5)
BW Verified
1/7 BW Auths Measured 32 bit/s Median
Stability
Not Overloaded | DOWN 1d 5h 45m ago | UP 99% (1M)
Reachability
IPv4: 1/9 | v6: 0/8 (Directory Auths)
BW Weight
0.00% of Network | 1 Mbit/s Observed By Relay
Version
0.4.9.11 Recommended
Issues Detected:
  • Not in consensus : Only 1/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 1/9 authorities can reach this relay
    Suggestion: Authorities that cannot reach you: bastet, dannenberg, dizum, 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.
  • IPv6 not reachable : 0/8 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/
  • 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: bandwidth below threshold : Observed bandwidth 1 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.
  • 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 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
  • Low bandwidth authority measurements : Only 1/7 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
185.100.87.136:9001
Reachability (Directory Authorities)
IPv4
1/9
IPv6
0/8 (1 don't test)
Location
Country
Romania Romania
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS200651
AS Name
FlokiNET ehf (BGP.tools)
AS Rarity
Emerging (score: 1/5, 0.68% consensus weight, 21 operators)

Current Flags (4): Running, Valid, Stable, Exit
Eligible Flags (0): Running: 1/9 | Valid: 1/9 | V2Dir: 1/9 | Fast: 0/9 | Stable: 1/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 1/9
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Running IPv4 Reachability Below (1/9 DA) 1/9 authorities reached relay ≥5/9 DA ORPort reachable
IPv6 Reachability Below (0/8 DA) 0/8 tested authorities reached relay ≥5/8 tested (majority) (≥5/8 DA)
Valid Descriptor Partial (1/9 DA) 1/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) 1.0 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 (1/9 DA) Median: 23.2d (1/9 DA above threshold) ≥9.9d - 12.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8501.8d
Uptime Below (0/9 DA) 0.5d (R) ≥5.3d - 5.5d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (0/9 DA) 0/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 (1/9 DA) 1/9 DA assigned Stable ≥9.9d - 12.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8501.8d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (1/9 DA) Median: 98.0% (1/9 DA above threshold) ≥98.0% (≥5/9 DA)
Time Known Below (1/9 DA) Median: 55.0d (1/9 DA above threshold) ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Below (0/9 DA) 0/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 (1/9 DA) 1/9 DA assigned Stable ≥9.9d - 12.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥8501.8d
Prereq: V2Dir Below (0/9 DA) 0/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (1/9 DA) Median: 98.0% (1/9 DA above threshold) ≥98% (≥5/9 DA)
Time Known Meets (1/9 DA) Median: 55.0d (1/9 DA above threshold) ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 1.0 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.0 Mbit/s (≥5/9 DA)
Exit Exit Policy Partial (1/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-08-06 05:15:06).

Capacity (Relay Reported)
Observed Bandwidth
1.01 Mbit/s
Advertised Bandwidth
737.28 Kbit/s
Rate Limit
737.28 Kbit/s
Burst Limit
983.04 Kbit/s
Total Data
2.8 TB (5 years)
1mo: 13 GB | 6mo: 138 GB | 1y: 409 GB | 5y: 2.8 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-08-06 05:15:06

Measured By
1/7 Bandwidth Authorities
Not measured by: dannenberg, faravahar, gabelmoo, longclaw, maatuska, moria1
Median Measurement
32 bit/s
Min / Max
32 bit/s / 32 bit/s
Network Participation: Consensus Weight: 0.0000% of network (2th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime Metrics
Current Status
DOWN 1d 5h 45m ago
Overall Uptime (1M/6M/1Y/5Y)
99.9%/99.7%/99.8%/95.1%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (99.9%/99.7%/99.8%/95.1%)
Hibernating
No
Timestamps
First Seen
5y 2w 1d ago (2021-07-22 18:00:00)
Last Seen
1d 5h 45m ago (2026-08-05 00:00:00)
Last Restarted
12h 25m 9s ago (2026-08-05 17:20:49)
Last Changed Address
2026-04-06 23:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator Identity

Source: AROI Validation API — 2026-08-05 22: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
9366185B4ECB1CC3634F475D20FDDFE7A302BAF2 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

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

DNS Health
Status
Not Tested
IPv4 Exit Policy Summary
accept: 
  20-21
  43
  53
  80
  443
  989-990
  1194
  4321
  5222-5223
  11371
  64738
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 185.100.87.136:*
accept *:20-21
accept *:43
accept *:53
accept *:80
accept *:443
accept *:989-990
accept *:1194
accept *:4321
accept *:5222-5223
accept *:11371
accept *:64738
reject *:*

Last fetch was at Thu, 06 Aug 2026 05:45:54 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-08-06 05:15:06).

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) No Y No
dizum (NL) No N No
faravahar (US) No Y 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 Yes Y Yes Valid, Stable, Exit 1.0 Mbit/s | 816.0 Kbit/s 1.0 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 98.0% | 98% 55.0d | 8d 23.2d | 12.6d 0.5d | 5.4d 98.0% | 98.0% 55.0d | 1.0d 2026-08-06 03:05:08 32 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.