View Relay "1272008509320607"
Fingerprint: 01E44F7EE449B38FA95236791E67A39786CDBDB6 |
Family: 13 relays
|
john_rt291141(at)proton(dot)me |
AS211507
|
Netherlands
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- DNS Health
- Healthy (15.9s, 62nd percentile) (via exitdnshealth.1aeo.com)
- BW Verified
- 5/7 BW Auths Measured 36 Mbit/s Median
- Stability
- Not Overloaded | UP 2d 20m 48s ago | UP 83% (1M)
- Reachability
- IPv4: 9/9 | v6: None configured(Directory Auths)
- BW Weight
- 0.00% of Network | 96 Mbit/s Observed By Relay
- Version
- 0.4.9.12 Not Recommended
-
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: WFU below threshold
: 0/9 authorities meet guard-wfu (≥98%; dizum: ≥97.84099999999999%; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 measured 0.0%–66.0%.
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. -
Not eligible for Stable flag
: 1/9 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska 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 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. -
Tor version not recommended
: Running Tor version 0.4.9.12 which is not on the recommended list.
Suggestion: Update to the latest stable Tor version. Outdated versions may have security vulnerabilities and could eventually be rejected by the network. See torproject.org/download for latest releases.
Addresses
- OR Address
- 185.132.53.45:9001
- Exit Address
- 185.132.53.45
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- None configured
Location
- Country
-
Netherlands
- Interactive Map
- View in RouteFluxMap
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) | 18.4 Mbit/s – 43.2 Mbit/s (5 DA measured) 24.6 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 (1/9 DA) | Median: 4.7d (1/9 DA above threshold) Min/Max: 1.6d / 20733.1d (9/9 DA, Voting / Total Eligible) |
≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
| Uptime | Below (0/9 DA) | 2.0d (R) | ≥5.2d - 5.3d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 18.4 Mbit/s – 43.2 Mbit/s (5 DA measured) 24.6 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 | Below (1/9 DA) | 1/9 DA assigned Stable | ≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
|
| 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) | 2.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 18.4 Mbit/s – 43.2 Mbit/s (5 DA measured) 24.6 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 | Below (1/9 DA) | 1/9 DA assigned Stable | ≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Below (0/9 DA) | Median: 65.1% (0/9 DA above threshold) Min/Max: 0.0% / 66.0% (9/9 DA, Voting / Total Eligible) |
≥98%; dizum: ≥97.84099999999999% (≥5/9 DA) | |
| Time Known | Meets (9/9 DA) | Median: 14.4d (9/9 DA above threshold) Min/Max: 9.1d / 14.9d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Meets (9/9 DA) | 18.4 Mbit/s – 43.2 Mbit/s (5 DA measured) 24.6 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 | Meets (9/9 DA) | Port 80: Yes | Port 443: Yes (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 12:45:10).
Capacity (Relay Reported)
- Observed Bandwidth
- 96.22 Mbit/s
- Advertised Bandwidth
- 24.58 Mbit/s
- Rate Limit
- 24.58 Mbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
- 2.2 TB (1 month)
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-04 12:45:10
- Measured By
-
5/7
Bandwidth Authorities
Not measured by: faravahar, longclaw - Consensus Weight
- 36.8 Mbit/s (median of 5 measurements)
- Measured Min / Max
- 18.4 Mbit/s / 43.2 Mbit/s
- Deviation
- 24.8 Mbit/s [Warning] High variation
History
Uptime Metrics
- Current Status
- UP 2d 20m 48s ago
- Overall Uptime (1M/6M/1Y/5Y)
- 83.5%/0.0%/0.0%/0.0%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (83.5%/0.0%/0.0%/0.0%)
- Hibernating
- No
Timestamps
- First Seen
- 1w 1d 19h ago (2026-10-26 18:00:00)
- Last Seen
- 2h 45m 39s ago (2026-11-04 11:00:00)
- Last Restarted
- 2d 20m 48s ago (2026-11-02 13:24:51)
- Last Changed Address
- 2026-10-26 18:00:00
Evaluated 2026-11-04 13:45 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 42s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 6h 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 04:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- john_rt291141(at)proton(dot)me
Family Configuration
- Family Support
- MyFamily Only (13) — Legacy only. Consider migrating to Happy Families. | View Full Family (13)
- Effective Members: 0
- none
- Effective Members: 13
01E44F7EE449B38FA95236791E67A39786CDBDB6 (this relay) 1EF5EABE2FD572F4C0AEBAB6993B6DD4A29FC897 2739C3580FE65466FE93721EADA1D47478EE718C 3117B3808524C537EC8C866D6F2A0C2E790051C9 3B4B654492E48F6A2E2C0D8AAD789B1F49CD1D46 50DF6CC50A8E1B7F064EF093F7423E7A754C8F8B 80BFA9FB374B691641D9E76DF961D31DB94DE083 87E1475430F00544872D7D83D191CF7EB6752660 9EB2800D5F985BF24D0547FC9B7EE6F5CB7F0852 C7F7260F15CEA13AC15E897DDFAC623B6E97476F D8573263B0D746E598B79C3266BC9204BFF900CD F0414FB9520E5DB41E156C1B7EEF7300BDD41CF3 F6EB1D746A67E28AE775249FFD0CBBBFB94C3E45
- Alleged Members: 0
- none
- Indirect Members: 0
- none
- Platform
- Linux — Tor 0.4.9.12 on Linux
- Version
- 0.4.9.12 — Not Recommended
- Version Status
- Obsolete — Update urgently. See torproject.org/download
DNS Health
- Status
- Healthy (avg. 15.9s, 62nd percentile)
- Query Domain
78f63991e7aa4d21b9d76f8486183e29.01e44f7e.tor.exit.validator.1aeo.com- DNS Result
-
Resolved to
64.65.4.1 - Upstream Resolver
-
Not enough data
Google 100% (~16 estimated queries) - Cross-Validation
- 4/4 instances succeeded
- First Hop
- TorScale (FR) B7B35AFD69A1F8C0453A45FDC92B28824F34F402
- Exit Address Used
185.132.53.45- Per-Instance Results
-
Cross Validation Attempt 1: Success, 7.5s (cv1_w1) Cross Validation Attempt 2: Success, 19.7s (cv2_w1) Cross Validation Attempt 3: Success, 15.3s (cv3_w1) Cross Validation Attempt 4: Success, 21.0s (cv4_w1)
IPv4 Exit Policy Summary
accept: 80 443 8080 8443
IPv6 Exit Policy Summary
NoneFull Exit Policy
reject 0.0.0.0/8:* reject 169.254.0.0/16:* reject 127.0.0.0/8:* reject 192.168.0.0/16:* reject 10.0.0.0/8:* reject 172.16.0.0/12:* reject 185.132.53.45:* accept *:80 accept *:443 accept *:8080 accept *:8443 reject *:*
Last fetch was at Wed, 04 Nov 2026 13:45:39 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-04 12:45:10).
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 | Yes | — | Y | Yes | Running, Valid, V2Dir, Fast, Exit | 43.2 Mbit/s (M) | 816.0 Kbit/s | 43.2 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 65.6% | 98% | 14.9d | 8d | 4.8d | 8.4d | 2.0d | 5.2d | 2026-11-04 01:26:01 | 43.2 Mbit/s (M) |
| dannenberg (DE) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, V2Dir, Fast, Exit | 18.4 Mbit/s (M) | 816.0 Kbit/s | 18.4 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s | 65.5% | 98% | 14.9d | 8d | 4.8d | 9.3d | 2.0d | 5.3d | 2026-11-04 01:26:01 | 18.4 Mbit/s (M) |
| dizum (NL) | Yes | Yes | Yes | — | N | Yes | Running, Valid, V2Dir, Fast, Exit | 24.6 Mbit/s (R) | 816.0 Kbit/s | 24.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 63.4% | 98% | 14.0d | 8d | 3.6d | 6.7d | 2.0d | 5.3d | 2026-11-04 01:26:01 | 24.6 Mbit/s (R) |
| faravahar (US) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, V2Dir, Fast, Exit | 24.6 Mbit/s (R) | 816.0 Kbit/s | 24.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 64.6% | 98% | 14.4d | 8d | 3.5d | 6.5d | 2.0d | 5.3d | 2026-11-04 01:26:01 | 24.6 Mbit/s (R) |
| gabelmoo (DE) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, V2Dir, Fast, Exit | 42.4 Mbit/s (M) | 816.0 Kbit/s | 42.4 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s | 66.0% | 98% | 14.4d | 8d | 4.8d | 10.8d | 2.0d | 5.3d | 2026-11-04 01:26:01 | 42.4 Mbit/s (M) |
| longclaw (US) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, V2Dir, Fast, Exit | 24.6 Mbit/s (R) | 816.0 Kbit/s | 24.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 65.1% | 98% | 14.6d | 8d | 4.7d | 10.9d | 2.0d | 5.3d | 2026-11-04 01:26:01 | 24.6 Mbit/s (R) |
| maatuska (SE) | Yes | Yes | Yes | — | N | Yes | Running, Valid, V2Dir, Fast, Exit | 24.6 Mbit/s (R) | 816.0 Kbit/s | 24.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 63.6% | 98% | 13.7d | 8d | 1.6d | 2.4d | 2.0d | 5.3d | 2026-11-04 01:26:01 | 24.6 Mbit/s (R) |
| moria1 (US) | Yes | Yes | Yes | — | Y | Yes | Valid, V2Dir, Fast, Stable, Exit | 36.8 Mbit/s (M) | 8.4 Mbit/s | 36.8 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 0.0% | 98% | 9.1d | 8d | 20733.1d | 7607.5d | 2.0d | 5.3d | 2026-11-04 01:26:01 | 36.8 Mbit/s (M) |
| tor26 (AT) | Yes | Yes | Yes | — | Y | Yes | Running, Valid, V2Dir, Fast, Exit | 36.8 Mbit/s (M) | 816.0 Kbit/s | 36.8 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s | 65.3% | 98% | 14.6d | 8d | 4.7d | 10.6d | 2.0d | 5.3d | 2026-11-04 01:26:01 | 36.8 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
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.
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.

