View Relay "dnslgbtonion1"
Fingerprint: 469FB12BF25E0EA9ED889D0FE8BDC0E5AB2CD74C |
Family: 3 relays
|
kontakt@schramm.software |
AS8560
|
Germany
|
Linux
- Consensus
- Not In Consensus (2/9 Directory Auths, need 5)
- BW Verified
- 1/7 BW Auths Measured 160 Kbit/s Median
- Stability
- Not Overloaded | DOWN 12h 15m 39s ago | UP 97% (1M)
- Reachability
- IPv4: 2/9 | v6: 0/1(Directory Auths)
- BW Weight
- 0.02% of Network | 271 Mbit/s Observed By Relay
- Version
- 0.4.9.15 Recommended
Issues Detected:
-
Not in consensus
: Only 2/9 authorities voted for this relay (need 5)
Suggestion: Verify your relay is reachable from multiple geographic locations. Check firewall rules allow incoming connections on your ORPort from all directory authority IP addresses. -
IPv4 reachability issues
: Only 2/9 authorities can reach this relay
Suggestion: Authorities that cannot reach you: dannenberg, dizum, faravahar, gabelmoo, maatuska, moria1, tor26. Check: 1) Firewall allows incoming TCP on ORPort, 2) No ISP-level blocking, 3) Tor is running and listening. Use 'nc -zv your-ip your-orport' from external hosts to test. -
IPv6 not reachable
: 0/1 authorities that test IPv6 can reach your IPv6 address
Suggestion: Verify IPv6 is correctly configured: 1) Check ORPort binding includes IPv6 address, 2) Firewall allows IPv6 traffic, 3) IPv6 address is publicly routable. Test with: curl -6 http://ipv6.icanhazip.com/ -
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
: 2/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 – 192.0 Mbit/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
: 2/9 authorities meet guard-wfu (≥98%; 5 needed).
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
: 2/9 authorities meet guard-tk (≥8 days; 5 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
: 0/9 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). bastet and longclaw 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. -
Low bandwidth authority measurements
: Only 1/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. -
StaleDesc flag assigned
: Relay descriptor is older than 18 hours
Suggestion: Your relay is not publishing fresh descriptors. Check: 1) Tor process is running, 2) Network connectivity, 3) Clock is synchronized (NTP). Restart Tor if needed.
Addresses
- OR Address
-
87.106.107.89:9001
[2a01:239:381:8e00::1]:9001
Reachability (Directory Authorities)
- IPv4
- 2/9
- IPv6
- 0/1 (1 don't test)
Location
- Country
-
Germany
- Interactive Map
- View in RouteFluxMap
Eligible Flags (0):
Running: 2/9 | Valid: 2/9 | V2Dir: 2/9 | Fast: 2/9 | Stable: 2/9 | HSDir: 0/9 | Guard: 2/9 | Exit: 0/9
Eligibility Flag Vote Details
| Flag | Metric | Status | Relay Value | Threshold Required |
|---|---|---|---|---|
| Running | IPv4 Reachability | Below (2/9 DA) | 2/9 authorities reached relay | ≥5/9 DA ORPort reachable |
| IPv6 Reachability | Below (0/1 DA) | 0/1 tested authorities reached relay | ≥1/1 tested (majority) (≥1/1 DA) | |
| Valid | Descriptor | Partial (2/9 DA) | 2/9 authorities assigned Valid | Not blacklisted + valid descriptor (≥5/9 DA) |
| V2Dir | DirPort Available | Meets (2/9 DA) | Tunnelled: Yes (no DirPort) (R) | Tunnelled directory via ORPort or DirPort (≥5/9 DA) |
| Fast | Speed | Below (2/9 DA) | 288.0 Mbit/s (1 DA measured) 80.0 Mbit/s (1 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 (0/9 DA) | Median: 6.7d (0/9 DA above threshold) Min/Max: 6.4d / 7.1d (2/9 DA, Voting / Total Eligible) |
≥2.4d - 9.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥7616.8d |
| Uptime | Below (0/9 DA) | 1.2d (R) | ≥5.2d - 5.5d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Below (2/9 DA) | 2/9 DA assigned Fast 288.0 Mbit/s (1 DA measured) 80.0 Mbit/s (1 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 (2/9 DA) | 2/9 DA assigned Stable | ≥2.4d - 9.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥7616.8d |
|
| Prereq: V2Dir | Below (2/9 DA) | 2/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Below (0/9 DA) | 1.2d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known |
|
| Guard | Prereq: Fast | Below (2/9 DA) | 2/9 DA assigned Fast 288.0 Mbit/s (1 DA measured) 80.0 Mbit/s (1 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 (2/9 DA) | 2/9 DA assigned Stable | ≥2.4d - 9.4d (varies) (≥5/9 DA) [Stricter] moria1: ≥7616.8d |
|
| Prereq: V2Dir | Below (2/9 DA) | 2/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Below (2/9 DA) | Median: 98.6% (2/9 DA above threshold) Min/Max: 98.5% / 98.6% (2/9 DA, Voting / Total Eligible) |
≥98% (≥5/9 DA) | |
| Time Known | Below (2/9 DA) | Median: 17.0d (2/9 DA above threshold) Min/Max: 16.9d / 17.1d (2/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Below (2/9 DA) | 288.0 Mbit/s (1 DA measured) 80.0 Mbit/s (1 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 17:15:06).
Capacity (Relay Reported)
- Observed Bandwidth
- 271.82 Mbit/s
- Advertised Bandwidth
- 271.82 Mbit/s
- Rate Limit
- 8.59 Gbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
-
3.1 PB
(5 years)
1mo: 113 TB | 6mo: 823 TB | 1y: 1.5 PB | 5y: 3.1 PB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-04 17:15:06
- Measured By
-
1/7
Bandwidth Authorities
Not measured by: dannenberg, faravahar, gabelmoo, longclaw, moria1, tor26 - Consensus Weight
- 160.0 Kbit/s (Unmeasured)
- Measured Min / Max
- 288.0 Mbit/s / 288.0 Mbit/s
Network Participation:
Consensus Weight:
0.0214% of network
(85th pctl)
|
Guard:
N/A |
Middle:
N/A |
Exit:
N/A
History
Uptime Metrics
- Current Status
- DOWN 12h 15m 39s ago
- Overall Uptime (1M/6M/1Y/5Y)
- 97.3%/99.4%/99.8%/99.9%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (97.3%/99.4%/99.8%/99.9%)
- Hibernating
- No
Timestamps
- First Seen
- 2y 9mo 2d ago (2024-02-05 18:00:00)
- Last Seen
- 12h 15m 39s ago (2026-11-04 05:00:00)
- Last Restarted
- 1d 4h 26m ago (2026-11-03 12:48:53)
- Last Changed Address
- 2026-10-25 22:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
Evaluated 2026-11-04 17:15 UTC. /details snapshot 2026-11-04 15:00:00 UTC (cached 33s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 9h 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 08:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- kontakt@schramm.software
Family Configuration
- Family Support
- Happy Families (3) — Has family-cert in server descriptor (guide) | View Full Family (3)
Happy Families (family-cert)
- Effective Members: 3
4552C6ACA869EC44672EE42D7D6BB2AA85BE92C8 469FB12BF25E0EA9ED889D0FE8BDC0E5AB2CD74C (this relay) DDA78101FC40690FC8F12D270DB76F8A92B1B783
MyFamily (legacy declarations) — none
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Wed, 04 Nov 2026 17:15:39 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-04 17:15:06).
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 | No | Valid, V2Dir, Fast, Stable, Guard, StaleDesc | 288.0 Mbit/s (M) | 816.0 Kbit/s | 288.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 98.6% | 98% | 17.1d | 8d | 6.4d | 8.4d | 1.2d | 5.2d | 2026-11-03 12:48:55 [Stale] | 80.0 Mbit/s (R) |
| dannenberg (DE) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — |
| dizum (NL) | No | — | — | — | N | No | — | — | — | — | — | — | — | — | — | — |
| faravahar (US) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — |
| gabelmoo (DE) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — |
| longclaw (US) | Yes | Yes | No | — | Y | Yes | N/T | Valid, V2Dir, Fast, Stable, Guard, StaleDesc | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 98.5% | 98% | 16.9d | 8d | 7.1d | 10.9d | 1.2d | 5.3d | 2026-11-03 12:48:55 [Stale] | 80.0 Mbit/s (R) |
| maatuska (SE) | No | — | — | — | N | No | — | — | — | — | — | — | — | — | — | — |
| moria1 (US) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — |
| tor26 (AT) | No | — | — | — | Y | No | — | — | — | — | — | — | — | — | — | — |
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 (
Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (
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.
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.
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.