View Relay "torfan"

Fingerprint: EDC3C33AF59C2C4999D88CD884BC523D63DFB80B | Family: 1 relay | TorFan <torfan AT mailinator dot com> | AS16019 | Czechia | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
5/6 BW Auths Measured 24 Kbit/s Median
Stability
Overloaded | UP 2d 13h 58m ago
Reachability
IPv4: 9/9 (Directory Auths)
BW Weight
0.00% of Network | 28 Mbit/s Observed By Relay
Version
0.4.8.21 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: Time Known below threshold : Time Known 1.9 days is below 8 days requirement (6.1 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.
  • Write Bandwidth Limit Hit : Write rate limit (25 Mbit/s) was hit 9 times. Relay is throttling outbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more upload capacity.
  • Read Bandwidth Limit Hit : Read rate limit (25 Mbit/s) was hit 24 times. Relay is throttling inbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more download capacity.
Notes:
  • Rate Limit Configuration: Configured limits: Rate=25 Mbit/s, Burst=74 Mbit/s. Limits hit: Write=9, Read=24.

Addresses
OR Address
ip-94-112-34-205.bb.vodafone.cz
94.112.34.205:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Czechia Czechia
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS16019
AS Name
Vodafone Czech Republic a.s. (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.07% consensus weight, 11 operators)

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 7/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 Meets (9/9 DA) Tunnelled: Yes (no DirPort) (R) Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast Speed Meets (9/9 DA) 28.5 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: 1.9d (0/9 DA above threshold)
Min/Max: 1.9d / 1.9d (9/9 DA, Voting / Total Eligible)
≥11.8d - 52.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥430.3d
Uptime Below (0/9 DA) 2.6d (R) ≥8.0d - 10.0d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (7/9 DA) 7/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 ≥11.8d - 52.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥430.3d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Majority: 100.0% (9/9 DA) ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 1.9d (0/9 DA above threshold)
Min/Max: 1.8d / 1.9d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Meets (7/9 DA) 7/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 ≥11.8d - 52.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥430.3d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (9/9 DA) Majority: 100.0% (9/9 DA) ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 6.1 more days) Median: 1.9d (0/9 DA above threshold)
Min/Max: 1.8d / 1.9d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 28.5 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-304.0 Mbit/s (≥5/9 DA)
Exit Exit Policy Below (0/9 DA) Port 80: No | Port 443: No (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-03-04 22:15:08).

Capacity (Relay Reported)
Observed Bandwidth
28.52 Mbit/s
Advertised Bandwidth
24.58 Mbit/s
Rate Limit
24.58 Mbit/s
Burst Limit
73.73 Mbit/s
Total Data
6.3 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-04 22:15:08

Measured By
5/6 Bandwidth Authorities
Not measured by: longclaw
Median Measurement
24.6 Kbit/s
Min / Max
8 bit/s / 40.0 Kbit/s
Deviation
40.0 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0019% of network (30th pctl) | Guard: N/A | Middle: 0.0057% (61th pctl) | Exit: N/A

Uptime Metrics
Current Status
UP 2d 13h 58m 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
2d 13h 15m ago (2026-03-02 10:00:00)
Last Seen
1h 15m 41s ago (2026-03-04 22:00:00)
Last Restarted
2d 13h 58m ago (2026-03-02 09:17:34)
Last Changed Address
2026-03-02 10:00:00
[Warning] OVERLOADED — Rate limits hit W:9 R:24 (limit: 25 Mbit/s)
General Overload (from /details)
Status
Not Reported

OOM killer, onionskin queue saturation, or TCP port exhaustion. Flag remains 72h after last event (Tor spec 328).

File Descriptor Exhaustion (from /bandwidth)
Status
Not Reported
Rate Limits (from /bandwidth)
Rate Limit
24.58 Mbit/s
Burst Limit
73.73 Mbit/s
Write Limit Hit
9 times
Read Limit Hit
24 times
Last Reported
8 hours ago
Recommendations
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic

Operator Identity

Source: AROI Validation API — 2026-03-04 14:00 UTC

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

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

Full Exit Policy
reject *:*

Last fetch was at Wed, 04 Mar 2026 23:15:39 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-03-04 22:15:08).

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 Y Yes Running, Valid, V2Dir, Fast 28.5 Mbit/s | 816.0 Kbit/s 28.5 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.9d | 8d 1.9d | 56.3d 2.6d | 9.6d 100.0% | 98.0% 1.9d | 1.0d 2026-03-03 22:30:47 39.2 Kbit/s
dannenberg (DE) Yes Yes No N Yes Running, Valid, V2Dir, Fast 28.5 Mbit/s | 816.0 Kbit/s 28.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.9d | 8d 1.9d | 11.8d 2.6d | 8.2d 100.0% | 98.0% 1.9d | 1.0d 2026-03-03 22:30:47 24.6 Kbit/s
dizum (NL) Yes Yes No N Yes Running, Valid, V2Dir, Fast 28.5 Mbit/s | 816.0 Kbit/s 28.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.9d | 8d 1.9d | 42.7d 2.6d | 8.0d 100.0% | 98.0% 1.9d | 1.0d 2026-03-03 22:30:47 24.6 Kbit/s
faravahar (US) Yes Yes No N Yes Running, Valid, V2Dir, Fast 28.5 Mbit/s | 816.0 Kbit/s 28.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.9d | 8d 1.9d | 48.6d 2.6d | 10.0d 100.0% | 98.0% 1.9d | 1.0d 2026-03-03 22:30:47 24.6 Kbit/s
gabelmoo (DE) Yes Yes No Y Yes Running, Valid, V2Dir 28.5 Mbit/s | 816.0 Kbit/s 28.5 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.9d | 8d 1.9d | 58.8d 2.6d | 10.1d 100.0% | 98.0% 1.9d | 1.0d 2026-03-03 22:30:47 8 bit/s
longclaw (US) Yes Yes No Y Yes Running, Valid, V2Dir, Fast 28.5 Mbit/s | 816.0 Kbit/s 28.5 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.9d | 8d 1.9d | 59.0d 2.6d | 9.6d 100.0% | 98.0% 1.9d | 1.0d 2026-03-03 22:30:47 24.6 Kbit/s
maatuska (SE) Yes Yes No Y Yes Running, Valid, V2Dir, Fast 28.5 Mbit/s | 816.0 Kbit/s 28.5 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.9d | 8d 1.9d | 39.2d 2.6d | 10.1d 100.0% | 98.0% 1.9d | 1.0d 2026-03-03 22:30:47 34.4 Kbit/s
moria1 (US) Yes Yes No Y Yes Running, Valid, V2Dir, Fast 28.5 Mbit/s | 8.4 Mbit/s 28.5 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.8d | 8d 1.9d | 430.3d 2.6d | 10.8d 100.0% | 98.0% 1.8d | 9.9d 2026-03-03 22:30:47 40.0 Kbit/s
tor26 (AT) Yes Yes No Y Yes Running, Valid, V2Dir 28.5 Mbit/s | 816.0 Kbit/s 28.5 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.9d | 8d 1.9d | 52.7d 2.6d | 10.1d 100.0% | 98.0% 1.9d | 1.0d 2026-03-03 22:30:47 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.