View Relay "INSRelay26at8443"

Fingerprint: CB2EC8D80624CA6DD5092E1A794DEA488A81B50A | Operator: digidow.eu v2 (50 relays) ✓ Validated ⚠ this relay: Misconfigured| Family: 49 relays | This Relay is operated as part of a... | AS1205 | Austria | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
0/7 BW Auths Measured
Stability
Incomplete | UP 1h 59m 31s ago
Reachability
IPv4: 9/9 | v6: None configured(Directory Auths)
BW Weight
0 Kbit/s Observed By Relay
Version
0.5.0.0-alpha-dev Not Recommended
Issues Detected:
  • Not getting the Fast flag : Only 0/9 authorities vote Fast (5 needed). dizum, faravahar and maatuska used the relay-reported unknown, below the Fast threshold (816.0 Kbit/s). E30CF7B3, dannenberg, gabelmoo, longclaw, moria1 and tor26 counted this relay as 0 (no measurement, relay-reported bandwidth ignored).
    Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports. A low measurement means the scanners see your relay underperforming compared with other relays that report a similar speed. Clients only build circuits through Fast relays, so a relay near the threshold can gain and lose most of its traffic from one hourly consensus to the next.
  • Guard: requires Fast flag : Guard flag requires having the Fast flag first
    Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports.
  • 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 – 248.0 Mbit/s). dizum, faravahar and maatuska used the relay-reported unknown. E30CF7B3, dannenberg, gabelmoo, longclaw, moria1 and tor26 counted this relay as 0 (no measurement, relay-reported bandwidth ignored).
    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: Time Known below threshold : 0/9 authorities meet guard-tk (≥8 days; E30CF7B3: ≥5 days 13 hours 47 minutes 56 seconds; 5 needed). E30CF7B3, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 have no time-known history (1798 seconds–1809 seconds).
    Suggestion: Time Known stays near zero until an authority has observed the relay. Keep it running with the same identity key so those authorities accumulate history.
  • Not eligible for Stable flag : 0/9 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). E30CF7B3, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 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 Fast flag : HSDir flag requires having the Fast flag first
    Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports.
  • 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.
  • Low bandwidth authority measurements : Only 0/7 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
    Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.
  • 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.

Addresses
OR Address
140.78.100.26: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)

Current Flags (3): Running, Valid, V2Dir
Eligible Flags (3): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 0/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 Below (0/9 DA) 0 bit/s (3 DA relay-reported)
0 bit/s (6 DA unmeasured, counted as 0)
≥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 (0/9 DA) Median: 0.0d (0/9 DA above threshold)
Min/Max: 0.0d / 0.0d (9/9 DA, Voting / Total Eligible)
≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12424.3d
Uptime Below (0/9 DA) 0.1d (R) ≥5.0d - 5.2d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (0/9 DA) 0/9 DA assigned Fast
0 bit/s (3 DA relay-reported)
0 bit/s (6 DA unmeasured, counted as 0)
≥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 (0/9 DA) 0/9 DA assigned Stable ≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12424.3d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Below (0/9 DA) 0.1d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.4d Time Known
Guard Prereq: Fast Below (0/9 DA) 0/9 DA assigned Fast
0 bit/s (3 DA relay-reported)
0 bit/s (6 DA unmeasured, counted as 0)
≥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 (0/9 DA) 0/9 DA assigned Stable ≥2.3d - 8.2d (varies) (≥5/9 DA)
[Stricter] moria1: ≥12424.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 above threshold) ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) Median: 0.0d (0/9 DA above threshold)
Min/Max: 0.0d / 0.0d (9/9 DA, Voting / Total Eligible)
≥8 days; E30CF7B3: ≥5 days 13 hours 47 minutes 56 seconds (≥5/9 DA)
Bandwidth Below (0/9 DA) 0 bit/s (3 DA relay-reported)
0 bit/s (6 DA unmeasured, counted as 0)
≥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 11:45:05).

