View Relay "Gabara"

Fingerprint: 9A88D6739698A0D08B1F4FE27AAF57EE08054F2F | Operator: gojira-family.dedyn.io v2 (6 relays) ⚠ Misconfigured | Family: 6 relays | email:gojira-family[]riseup.net... | AS210226 | Germany | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
5/7 BW Auths Measured 296 Mbit/s Median
Stability
Not Overloaded | UP 3d 23h 23m ago | UP 98% (1M)
Reachability
IPv4: 9/9 | v6: 8/8(Directory Auths)
BW Weight
0.02% of Network | 193 Mbit/s Observed By Relay
Version
0.4.9.15 Recommended
Issues Detected:
  • HSDir: uptime below 96 hours : Only 0/9 authorities voted HSDir, though this relay has Fast, Stable and V2Dir
    Suggestion: HSDir needs 96 hours of uptime as each authority sees it (MinUptimeHidServDirectoryV2): the time since your relay restarted, or since that authority last failed to reach it if that is shorter. Keep the relay running and reachable.
Notes:
  • Guard: WFU near threshold: Weighted Fractional Uptime is just above the Guard bar at dizum (97.9%, need ≥97.774%) and maatuska (98.4%, 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
128.0.64.148:9001
[2a0c:d480:c1c1:1286:ffff:ffff:ffff:ffe]:9001
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS210226
AS Name
Windcloud 4.0 GmbH (BGP.tools)
AS Rarity
Legendary (score: 4/5, 0.06% consensus weight, 1 operator)

Current Flags (6): Running, Valid, V2Dir, Fast, Stable, Guard
Eligible Flags (6): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 8/9 | HSDir: 0/9 | Guard: 8/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
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) 216.0 Mbit/s – 360.0 Mbit/s (5 DA measured)
80.0 Mbit/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 (2/9 DA) Median: 7.7d (4/9 DA above threshold)
Min/Max: 2.1d / 8322.9d (9/9 DA, Voting / Total Eligible)
≥2.3d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.9d
Uptime Below (0/9 DA) 4.0d (R) ≥5.2d - 5.3d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
216.0 Mbit/s – 360.0 Mbit/s (5 DA measured)
80.0 Mbit/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 Meets (8/9 DA) 8/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 Below (0/9 DA) 4.0d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.8d Time Known
Guard Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
216.0 Mbit/s – 360.0 Mbit/s (5 DA measured)
80.0 Mbit/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 Meets (8/9 DA) 8/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 Meets (9/9 DA) Median: 99.4% (9/9 DA above threshold)
Min/Max: 97.9% / 99.6% (9/9 DA, Voting / Total Eligible)
≥98%; dizum: ≥97.774% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 15.8d (9/9 DA above threshold)
Min/Max: 9.6d / 16.7d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 216.0 Mbit/s – 360.0 Mbit/s (5 DA measured)
80.0 Mbit/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).

Capacity (Relay Reported)
Observed Bandwidth
193.38 Mbit/s
Advertised Bandwidth
193.38 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
2.6 PB (5 years)
1mo: 73 TB | 6mo: 532 TB | 1y: 934 TB | 5y: 2.6 PB
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
296.0 Mbit/s (median of 5 measurements)
Measured Min / Max
216.0 Mbit/s / 360.0 Mbit/s
Network Participation: Consensus Weight: 0.0187% of network (82th pctl) | Guard: 0.0392% (73th pctl) | Middle: 0.0147% (74th pctl) | Exit: N/A
History

Uptime Metrics
Current Status
UP 3d 23h 23m ago
Overall Uptime (1M/6M/1Y/5Y)
98.7%/99.4%/99.7%/99.2%
Flag Uptime (1M/6M/1Y/5Y)
85.1%/95.7%/97.8%/96.9%
Hibernating
No
Timestamps
First Seen
3y 3mo 3w ago (2023-07-17 00:00:00)
Last Seen
1h 15m 40s ago (2026-11-04 11:00:00)
Last Restarted
3d 23h 23m ago (2026-10-31 12:52:16)
Last Changed Address
2026-04-06 23:00:00
Overload Status: Not Overloaded — No overload conditions reported.

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).

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-04 03:00 UTC

