View Relay "flokinet2n4"

Fingerprint: 2CBD595E8F51D3814130241B8105FEE9E303719E | Family: 24 relays | FlokiNET <noc@flokinet.is> | AS200651 | Netherlands | Linux

Consensus
In Consensus (9/9 Directory Auths)
DNS Health
Healthy (15.3s, 48th percentile) (via exitdnshealth.1aeo.com)
BW Verified
6/7 BW Auths Measured 160 Mbit/s Median
Stability
Not Overloaded | UP 2d 16h 24m ago | UP 99% (1M)
Reachability
IPv4: 9/9 | v6: 8/8(Directory Auths)
BW Weight
0.01% of Network | 226 Mbit/s Observed By Relay
Version
0.4.9.17 Recommended
Issues Detected:
  • 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.
Notes:
  • Guard: WFU near threshold: Weighted Fractional Uptime is just above the Guard bar at maatuska (98.48%, need ≥98%). Recent downtime weighs more than older downtime. Avoid restarts while it is this close; a short outage can drop the Guard flag.
    Suggestion: Recent downtime weighs more than older downtime. Minimize restarts, use systemd Restart=always, and watch for OOM kills until each authority has more room above its own guard-wfu.

Addresses
OR Address
185.246.188.74:447
[2a06:1700:3:19::1]:447
Exit Address
185.246.188.74
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Netherlands Netherlands
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS200651
AS Name
FlokiNET ehf (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.69% consensus weight, 25 operators)

Current Flags (8): Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit
Eligible Flags (8): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 8/9 | HSDir: 7/9 | Guard: 7/9 | Exit: 9/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
IPv6 Reachability Meets (8/8 DA) 8/8 tested authorities reached relay ≥5/8 tested (majority) (≥5/8 DA)
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) 88.0 Mbit/s – 384.0 Mbit/s (6 DA measured)
80.0 Mbit/s (3 DA relay-reported)
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Partial (8/9 DA) Median: 10.4d (7/9 DA above threshold)
Min/Max: 1.5d / 20770.2d (9/9 DA, Voting / Total Eligible)
≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
Uptime Below (0/9 DA) 2.7d (R) ≥5.0d - 5.1d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
88.0 Mbit/s – 384.0 Mbit/s (6 DA measured)
80.0 Mbit/s (3 DA relay-reported)
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (8/9 DA) 8/9 DA assigned Stable ≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Partial (7/9 DA) 2.7d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.7d Time Known
Guard Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
88.0 Mbit/s – 384.0 Mbit/s (6 DA measured)
80.0 Mbit/s (3 DA relay-reported)
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (8/9 DA) 8/9 DA assigned Stable ≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Partial (8/9 DA) Median: 99.5% (8/9 DA above threshold)
Min/Max: 86.8% / 100.0% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 16.4d (9/9 DA above threshold)
Min/Max: 6.8d / 18.4d (9/9 DA, Voting / Total Eligible)
≥8 days; E30CF7B3: ≥5 days 10 hours 41 minutes 56 seconds (≥5/9 DA)
Bandwidth Meets (9/9 DA) 88.0 Mbit/s – 384.0 Mbit/s (6 DA measured)
80.0 Mbit/s (3 DA relay-reported)
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-248.0 Mbit/s) (≥5/9 DA)
Exit Exit Policy Meets (9/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-11-20 08:45:05).

Capacity (Relay Reported)
Observed Bandwidth
226.18 Mbit/s
Advertised Bandwidth
226.18 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
1.2 PB (5 years)
1mo: 79 TB | 6mo: 369 TB | 1y: 687 TB | 5y: 1.2 PB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-20 08:45:05