Capacity (Relay Reported)
Observed Bandwidth
0.00 Kbit/s
Advertised Bandwidth
Unknown
Rate Limit
860.16 Kbit/s
Burst Limit
8.59 Gbit/s
Total Data
N/A
Measurement (Directory Authority Verified)

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

Measured By
0/7 Bandwidth Authorities
Not measured by: E30CF7B3, dannenberg, faravahar, gabelmoo, longclaw, moria1, tor26
Consensus Weight
0 bit/s (Unmeasured)
Measured Min / Max
N/A / N/A
Network Participation: Consensus Weight: N/A | Guard: N/A | Middle: N/A | Exit: N/A

Uptime Metrics
Current Status
UP 1h 59m 31s ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
N/A
Hibernating
No
Timestamps
First Seen
1h 16m 17s ago (2026-11-20 11:00:00)
Last Seen
1h 16m 17s ago (2026-11-20 11:00:00)
Last Restarted
1h 59m 31s ago (2026-11-20 10:16:46)
Last Changed Address
2026-11-20 11:00:00
Overload status: Incomplete — not every signal could be evaluated. (No bandwidth record available for this relay)

Evaluated 2026-11-20 12:16 UTC. /details snapshot 2026-11-20 11:00:00 UTC (cached 11s ago). /bandwidth snapshot 2026-11-20 02:00:00 UTC (cached 9h 1m ago).

General Overload (from /details)
Status
No general overload report in available data
File Descriptor Exhaustion (from /bandwidth)
Status
No bandwidth record available for this relay
Rate Limits (from /bandwidth)
Status
No bandwidth record available for this relay
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