AROI Domain (?)
gojira-family.dedyn.io
Operator Validation
Unvalidated
This Relay
Unvalidated
Error: DNS-RSA: TXT record not found at gojira-family.dedyn.io
Contact
email:gojira-family[]riseup.net url:gojira-family.dedyn.io proof:dns-rsa pgp:F0BA73A5A8DFDF02517871299FC70E9B2760BD4E xmr:893XjtXXkGUYoxentiw4K6RQzfsFLwybR9oKnGujGHmhXfFEfBoyXKw2JqxJr6po5fB8qL6DG5tvWAPbEQDU1Aq4UX41QRo ciissversion:2
Family Configuration
Family Support
MyFamily Only (6) — Legacy only. Consider migrating to Happy Families. | View Full Family (6)
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Members: 6
08C1572C09F270010A277E58CDFBE270CBE2331B
8804E86FD02549118F0F6B6F91F634409423ACDD
9289033F9CC6667E4A8B457C462E754F01C044F0
9A88D6739698A0D08B1F4FE27AAF57EE08054F2F (this relay)
AD0D7618B6E7A4D125ABB07B53EACB2146FFC8D9
E31B3E63F132961C70C5FCEE2187F4F935391234
Alleged Members: 6
(they don't list you back)
2B127A5099E503DBD3AA5D8F51E49D236059832A (not in the network)
366F597A7F95581904DC05EB811240C958C17F3D (not in the network)
ADFAC932FD6BFBE3547D055E20F220512C156D1B (not in the network)
CCDFC7112CE4FCC190DB6463B5AB623A978B9246 (not in the network)
CFD56B3FC2F6787D6205EA2C9B76D1ED7F6E406C (not in the network)
E217ADB4536BD5A8892F4B51449171BE48CBAEBE (not in the network)
Indirect Members: 0
none

Platform
Linux — Tor 0.4.9.15 on Linux
Version
0.4.9.15 — 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 Wed, 04 Nov 2026 12:15:39 GMT.

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

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)
bastet (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, Guard 216.0 Mbit/s (M) | 816.0 Kbit/s 216.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 99.3% | 98% 15.0d | 8d 6.7d | 8.4d 4.0d | 5.2d 2026-11-04 06:52:44 216.0 Mbit/s (M)
dannenberg (DE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, Guard 360.0 Mbit/s (M) | 816.0 Kbit/s 360.0 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 99.5% | 98% 16.5d | 8d 7.7d | 9.3d 4.0d | 5.3d 2026-11-04 06:52:44 360.0 Mbit/s (M)
dizum (NL) Yes Yes No — N Yes Yes Running, Valid, V2Dir, Fast, Stable, Guard 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 97.9% | 98% 15.8d | 8d 7.1d | 6.7d 4.0d | 5.3d 2026-11-04 06:52:44 80.0 Mbit/s (R)
faravahar (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, Guard 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.4% | 98% 15.1d | 8d 6.4d | 6.5d 4.0d | 5.3d 2026-11-04 06:52:44 80.0 Mbit/s (R)
gabelmoo (DE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, Guard 296.0 Mbit/s (M) | 816.0 Kbit/s 296.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 99.6% | 98% 16.7d | 8d 9.7d | 10.7d 4.0d | 5.3d 2026-11-04 06:52:44 296.0 Mbit/s (M)
longclaw (US) Yes Yes No — Y Yes N/T Running, Valid, V2Dir, Fast, Stable, Guard 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.3d | 8d 9.7d | 10.9d 4.0d | 5.3d 2026-11-04 06:52:44 80.0 Mbit/s (R)
maatuska (SE) Yes Yes No — N Yes Yes Running, Valid, V2Dir, Fast 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 98.4% | 98% 13.9d | 8d 2.1d | 2.3d 4.0d | 5.3d 2026-11-04 06:52:44 80.0 Mbit/s (R)
moria1 (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, Guard 296.0 Mbit/s (M) | 8.4 Mbit/s 296.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 99.3% | 98% 9.6d | 8d 8322.9d | 7607.9d 4.0d | 5.3d 2026-11-04 06:52:44 296.0 Mbit/s (M)
tor26 (AT) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, Guard 328.0 Mbit/s (M) | 816.0 Kbit/s 328.0 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s 99.6% | 98% 16.3d | 8d 9.7d | 10.6d 4.0d | 5.3d 2026-11-04 06:52:44 328.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.