View Relay "SaruTorIruka"

Fingerprint: `BBC61AD2E18AFE70E9BE426D0B22A98252000FBB` | Operator: tor.saru.moe v2 (4 relays) ✓ Validated | Family: 4 relays | DannyAAM DannyAAMtw... | AS14061 | Singapore | Linux

Health Status

Consensus: In Consensus (9/9 Directory Auths)
Flags: Running, Valid (2)
BW Verified: 5/7 BW Auths Measured 648 Kbit/s Median
Stability: Not Overloaded | UP 2d 21h 45m ago | UP 85% (1M)

Reachability: IPv4: 9/9 | v6: 8/8(Directory Auths)
First Seen: 11y 1mo 3h ago
BW Weight: 0.00% of Network | 7 Mbit/s Observed By Relay
Version: 0.4.9.8 Not Recommended

Issues Detected:

Guard: requires Fast flag : Guard flag requires having the Fast flag first
Suggestion: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports.
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 : 0/9 authorities credit this relay with enough bandwidth for Guard (5 needed): at least 16.8 Mbit/s (AuthDirGuardBWGuarantee) or a place in their top 25% (80.0 Mbit/s – 272.0 Mbit/s). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 648.0 Kbit/s – 2.6 Mbit/s. dizum, faravahar, longclaw and maatuska used the relay-reported 4.2 Mbit/s.
Suggestion: Guard requires a bandwidth of at least AuthDirGuardBWGuarantee (16.8 Mbit/s by default) or one in the top 25% of relays, judged by each authority the same way as for Fast. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx.
Guard: WFU below threshold : 0/9 authorities meet guard-wfu (≥98%; dizum: ≥97.84099999999999%; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska, moria1 and tor26 measured 90.7%–93.5%.
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 : 1/9 authorities meet Stable (uptime or MTBF at or above their own median; 5 needed). bastet, dannenberg, dizum, faravahar, gabelmoo, longclaw, maatuska and tor26 do not.
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: Fast requires a bandwidth in the top 7/8 of relays or at least AuthDirFastGuarantee (816.0 Kbit/s by default), judged by each authority. Authorities that have a bandwidth-scanner measurement of your relay judge by it, not by the bandwidth your relay reports.
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: requires V2Dir (tunnelled-dir-server) : HSDir requires the relay to support tunnelled directory requests (V2Dir flag). This relay is missing V2Dir — the descriptor likely does not include tunnelled-dir-server, usually because DirCache 0 is set in torrc.
Suggestion: Remove DirCache 0 from torrc (DirCache is enabled by default in Tor ≥0.3.3). Restart Tor and verify the descriptor includes tunnelled-dir-server. You can check with: grep tunnelled-dir-server /var/lib/tor/cached-descriptors
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.8 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.

Connectivity and Location

Addresses

OR Address: iruka.saru.moe
128.199.131.168:9001
[2400:6180:0:d0::1a6:f001]:9001

Reachability (Directory Authorities)

IPv4: 9/9
IPv6: 8/8 (1 don't test)

Location

Country: Singapore
Interactive Map: View in RouteFluxMap

Autonomous System

AS Number: AS14061
AS Name: DigitalOcean, LLC (BGP.tools)
AS Rarity: Rare (score: 2/5, 0.12% consensus weight, 43 operators)

Flags and Eligibility

Current Flags (2): Running, Valid

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
Running	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	Below (0/9 DA)	No DirPort, no tunnelled-dir-server (R)	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Fast	Speed	Partial (5/9 DA)	648.0 Kbit/s – 2.6 Mbit/s (5 DA measured) 4.2 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 (1/9 DA)	Median: 3.0d (1/9 DA above threshold) Min/Max: 1.8d / 15528.2d (9/9 DA, Voting / Total Eligible)	≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d
Stable	Uptime	Below (0/9 DA)	2.9d (R)	≥5.2d - 5.3d (varies) (≥5/9 DA)
HSDir	Prereq: Fast	Meets (5/9 DA)	5/9 DA assigned Fast 648.0 Kbit/s – 2.6 Mbit/s (5 DA measured) 4.2 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	Below (1/9 DA)	1/9 DA assigned Stable	≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d
	Prereq: V2Dir	Below (0/9 DA)	0/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	Uptime	Below (0/9 DA)	2.9d (R)	≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known
Guard	Prereq: Fast	Meets (5/9 DA)	5/9 DA assigned Fast 648.0 Kbit/s – 2.6 Mbit/s (5 DA measured) 4.2 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	Below (1/9 DA)	1/9 DA assigned Stable	≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d
	Prereq: V2Dir	Below (0/9 DA)	0/9 DA assigned V2Dir	Tunnelled directory via ORPort or DirPort (≥5/9 DA)
	WFU	Below (0/9 DA)	Median: 92.9% (0/9 DA above threshold) Min/Max: 90.7% / 93.5% (9/9 DA, Voting / Total Eligible)	≥98%; dizum: ≥97.84099999999999% (≥5/9 DA)
	Time Known	Meets (9/9 DA)	Median: 13.1d (9/9 DA above threshold) Min/Max: 9.8d / 13.6d (9/9 DA, Voting / Total Eligible)	≥8 days (≥5/9 DA)
	Bandwidth	Below (0/9 DA)	648.0 Kbit/s – 2.6 Mbit/s (5 DA measured) 4.2 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 12:45:10).

Bandwidth Metrics

Capacity (Relay Reported)

Observed Bandwidth: 7.54 Mbit/s
Advertised Bandwidth: 4.19 Mbit/s
Rate Limit: 4.19 Mbit/s
Burst Limit: 41.94 Mbit/s
Total Data: 11 TB (5 years)
1mo: 461 GB | 6mo: 1.8 TB | 1y: 2.5 TB | 5y: 11 TB

Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-04 12:45:10

Measured By: 5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight: 648.0 Kbit/s (median of 5 measurements)
Measured Min / Max: 648.0 Kbit/s / 2.6 Mbit/s
Deviation: 2.0 Mbit/s [Warning] High variation

Network Participation: Consensus Weight: 0.0000% of network (4th pctl) | Guard: N/A | Middle: 0.0001% (5th pctl) | Exit: N/A

History

Throughput and write/read, last 6 months

Uptime and Stability

Uptime Metrics

Current Status: UP 2d 21h 45m ago
Overall Uptime (1M/6M/1Y/5Y): 85.1%/93.2%/96.5%/90.1%
Flag Uptime (1M/6M/1Y/5Y): Matches Overall Uptime (85.1%/93.2%/96.5%/90.1%)
Hibernating: No

Timestamps

First Seen: 11y 1mo 3h ago (2015-10-08 10:00:00)
Last Seen: 2h 45m 39s ago (2026-11-04 11:00:00)
Last Restarted: 2d 21h 45m ago (2026-11-01 15:59:59)
Last Changed Address: 2026-04-06 23:00:00

Overload Status: Not Overloaded — No overload conditions reported.

Evaluated 2026-11-04 13:45 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 42s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 6h ago).

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: No rate-limit report in available data
Rate Limit: —
Burst Limit: —
Write counter: —
Read counter: —

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 and Family

