View Relay "Mainframe"

Fingerprint: 67510E534191C9115F080C4565B2F1F348CDF9E7 | Family: 2 relays | Mafra01(AT)Safe-mail(DOT)net | AS3320 | Germany | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
5/6 BW Auths Measured 264 bit/s Median
Stability
Not Overloaded | UP 16h 9m 36s ago | UP 3% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
BW Weight
0.00% of Network | 0 Kbit/s Observed By Relay
Version
0.4.9.5 Recommended
Issues Detected:
  • Guard: requires Fast flag : Guard flag requires having the Fast flag first
    Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • 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 : Weighted Fractional Uptime 3.3% is below 98% requirement
    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 : 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 Fast flag : HSDir flag requires having the Fast flag first
    Suggestion: Get Fast flag by having bandwidth ≥100 KB/s OR in top 7/8ths of network. Most relays get this easily.
  • 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: WFU below threshold : WFU 3.3% below 98% required for HSDir
    Suggestion: HSDir requires ≥98% WFU, Stable flag, and Time Known ≥25 hours (or ~10 days for moria1). Improve uptime consistency.
  • 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
p4fc5ea1c.dip0.t-ipconnect.de
79.197.234.28:24192
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS3320
AS Name
Deutsche Telekom AG (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.21% consensus weight, 53 operators)

Current Flags (3): Running, Valid, V2Dir
Eligible Flags (3): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 0/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 Below (0/9 DA) 264 bit/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: 0.7d (1/9 DA above threshold)
Min/Max: 0.7d / 4098.5d (9/9 DA, Voting / Total Eligible)
≥13.1d - 56.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥324.3d
Uptime Below (0/9 DA) 0.7d (R) ≥9.3d - 12.3d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (0/9 DA) 0/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 ≥13.1d - 56.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥324.3d
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: 3.3% (0/9 DA above threshold)
Min/Max: 3.3% / 7.8% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 26.1d (9/9 DA above threshold)
Min/Max: 9.9d / 26.1d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Below (0/9 DA) 0/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 ≥13.1d - 56.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥324.3d
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: 3.3% (0/9 DA above threshold)
Min/Max: 3.3% / 7.8% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 26.1d (9/9 DA above threshold)
Min/Max: 9.9d / 26.1d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 264 bit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-288.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-19 21:45:07).

Capacity (Relay Reported)
Observed Bandwidth
0.00 Kbit/s
Advertised Bandwidth
Unknown
Rate Limit
41.94 Mbit/s
Burst Limit
83.89 Mbit/s
Total Data
172 TB (5 years)
1mo: 1.6 TB | 6mo: 26 TB | 1y: 69 TB | 5y: 172 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-03-19 21:45:07

Measured By
5/6 Bandwidth Authorities
Not measured by: longclaw
Median Measurement
264 bit/s
Min / Max
0 bit/s / 352 bit/s
Deviation
352 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (4th pctl) | Guard: N/A | Middle: 0.0001% (3th pctl) | Exit: N/A

Uptime Metrics
Current Status
UP 16h 9m 36s ago
Overall Uptime (1M/6M/1Y/5Y)
3.9%/76.2%/87.3%/88.6%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (3.9%/76.2%/87.3%/88.6%)
Hibernating
No
Timestamps
First Seen
6y 2mo 3w ago (2019-12-25 00:00:00)
Last Seen
2h 46m 19s ago (2026-03-19 19:00:00)
Last Restarted
16h 9m 36s ago (2026-03-19 05:36:43)
Last Changed Address
2026-03-19 08:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator Identity

Source: AROI Validation API — 2026-03-19 14:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
Mafra01(AT)Safe-mail(DOT)net
Family Configuration
Family Support
MyFamily Only (2) — Legacy only. Consider migrating to Happy Families. | View Full Family (2)
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Members: 2
06EAC8981843984BE267EF22EC1313911BC32F3A
67510E534191C9115F080C4565B2F1F348CDF9E7 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Platform
Linux — Tor 0.4.9.5 on Linux
Version
0.4.9.5Recommended
Version Status
Recommended

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 Thu, 19 Mar 2026 21:46:19 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-03-19 21: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 Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 208.0 Mbit/s OR 16.0 Mbit/s 3.3% | 98% 26.1d | 8d 0.7d | 60.7d 0.7d | 11.4d 3.3% | 98.0% 26.1d | 1.0d 2026-03-19 06:59:51 264 bit/s
dannenberg (DE) Yes Yes No N Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 3.3% | 98% 26.0d | 8d 0.7d | 13.1d 0.7d | 12.2d 3.3% | 98.0% 26.0d | 1.0d 2026-03-19 06:59:51
dizum (NL) Yes Yes No N Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 3.3% | 98% 26.1d | 8d 0.7d | 44.0d 0.7d | 9.3d 3.3% | 98.0% 26.1d | 1.0d 2026-03-19 06:59:51
faravahar (US) Yes Yes No N Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 3.3% | 98% 26.1d | 8d 0.7d | 55.5d 0.7d | 12.3d 3.3% | 98.0% 26.1d | 1.0d 2026-03-19 06:59:51
gabelmoo (DE) Yes Yes No Y Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 272.0 Mbit/s OR 16.0 Mbit/s 3.3% | 98% 26.1d | 8d 0.7d | 61.2d 0.7d | 12.4d 3.3% | 98.0% 26.1d | 1.0d 2026-03-19 06:59:51 352 bit/s
longclaw (US) Yes Yes No Y Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 232.0 Mbit/s OR 16.0 Mbit/s 3.5% | 98% 24.4d | 8d 0.7d | 65.1d 0.7d | 12.8d 3.5% | 98.0% 24.4d | 1.0d 2026-03-19 06:59:51
maatuska (SE) Yes Yes No Y Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 288.0 Mbit/s OR 16.0 Mbit/s 3.3% | 98% 26.1d | 8d 0.7d | 44.1d 0.7d | 12.2d 3.3% | 98.0% 26.1d | 1.0d 2026-03-19 06:59:51 288 bit/s
moria1 (US) Yes Yes No Y Yes Running, Valid, V2Dir, Stable 0 bit/s | 8.4 Mbit/s 0 bit/s | 216.0 Mbit/s OR 16.0 Mbit/s 7.8% | 98% 9.9d | 8d 4098.5d | 324.3d 0.7d | 15.9d 7.8% | 98.0% 9.93d | 9.90d 2026-03-19 06:59:51 320 bit/s
tor26 (AT) Yes Yes No Y Yes Running, Valid, V2Dir 0 bit/s | 816.0 Kbit/s 0 bit/s | 264.0 Mbit/s OR 16.0 Mbit/s 3.3% | 98% 26.1d | 8d 0.7d | 56.4d 0.7d | 13.1d 3.3% | 98.0% 26.1d | 1.0d 2026-03-19 06:59:51 296 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.
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.