View Relay "ajourmag"
Fingerprint: 047EDF6B885CA60989AB921BB2D1D20CC4306546 |
Family: 1 relay
|
<admin@ajour-mag.com> |
AS24940
|
Germany
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- BW Verified
- 5/7 BW Auths Measured 1 Mbit/s Median
- Stability
- Not Overloaded | UP 1d 8h 51m ago
- Reachability
- IPv4: 9/9 (Directory Auths)
- BW Weight
- 0.00% of Network | 50 Mbit/s Observed By Relay
- Version
- 0.4.9.14 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: bandwidth below threshold
: 3/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 – 280.0 Mbit/s). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 192.0 Kbit/s – 1.9 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: Time Known below threshold
: Time Known 1.3 days is below 8 days requirement (6.7 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. -
HSDir: requires V2Dir (tunnelled-dir-server)
: HSDir requires the relay to support tunnelled directory requests (V2Dir flag). This relay is missing V2Dir — the descriptor likely does not include
tunnelled-dir-server, usually becauseDirCache 0is set in torrc.
Suggestion: RemoveDirCache 0from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includestunnelled-dir-server. You can check with:grep tunnelled-dir-server /var/lib/tor/cached-descriptors -
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
-
ajourmag.ch
49.12.71.113:9005
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: 6/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 | Below (0/9 DA) | No DirPort, no tunnelled-dir-server (R) | Tunnelled directory via ORPort or DirPort (≥5/9 DA) |
| Fast | Speed | Partial (6/9 DA) | 192.0 Kbit/s – 1.9 Mbit/s (5 DA measured) 50.3 Mbit/s (3 DA relay-reported) faravahar: not published |
≥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: 1.3d (0/9 DA above threshold) Min/Max: 1.3d / 1.3d (9/9 DA, Voting / Total Eligible) |
≥6.1d - 8.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥10277.4d |
| Uptime | Below (0/9 DA) | 1.4d (R) | ≥5.2d - 5.4d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Meets (6/9 DA) | 6/9 DA assigned Fast 192.0 Kbit/s – 1.9 Mbit/s (5 DA measured) 50.3 Mbit/s (3 DA relay-reported) faravahar: not published |
≥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 | ≥6.1d - 8.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥10277.4d |
|
| Prereq: V2Dir | Below (0/9 DA) | 0/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Below (0/9 DA) | 1.4d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known |
|
| Guard | Prereq: Fast | Meets (6/9 DA) | 6/9 DA assigned Fast 192.0 Kbit/s – 1.9 Mbit/s (5 DA measured) 50.3 Mbit/s (3 DA relay-reported) faravahar: not published |
≥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 | ≥6.1d - 8.5d (varies) (≥5/9 DA) [Stricter] moria1: ≥10277.4d |
|
| Prereq: V2Dir | Below (0/9 DA) | 0/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Meets (9/9 DA) | Majority: 100.0% (9/9 DA) | ≥98% (≥5/9 DA) | |
| Time Known | Below (0/9 DA) (need 6.7 more days) | Median: 1.3d (0/9 DA above threshold) Min/Max: 1.2d / 1.3d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Below (3/9 DA) | 192.0 Kbit/s – 1.9 Mbit/s (5 DA measured) 50.3 Mbit/s (3 DA relay-reported) faravahar: not published |
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-280.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-10-20 01:45:06).
Capacity (Relay Reported)
- Observed Bandwidth
- 50.28 Mbit/s
- Advertised Bandwidth
- 50.28 Mbit/s
- Rate Limit
- 8.59 Gbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
-
2.4 GB
(6 months)
1mo: 1.2 GB | 6mo: 2.4 GB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-10-20 01:45:06
- Measured By
-
5/7
Bandwidth Authorities
Not measured by: faravahar, longclaw - Consensus Weight
- 1.4 Mbit/s (median of 5 measurements)
- Measured Min / Max
- 192.0 Kbit/s / 1.9 Mbit/s
- Deviation
- 1.7 Mbit/s [Warning] High variation
Network Participation:
Consensus Weight:
0.0001% of network
(6th pctl)
|
Guard:
N/A |
Middle:
0.0003% (7th pctl) |
Exit:
N/A
History
Uptime Metrics
- Current Status
- UP 1d 8h 51m 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
- 1d 8h 15m ago (2026-10-18 18:00:00)
- Last Seen
- 1h 15m 35s ago (2026-10-20 01:00:00)
- Last Restarted
- 1d 8h 51m ago (2026-10-18 17:24:00)
- Last Changed Address
- 2026-10-18 18:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
History
Operator Identity
Source: AROI Validation API — 2026-10-19 18:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- <admin@ajour-mag.com>
Family Configuration
- Family Support
- None — No family membership configured
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Member: 1
047EDF6B885CA60989AB921BB2D1D20CC4306546 (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 Tue, 20 Oct 2026 02:15:34 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-10-20 01:45: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 | 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 | Running, Valid | 192.0 Kbit/s (M) | 816.0 Kbit/s | 192.0 Kbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 1.3d | 8d | 1.3d | 8.5d | 1.4d | 5.2d | 2026-10-19 16:15:04 | 192.0 Kbit/s (M) |
| dannenberg (DE) | Yes | Yes | No | — | Y | Yes | Running, Valid, Fast | 1.1 Mbit/s (M) | 816.0 Kbit/s | 1.1 Mbit/s (M) | 280.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 1.3d | 8d | 1.3d | 6.1d | 1.4d | 5.6d | 2026-10-19 16:15:04 | 1.1 Mbit/s (M) |
| dizum (NL) | Yes | Yes | No | — | N | Yes | Running, Valid, Fast | 50.3 Mbit/s (R) | 816.0 Kbit/s | 50.3 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 1.3d | 8d | 1.3d | 8.4d | 1.4d | 5.2d | 2026-10-19 16:15:04 | 50.3 Mbit/s (R) |
| faravahar (US) | Yes | Yes | No | — | Y | Yes | Running, Valid | not published | 816.0 Kbit/s | not published | 264.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 1.3d | 8d | 1.3d | 8.9d | 1.4d | 6.5d | 2026-10-19 16:15:04 | 50.3 Mbit/s (R) |
| gabelmoo (DE) | Yes | Yes | No | — | Y | Yes | Running, Valid, Fast | 1.4 Mbit/s (M) | 816.0 Kbit/s | 1.4 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 1.3d | 8d | 1.3d | 8.5d | 1.4d | 5.5d | 2026-10-19 16:15:04 | 1.4 Mbit/s (M) |
| longclaw (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, Fast | 50.3 Mbit/s (R) | 816.0 Kbit/s | 50.3 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 1.3d | 8d | 1.3d | 8.8d | 1.4d | 5.3d | 2026-10-19 16:15:04 | 50.3 Mbit/s (R) |
| maatuska (SE) | Yes | Yes | No | — | N | Yes | Running, Valid, Fast | 50.3 Mbit/s (R) | 816.0 Kbit/s | 50.3 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 1.3d | 8d | 1.3d | 8.4d | 1.4d | 5.2d | 2026-10-19 16:15:04 | 50.3 Mbit/s (R) |
| moria1 (US) | Yes | Yes | No | — | Y | Yes | Running, Valid | 1.4 Mbit/s (M) | 8.4 Mbit/s | 1.4 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 1.2d | 8d | 1.3d | 10277.4d | 1.4d | 5.4d | 2026-10-19 16:15:04 | 1.4 Mbit/s (M) |
| tor26 (AT) | Yes | Yes | No | — | Y | Yes | Running, Valid, Fast | 1.9 Mbit/s (M) | 816.0 Kbit/s | 1.9 Mbit/s (M) | 264.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 1.3d | 8d | 1.3d | 8.8d | 1.4d | 5.7d | 2026-10-19 16:15:04 | 1.9 Mbit/s (M) |
— = not tested/available • 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.