View Relay "shrdrelay35"
Fingerprint: D702BC88C82D21CC5FD66D3FB0FDC842D86BA9EC |
Family: 38 relays
|
AS204464
|
United States of America
|
Platform: unknown
- Consensus
- In Consensus (8/8 Directory Auths)
- BW Verified
- 0/6 BW Auths Measured
- Stability
- Incomplete | Unknown
- Reachability
- IPv4: 8/8 | v6: 7/7(Directory Auths)
- BW Weight
- 0 Kbit/s Observed By Relay
- Version
- 0.4.9.15 Recommended
Issues Detected:
-
Not getting the Fast flag
: Only 0/8 authorities vote Fast (5 needed). dizum, faravahar, longclaw and maatuska used the relay-reported unknown, below the Fast threshold (816.0 Kbit/s). dannenberg, gabelmoo, 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/8 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). dizum, faravahar, longclaw and maatuska used the relay-reported unknown. dannenberg, gabelmoo, 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/8 authorities meet guard-tk (≥8 days; 5 needed). dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 have known this relay for 1.5 hours.
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/8 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). 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/6 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.
Addresses
- OR Address
-
static.134.113.17.38.clients.abuse.eu
38.17.113.134:9001
[2a14:7581:5080::3022]:9001
Reachability (Directory Authorities)
- IPv4
- 8/8
- IPv6
- 7/7 (1 don't test)
Location
- Country
-
United States of America
- Interactive Map
- View in RouteFluxMap
Eligible Flags (3):
Running: 8/8 | Valid: 8/8 | V2Dir: 8/8 | Fast: 0/8 | Stable: 0/8 | HSDir: 0/8 | Guard: 0/8 | Exit: 0/8
Eligibility Flag Vote Details
| Flag | Metric | Status | Relay Value | Threshold Required |
|---|---|---|---|---|
| Running | IPv4 Reachability | Meets (8/8 DA) | 8/8 authorities reached relay | ≥5/8 DA ORPort reachable |
| IPv6 Reachability | Meets (7/7 DA) | 7/7 tested authorities reached relay | ≥4/7 tested (majority) (≥4/7 DA) | |
| Valid | Descriptor | Meets (8/8 DA) | 8/8 authorities assigned Valid | Not blacklisted + valid descriptor (≥5/8 DA) |
| V2Dir | DirPort Available | Meets (8/8 DA) | Tunnelled: Yes (no DirPort) (R) | Tunnelled directory via ORPort or DirPort (≥5/8 DA) |
| Fast | Speed | Below (0/8 DA) | 0 bit/s (4 DA relay-reported) 0 bit/s (4 DA unmeasured, counted as 0) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/8 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Stable | MTBF | Below (0/8 DA) | Majority: 0.1d (5/8 DA) Min/Med/Max: 0.1d / 0.1d / 0.1d (8/8 DA, Voting / Total Eligible) |
≥1.4d - 12.9d (varies) (≥5/8 DA) [Stricter] moria1: ≥6724.7d |
| Uptime | Below (0/8 DA) | N/A (R) | ≥5.0d - 5.0d (varies) (≥5/8 DA) | |
| HSDir | Prereq: Fast | Below (0/8 DA) | 0/8 DA assigned Fast 0 bit/s (4 DA relay-reported) 0 bit/s (4 DA unmeasured, counted as 0) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/8 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Below (0/8 DA) | 0/8 DA assigned Stable | ≥1.4d - 12.9d (varies) (≥5/8 DA) [Stricter] moria1: ≥6724.7d |
|
| Prereq: V2Dir | Meets (8/8 DA) | 8/8 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/8 DA) | |
| Uptime | Below (0/8 DA) | N/A (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/8 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known |
|
| Guard | Prereq: Fast | Below (0/8 DA) | 0/8 DA assigned Fast 0 bit/s (4 DA relay-reported) 0 bit/s (4 DA unmeasured, counted as 0) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/8 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Below (0/8 DA) | 0/8 DA assigned Stable | ≥1.4d - 12.9d (varies) (≥5/8 DA) [Stricter] moria1: ≥6724.7d |
|
| Prereq: V2Dir | Meets (8/8 DA) | 8/8 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/8 DA) | |
| WFU | Meets (8/8 DA) | Majority: 100.0% (8/8 DA above threshold) | ≥98%; maatuska: ≥96.571% (≥5/8 DA) | |
| Time Known | Below (0/8 DA) | Median: 0.1d (0/8 DA above threshold) Min/Med/Max: 0.1d / 0.1d / 0.1d (8/8 DA, Voting / Total Eligible) |
≥8 days (≥5/8 DA) | |
| Bandwidth | Below (0/8 DA) | 0 bit/s (4 DA relay-reported) 0 bit/s (4 DA unmeasured, counted as 0) |
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-272.0 Mbit/s) (≥5/8 DA) | |
| Exit | Exit Policy | Below (0/8 DA) | Port 80: No | Port 443: No (R) | Allows ≥1 /8 on ports 80 AND 443 (≥5/8 DA) |
(DA) = Dir. Auth. Measured |
(R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-11-11 13:45:07).
Capacity (Relay Reported)
- Observed Bandwidth
- 0.00 Kbit/s
- Advertised Bandwidth
- Unknown
- Rate Limit
- Not set
- Burst Limit
- Not set
- Total Data
- N/A
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-11 13:45:07
- Measured By
-
0/6
Bandwidth Authorities
Not measured by: 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
- Unknown
- 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
- 2h 15m 38s ago (2026-11-11 12:00:00)
- Last Seen
- 1h 15m 38s ago (2026-11-11 13:00:00)
- Last Restarted
- Unknown
- Last Changed Address
- 2026-11-11 12:00:00
Overload status:
Incomplete — not every signal could be evaluated.
(Invalid overload data; No bandwidth record available for this relay)
Evaluated 2026-11-11 14:15 UTC. /details snapshot 2026-11-11 13:00:00 UTC (cached 29s ago). /bandwidth snapshot 2026-11-11 02:00:00 UTC (cached 11h ago).
General Overload (from /details)
- Status
- Invalid overload 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
Operator Identity
Source: AROI Validation API — 2026-11-11 05:00 UTC
Family Configuration
- Family Support
- MyFamily Only (38) — Legacy only. Consider migrating to Happy Families. | View Full Family (38)
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Members: 38
0272835A7D76C84CC3327533D8AE4388A06F144B 08A954BD3EB4FEB4AF80E28E2153E3AE3298F3D0 09EF4353F98F7F73384ED3D656EFFFBC8F4EA183 0CF9A9E7CFABEA95BEF19A52DF18024C9C86DF7E 140B29C11CCC23F1281B9ED1A29C256CAF2EC490 1E475BC6968991654A8A1E86537139DE0CC88457 232A6A8202C9364C1487943AA8D4E1730EA8938F 25B4A79BED2A40FBB48212746B66222D5658CF13 376C296D88E5E529DBED412902559905A7110A07 3B4955C3A1063570C8CB158CD127EFD2B8C4AB26 3CA2110917C65EFCE3637C814BF35B276D14333B 3F18E8A1F11CB0DB13BB7D98717A8B4CD93E083A 49CB1170F406F5B89CC68668941ED5325D84AD68 511C35295239A6EDD1BC9455682D4768267674B6 5A78F83E91A8C275D0A7F5472C78D1975574EFD1 5B88A92E376F20E06E68DD82AC7E988F365FBDE7 5C86A36F557B64B4327AC661806387944F040469 617728C913FE871D03A296B3C5997693BB1F2A6D 6686C72471572A1CD5AC252DE1F05E86D5DFF0CC 74473E670DCEBE16B842897A2832D181D0EBC497 75A79919039D404645AA9BCC934FD45F8B2170C8 760EE45406907D89CA155E24C45AF89443C8D89B 802A69C09FC8C46D968C54093797E535BDF599B5 835BFE9ADD4CC56DD3C1B66E25C45F0C5E0937B1 94280DDE492A0BADF78CD1740C0704B1035A16AE 998CA8E197BFEFFDD35AEBF3BB10CC4D41C6E872 9D502D2CC09E5BA564E43B1C2E0D1F0101EA6F6C AB8C686652F8E2A260C70D3F5229CCF8700CD35E B31B2FE92EFE7AA6964D42B04ADA2C8F299CC5BD B8BA9BFF0A149913964C97330D134F1758772246 B9F9BBA5741FBC06F9529B9C7A02B9BDCE5F7B42 C100A707B37413A4336CDA7678DD79F1F82F2BB4 CEAAA4504DE82C411639F14916A905EA767B4EF5 D702BC88C82D21CC5FD66D3FB0FDC842D86BA9EC (this relay) DB4E6EDC885A4350BC0366959E64B231478FFC9B E85B958EA4CDCDDB48CA44D87474205906BCB250 EEA30D140C0C3AC072A09AC56C11599E55F88CB5 F004DA26E4ED2A9D7E61E7B32206124AF3094B06
- Alleged Members: 0
- none
- Indirect Members: 0
- none
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Wed, 11 Nov 2026 14:15:38 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-11 13:45:07).
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) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| dannenberg (DE) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir | 0 bit/s (U) | 816.0 Kbit/s | 0 bit/s (U) | 272.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 0.1d | 8d | 0.1d | 11.7d | N/A | 5.0d | 2026-11-11 11:19:28 | — |
| dizum (NL) | Yes | Yes | No | — | N | Yes | 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.1d | 8d | 0.1d | 10.0d | N/A | 5.0d | 2026-11-11 11:19:28 | — |
| faravahar (US) | Yes | Yes | No | — | Y | Yes | 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.1d | 8d | 0.1d | 9.4d | N/A | 5.0d | 2026-11-11 11:19:28 | — |
| gabelmoo (DE) | Yes | Yes | No | — | Y | Yes | 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.1d | 8d | 0.1d | 12.9d | N/A | 5.0d | 2026-11-11 11:19:28 | — |
| longclaw (US) | Yes | Yes | No | — | Y | Yes | N/T | 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.1d | 8d | 0.1d | 13.1d | N/A | 5.0d | 2026-11-11 11:19:28 | — |
| maatuska (SE) | Yes | Yes | No | — | N | Yes | 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% | 97% | 0.1d | 8d | 0.1d | 1.4d | N/A | 5.0d | 2026-11-11 11:19:28 | — |
| moria1 (US) | Yes | Yes | No | — | Y | Yes | 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.1d | 8d | 0.1d | 6724.7d | N/A | 5.1d | 2026-11-11 11:19:28 | — |
| tor26 (AT) | Yes | Yes | No | — | Y | Yes | Yes | Running, Valid, V2Dir | 0 bit/s (U) | 816.0 Kbit/s | 0 bit/s (U) | 256.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 0.1d | 8d | 0.1d | 12.9d | N/A | 5.0d | 2026-11-11 11:19:28 | — |
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.