Measured By
6/7 Bandwidth Authorities
Not measured by: faravahar
Consensus Weight
160.0 Mbit/s (median of 6 measurements)
Measured Min / Max
88.0 Mbit/s / 384.0 Mbit/s
Deviation
296.0 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0108% of network (67th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0337% (59th pctl)
History

Uptime Metrics
Current Status
UP 2d 16h 24m ago
Overall Uptime (1M/6M/1Y/5Y)
99.2%/99.4%/99.7%/99.8%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (99.2%/99.4%/99.7%/99.8%)
Hibernating
No
Timestamps
First Seen
1y 10mo 2w ago (2025-01-09 00:00:00)
Last Seen
1h 15m 37s ago (2026-11-20 08:00:00)
Last Restarted
2d 16h 24m ago (2026-11-17 16:51:30)
Last Changed Address
2026-04-06 23:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-20 09:15 UTC. /details snapshot 2026-11-20 08:00:00 UTC (cached 33s ago). /bandwidth snapshot 2026-11-20 02:00:00 UTC (cached 6h ago).

General Overload (from /details)
Status
No general overload report in available data
File Descriptor Exhaustion (from /bandwidth)
Status
No file-descriptor exhaustion report in available data
Rate Limits (from /bandwidth)
Status
No rate-limit report in available data
Rate Limit
—
Burst Limit
—
Write counter
—
Read counter
—
About these reports and MetricsPort

Allium’s eligibility windows are applied to the reported timestamps: 72 hours for general overload and file-descriptor exhaustion, 24 hours for a rate-limit hit. A report at the cutoff is historical. An older report can remain visible after Onionoo or Allium’s cache still has it. The cutoff does not prove the relay recovered at that moment. Allium caches the bandwidth document for 12 hours by default. The snapshot time is when Onionoo published that document. It is not the relay’s event time, and it is not necessarily the extra-info publication time. Cache age is how old Allium’s copy is.

MetricsPort counters are cumulative. Compare samples, and account for process restarts. A nonzero total alone does not show ongoing activity. Gauges describe current values. An unavailable metric is unknown, not zero. Allium does not have this relay’s MetricsPort readings and does not invent them.

The port below is an example for an endpoint you have already configured. MetricsPort must be enabled with restricted access and must not be exposed publicly. Setup stays in the Tor overload troubleshooting guide.

curl http://127.0.0.1:9035/metrics
History

Operator Identity

Source: AROI Validation API — 2026-11-19 23:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
FlokiNET <noc@flokinet.is>
Family Configuration
Family Support
MyFamily Only (24) — Legacy only. Consider migrating to Happy Families. | View Full Family (24)
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Members: 24
04E666AF3A39A54BE9138BEE97AE2DB21EA9D4E6
25F9E478895618682AB5A866456150687E2119ED
2CBD595E8F51D3814130241B8105FEE9E303719E (this relay)
31DC5DB002D7DBF051EC6C0704FBC5F7D0B93A2D
422AB737CEBF3A4659C2B435DD44A77D2531BD77
4FE038C29B3BC642DAB041F7F349F08D45624F2C
5A3F1940AA47854BA6F315641FB473AB32F7CCF5
5DB17AFAE8684C7425F4464BA9E681394BBEA20A
605DF0AAC4B68BD945639CF5F88BFA0400DD883D
67DE7272159CFE628CDF17D2A719A6E395BAA4C8
72DC38F052B1F4FB453B7DD787631CCAAD4234BC
7CA64075C4B9AC6BBF786DAF09B15969D8993D47
80DB0EC4F65BC7254D729933D3887EA26A24CA0F
9665C3CF3A4A65EBDCE3566F367CA393BF5CD4E5
99127348D47CBD2496434A0B5A5FEB976124CA75
AC2F431A218553FA26AE642ED64ABB9AFB9792C1
B7E83B20112556F6CB8BD48A311E41E55AA9D37F
C3A7530B541FCAE49095E7E70958C99840F830C2
CF61477466FCEAAF0FFC405CE028B98DBF6ABB2B
CFFDC35415115BB18EDB7226BB83B02786F0C082
D82D18E8359EDFAD0B374887002ABDF1F29EA430
E47DBDAE90DC47AEBD488E17DE90343E21DAF912
F524BE1EEE48640594585B44427F3D8DD35DEBCA
F5D0054146D1E4AD67EE71590D59691721432EF4
Alleged Members: 8
(they don't list you back)
103C5566735DA429718037311AB9D7EADA03F727 (not in the network)
1786082A96D6E54170269A35BE202589E95B33F7 (not in the network)
45D37193BDADCB6E8AD392C81B022BBB127D5451 (not in the network)
8ABE418A1404814E10BB5732D72EB6454CFD2224 (not in the network)
96D59D2FA3224F04F11AD601B31A2869C85B9E9C (not in the network)
AD1EE5A54C9087601E14D430CFBC3B75C079DFDC (not in the network)
F16BA552F0B522F094114591ECC65293A1FA9E94 (not in the network)
FC62DC4DF198F8E952A46857CF570393E260D014 (not in the network)
Indirect Members: 0
none

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

DNS Health
Status
Healthy (avg. 15.3s, 48th percentile)
Query Domain
232eab9c84fb4f579730a7eeaf77baa8.2cbd595e.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Upstream Resolver
Local /24 (exit's own network)
Local /24 42%, Cloudflare 38%, Local /22 17%, Local AS 2% (~130 estimated queries)
Cross-Validation
4/4 instances succeeded
First Hop
outerhaven (NL) CBD05C5E1EC91AD648B2BE16EC909024F2F096B0
Exit Address Used
185.246.188.74
Per-Instance Results
Cross Validation Attempt 1: Success, 19.5s (cv1_w1)
Cross Validation Attempt 2: Success, 12.9s (cv2_w1)
Cross Validation Attempt 3: Success, 15.6s (cv3_w1)
Cross Validation Attempt 4: Success, 13.3s (cv4_w1)
Tested: 2026-11-19 20:05:35 UTC
IPv4 Exit Policy Summary
reject: 
  25
  465
  587
  2525
IPv6 Exit Policy Summary
reject: 
  25
  465
  587
  2525
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.246.188.74:*
reject *:25
reject *:587
reject *:465
reject *:2525
accept *:*

Last fetch was at Fri, 20 Nov 2026 09:15:37 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-11-20 08:45:05).

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 (BW|T) Guard BW (BW|Threshold) Guard WFU (M|T) Guard TK (M|T) Stable MTBF (M|T) Stable Uptime (Relay|T) Desc Published Cons Wt (Authority)
E30CF7B3 Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 136.0 Mbit/s (M) | 816.0 Kbit/s 136.0 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 6.8d | 5d 6.8d | 3.9d 2.7d | 5.1d 2026-11-19 22:51:37 136.0 Mbit/s (M)
dannenberg (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 192.0 Mbit/s (M) | 816.0 Kbit/s 192.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 99.6% | 98% 18.3d | 8d 10.5d | 8.2d 2.7d | 5.1d 2026-11-19 22:51:37 192.0 Mbit/s (M)
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.2% | 98% 16.4d | 8d 8.8d | 6.8d 2.7d | 5.1d 2026-11-19 22:51:37 80.0 Mbit/s (R)
faravahar (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.5% | 98% 16.2d | 8d 8.7d | 7.0d 2.7d | 5.1d 2026-11-19 22:51:37 80.0 Mbit/s (R)
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 384.0 Mbit/s (M) | 816.0 Kbit/s 384.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 99.6% | 98% 18.4d | 8d 10.4d | 8.3d 2.7d | 5.1d 2026-11-19 22:51:37 384.0 Mbit/s (M)
longclaw (US) Yes Yes Yes — Y Yes N/T Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 232.0 Mbit/s (M) | 816.0 Kbit/s 232.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 99.6% | 98% 18.3d | 8d 10.5d | 9.1d 2.7d | 5.1d 2026-11-19 22:51:37 232.0 Mbit/s (M)
maatuska (SE) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Fast, Exit 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 98.5% | 98% 14.8d | 8d 1.5d | 2.3d 2.7d | 5.1d 2026-11-19 22:51:37 80.0 Mbit/s (R)
moria1 (US) Yes Yes Yes — Y Yes Yes Valid, V2Dir, Fast, Stable, Exit 88.0 Mbit/s (M) | 8.4 Mbit/s 88.0 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 86.8% | 98% 9.8d | 8d 20770.2d | 12669.7d 2.7d | 5.0d 2026-11-19 22:51:37 88.0 Mbit/s (M)
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard, Exit 160.0 Mbit/s (M) | 816.0 Kbit/s 160.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 99.5% | 98% 18.3d | 8d 10.5d | 8.2d 2.7d | 5.1d 2026-11-19 22:51:37 160.0 Mbit/s (M)

N/T = this authority does not test IPv6 • — = not in this vote • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known • Bandwidth source: (M) bandwidth-scanner measurement, (R) relay-reported, (U) unmeasured, counted as 0

Bandwidth Values Explained:
Measured (M) = An authority's bandwidth-scanner measurement of your relay (Measured= in its vote). An authority that has one uses it for the Fast and Guard flags, and the consensus weight is the median of these measurements when 3 or more authorities have one.
Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (Bandwidth= in every vote). An authority without a measurement uses it for flags, unless it has measurements for enough other relays (ignoring-advertised-bws=1); then your relay counts as 0 (U). It sets the consensus weight only when fewer than 3 authorities measured the relay, capped at 20 KB/s (maxunmeasuredbw) while 3 or more authorities publish measurements.
Not published = The authority has no measurement of your relay in its vote and ignores relay-reported bandwidth, yet it voted Fast or its vote has no measurements at all: it judges your relay by a measurement kept from an earlier bandwidth file (0 if none), which its vote doesn't show.
Why different? A low measurement means the bandwidth scanners see your relay underperforming compared with other relays that report a similar speed. Votes list both values in kilobytes per second. Rules: Assigning flags in a vote, Computing a consensus.
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.