View Relay "LouneaGigabitFiber"

Fingerprint: 9B54BBAA6711884F0EAC977F3EF58DE6FAF6F98F | Operator: pirkkarelays.dy.fi v2 (2 relays) ⚠ Misconfigured | Family: 2 relays | email:pirkkarelays[]proton.me... | AS39699 | Finland | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
6/7 BW Auths Measured 33 Mbit/s Median
Stability
Not Overloaded | UP 5d 3h 11m ago | UP 98% (1M)
Reachability
IPv4: 9/9 | v6: None configured(Directory Auths)
BW Weight
0.00% of Network | 77 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 E30CF7B3 (98.1%, need ≥98%) and just under the Guard bar at maatuska (97.7%, need ≥98%) and moria1 (97.6%, 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.
  • Guard: Time Known near threshold: Time Known is just above the Guard bar at E30CF7B3 (5.8 days, need ≥5 days 10 hours 41 minutes 56 seconds). This is weighted time, so the day count is shorter than calendar uptime, and it falls while the relay is unreachable. Stay reachable so it can move clear of the bar.
    Suggestion: Weighted time-known falls while the relay is unreachable and resets if the identity key changes. Authorities cap it at 8 days (AuthDirVoteGuardGuaranteeTimeKnown), about a few weeks of continuous uptime. Stay up with the same key.
  • Guard: bandwidth near threshold: Bandwidth counted for Guard is just above the Guard bar at longclaw (17.6 Mbit/s, need ≥16.8 Mbit/s). The bar is the lower of AuthDirGuardBWGuarantee and that authority's top 25%. A dip in the bandwidth it counts can drop the Guard flag.
    Suggestion: The bandwidth that counts is that authority's measurement when it has one, otherwise the relay-reported rate. Keep it above the lower of AuthDirGuardBWGuarantee (2 MB by default) and that authority's top 25%.

Addresses
OR Address
83.148.245.77:9001
Reachability (Directory Authorities)
IPv4
9/9
IPv6
None configured
Location
Country
Finland Finland
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS39699
AS Name
Lounea Palvelut Oy (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 2 operators)

Current Flags (7): Running, Valid, V2Dir, Fast, Stable, HSDir, Guard
Eligible Flags (7): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 8/9 | HSDir: 7/9 | Guard: 6/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) 17.6 Mbit/s – 64.0 Mbit/s (6 DA measured)
77.9 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 Below (2/9 DA) Median: 5.8d (1/9 DA above threshold)
Min/Max: 2.7d / 14304.6d (9/9 DA, Voting / Total Eligible)
≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12669.7d
Uptime Meets (9/9 DA) 5.1d (R) ≥5.0d - 5.1d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
17.6 Mbit/s – 64.0 Mbit/s (6 DA measured)
77.9 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 (8/9 DA) 5.1d (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
17.6 Mbit/s – 64.0 Mbit/s (6 DA measured)
77.9 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 (7/9 DA) Median: 98.9% (7/9 DA above threshold)
Min/Max: 97.6% / 99.3% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 14.6d (9/9 DA above threshold)
Min/Max: 5.8d / 15.8d (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) 17.6 Mbit/s – 64.0 Mbit/s (6 DA measured)
77.9 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 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-11-20 08:45:05).

Capacity (Relay Reported)
Observed Bandwidth
77.91 Mbit/s
Advertised Bandwidth
77.91 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
569 TB (5 years)
1mo: 25 TB | 6mo: 155 TB | 1y: 400 TB | 5y: 569 TB
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
33.6 Mbit/s (median of 6 measurements)
Measured Min / Max
17.6 Mbit/s / 64.0 Mbit/s
Deviation
46.4 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0023% of network (28th pctl) | Guard: 0.0054% (10th pctl) | Middle: 0.0013% (19th pctl) | Exit: N/A
History