Operator Identity

Source: AROI Validation API — 2026-11-04 04:00 UTC

AROI Domain (?): tor.saru.moe
Operator Validation: Validated (4/4 relays)
This Relay: Validated (dns-rsa)
Contact: DannyAAM DannyAAMtw email:tor[]saru.moe pgp:EA96C1332576439D68CEB0AA60E0EA4B53ACB4E9 url:tor.saru.moe keybase:dannyaamtw twitter:DannyAAMtw donationurl:https://tor.saru.moe/donate.html proof:dns-rsa ciissversion:2

Family Configuration

Family Support: MyFamily Only (4) — Legacy only. Consider migrating to Happy Families. | View Full Family (4)

Happy Families (family-cert)

Effective Members: 0: none

MyFamily (legacy declarations)

Effective Members: 4

2A0AC8016D9A0297BE4CCA1C575DFCEC9866E681
56C5F16D06C8EBA6DFA5C139EFA82BDA6174FA4F
7040C1F5728746C5FB5E12845101A26EE8636D7E
BBC61AD2E18AFE70E9BE426D0B22A98252000FBB (this relay)

Alleged Members: 0

none

Indirect Members: 0

none

Software and Version

Platform: Linux — Tor 0.4.9.8 on Linux
Version: 0.4.9.8 — Not Recommended
Version Status: Obsolete — Update urgently. See torproject.org/download

