View Relay "philotes2"
Fingerprint: 9DB6BCDC10AEFB2C032857E114AF585A252E9CFB |
Family: 10 relays
|
philotes2 <at> tor.rndsh <dot> it |
AS197540
|
Germany
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- BW Verified
- 5/7 BW Auths Measured 112 Mbit/s Median
- Stability
- Not Overloaded | UP 8h 9m 37s ago | UP 99% (1M)
- Reachability
- IPv4: 9/9 | v6: None configured(Directory Auths)
- BW Weight
- 0.01% of Network | 98 Mbit/s Observed By Relay
- Version
- 0.4.9.14 Not Recommended
Issues Detected:
-
HSDir: uptime below 96 hours
: Only 0/9 authorities voted HSDir, though this relay has Fast, Stable and V2Dir
Suggestion: HSDir needs 96 hours of uptime as each authority sees it (MinUptimeHidServDirectoryV2): the time since your relay restarted, or since that authority last failed to reach it if that is shorter. Keep the relay running and reachable. -
Tor version not recommended
: Running Tor version 0.4.9.14 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
-
philotes.leonklingele.de
94.16.118.250:1993
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- None configured
Location
- Country
-
Germany
- Interactive Map
- View in RouteFluxMap
Eligible Flags (6):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 9/9 | HSDir: 0/9 | Guard: 9/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) | 88.0 Mbit/s – 136.0 Mbit/s (5 DA measured) 80.0 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 | Partial (8/9 DA) | Median: 40.1d (8/9 DA above threshold) Min/Max: 4.9d / 6576.0d (9/9 DA, Voting / Total Eligible) |
≥2.3d - 9.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥7858.2d |
| Uptime | Below (0/9 DA) | 0.3d (R) | ≥5.0d - 5.1d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 88.0 Mbit/s – 136.0 Mbit/s (5 DA measured) 80.0 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 | Meets (9/9 DA) | 9/9 DA assigned Stable | ≥2.3d - 9.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥7858.2d |
|
| 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) | 0.3d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.9d Time Known |
|
| Guard | Prereq: Fast | Meets (9/9 DA) | 9/9 DA assigned Fast 88.0 Mbit/s – 136.0 Mbit/s (5 DA measured) 80.0 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 | Meets (9/9 DA) | 9/9 DA assigned Stable | ≥2.3d - 9.2d (varies) (≥5/9 DA) [Stricter] moria1: ≥7858.2d |
|
| 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: 99.9% (9/9 DA above threshold) Min/Max: 99.3% / 100.0% (9/9 DA, Voting / Total Eligible) |
≥98%; dizum: ≥97.756% (≥5/9 DA) | |
| Time Known | Meets (9/9 DA) | Median: 57.9d (9/9 DA above threshold) Min/Max: 9.9d / 383.8d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Meets (9/9 DA) | 88.0 Mbit/s – 136.0 Mbit/s (5 DA measured) 80.0 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 | 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 08:15:15).
Capacity (Relay Reported)
- Observed Bandwidth
- 98.15 Mbit/s
- Advertised Bandwidth
- 98.15 Mbit/s
- Rate Limit
- 8.59 Gbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
-
972 TB
(5 years)
1mo: 27 TB | 6mo: 114 TB | 1y: 245 TB | 5y: 972 TB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-04 08:15:15
- Measured By
-
5/7
Bandwidth Authorities
Not measured by: faravahar, longclaw - Consensus Weight
- 112.0 Mbit/s (median of 5 measurements)
- Measured Min / Max
- 88.0 Mbit/s / 136.0 Mbit/s
Network Participation:
Consensus Weight:
0.0071% of network
(58th pctl)
|
Guard:
0.0157% (48th pctl) |
Middle:
0.0047% (52th pctl) |
Exit:
N/A
History
Uptime Metrics
- Current Status
- UP 8h 9m 37s ago
- Overall Uptime (1M/6M/1Y/5Y)
- 99.6%/99.9%/100.0%/100.0%
- Flag Uptime (1M/6M/1Y/5Y)
- Matches Overall Uptime (99.6%/99.9%/100.0%/100.0%)
- Hibernating
- No
Timestamps
- First Seen
- 6y 3mo 1w ago (2020-07-29 16:00:00)
- Last Seen
- 1h 15m 43s ago (2026-11-04 08:00:00)
- Last Restarted
- 8h 9m 37s ago (2026-11-04 01:06:06)
- Last Changed Address
- 2026-04-06 23:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
Evaluated 2026-11-04 09:15 UTC. /details snapshot 2026-11-04 08:00:00 UTC (cached 11s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 1h 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 00:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- philotes2 <at> tor.rndsh <dot> it
Family Configuration
- Family Support
- MyFamily Only (10) — Legacy only. Consider migrating to Happy Families. | View Full Family (10)
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Members: 10
037BCD0EBDF7DB9F3D562DA27D463F0F78F1494B 20E0DD3AD266195F4620E8334B4CF7F51A3F210D 26B2BBE67149973AA6F631FD09E2A34E73253AB4 502774BA0466D3AE9B7A7A0EA2259CC62B8398A9 759BB10724C622B1238184FE43773B6481B1AD43 9DB6BCDC10AEFB2C032857E114AF585A252E9CFB (this relay) CBA653B8678CF7BEF7C2C1BCDCA0807CD449A8AB E9F71AC06F29B2110E3FC09016B0E50407444EE2 F1E6676A0551B4D88262536FAAB488B861AACA1A F3EB1E1FF45A3CDE4E02FBD4E805D4FC37A4AD56
- Alleged Members: 0
- none
- Indirect Members: 0
- none
- Platform
- Linux — Tor 0.4.9.14 on Linux
- Version
- 0.4.9.14 — Not Recommended
- Version Status
- Obsolete — Update urgently. See torproject.org/download
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Wed, 04 Nov 2026 09:15:43 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-04 08:15:15).
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, V2Dir, Fast, Stable, Guard | 104.0 Mbit/s (M) | 816.0 Kbit/s | 104.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 99.7% | 98% | 30.2d | 8d | 15.3d | 8.4d | 0.3d | 5.2d | 2026-11-04 01:06:15 | 104.0 Mbit/s (M) |
| dannenberg (DE) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Fast, Stable, Guard | 112.0 Mbit/s (M) | 816.0 Kbit/s | 112.0 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 109.3d | 8d | 75.8d | 9.2d | 0.3d | 5.2d | 2026-11-04 01:06:15 | 112.0 Mbit/s (M) |
| dizum (NL) | Yes | Yes | No | — | N | Yes | Running, Valid, V2Dir, Fast, Stable, Guard | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.6% | 98% | 85.3d | 8d | 43.6d | 6.6d | 0.3d | 5.1d | 2026-11-04 01:06:15 | 80.0 Mbit/s (R) |
| faravahar (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Fast, Stable, Guard | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.9% | 98% | 57.9d | 8d | 28.0d | 6.4d | 0.3d | 5.1d | 2026-11-04 01:06:15 | 80.0 Mbit/s (R) |
| gabelmoo (DE) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Fast, Stable, Guard | 120.0 Mbit/s (M) | 816.0 Kbit/s | 120.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s | 99.9% | 98% | 51.2d | 8d | 35.5d | 10.6d | 0.3d | 5.1d | 2026-11-04 01:06:15 | 120.0 Mbit/s (M) |
| longclaw (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Fast, Stable, Guard | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.9% | 98% | 57.9d | 8d | 40.1d | 10.7d | 0.3d | 5.0d | 2026-11-04 01:06:15 | 80.0 Mbit/s (R) |
| maatuska (SE) | Yes | Yes | No | — | N | Yes | Running, Valid, V2Dir, Fast, Stable, Guard | 80.0 Mbit/s (R) | 816.0 Kbit/s | 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.3% | 98% | 38.7d | 8d | 4.9d | 2.3d | 0.3d | 5.1d | 2026-11-04 01:06:15 | 80.0 Mbit/s (R) |
| moria1 (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Fast, Stable, Guard | 88.0 Mbit/s (M) | 8.4 Mbit/s | 88.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 99.4% | 98% | 9.9d | 8d | 6576.0d | 7858.2d | 0.3d | 5.2d | 2026-11-04 01:06:15 | 88.0 Mbit/s (M) |
| tor26 (AT) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Fast, Stable, Guard | 136.0 Mbit/s (M) | 816.0 Kbit/s | 136.0 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 383.8d | 8d | 266.5d | 10.5d | 0.3d | 5.1d | 2026-11-04 01:06:15 | 136.0 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
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.