View Relay "StormyCloud"

Fingerprint: C9AC72CFB57563C608B3C978C3D9BBB0D8069564 | Operator: stormycloud.org v3 (30 relays) ✓ Validated | Family: 30 relays | email:admin[]stormycloud.org... | AS400226 | United States of America | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Exit (4)
DNS Health
Not Tested (via exitdnshealth.1aeo.com)
BW Verified
5/7 BW Auths Measured 8 bit/s Median
Stability
Not Overloaded | UP 16h 20m ago
Reachability
IPv4: 9/9 | v6: 7/7 (Directory Auths)
First Seen
15h 15m 40s ago
BW Weight
0.00% of Network | 0 Kbit/s Observed By Relay
Version
0.4.9.8 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: Time Known below threshold : Time Known 0.6 days is below 8 days requirement (7.4 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 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: Time Known below threshold : Time Known 14.9 hours below 25 hours (dir-spec default)
    Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably.
  • 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
tor-exit007.stormycloud.org
23.128.248.166:9001
[2602:fc05::166]:9001
Exit Address
23.128.248.166
Reachability (Directory Authorities)
IPv4
9/9
IPv6
7/7 (2 don't test)
Location
Country
United States of America United States of America
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS400226
AS Name
StormyCloud Inc (BGP.tools)
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Flags and Eligibility

Current Flags (4): Running, Valid, V2Dir, Exit
Eligible Flags (4): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 0/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
IPv6 Reachability Meets (7/7 DA) 7/7 tested authorities reached relay ≥4/7 tested (majority) (≥4/7 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 Below (0/9 DA) 0 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 (0/9 DA) Median: 0.6d (0/9 DA above threshold)
Min/Max: 0.0d / 0.6d (9/9 DA, Voting / Total Eligible)		 ≥31.5d - 54.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥286.6d
Uptime Below (0/9 DA) 0.7d (R) ≥9.9d - 9.9d (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 (0/9 DA) 0/9 DA assigned Stable ≥31.5d - 54.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥286.6d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Majority: 100.0% (8/9 DA)
Min/Med/Max: 0.0% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Below (0/9 DA) Median: 0.6d (0/9 DA above threshold)
Min/Max: 0.0d / 0.6d (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 (0/9 DA) 0/9 DA assigned Stable ≥31.5d - 54.7d (varies) (≥5/9 DA)
[Stricter] moria1: ≥286.6d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Meets (8/9 DA) Majority: 100.0% (8/9 DA)
Min/Med/Max: 0.0% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 7.4 more days) Median: 0.6d (0/9 DA above threshold)
Min/Max: 0.0d / 0.6d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 0 bit/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-06-17 09:45:07).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
0.00 Kbit/s
Advertised Bandwidth
Unknown
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
N/A
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-06-17 09:45:07

Measured By
5/7 Bandwidth Authorities
Not measured by: bastet, dannenberg
Median Measurement
8 bit/s
Min / Max
0 bit/s / 8 bit/s
Deviation
8 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (0th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0000% (0th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 16h 20m 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
15h 15m 40s ago (2026-06-16 19:00:00)
Last Seen
1h 15m 40s ago (2026-06-17 09:00:00)
Last Restarted
16h 20m ago (2026-06-16 17:55:40)
Last Changed Address
2026-06-16 19:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-06-17 02:00 UTC

AROI Domain (?)
stormycloud.org
Operator Validation
Validated (23/30 relays)
This Relay
Validated (uri-familyid-ed25519)
Contact
email:admin[]stormycloud.org url:https://stormycloud.org proof:uri-familyid-ed25519 ciissversion:3 abuse:abuse[]stormycloud.org trafficacct:unmetered memory:3072 virtualization:kvm btc:1NDRuQNyJZmYK4AJwve1aqa56ntuXpbyA7 donationurl:https://www.stormycloud.org/donate/ offlinemasterkey:y os:ubuntu/24.04 tls:openssl aesni:y autoupdate:y confmgmt:ansible dnslocation:sameas dnsqname:y dnssec:y dnslocalrootzone:n
Family Configuration
Family Support
Happy Families (30) — Has family-cert in server descriptor (guide) | View Full Family (30)
Happy Families (family-cert)
Effective Members: 30 
0B34499721261A055AC5153D63F6E312FC5665F2
24A14EA0890FE2A6A756D4DE68E6E5589ACE0255
2641A87C24F3DEAEB838B79DB0E2D73C425DA220
2F27B582853D60762EBE2C46C8B79709A346B044
3188F8B1296C37D908327B4669F798C80BAB39F2
3877B02338ADF1093F58E2DBAA6AEE29D92DE4BA
3A9A1626A3CDB06987FF5EA2FFF99309196F8589
409003B7855CAEB106867DD054C43EB48120A437
433922460A858A7A162112D25FF5ECA0DFE27696
478D1C22F031669A6FC0886481524ADEC491F5C5
4E8A38AA1D299773B0CE654C310D4B052DFE662B
56D90119C2069B1E1B9B02889289F909D5CAE1C4
61E6BFC3FE5EC6C0C48728863474FD0380DA1C2B
634B891DAF74FB17C94C4AA73CB394CE6B2531F1
68BD148FCFFE338CFA457D578F6ABBAD1A7C6A17
766A620BD623D7615BD30A1B33CF671D6703D7A4
79F2C56247215967B728560171B404FFA7F49D69
7BB0F15CF3A28A22A3B5C0ED671F5065D0513490
801E7435B320CE81B43B9F91216BDD6381F30202
8B2A5D3943B4A29C91EC1DE9F0E21C03C29286E7
AA8E0324E0D91403737E86F51626FC370D041672
AC9E222B0DD1E9254435CB833EBBA34BF2D1D003
B189913DBA8AC0B7085BB86B229B92BA5753A7C6
B6940EE982D449B2B75E15C2AC5FFE8768DC5C49
B9BF430E8679A8AFDE1248723F197C6C2AD76F3F
C9AC72CFB57563C608B3C978C3D9BBB0D8069564 (this relay)
CC442B08E798DA97CD595DDDC18AC355070E65A8
DC98C3DFCDAC1931050DBBB88DA628809A6626FD
E935CF0228548CA34DF36262AC3800977E26A36C
F96F5DF0245D3B717B89CB5797E72A6EE2FAB3C2
MyFamily (legacy declarations) — none

Software and Version

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

Exit Health & Policy

DNS Health
Status
Not Tested
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
accept: 
  20-22
  43
  53
  79-81
  194
  220
  389
  443
  465
  531
  543-544
  554
  563
  587
  636
  706
  853
  873
  902-904
  981
  989-995
  1194
  1220
  1293
  1500
  1533
  1677
  1723
  1755
  1863
  2082-2083
  2086-2087
  2095-2096
  2102-2104
  3128
  3690
  4321
  4643
  5050
  5190
  5222-5223
  5228
  5900
  6660-6669
  6679
  6697
  8000
  8008
  8074
  8080
  8082
  8087-8088
  8332-8333
  8443
  8888
  9418
  9999-10000
  11371
  19294
  19638
  50002
  64738
IPv6 Exit Policy Summary
accept: 
  20-22
  43
  53
  79-81
  194
  220
  389
  443
  465
  531
  543-544
  554
  563
  587
  636
  706
  853
  873
  902-904
  981
  989-995
  1194
  1220
  1293
  1500
  1533
  1677
  1723
  1755
  1863
  2082-2083
  2086-2087
  2095-2096
  2102-2104
  3128
  3690
  4321
  4643
  5050
  5190
  5222-5223
  5228
  5900
  6660-6669
  6679
  6697
  8000
  8008
  8074
  8080
  8082
  8087-8088
  8332-8333
  8443
  8888
  9418
  9999-10000
  11371
  19294
  19638
  50002
  64738
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 23.128.248.166:*
accept *:20-22
accept *:43
accept *:53
accept *:79-81
accept *:194
accept *:220
accept *:389
accept *:443
accept *:465
accept *:531
accept *:543-544
accept *:554
accept *:563
accept *:587
accept *:636
accept *:706
accept *:853
accept *:873
accept *:902-904
accept *:981
accept *:989-995
accept *:1194
accept *:1220
accept *:1293
accept *:1500
accept *:1533
accept *:1677
accept *:1723
accept *:1755
accept *:1863
accept *:2082
accept *:2083
accept *:2086-2087
accept *:2095-2096
accept *:2102-2104
accept *:3128
accept *:3690
accept *:4321
accept *:4643
accept *:5050
accept *:5190
accept *:5222-5223
accept *:5228
accept *:5900
accept *:6660-6669
accept *:6679
accept *:6697
accept *:8000
accept *:8008
accept *:8074
accept *:8080
accept *:8082
accept *:8087-8088
accept *:8332-8333
accept *:8443
accept *:8888
accept *:9418
accept *:9999
accept *:10000
accept *:11371
accept *:19294
accept *:19638
accept *:50002
accept *:64738
reject *:*

Last fetch was at Wed, 17 Jun 2026 10:15:39 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-06-17 09:45:07).

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 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 Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 256.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.6d | 8d 0.6d | 57.5d 0.7d | 11.0d 100.0% | 98.0% 0.6d | 1.0d 2026-06-16 17:56:04 —
dannenberg (DE) Yes Yes Yes — Y Yes — Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 0.0% | 98% 0.0d | 8d 0.0d | 31.5d 0.7d | 9.9d 0.0% | 98.0% 0.0d | 1.0d 2026-06-16 17:56:04 —
dizum (NL) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.6d | 8d 0.6d | 36.2d 0.7d | 9.9d 100.0% | 98.0% 0.6d | 1.0d 2026-06-16 17:56:04 —
faravahar (US) Yes Yes Yes — N Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.6d | 8d 0.6d | 53.4d 0.7d | 9.9d 100.0% | 98.0% 0.6d | 1.0d 2026-06-16 17:56:04 —
gabelmoo (DE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.6d | 8d 0.6d | 54.7d 0.7d | 9.9d 100.0% | 98.0% 0.6d | 1.0d 2026-06-16 17:56:04 8 bit/s
longclaw (US) Yes Yes Yes — Y Yes — Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 240.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.6d | 8d 0.6d | 61.5d 0.7d | 9.9d 100.0% | 98.0% 0.6d | 1.0d 2026-06-16 17:56:04 8 bit/s
maatuska (SE) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 320.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.6d | 8d 0.6d | 32.9d 0.7d | 9.9d 100.0% | 98.0% 0.6d | 1.0d 2026-06-16 17:56:04 8 bit/s
moria1 (US) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 8.4 Mbit/s 0 bit/s | 240.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.6d | 8d 0.6d | 286.6d 0.7d | 10.8d 100.0% | 98.0% 0.6d | 9.9d 2026-06-16 17:56:04 8 bit/s
tor26 (AT) Yes Yes Yes — Y Yes Yes Running, Valid, V2Dir, Exit 0 bit/s | 816.0 Kbit/s 0 bit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.6d | 8d 0.6d | 54.7d 0.7d | 9.9d 100.0% | 98.0% 0.6d | 1.0d 2026-06-16 17:56:04 8 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.