View Relay "pKD9jZ19N1LiTvsjOF3"

Fingerprint: 37DDF1906EE3DB96130A717EA54667C64DAC78DF | Family: 1 relay | pKD9jZ19N1LiTvsjOF3 at ttutanota com | AS197540 | Germany | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
5/7 BW Auths Measured 272 Mbit/s Median
Stability
Not Overloaded | UP 1w 5d 22h ago | UP 99% (1M)
Reachability
IPv4: 9/9 | v6: 8/8(Directory Auths)
BW Weight
0.02% of Network | 173 Mbit/s Observed By Relay
Version
0.4.9.14 Not Recommended
Issues Detected:
  • 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.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.
Notes:
  • Guard: WFU near threshold: Weighted Fractional Uptime is just above the Guard bar at maatuska (98.2%, need ≥98%) and just under the Guard bar at moria1 (97.9%, need ≥98%). Recent downtime weighs more than older downtime. Avoid restarts while it is this close; a short outage can drop the Guard flag.
    Suggestion: Recent downtime weighs more than older downtime. Minimize restarts, use systemd Restart=always, and watch for OOM kills until each authority has more room above its own guard-wfu.

Addresses
OR Address
pKD9jZ19N1LiTvsjOF3.ultrasrv.de
202.61.224.179:9030
[2a03:4000:56:c1b::1]:9032
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS197540
AS Name
netcup GmbH (BGP.tools)
AS Rarity
Common (score: 0/5, 4.13% consensus weight, 175 operators)

Current Flags (7): Running, Valid, V2Dir, Fast, Stable, HSDir, Guard
Eligible Flags (7): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 6/9 | HSDir: 5/9 | Guard: 5/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
IPv6 Reachability Meets (8/8 DA) 8/8 tested authorities reached relay ≥5/8 tested (majority) (≥5/8 DA)
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) 160.0 Mbit/s – 328.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 Below (2/9 DA) Median: 5.3d (1/9 DA above threshold)
Min/Max: 2.8d / 14338.4d (9/9 DA, Voting / Total Eligible)
≥2.4d - 9.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7616.8d
Uptime Meets (9/9 DA) 13.0d (R) ≥5.2d - 5.5d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
160.0 Mbit/s – 328.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 (6/9 DA) 6/9 DA assigned Stable ≥2.4d - 9.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7616.8d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Partial (8/9 DA) 13.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
160.0 Mbit/s – 328.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 (6/9 DA) 6/9 DA assigned Stable ≥2.4d - 9.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7616.8d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Partial (7/9 DA) Median: 99.0% (7/9 DA above threshold)
Min/Max: 97.2% / 99.2% (9/9 DA, Voting / Total Eligible)
≥98%; dizum: ≥97.86% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 19.1d (9/9 DA above threshold)
Min/Max: 9.7d / 21.4d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 160.0 Mbit/s – 328.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 17:15:06).

Capacity (Relay Reported)
Observed Bandwidth
173.99 Mbit/s
Advertised Bandwidth
142.61 Mbit/s
Rate Limit
142.61 Mbit/s
Burst Limit
167.77 Mbit/s
Total Data
4.0 PB (5 years)
1mo: 67 TB | 6mo: 356 TB | 1y: 746 TB | 5y: 4.0 PB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-04 17:15:06

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight
272.0 Mbit/s (median of 5 measurements)
Measured Min / Max
160.0 Mbit/s / 328.0 Mbit/s
Deviation
168.0 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0176% of network (79th pctl) | Guard: 0.0387% (72th pctl) | Middle: 0.0127% (71th pctl) | Exit: N/A
History

Uptime Metrics
Current Status
UP 1w 5d 22h ago
Overall Uptime (1M/6M/1Y/5Y)
99.1%/99.4%/99.7%/99.9%
Flag Uptime (1M/6M/1Y/5Y)
94.4%/95.7%/97.9%/99.0%
Hibernating
No
Timestamps
First Seen
7y 7mo 1w ago (2019-03-29 15:00:00)
Last Seen
1h 15m 22s ago (2026-11-04 17:00:00)
Last Restarted
1w 5d 22h ago (2026-10-22 19:20:17)
Last Changed Address
2026-04-06 23:00:00
Overload Status: Not Overloaded. Historical rate-limit report outside the 24-hour window