Family Configuration
Family Support
MyFamily Only (49) — Legacy only. Consider migrating to Happy Families. | View Full Family (49)
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Members: 49
008196DC449482C73CFA9712445223917F760921
0DBA891A70AE95D4AD77593A936E6C04ABF2E7CE
0FB07690D64CE5C22B5175183C0E59678CDF7EAB
23D5D8219A8EB7610AB33CFAD589FD72A844356A
249C3A5ED8B1A8D21A3853EE7366F4FF966DD4FD
40B334132EB4D680AC00202E0186DBB57BFF17CE
4FDEC4A52538AA91220D04FC25EE4AE2C725C2FE
58CBD772422AEFA87190560C193C0E8C03BDA6BF
592AB80372DB0365F9A2357702AC97C06E5F835C
5B07A1CEA43BCA98A971E47611C0F0D61B18761D
5BFFE8DAE56B1DA090BBB7BAEFC911B102D065F8
6569D762AC448127664750B089F80D1597ECB709
69D7FEF9B0026393C2FD73E897C71C102ABACA5C
6E3508CB2374D411CD41FEE8ECDF70DA3A2F7A28
70882B116C73BE323036D824315A050EE796C445
70B2D83BFCA9502E37EAF49DC685166718EADEFE
73F34CDC592584C0519988E443E6FDFBA72C790B
742425F73781A5A50932C09EEA8A5A596995217E
746BE16C31791C9A7D15461F734F0C017DDC55EE
795D165D2AD5E7FFE28573924F92895D08E0170D
831F731BA469539EFBEEF609D4DEE0382BB8FC68
837405E32D70E1B29CE1FFE85C053E41CBF267A8
877AAA1DF08D902DCA667056EB6DFC4CD2B06658
885C7B6EB943068B762070E276E299319E5AB08C
8AC81A91A1196C2C1CBED71C96AA204F7B0FFE00
9385FF13D9E3BAB934ABCBA61EE63E10346E3673
97E348CE78F9525797DA4827FCAE94C15FDFF9AA
9C4CD321BFEA796CE871F186776001FBEF886427
9C97939FD72EA7A301195E41DCDA907E4494A9B5
9D970B7FBAC353D8F6049AD4E0CEE06BBDE4E17E
9D97F82F160AEF3FFD7A0AB2BFB68B691121CB11
B143359560E1930347825D441AF91E737A4B9DF3
B65EBC8D596BBCAD0AF6092C733C00872959FD68
B8C9CA7A90A2D94406C6D9899340EB68DA4265B8
B9208EAD1E688E9EE43A05159ACD4638EB4DFD8A
B97715C8A1EE72679C74480F301B11AC015B4C54
BC6E80744314F16054A64EE0F2302F082C929958
C0360EB664017B831FF73FE2A41A154CE264FAC4
C1CA4E603F152E8C86E864F4FBF1162A3BFDF587
C9525872E3AA926402D8998085A409C7BBDFAE59
CB2EC8D80624CA6DD5092E1A794DEA488A81B50A (this relay)
CFB535715442BC0E9F6AF224A794BBFA02D0B343
D6015DEF7073A550DB4E797C76A71F35D28468A2
DC5BACF269EFDC7FE91356F2A98ADDAA49BD82EC
DE879EBAF50B900E1940A97B048293006874EA93
E637AA0AD4BCCDD1643ADBBD6E7BDE1B13527864
F6ECFD31A46F5174C25660E16C3C62E79974F9DD
F878ACA29A644FF361D998B0724863EFC077AE17
F97CF76D9121AC28727C22902681A9B539ABAE99
Alleged Members: 2
(they don't list you back)
3434F6A8D29D147D901FCCD46BCA03A76F5181AD
6FB68261B9CDD76CD5195A574D4FF561A2CC0204 (not in the network)
Indirect Members: 0
none

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

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 12:16:16 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-11-20 11: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 0 bit/s (U) | 816.0 Kbit/s 0 bit/s (U) | 184.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.0d | 6d 0.0d | 3.9d 0.1d | 5.2d 2026-11-20 10:20:04 —
dannenberg (DE) Yes Yes No — Y Yes Running, Valid, V2Dir 0 bit/s (U) | 816.0 Kbit/s 0 bit/s (U) | 248.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.0d | 8d 0.0d | 8.2d 0.1d | 5.2d 2026-11-20 10:20:04 —
dizum (NL) Yes Yes No — N Yes Running, Valid, V2Dir 0 bit/s (R) | 816.0 Kbit/s 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.0d | 8d 0.0d | 6.9d 0.1d | 5.2d 2026-11-20 10:20:04 —
faravahar (US) Yes Yes No — Y Yes Running, Valid, V2Dir 0 bit/s (R) | 816.0 Kbit/s 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.0d | 8d 0.0d | 7.1d 0.1d | 5.2d 2026-11-20 10:20:04 —
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, V2Dir 0 bit/s (U) | 816.0 Kbit/s 0 bit/s (U) | 240.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.0d | 8d 0.0d | 8.3d 0.1d | 5.2d 2026-11-20 10:20:04 —
longclaw (US) Yes Yes No — Y Yes Running, Valid, V2Dir 0 bit/s (U) | 816.0 Kbit/s 0 bit/s (U) | 248.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.0d | 8d 0.0d | 9.1d 0.1d | 5.2d 2026-11-20 10:20:04 —
maatuska (SE) Yes Yes No — N Yes Running, Valid, V2Dir 0 bit/s (R) | 816.0 Kbit/s 0 bit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.0d | 8d 0.0d | 2.3d 0.1d | 5.2d 2026-11-20 10:20:04 —
moria1 (US) Yes Yes No — Y Yes Running, Valid, V2Dir 0 bit/s (U) | 8.4 Mbit/s 0 bit/s (U) | 184.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.0d | 8d 0.0d | 12424.3d 0.1d | 5.0d 2026-11-20 10:20:04 —
tor26 (AT) Yes Yes No — Y Yes Running, Valid, V2Dir 0 bit/s (U) | 816.0 Kbit/s 0 bit/s (U) | 248.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 0.0d | 8d 0.0d | 8.2d 0.1d | 5.2d 2026-11-20 10:20:04 —

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.