View Relay "GamerRelayNumberOne"
Fingerprint: C878EC8299C3C8E20A9592D75976373985D48A57 |
Family: 1 relay
|
tor_relay@gmx.de |
AS3320
|
Germany
|
Windows
- Consensus
- In Consensus (9/9 Directory Auths)
- BW Verified
- 5/6 BW Auths Measured 34 Kbit/s Median
- Stability
- Not Overloaded | DOWN 5h 45m 38s ago
- Reachability
- IPv4: 9/9 (Directory Auths)
- BW Weight
- 0.00% of Network | 34 Mbit/s Observed By Relay
- Version
- 0.4.9.5 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: Time Known below threshold
: Time Known 3.6 days is below 8 days requirement (4.4 more days 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
: Uptime or MTBF below network median for most authorities
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.
Addresses
- OR Address
-
pd9e9bde3.dip0.t-ipconnect.de
217.233.189.227:9002
Reachability (Directory Authorities)
- IPv4
- 9/9
Location
- Country
-
Germany
- Interactive Map
- View in RouteFluxMap
Eligible Flags (4):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 7/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 | Meets (9/9 DA) | 34.2 Mbit/s (R) | ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Stable | MTBF | Below (1/9 DA) | Median: 3.5d (1/9 DA above threshold) Min/Max: 2.5d / 20541.4d (9/9 DA, Voting / Total Eligible) |
≥18.0d - 58.7d (varies) (≥5/9 DA) |
| Uptime | Partial (8/9 DA) | 3.8d (R) | ≥3.5d - 3.5d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Meets (7/9 DA) | 7/9 DA assigned Fast | ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Below (1/9 DA) | 1/9 DA assigned Stable | ≥18.0d - 58.7d (varies) (≥5/9 DA) | |
| 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: 98.9% (9/9 DA above threshold) Min/Max: 98.5% / 99.1% (9/9 DA, Voting / Total Eligible) |
≥98.0% (≥5/9 DA) | |
| Time Known | Meets (8/9 DA) | Median: 3.6d (0/9 DA above threshold) Min/Max: 2.6d / 3.6d (9/9 DA, Voting / Total Eligible) |
≥1.0d (most) (≥5/9 DA) [Stricter] moria1: ≥9.8d |
|
| Guard | Prereq: Fast | Meets (7/9 DA) | 7/9 DA assigned Fast | ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Below (1/9 DA) | 1/9 DA assigned Stable | ≥18.0d - 58.7d (varies) (≥5/9 DA) | |
| 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: 98.9% (9/9 DA above threshold) Min/Max: 98.5% / 99.1% (9/9 DA, Voting / Total Eligible) |
≥98% (≥5/9 DA) | |
| Time Known | Below (0/9 DA) (need 4.4 more days) | Median: 3.6d (0/9 DA above threshold) Min/Max: 2.6d / 3.6d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Meets (9/9 DA) | 34.2 Mbit/s (R) | ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-296.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-03-29 15:45:07).
Capacity (Relay Reported)
- Observed Bandwidth
- 34.18 Mbit/s
- Advertised Bandwidth
- 34.18 Mbit/s
- Rate Limit
- 8.59 Gbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
- 19 GB (1 month)
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-03-29 15:45:07
- Measured By
-
5/6
Bandwidth Authorities
Not measured by: bastet - Median Measurement
- 34.2 Kbit/s
- Min / Max
- 8 bit/s / 56.0 Kbit/s
- Deviation
- 56.0 Kbit/s [Warning] High variation
Network Participation:
Consensus Weight:
0.0029% of network
(38th pctl)
|
Guard:
N/A |
Middle:
N/A |
Exit:
N/A
Uptime Metrics
- Current Status
- DOWN 5h 45m 38s ago
- Overall Uptime (1M/6M/1Y/5Y)
- 0.0%/0.0%/0.0%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (0.0%/0.0%/0.0%/0.0%)
- Hibernating
- No
Timestamps
- First Seen
- 3d 15h 45m ago (2026-03-26 00:00:00)
- Last Seen
- 5h 45m 38s ago (2026-03-29 10:00:00)
- Last Restarted
- 3d 19h 27m ago (2026-03-25 20:17:46)
- Last Changed Address
- 2026-03-26 00:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
Operator Identity
Source: AROI Validation API — 2026-03-29 08:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- tor_relay@gmx.de
Family Configuration
- Family Support
- None — No family membership configured
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Member: 1
C878EC8299C3C8E20A9592D75976373985D48A57 (this relay)
- Alleged Members: 0
- none
- Indirect Members: 0
- none
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Sun, 29 Mar 2026 15:45:37 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-03-29 15: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 | Flags | Fast (Relay|T) | Guard BW (Relay|Threshold) | Guard WFU (M|T) | Guard TK (M|T) | Stable MTBF (M|T) | Stable Uptime (Relay|T) | HSDir WFU (M|T) | HSDir TK (M|T) | Desc Published | Cons Wt (Authority) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bastet (US) | Yes | Yes | No | — | Y | Yes | Valid, V2Dir | 34.2 Mbit/s | 816.0 Kbit/s | 34.2 Mbit/s | 200.0 Mbit/s OR 16.0 Mbit/s | 98.9% | 98% | 3.6d | 8d | 3.5d | 63.5d | 3.8d | 3.5d | 98.9% | 98.0% | 3.6d | 1.0d | 2026-03-28 23:16:49 | 34.2 Kbit/s |
| dannenberg (DE) | Yes | Yes | No | — | N | Yes | Valid, V2Dir, Fast | 34.2 Mbit/s | 816.0 Kbit/s | 34.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 98.9% | 98% | 3.6d | 8d | 3.5d | 18.0d | 3.8d | 3.5d | 98.9% | 98.0% | 3.6d | 1.0d | 2026-03-28 23:16:49 | 34.2 Kbit/s |
| dizum (NL) | Yes | Yes | No | — | N | Yes | Valid, V2Dir, Fast | 34.2 Mbit/s | 816.0 Kbit/s | 34.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 98.6% | 98% | 2.6d | 8d | 2.5d | 42.7d | 3.8d | 3.5d | 98.6% | 98.0% | 2.6d | 1.0d | 2026-03-28 23:16:49 | 34.2 Kbit/s |
| faravahar (US) | Yes | Yes | No | — | N | Yes | Valid, V2Dir, Fast | 34.2 Mbit/s | 816.0 Kbit/s | 34.2 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 99.1% | 98% | 3.6d | 8d | 3.5d | 56.6d | 3.8d | 3.5d | 99.1% | 98.0% | 3.6d | 1.0d | 2026-03-28 23:16:49 | 34.2 Kbit/s |
| gabelmoo (DE) | Yes | Yes | No | — | Y | Yes | Valid, V2Dir, Fast | 34.2 Mbit/s | 816.0 Kbit/s | 34.2 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s | 99.0% | 98% | 3.6d | 8d | 3.5d | 61.8d | 3.8d | 3.5d | 99.0% | 98.0% | 3.6d | 1.0d | 2026-03-28 23:16:49 | 36.8 Kbit/s |
| longclaw (US) | Yes | Yes | No | — | Y | Yes | Valid, V2Dir, Fast | 34.2 Mbit/s | 816.0 Kbit/s | 34.2 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s | 99.0% | 98% | 3.6d | 8d | 3.5d | 62.8d | 3.8d | 3.5d | 99.0% | 98.0% | 3.6d | 1.0d | 2026-03-28 23:16:49 | 56.0 Kbit/s |
| maatuska (SE) | Yes | Yes | No | — | Y | Yes | Valid, V2Dir, Fast | 34.2 Mbit/s | 816.0 Kbit/s | 34.2 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s | 98.9% | 98% | 3.6d | 8d | 3.5d | 50.8d | 3.8d | 3.5d | 98.9% | 98.0% | 3.6d | 1.0d | 2026-03-28 23:16:49 | 47.2 Kbit/s |
| moria1 (US) | Yes | Yes | No | — | Y | Yes | Valid, V2Dir, Fast, Stable | 34.2 Mbit/s | 8.4 Mbit/s | 34.2 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s | 98.5% | 98% | 2.9d | 8d | 20541.4d | 291.2d | 3.8d | 4.2d | 98.5% | 98.0% | 2.9d | 9.8d | 2026-03-28 23:16:49 | 52.8 Kbit/s |
| tor26 (AT) | Yes | Yes | No | — | Y | Yes | Valid, V2Dir | 34.2 Mbit/s | 816.0 Kbit/s | 34.2 Mbit/s | 264.0 Mbit/s OR 16.0 Mbit/s | 99.1% | 98% | 3.6d | 8d | 3.5d | 58.7d | 3.8d | 3.8d | 99.1% | 98.0% | 3.6d | 1.0d | 2026-03-28 23:16:49 | 8 bit/s |
— = not tested/available • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known
Bandwidth Values Explained:
Relay Reported = Your relay's self-reported bandwidth from its descriptor (observed_bandwidth). Used for flag eligibility (Guard, Fast).
Authority Measured = Bandwidth measured by authority's sbws scanner. Used for consensus weight (path selection probability).
Why different? Authorities verify your reported bandwidth independently. 6 of 9 authorities run bandwidth scanners; 3 use relay-reported values directly.
Relay Reported = Your relay's self-reported bandwidth from its descriptor (observed_bandwidth). Used for flag eligibility (Guard, Fast).
Authority Measured = Bandwidth measured by authority's sbws scanner. Used for consensus weight (path selection probability).
Why different? Authorities verify your reported bandwidth independently. 6 of 9 authorities run bandwidth scanners; 3 use relay-reported values directly.
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.