View Relay "smurfixNSC"

Fingerprint: B51FAC83BD8CEE69933D9ECA07CAC6A8FF990754 | Family: 1 relay | 4096R/25B4C293 Matthias Urlichs... | AS12337 | Germany | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast, Exit (5)
DNS Health
Healthy (14.6s, 11th percentile) (via exitdnshealth.1aeo.com)
BW Verified
4/6 BW Auths Measured 816 bit/s Median
Stability
Not Overloaded | UP 6h 58m 11s ago
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
2d 4h 3m ago
BW Weight
0.00% of Network | 2 Mbit/s Observed By Relay
Version
0.4.9.11 Recommended
Issues Detected:
  • 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: bandwidth below threshold : Observed bandwidth 3 Mbit/s is below 2 MB/s minimum (AuthDirGuardBWGuarantee)
    Suggestion: Guard requires ≥2 MB/s bandwidth OR being in top 25% of network. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx or ARM.
  • Guard: Time Known below threshold : Time Known 2.2 days is below 8 days requirement (5.8 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.
  • 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 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.

Connectivity and Location

Addresses
OR Address
213.95.55.63:9001
Exit Address
213.95.55.63
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS12337
AS Name
noris network AG (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 2 operators)

Flags and Eligibility

Current Flags (5): Running, Valid, V2Dir, Fast, Exit
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 5/9 | Stable: 0/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 9/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) 2.7 Mbit/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 (0/9 DA) Median: 2.2d (0/9 DA above threshold)
Min/Max: 2.0d / 2.2d (9/9 DA, Voting / Total Eligible)		 ≥7.8d - 13.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7051.8d
Uptime Below (0/9 DA) 0.3d (R) ≥9.7d - 10.2d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (5/9 DA) 5/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 (0/9 DA) 0/9 DA assigned Stable ≥7.8d - 13.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7051.8d
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) Majority: 100.0% (9/9 DA) ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 2.2d (0/9 DA above threshold)
Min/Max: 1.9d / 2.2d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Meets (5/9 DA) 5/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 (0/9 DA) 0/9 DA assigned Stable ≥7.8d - 13.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7051.8d
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) Majority: 100.0% (9/9 DA) ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 5.8 more days) Median: 2.2d (0/9 DA above threshold)
Min/Max: 1.9d / 2.2d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 2.7 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-320.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-08-24 00:01:31).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
2.70 Mbit/s
Advertised Bandwidth
819.20 Kbit/s
Rate Limit
819.20 Kbit/s
Burst Limit
1.64 Mbit/s
Total Data
1.3 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-08-24 00:01:31

Measured By
4/6 Bandwidth Authorities
Not measured by: faravahar, longclaw
Median Measurement
816 bit/s
Min / Max
24 bit/s / 816 bit/s
Deviation
792 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (2th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0000% (1th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 6h 58m 11s ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
2d 4h 3m ago (2026-08-21 20:00:00)
Last Seen
3h 3m 15s ago (2026-08-23 21:00:00)
Last Restarted
6h 58m 11s ago (2026-08-23 17:05:04)
Last Changed Address
2026-08-21 20:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-08-23 16:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
4096R/25B4C293 Matthias Urlichs <matthias@urlichs.de>
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
B51FAC83BD8CEE69933D9ECA07CAC6A8FF990754 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Software and Version

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

Exit Health & Policy

DNS Health
Status
Healthy (avg. 14.6s, 11th percentile)
Query Domain
80847d46c8aa425e8775780b25a44e47.b51fac83.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
4/4 instances succeeded
First Hop
TheSwissNode (CH) 1EBAAB56426723D5F25B296A651436568810CF91
Exit Address Used
213.95.55.63
Per-Instance Results
Cross Validation Attempt 1: Success, 16.3s (cv1_w3)
Cross Validation Attempt 2: Success, 12.9s (cv2_w3)
Cross Validation Attempt 3: Success, 11.0s (cv3_w3)
Cross Validation Attempt 4: Success, 18.0s (cv4_w3)
Tested: 2026-08-23 07:13:07 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
reject: 
  25
  119
  135-139
  194
  445
  465
  563
  587
  994
  1214
  4661-4666
  6346-6429
  6657
  6660-6670
  6697
  6699
  6881-7005
  7070
  8000-8004
  8008
  8080
  9000-9001
  9998-9999
IPv6 Exit Policy Summary
None
Full 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 213.95.55.63:*
reject *:25
reject *:194
reject *:465
reject *:587
reject *:994
reject *:6657
reject *:6660-6670
reject *:6697
reject *:7000-7005
reject *:7070
reject *:8000-8004
reject *:8008
reject *:8080
reject *:9000
reject *:9001
reject *:9998
reject *:9999
reject *:119
reject *:135-139
reject *:445
reject *:563
reject *:1214
reject *:4661-4666
reject *:6346-6429
reject *:6699
reject *:6881-6999
accept *:*

Last fetch was at Mon, 24 Aug 2026 00:03:03 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-08-24 00:01:31).

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 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 Yes — N Yes Running, Valid, V2Dir, Fast, Exit 2.7 Mbit/s | 816.0 Kbit/s 2.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.2d | 11.2d 0.3d | 9.7d 100.0% | 98.0% 2.2d | 1.0d 2026-08-23 17:06:06 816 bit/s
dannenberg (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 2.7 Mbit/s | 816.0 Kbit/s 2.7 Mbit/s | 320.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.2d | 13.4d 0.3d | 11.7d 100.0% | 98.0% 2.2d | 1.0d 2026-08-23 17:06:06 24 bit/s
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 2.7 Mbit/s | 816.0 Kbit/s 2.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.0d | 8d 2.0d | 12.8d 0.3d | 10.0d 100.0% | 98.0% 2.0d | 1.0d 2026-08-23 17:06:06 816 bit/s
faravahar (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 2.7 Mbit/s | 816.0 Kbit/s 2.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.2d | 12.7d 0.3d | 10.2d 100.0% | 98.0% 2.2d | 1.0d 2026-08-23 17:06:06 816 bit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 2.7 Mbit/s | 816.0 Kbit/s 2.7 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.2d | 13.7d 0.3d | 10.2d 100.0% | 98.0% 2.2d | 1.0d 2026-08-23 17:06:06 24 bit/s
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 2.7 Mbit/s | 816.0 Kbit/s 2.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.2d | 17.1d 0.3d | 10.2d 100.0% | 98.0% 2.2d | 1.0d 2026-08-23 17:06:06 816 bit/s
maatuska (SE) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 2.7 Mbit/s | 816.0 Kbit/s 2.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.2d | 7.8d 0.3d | 10.1d 100.0% | 98.0% 2.2d | 1.0d 2026-08-23 17:06:06 816 bit/s
moria1 (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 2.7 Mbit/s | 8.4 Mbit/s 2.7 Mbit/s | 208.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 1.9d | 8d 2.2d | 7051.8d 0.3d | 9.7d 100.0% | 98.0% 1.9d | 9.8d 2026-08-23 17:06:06 72 bit/s
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Exit 2.7 Mbit/s | 816.0 Kbit/s 2.7 Mbit/s | 280.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.2d | 8d 2.2d | 13.5d 0.3d | 10.6d 100.0% | 98.0% 2.2d | 1.0d 2026-08-23 17:06:06 24 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.