Exit Health & Policy

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 13:45:39 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-11-04 12:45:10).

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 (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, Fast	2.6 Mbit/s (M) \| 816.0 Kbit/s	2.6 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	92.1% \| 98%	12.4d \| 8d	2.5d \| 8.4d	2.9d \| 5.2d	2026-11-03 22:01:23	2.6 Mbit/s (M)
dannenberg (DE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid	648.0 Kbit/s (M) \| 816.0 Kbit/s	648.0 Kbit/s (M) \| 272.0 Mbit/s OR 16.8 Mbit/s	92.9% \| 98%	13.3d \| 8d	2.5d \| 9.3d	2.9d \| 5.3d	2026-11-03 22:01:23	648.0 Kbit/s (M)
dizum (NL)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, Fast	4.2 Mbit/s (R) \| 816.0 Kbit/s	4.2 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	90.7% \| 98%	12.2d \| 8d	2.5d \| 6.7d	2.9d \| 5.3d	2026-11-03 22:01:23	4.2 Mbit/s (R)
faravahar (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, Fast	4.2 Mbit/s (R) \| 816.0 Kbit/s	4.2 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	93.2% \| 98%	13.6d \| 8d	3.1d \| 6.5d	2.9d \| 5.3d	2026-11-03 22:01:23	4.2 Mbit/s (R)
gabelmoo (DE)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid	648.0 Kbit/s (M) \| 816.0 Kbit/s	648.0 Kbit/s (M) \| 248.0 Mbit/s OR 16.8 Mbit/s	93.5% \| 98%	13.1d \| 8d	3.6d \| 10.8d	2.9d \| 5.3d	2026-11-03 22:01:23	648.0 Kbit/s (M)
longclaw (US)	Yes	Yes	No	—	Y	Yes	N/T	Running, Valid, Fast	4.2 Mbit/s (R) \| 816.0 Kbit/s	4.2 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	93.0% \| 98%	13.2d \| 8d	3.0d \| 10.9d	2.9d \| 5.3d	2026-11-03 22:01:23	4.2 Mbit/s (R)
maatuska (SE)	Yes	Yes	No	—	N	Yes	Yes	Running, Valid, Fast	4.2 Mbit/s (R) \| 816.0 Kbit/s	4.2 Mbit/s (R) \| 80.0 Mbit/s OR 16.8 Mbit/s	92.4% \| 98%	12.8d \| 8d	1.8d \| 2.4d	2.9d \| 5.3d	2026-11-03 22:01:23	4.2 Mbit/s (R)
moria1 (US)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid, Stable	1.8 Mbit/s (M) \| 8.4 Mbit/s	1.8 Mbit/s (M) \| 192.0 Mbit/s OR 16.8 Mbit/s	91.0% \| 98%	9.8d \| 8d	15528.2d \| 7607.5d	2.9d \| 5.3d	2026-11-03 22:01:23	1.8 Mbit/s (M)
tor26 (AT)	Yes	Yes	No	—	Y	Yes	Yes	Running, Valid	648.0 Kbit/s (M) \| 816.0 Kbit/s	648.0 Kbit/s (M) \| 256.0 Mbit/s OR 16.8 Mbit/s	92.9% \| 98%	13.3d \| 8d	3.1d \| 10.6d	2.9d \| 5.3d	2026-11-03 22:01:23	648.0 Kbit/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.

View Relay "SaruTorIruka"

Fingerprint: BBC61AD2E18AFE70E9BE426D0B22A98252000FBB | Operator: tor.saru.moe v2 (4 relays) ✓ Validated | Family: 4 relays | DannyAAM DannyAAMtw... | AS14061 | Singapore | Linux

Addresses

Reachability (Directory Authorities)

Location

Autonomous System

Eligibility Flag Vote Details

Capacity (Relay Reported)

Measurement (Directory Authority Verified)

History

Uptime Metrics

Timestamps

General Overload (from /details)

File Descriptor Exhaustion (from /bandwidth)

Rate Limits (from /bandwidth)

History

Operator Identity

Family Configuration

Full Exit Policy

Fingerprint: `BBC61AD2E18AFE70E9BE426D0B22A98252000FBB` | Operator: tor.saru.moe v2 (4 relays) ✓ Validated | Family: 4 relays | DannyAAM DannyAAMtw... | AS14061 | Singapore | Linux