View Relay "datashield"

Family: 1 relay | AS48314 | Germany | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Fast, Running, Valid (3)
BW Verified
5/6 BW Auths Measured 96 Kbit/s Median
Stability
Not Overloaded | UP 3d 9h 28m ago | UP 100% (1M)
Reachability
IPv4: 9/9 | v6: 7/7 (Directory Auths)
First Seen
6d 5h 54m ago
BW Weight
0.01% of Network | 94 Mbit/s Observed By Relay
Version
0.4.8.21 Recommended
Issues Detected:
  • Guard: Time Known below threshold : Time Known 5.4 days is below 8 days requirement (2.6 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.
  • 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).
  • 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.
  • 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.

Connectivity and Location

Addresses
OR Address
vm828.ipp-vps.net
185.248.141.202:9001
[2a0a:51c1:a:1df::1]:9001
Reachability (Directory Authorities)
IPv4
9/9
IPv6
7/7 (2 don't test)
Location
Country
Germany Germany
Interactive Map
View on Interactive Map
Autonomous System
AS Number
AS48314
AS Name
Michael Sebastian Schinzel trading as IP-Projects GmbH & Co. KG (BGP.tools)

Flags and Eligibility

Current Flags (3): Fast, Running, Valid
Eligible Flags (5): Guard: 0/9 | Stable: 1/9 | Fast: 9/9 | HSDir: 8/9 | Running: 9/9 | V2Dir: 9/9 | Valid: 9/9 (need ≥5/9 for flag)
Eligibility Flag Vote Details
Flag Metric Status Relay Value Threshold Required
Guard WFU Meets 98.9% (DA) ≥98% (all authorities)
Time Known Below (need 2.6 more days) 5.4 days (DA) ≥8 days (all authorities)
Bandwidth Meets (≥2 MB/s) 94.7 Mbit/s (R) ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s
Stable MTBF Below 5 days (DA) ≥26.6d - 45.4d (varies)
Uptime Below 3.4d (R) ≥19.1d - 19.7d (varies)
Fast Speed Meets (≥100 KB/s) 94.7 Mbit/s (R) ≥800.0 Kbit/s (guarantee) OR top 7/8
HSDir WFU Meets 98.9% (DA) ≥98.0%
Time Known Below 5.4 days (DA) ≥1.0d (most) / 9.9d (max)

(DA) = Dir. Auth. Measured | (R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-01-10 04:46:16).

Last fetch was at Sat, 10 Jan 2026 04:47:26 GMT.

Nickname
datashield
Fingerprint
6AA7D81FCB70A7B348FDCAC8F2B2526279D731B7
AROI (?)
none
Contact
none
IPv4 Exit Policy Summary 
reject: 
  1-65535
IPv6 Exit Policy Summary 
none
Exit Policy 
reject *:*
Effective Family Member: 1 
6AA7D81FCB70A7B348FDCAC8F2B2526279D731B7
Alleged Family Members: 0 
none
Indirect Family Members: 0 
none
Bandwidth Capacity (Observed | Advertised | Rate Limit | Burst Limit)
94.67 Mbit/s | 94.67 Mbit/s| 754.97 Mbit/s| 838.86 Mbit/s  Measured
Network Participation (Consensus Weight | Guard | Middle | Exit)
0.01% | N/A | 0.03% | N/A
OR Address
vm828.ipp-vps.net | 185.248.141.202:9001, [2a0a:51c1:a:1df::1]:9001
Exit Address
none
Dir Address
none
Country
Germany Germany
Interactive Map
View on Interactive Map
Autonomous System (AS Number | AS Name)
AS48314 | Michael Sebastian Schinzel trading as IP-Projects GmbH & Co. KG (BGP.tools)
Flags: 3
Fast Fast Running Running Valid Valid
Flag Uptime (1M/6M/1Y/5Y)
74.3%/—/—/—
Uptime (1M/6M/1Y/5Y)
100.0%/0.0%/0.0%/0.0%
Uptime / Downtime
UP 3d 9h 28m ago
Seen (First | Last)
6d 5h 54m ago (2026-01-03 23:00:00) | 1h 54m 48s ago (2026-01-10 03:00:00)
Last Restarted
3d 9h 35m ago (2026-01-06 19:19:16)
Last Changed Address or Port
2026-01-06 20:00:00
Hibernating
No
Platform (Short | Long)
Linux | Tor 0.4.8.21 on Linux
Version (Running | Recommended | Status)
0.4.8.21 | Yes | recommended

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-01-10 04:46:16).

  • Consensus Status (need ≥5/9): In Consensus — 9/9 authorities voted.
  • Flag Eligibility (need ≥5/9 for flag): Guard: 0/9 | Stable: 1/9 | Fast: 9/9 | HSDir: 8/9 | Running: 9/9 | Valid: 9/9 | V2Dir: 9/9
  • Reachability: IPv4: 9/9 | IPv6: 7/7 (2 don't test)
  • Consensus Weight (Dir. Auth.): Median: 96.0 Kbit/s | Min: 80.0 Kbit/s | Max: 216.0 Kbit/s [Warning] High deviation
  • Identified Issues:
    • Guard: Time Known below threshold: Time Known 5.4 days is below 8 days requirement (2.6 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.
    • 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).
    • 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.
    • 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.

Summary: Your Relay vs Consensus

Green = meets threshold, Red = below threshold, Yellow = partial.

Metric Dir Auth Measured Dir Auth Threshold Status
In Consensus (Dir. Auth.) 9/9 authorities ≥5/9 (majority) IN CONSENSUS
Running (IPv4 Reachable) 9/9 authorities reached this relay ≥5/9 (majority) RUNNING
Valid 9/9 (Running + Valid Descriptor) ≥5/9 (majority) VALID
Consensus Weight (Dir. Auth.) 96.0 Kbit/s (median) N/A (no threshold, used for path selection) —
Guard WFU (Dir. Auth., guard-wfu) 98.9% ≥98% (all authorities) MEETS
Guard TK (Dir. Auth., tk) 5.4 days ≥8 days (all authorities) BELOW - need 2.6 more days
Guard BW (Relay Reported) 94.7 Mbit/s ≥16.0 Mbit/s OR ≥80.0 Mbit/s-296.0 Mbit/s MEETS - ≥2 MB/s guarantee
Stable Uptime (Relay Reported) 3.4d ≥19.1d - 19.7d (typical) BELOW - 0/9
Stable MTBF (Dir. Auth., mtbf) 5 days ≥26.6d - 45.4d (typical)
[Stricter] moria1: ≥376.2d 		BELOW - 1/9
Fast Speed (Relay Reported) 94.7 Mbit/s ≥800.0 Kbit/s (guarantee) OR ≥816.0 Kbit/s (typical)
[Stricter] moria1: ≥8.4 Mbit/s 		MEETS - ≥100 KB/s guarantee
HSDir WFU (Dir. Auth., wfu) 98.9% ≥98.0% (from all auths) PARTIAL - 8/9
HSDir TK (Dir. Auth., tk) 5.4 days ≥1.0d (8/9 auths)
[Stricter] moria1: ≥9.9d 		PARTIAL - 8/9
IPv6 Reachable (Dir. Auth.) 7/7 tested ≥4/7 (majority) REACHABLE

Per-Authority Details

Each cell shows: your measured value | authority threshold. Green = meets, red = below. Flags: green = all authorities agree, yellow = partial.

Authority Running Valid BW Scan (Authority) v4 v6 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 Y Yes Yes Fast, Running, Valid 94.7 Mbit/s | 816.0 Kbit/s 94.7 Mbit/s | 224.0 Mbit/s OR 16.0 Mbit/s 98.9% | 98% 5.4d | 8d 3.1d | 47.0d 3.4d | 19.7d 98.9% | 98.0% 5.4d | 1.0d 2026-01-09 19:20:22 96.0 Kbit/s
dannenberg (DE) Yes Yes N Yes Yes Fast, Running, Valid 94.7 Mbit/s | 816.0 Kbit/s 94.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 98.9% | 98% 5.4d | 8d 3.1d | 35.7d 3.4d | 20.2d 98.9% | 98.0% 5.4d | 1.0d 2026-01-09 19:20:22 80.0 Kbit/s
dizum (NL) Yes Yes N Yes — Fast, Running, Valid 94.7 Mbit/s | 816.0 Kbit/s 94.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 98.9% | 98% 5.3d | 8d 3.1d | 26.6d 3.4d | 20.4d 98.9% | 98.0% 5.3d | 1.0d 2026-01-09 19:20:22 80.0 Kbit/s
faravahar (US) Yes Yes N Yes Yes Fast, Running, Valid 94.7 Mbit/s | 816.0 Kbit/s 94.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 98.9% | 98% 5.4d | 8d 3.1d | 41.9d 3.4d | 19.1d 98.9% | 98.0% 5.4d | 1.0d 2026-01-09 19:20:22 80.0 Kbit/s
gabelmoo (DE) Yes Yes Y Yes Yes Fast, Running, Valid 94.7 Mbit/s | 816.0 Kbit/s 94.7 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 98.9% | 98% 5.3d | 8d 3.1d | 45.4d 3.4d | 19.6d 98.9% | 98.0% 5.3d | 1.0d 2026-01-09 19:20:22 200.0 Kbit/s
longclaw (US) Yes Yes Y Yes — Fast, Running, Valid 94.7 Mbit/s | 816.0 Kbit/s 94.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 98.9% | 98% 5.4d | 8d 3.1d | 48.7d 3.4d | 19.5d 98.9% | 98.0% 5.4d | 1.0d 2026-01-09 19:20:22 80.0 Kbit/s
maatuska (SE) Yes Yes Y Yes Yes Fast, Running, Valid 94.7 Mbit/s | 816.0 Kbit/s 94.7 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 98.9% | 98% 5.4d | 8d 3.1d | 42.3d 3.4d | 19.4d 98.9% | 98.0% 5.4d | 1.0d 2026-01-09 19:20:22 168.0 Kbit/s
moria1 (US) Yes Yes Y Yes Yes Fast, Running, Stable, Valid 94.7 Mbit/s | 8.4 Mbit/s 94.7 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 98.7% | 98% 4.6d | 8d 8414.8d | 376.2d 3.4d | 20.4d 98.7% | 98.0% 4.6d | 9.9d 2026-01-09 19:20:22 136.0 Kbit/s
tor26 (AT) Yes Yes Y Yes Yes Fast, Running, Valid 94.7 Mbit/s | 816.0 Kbit/s 94.7 Mbit/s | 272.0 Mbit/s OR 16.0 Mbit/s 98.9% | 98% 5.4d | 8d 3.1d | 51.8d 3.4d | 19.7d 98.9% | 98.0% 5.4d | 1.0d 2026-01-09 19:20:22 216.0 Kbit/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). This is your relay's self-reported uptime from its 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.