Evaluated 2026-11-04 18:15 UTC. /details snapshot 2026-11-04 17:00:00 UTC (cached 19s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 10h 30m ago).

Reported timestamps use hour precision, so the displayed minute is not an exact incident time.

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
Historical report — outside the 24-hour window
Rate Limit
159.38 Mbit/s
Burst Limit
21 MB
Write counter
3,038
Read counter
3
Reported
2026-11-03 14:00 UTC (1 day ago)

Read and write counters increment at most once per minute per direction. They are not a count of blocked connections, the duration of throttling, or necessarily the number of events in the last 24 hours. Rate is BandwidthRate and follows this site’s bits/bytes setting. Burst is BandwidthBurst, already a byte quantity. RelayBandwidthRate and RelayBandwidthBurst are extra torrc caps, not the names of these values. A hit stays eligible for 24 hours.

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 08:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
pKD9jZ19N1LiTvsjOF3 at ttutanota com
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1
37DDF1906EE3DB96130A717EA54667C64DAC78DF (this relay)
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.
IPv4 Exit Policy Summary
reject: 
  1-65535
IPv6 Exit Policy Summary
None
Full Exit Policy
reject *:*

Last fetch was at Wed, 04 Nov 2026 18:15:22 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-11-04 17:15: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 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)
bastet (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast 160.0 Mbit/s (M) | 816.0 Kbit/s 160.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 98.6% | 98% 17.0d | 8d 4.3d | 8.4d 13.0d | 5.2d 2026-11-03 18:25:51 160.0 Mbit/s (M)
dannenberg (DE) Yes Yes No — Y Yes Yes Valid, V2Dir, Fast, Stable, HSDir, Guard 328.0 Mbit/s (M) | 816.0 Kbit/s 328.0 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 99.0% | 98% 19.3d | 8d 5.3d | 9.4d 13.0d | 5.5d 2026-11-04 12:25:53 328.0 Mbit/s (M)
dizum (NL) Yes Yes No — N Yes Yes Running, Valid, V2Dir, Fast 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 97.2% | 98% 16.7d | 8d 2.8d | 6.8d 13.0d | 5.5d 2026-11-04 12:25:53 80.0 Mbit/s (R)
faravahar (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.0% | 98% 18.9d | 8d 4.9d | 6.5d 13.0d | 5.5d 2026-11-04 12:25:53 80.0 Mbit/s (R)
gabelmoo (DE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 272.0 Mbit/s (M) | 816.0 Kbit/s 272.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 99.0% | 98% 20.7d | 8d 6.3d | 10.8d 13.0d | 5.5d 2026-11-04 12:25:53 272.0 Mbit/s (M)
longclaw (US) Yes Yes No — Y Yes N/T Running, Valid, V2Dir, Fast, Stable, HSDir, 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.0% | 98% 21.4d | 8d 6.4d | 10.9d 13.0d | 5.3d 2026-11-03 18:25:51 80.0 Mbit/s (R)
maatuska (SE) Yes Yes No — N Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 98.2% | 98% 19.1d | 8d 2.9d | 2.4d 13.0d | 5.5d 2026-11-04 12:25:53 80.0 Mbit/s (R)
moria1 (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable 160.0 Mbit/s (M) | 8.4 Mbit/s 160.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 97.9% | 98% 9.7d | 8d 14338.4d | 7616.8d 13.0d | 5.5d 2026-11-04 12:25:53 160.0 Mbit/s (M)
tor26 (AT) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 272.0 Mbit/s (M) | 816.0 Kbit/s 272.0 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s 99.2% | 98% 20.7d | 8d 6.4d | 10.7d 13.0d | 5.5d 2026-11-04 12:25:53 272.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 (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.