View Relay "InVinoVeritas4"

Fingerprint: 4CAB6B3AB1121A50CCD057246627F273F3F640B7 | Family: 2 relays | kopfschusskorl@gmail.com | AS202053 | Norway | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast (4)
BW Verified
6/6 BW Auths Measured 63 Kbit/s Median
Stability
Not Overloaded | UP 3d 1h 42m ago | UP 100% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
5d 19h 46m ago
BW Weight
0.00% of Network | 57 Mbit/s Observed By Relay
Version
0.4.9.6 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: WFU below threshold : Weighted Fractional Uptime 97.6% 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 2.6 days is below 8 days requirement (5.4 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: WFU below threshold : WFU 97.6% 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.

Connectivity and Location

Addresses
OR Address
invinoveritas.fegefeuer.site
212.147.235.242:443
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Norway Norway
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS202053
AS Name
UpCloud Ltd (BGP.tools)
AS Rarity
Epic (score: 3/5, 0.08% consensus weight, 6 operators)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 1/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) 57.3 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: 3.6d (1/9 DA above threshold)
Min/Max: 1.5d / 7215.3d (9/9 DA, Voting / Total Eligible)		 ≥38.3d - 62.2d (varies) (≥5/9 DA)
Uptime Below (0/9 DA) 3.1d (R) ≥8.3d - 11.3d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/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 ≥38.3d - 62.2d (varies) (≥5/9 DA)
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Median: 99.2% (8/9 DA above threshold)
Min/Max: 97.6% / 99.2% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 5.7d (0/9 DA above threshold)
Min/Max: 2.6d / 5.8d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Meets (9/9 DA) 9/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 ≥38.3d - 62.2d (varies) (≥5/9 DA)
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Median: 99.2% (8/9 DA above threshold)
Min/Max: 97.6% / 99.2% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 2.3 more days) Median: 5.7d (0/9 DA above threshold)
Min/Max: 2.6d / 5.8d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 57.3 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.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-04-20 14:45:08).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
57.31 Mbit/s
Advertised Bandwidth
57.31 Mbit/s
Rate Limit
419.43 Mbit/s
Burst Limit
838.86 Mbit/s
Total Data
178 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-04-20 14:45:08

Measured By
6/6 Bandwidth Authorities
Median Measurement
63.3 Kbit/s
Min / Max
29.6 Kbit/s / 96.0 Kbit/s
Deviation
66.4 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0043% of network (41th pctl) | Guard: N/A | Middle: 0.0129% (74th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 3d 1h 42m ago
Overall Uptime (1M/6M/1Y/5Y)
100.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (100.0%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
5d 19h 46m ago (2026-04-14 19:00:00)
Last Seen
2h 46m 44s ago (2026-04-20 12:00:00)
Last Restarted
3d 1h 42m ago (2026-04-17 13:04:20)
Last Changed Address
2026-04-14 22:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-04-20 07:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
kopfschusskorl@gmail.com
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

Software and Version

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

Exit Health & Policy

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 Mon, 20 Apr 2026 14:46:43 GMT.

Consensus Evaluation

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

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 — Y Yes Running, Valid, V2Dir, Fast 57.3 Mbit/s | 816.0 Kbit/s 57.3 Mbit/s | 200.0 Mbit/s OR 16.0 Mbit/s 97.6% | 98% 2.6d | 8d 1.5d | 62.2d 3.1d | 8.3d 97.6% | 98.0% 2.6d | 1.0d 2026-04-17 08:53:21 29.6 Kbit/s
dannenberg (DE) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 57.3 Mbit/s | 816.0 Kbit/s 57.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.2% | 98% 5.7d | 8d 3.7d | 38.3d 3.1d | 11.3d 99.2% | 98.0% 5.7d | 1.0d 2026-04-20 13:27:22 63.3 Kbit/s
dizum (NL) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 57.3 Mbit/s | 816.0 Kbit/s 57.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.2% | 98% 5.7d | 8d 3.7d | 40.2d 3.1d | 11.3d 99.2% | 98.0% 5.7d | 1.0d 2026-04-20 13:27:22 63.3 Kbit/s
faravahar (US) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 57.3 Mbit/s | 816.0 Kbit/s 57.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.2% | 98% 5.8d | 8d 3.6d | 61.3d 3.1d | 11.3d 99.2% | 98.0% 5.8d | 1.0d 2026-04-20 13:27:22 63.3 Kbit/s
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 57.3 Mbit/s | 816.0 Kbit/s 57.3 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 99.2% | 98% 5.7d | 8d 3.7d | 62.9d 3.1d | 11.3d 99.2% | 98.0% 5.7d | 1.0d 2026-04-20 13:27:22 52.8 Kbit/s
longclaw (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 57.3 Mbit/s | 816.0 Kbit/s 57.3 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 99.2% | 98% 5.8d | 8d 3.6d | 62.4d 3.1d | 11.3d 99.2% | 98.0% 5.8d | 1.0d 2026-04-20 13:27:22 73.6 Kbit/s
maatuska (SE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 57.3 Mbit/s | 816.0 Kbit/s 57.3 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 98.9% | 98% 4.6d | 8d 2.8d | 61.4d 3.1d | 10.2d 98.9% | 98.0% 4.6d | 1.0d 2026-04-19 01:25:22 96.0 Kbit/s
moria1 (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable 57.3 Mbit/s | 8.4 Mbit/s 57.3 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 98.9% | 98% 4.3d | 8d 7215.3d | 303.9d 3.1d | 11.2d 98.9% | 98.0% 4.3d | 9.8d 2026-04-19 19:26:22 80.0 Kbit/s
tor26 (AT) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 57.3 Mbit/s | 816.0 Kbit/s 57.3 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 99.2% | 98% 5.8d | 8d 3.6d | 63.3d 3.1d | 11.3d 99.2% | 98.0% 5.8d | 1.0d 2026-04-20 13:27:22 69.6 Kbit/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.