View Relay "INSRelay28at8443"

Fingerprint: 592AB80372DB0365F9A2357702AC97C06E5F835C | Operator: digidow.eu v2 (10 relays) ✓ Validated | Family: 10 relays | This Relay is operated as part of a... | AS1205 | Austria | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast (4)
BW Verified
5/7 BW Auths Measured 1 Mbit/s Median
Stability
Not Overloaded | UP 6mo 4d 16h ago | UP 100% (1M)
Reachability
IPv4: 9/9 | v6: None configured(Directory Auths)
First Seen
5y 8mo 1w ago
BW Weight
0.00% of Network | 42 Mbit/s Observed By Relay
Version
0.5.0.0-alpha-dev Not 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: bandwidth below threshold : 0/9 authorities credit this relay with enough bandwidth for Guard (5 needed): at least 16.8 Mbit/s (AuthDirGuardBWGuarantee) or a place in their top 25% (80.0 Mbit/s – 272.0 Mbit/s). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 880.0 Kbit/s – 2.2 Mbit/s. dizum, faravahar, longclaw and maatuska used the relay-reported 856.0 Kbit/s.
    Suggestion: Guard requires a bandwidth of at least AuthDirGuardBWGuarantee (16.8 Mbit/s by default) or one in the top 25% of relays, judged by each authority the same way as for Fast. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx.
  • Guard: WFU below threshold : 0/9 authorities meet guard-wfu (≥98%; dizum: ≥97.774%; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 measured 92.4%–96.4%.
    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.
  • Not eligible for Stable flag : 1/9 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska and tor26 do not.
    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.
  • Tor version not recommended : Running Tor version 0.5.0.0-alpha-dev which is not on the recommended list.
    Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases.

Connectivity and Location

Addresses
OR Address
140.78.100.28:8443
Reachability (Directory Authorities)
IPv4
9/9
IPv6
None configured
Location
Country
Austria Austria
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS1205
AS Name
University Linz (BGP.tools)
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Fast
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 8/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 Partial (8/9 DA) 880.0 Kbit/s – 2.2 Mbit/s (5 DA measured)
856.0 Kbit/s (4 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 (1/9 DA) Median: 0.8d (1/9 DA above threshold)
Min/Max: 0.5d / 19594.1d (9/9 DA, Voting / Total Eligible)		 ≥2.3d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.9d
Uptime Meets (9/9 DA) 184.7d (R) ≥5.2d - 5.3d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (8/9 DA) 8/9 DA assigned Fast
880.0 Kbit/s – 2.2 Mbit/s (5 DA measured)
856.0 Kbit/s (4 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 Below (1/9 DA) 1/9 DA assigned Stable ≥2.3d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.9d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Meets (9/9 DA) 184.7d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.8d Time Known
Guard Prereq: Fast Meets (8/9 DA) 8/9 DA assigned Fast
880.0 Kbit/s – 2.2 Mbit/s (5 DA measured)
856.0 Kbit/s (4 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 Below (1/9 DA) 1/9 DA assigned Stable ≥2.3d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.9d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (0/9 DA) Median: 94.7% (0/9 DA above threshold)
Min/Max: 92.4% / 96.4% (9/9 DA, Voting / Total Eligible)		 ≥98%; dizum: ≥97.774% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 10.5d (9/9 DA above threshold)
Min/Max: 9.7d / 12.4d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 880.0 Kbit/s – 2.2 Mbit/s (5 DA measured)
856.0 Kbit/s (4 DA relay-reported)		 ≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-272.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-04 11:15:19).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
42.16 Mbit/s
Advertised Bandwidth
860.16 Kbit/s
Rate Limit
860.16 Kbit/s
Burst Limit
8.59 Gbit/s
Total Data
21 TB (5 years)
1mo: 441 GB | 6mo: 2.4 TB | 1y: 4.5 TB | 5y: 21 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-04 11:15:19

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight
1.1 Mbit/s (median of 5 measurements)
Measured Min / Max
880.0 Kbit/s / 2.2 Mbit/s
Deviation
1.3 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0001% of network (6th pctl) | Guard: N/A | Middle: 0.0002% (6th pctl) | Exit: N/A
History
Throughput and write/read, last 6 months Throughput and write/read, last year Throughput and write/read, last 5 years Throughput and write/read, last 30 days
1M 6M 1Y 5Y

Uptime and Stability

Uptime Metrics
Current Status
UP 6mo 4d 16h ago
Overall Uptime (1M/6M/1Y/5Y)
100.0%/99.7%/94.0%/94.9%
Flag Uptime (1M/6M/1Y/5Y)
86.3%/92.5%/89.6%/93.0%
Hibernating
No
Timestamps
First Seen
5y 8mo 1w ago (2021-02-26 18:00:00)
Last Seen
1h 15m 40s ago (2026-11-04 11:00:00)
Last Restarted
6mo 4d 16h ago (2026-05-03 20:10:46)
Last Changed Address
2026-04-06 23:00:00
Overload Status: Not Overloaded. Historical rate-limit report outside the 24-hour window

Evaluated 2026-11-04 12:15 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 25s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 4h 30m ago).

Reported timestamps use hour precision, so the displayed minute is not an exact incident time.

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
Historical report — outside the 24-hour window
Rate Limit
860.16 Kbit/s
Burst Limit
1.1 GB
Write counter
36,386
Read counter
104,676
Reported
2026-11-02 20:00 UTC (1 day ago)

Read and write counters increment at most once per minute per direction. They are not a count of blocked connections, the duration of throttling, or necessarily the number of events in the last 24 hours. Rate is BandwidthRate and follows this site’s bits/bytes setting. Burst is BandwidthBurst, already a byte quantity. RelayBandwidthRate and RelayBandwidthBurst are extra torrc caps, not the names of these values. A hit stays eligible for 24 hours.

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
Uptime, last 6 months Uptime, last year Uptime, last 5 years Uptime, last 30 days
1M 6M 1Y 5Y

Operator and Family

Operator Identity

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

AROI Domain (?)
digidow.eu
Operator Validation
Validated (10/10 relays)
This Relay
Validated (uri-rsa)
Contact
This Relay is operated as part of a research effort to measure how Onion Services are being used. Please see https://www.digidow.eu/onion-stats/ for more details. email:tobias.hoeller[]ins.jku.at url:www.digidow.eu proof:uri-rsa ciissversion:2
Family Configuration
Family Support
MyFamily Only (10) — Legacy only. Consider migrating to Happy Families. | View Full Family (10)
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Members: 10 
0DBA891A70AE95D4AD77593A936E6C04ABF2E7CE
592AB80372DB0365F9A2357702AC97C06E5F835C (this relay)
70B2D83BFCA9502E37EAF49DC685166718EADEFE
746BE16C31791C9A7D15461F734F0C017DDC55EE
8AC81A91A1196C2C1CBED71C96AA204F7B0FFE00
9385FF13D9E3BAB934ABCBA61EE63E10346E3673
9D970B7FBAC353D8F6049AD4E0CEE06BBDE4E17E
B97715C8A1EE72679C74480F301B11AC015B4C54
C9525872E3AA926402D8998085A409C7BBDFAE59
F97CF76D9121AC28727C22902681A9B539ABAE99
Alleged Members: 41
(they don't list you back) 
008196DC449482C73CFA9712445223917F760921 (not in the network)
0FB07690D64CE5C22B5175183C0E59678CDF7EAB (not in the network)
23D5D8219A8EB7610AB33CFAD589FD72A844356A (not in the network)
249C3A5ED8B1A8D21A3853EE7366F4FF966DD4FD (not in the network)
3434F6A8D29D147D901FCCD46BCA03A76F5181AD (not in the network)
40B334132EB4D680AC00202E0186DBB57BFF17CE (not in the network)
4FDEC4A52538AA91220D04FC25EE4AE2C725C2FE (not in the network)
58CBD772422AEFA87190560C193C0E8C03BDA6BF (not in the network)
5B07A1CEA43BCA98A971E47611C0F0D61B18761D (not in the network)
5BFFE8DAE56B1DA090BBB7BAEFC911B102D065F8 (not in the network)
6569D762AC448127664750B089F80D1597ECB709 (not in the network)
69D7FEF9B0026393C2FD73E897C71C102ABACA5C (not in the network)
6E3508CB2374D411CD41FEE8ECDF70DA3A2F7A28 (not in the network)
6FB68261B9CDD76CD5195A574D4FF561A2CC0204 (not in the network)
70882B116C73BE323036D824315A050EE796C445 (not in the network)
73F34CDC592584C0519988E443E6FDFBA72C790B (not in the network)
742425F73781A5A50932C09EEA8A5A596995217E (not in the network)
795D165D2AD5E7FFE28573924F92895D08E0170D (not in the network)
831F731BA469539EFBEEF609D4DEE0382BB8FC68 (not in the network)
837405E32D70E1B29CE1FFE85C053E41CBF267A8 (not in the network)
877AAA1DF08D902DCA667056EB6DFC4CD2B06658 (not in the network)
885C7B6EB943068B762070E276E299319E5AB08C (not in the network)
97E348CE78F9525797DA4827FCAE94C15FDFF9AA (not in the network)
9C4CD321BFEA796CE871F186776001FBEF886427 (not in the network)
9C97939FD72EA7A301195E41DCDA907E4494A9B5 (not in the network)
9D97F82F160AEF3FFD7A0AB2BFB68B691121CB11 (not in the network)
B143359560E1930347825D441AF91E737A4B9DF3 (not in the network)
B65EBC8D596BBCAD0AF6092C733C00872959FD68 (not in the network)
B8C9CA7A90A2D94406C6D9899340EB68DA4265B8 (not in the network)
B9208EAD1E688E9EE43A05159ACD4638EB4DFD8A (not in the network)
BC6E80744314F16054A64EE0F2302F082C929958 (not in the network)
C0360EB664017B831FF73FE2A41A154CE264FAC4 (not in the network)
C1CA4E603F152E8C86E864F4FBF1162A3BFDF587 (not in the network)
CB2EC8D80624CA6DD5092E1A794DEA488A81B50A (not in the network)
CFB535715442BC0E9F6AF224A794BBFA02D0B343 (not in the network)
D6015DEF7073A550DB4E797C76A71F35D28468A2 (not in the network)
DC5BACF269EFDC7FE91356F2A98ADDAA49BD82EC (not in the network)
DE879EBAF50B900E1940A97B048293006874EA93 (not in the network)
E637AA0AD4BCCDD1643ADBBD6E7BDE1B13527864 (not in the network)
F6ECFD31A46F5174C25660E16C3C62E79974F9DD (not in the network)
F878ACA29A644FF361D998B0724863EFC077AE17 (not in the network)
Indirect Members: 0
none

Software and Version

Platform
Linux — Tor 0.5.0.0-alpha-dev on Linux
Version
0.5.0.0-alpha-dev — Not Recommended
Version Status
Experimental

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 Wed, 04 Nov 2026 12:15:39 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-11-04 11:15:19).

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 (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)
bastet (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 1.1 Mbit/s (M) | 816.0 Kbit/s 1.1 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 93.2% | 98% 10.5d | 8d 0.6d | 8.4d 184.7d | 5.2d 2026-11-04 05:35:11 1.1 Mbit/s (M)
dannenberg (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 1.6 Mbit/s (M) | 816.0 Kbit/s 1.6 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 96.0% | 98% 10.7d | 8d 0.9d | 9.3d 184.7d | 5.3d 2026-11-04 05:35:11 1.6 Mbit/s (M)
dizum (NL) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 856.0 Kbit/s (R) | 816.0 Kbit/s 856.0 Kbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 96.4% | 98% 12.4d | 8d 2.1d | 6.7d 184.7d | 5.3d 2026-11-04 05:35:11 856.0 Kbit/s (R)
faravahar (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 856.0 Kbit/s (R) | 816.0 Kbit/s 856.0 Kbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 95.6% | 98% 10.5d | 8d 0.8d | 6.5d 184.7d | 5.3d 2026-11-04 05:35:11 856.0 Kbit/s (R)
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 880.0 Kbit/s (M) | 816.0 Kbit/s 880.0 Kbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 94.7% | 98% 10.7d | 8d 0.8d | 10.7d 184.7d | 5.3d 2026-11-04 05:35:11 880.0 Kbit/s (M)
longclaw (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 856.0 Kbit/s (R) | 816.0 Kbit/s 856.0 Kbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 92.4% | 98% 10.3d | 8d 0.5d | 10.9d 184.7d | 5.3d 2026-11-04 05:35:11 856.0 Kbit/s (R)
maatuska (SE) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 856.0 Kbit/s (R) | 816.0 Kbit/s 856.0 Kbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 92.6% | 98% 10.2d | 8d 0.5d | 2.3d 184.7d | 5.3d 2026-11-04 05:35:11 856.0 Kbit/s (R)
moria1 (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Stable 2.2 Mbit/s (M) | 8.4 Mbit/s 2.2 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 93.0% | 98% 9.7d | 8d 19594.1d | 7607.9d 184.7d | 5.3d 2026-11-04 05:35:11 2.2 Mbit/s (M)
tor26 (AT) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 960.0 Kbit/s (M) | 816.0 Kbit/s 960.0 Kbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s 95.1% | 98% 10.5d | 8d 0.8d | 10.6d 184.7d | 5.3d 2026-11-04 05:35:11 960.0 Kbit/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.