Uptime Metrics
Current Status
UP 5d 3h 11m ago
Overall Uptime (1M/6M/1Y/5Y)
98.8%/99.6%/97.0%/97.5%
Flag Uptime (1M/6M/1Y/5Y)
84.8%/97.2%/89.0%/88.7%
Hibernating
No
Timestamps
First Seen
1y 5mo 1w ago (2025-06-15 12:00:00)
Last Seen
1h 45m 32s ago (2026-11-20 08:00:00)
Last Restarted
5d 3h 11m ago (2026-11-15 06:33:50)
Last Changed Address
2026-04-06 23:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-20 09:45 UTC. /details snapshot 2026-11-20 08:00:00 UTC (cached 37s ago). /bandwidth snapshot 2026-11-20 02:00:00 UTC (cached 6h 30m 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 (?)
pirkkarelays.dy.fi
Operator Validation
Unvalidated
This Relay
Unvalidated
Error: URI-RSA: HTTP error name resolution failed for pirkkarelays.dy.fi at URL: https://pirkkarelays.dy.fi/.well-known/tor-relay/rsa-fingerprint.txt; URI-RSA: HTTP error name resolution failed for www.pirkkarelays.dy.fi at URL: https://www.pirkkarelays.dy.fi/.well-known/tor-relay/rsa-fingerprint.txt
Contact
email:pirkkarelays[]proton.me url:pirkkarelays.dy.fi proof:uri-rsa pgp:391490D78B1775B117CFEA0BF0F3FEA2BD9FF0D2 uplinkbw:500 virtualization:baremetal offlinemasterkey:n sandbox:y os:debian/13 tls:openssl aesni:y autoupdate:y confmgmt:manual ciissversion:2 trafficacct:unmetered
Family Configuration
Family Support
MyFamily Only (2) — Legacy only. Consider migrating to Happy Families. | View Full Family (2)
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Members: 2
5626DD3A077F79B9946A00FA3486A451134D9E5E
9B54BBAA6711884F0EAC977F3EF58DE6FAF6F98F (this relay)
Alleged Members: 2
(they don't list you back)
7C8B90FA15947119DC9B813B67CB0E63B49D262D (not in the network)
A7DE930F359C754A79AC3A80147CBD34428BED43 (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
Not an exit relay — DNS health testing does not apply.
IPv4 Exit Policy Summary
reject: 
  1-65535
IPv6 Exit Policy Summary
None
Full Exit Policy
reject *:*

Last fetch was at Fri, 20 Nov 2026 09:45:32 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 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 No — Y Yes Running, Valid, V2Dir, Fast 46.4 Mbit/s (M) | 816.0 Kbit/s 46.4 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 98.1% | 98% 5.8d | 5d 2.7d | 3.9d 5.1d | 5.1d 2026-11-19 18:36:56 46.4 Mbit/s (M)
dannenberg (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 64.0 Mbit/s (M) | 816.0 Kbit/s 64.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 99.3% | 98% 15.1d | 8d 7.5d | 8.2d 5.1d | 5.1d 2026-11-19 18:36:56 64.0 Mbit/s (M)
dizum (NL) Yes Yes No — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 77.9 Mbit/s (R) | 816.0 Kbit/s 77.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 98.5% | 98% 14.6d | 8d 5.4d | 6.8d 5.1d | 5.1d 2026-11-19 18:36:56 77.9 Mbit/s (R)
faravahar (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 77.9 Mbit/s (R) | 816.0 Kbit/s 77.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.0% | 98% 13.7d | 8d 5.0d | 7.0d 5.1d | 5.1d 2026-11-19 18:36:56 77.9 Mbit/s (R)
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 33.6 Mbit/s (M) | 816.0 Kbit/s 33.6 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 98.9% | 98% 15.2d | 8d 5.8d | 8.3d 5.1d | 5.1d 2026-11-19 18:36:56 33.6 Mbit/s (M)
longclaw (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 17.6 Mbit/s (M) | 816.0 Kbit/s 17.6 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 99.1% | 98% 15.7d | 8d 6.1d | 9.1d 5.1d | 5.1d 2026-11-19 18:36:56 17.6 Mbit/s (M)
maatuska (SE) Yes Yes No — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir 77.9 Mbit/s (R) | 816.0 Kbit/s 77.9 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 97.7% | 98% 13.0d | 8d 3.2d | 2.3d 5.1d | 5.1d 2026-11-19 18:36:56 77.9 Mbit/s (R)
moria1 (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable 56.8 Mbit/s (M) | 8.4 Mbit/s 56.8 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 97.6% | 98% 10.0d | 8d 14304.6d | 12669.7d 5.1d | 5.0d 2026-11-19 18:36:56 56.8 Mbit/s (M)
tor26 (AT) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 20.0 Mbit/s (M) | 816.0 Kbit/s 20.0 Mbit/s (M) | 240.0 Mbit/s OR 16.8 Mbit/s 99.1% | 98% 15.8d | 8d 6.1d | 8.2d 5.1d | 5.1d 2026-11-19 18:36:56 20.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.