View Relay "poppers"

Fingerprint: CB8A6A9076665C12340431A105EAB69CA2042C1F | Family: 1 relay | contact info is ardbarkardvark @proton.me | AS45731 | Indonesia | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast, Exit (5)
DNS Health
Healthy (16.2s, 35th percentile) (via exitdnshealth.1aeo.com)
BW Verified
4/6 BW Auths Measured 47 Kbit/s Median
Stability
Overloaded | UP 6d 16h 56m ago | UP 99% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
6d 16h 2m ago
BW Weight
0.00% of Network | 47 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: Time Known below threshold : Time Known 6.6 days is below 8 days requirement (1.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 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.
  • General Overload Active : Relay reported general overload at 2026-09-01 05:00 UTC. This indicates OOM killer invocation, onionskin queue saturation, or TCP port exhaustion.
    Suggestion: Check CPU/memory with htop. Review logs for "out of memory" or "onionskins" warnings. Consider increasing MaxMemInQueues in torrc. Verify TCP ports available.

Connectivity and Location

Addresses
OR Address
113.20.28.236:443
Exit Address
113.20.28.236
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Indonesia Indonesia
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS45731
AS Name
ARDH GLOBAL INDONESIA, PT (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 4 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: 8/9 | Stable: 4/9 | HSDir: 3/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) 47.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: 3.2d (0/9 DA above threshold)
Min/Max: 0.0d / 6.6d (9/9 DA, Voting / Total Eligible)		 ≥11.9d - 15.6d (varies) (≥5/9 DA)
[Stricter] moria1: ≥5986.6d
Uptime Partial (5/9 DA) 6.7d (R) ≥6.3d - 6.5d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (8/9 DA) 8/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 (4/9 DA) 4/9 DA assigned Stable ≥11.9d - 15.6d (varies) (≥5/9 DA)
[Stricter] moria1: ≥5986.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) Median: 99.3% (8/9 DA above threshold)
Min/Max: 0.0% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 6.1d (0/9 DA above threshold)
Min/Max: 0.0d / 6.6d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
Guard Prereq: Fast Meets (8/9 DA) 8/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 (4/9 DA) 4/9 DA assigned Stable ≥11.9d - 15.6d (varies) (≥5/9 DA)
[Stricter] moria1: ≥5986.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) Median: 99.3% (8/9 DA above threshold)
Min/Max: 0.0% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 1.9 more days) Median: 6.1d (0/9 DA above threshold)
Min/Max: 0.0d / 6.6d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 47.7 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.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-09-02 06:00:25).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
47.72 Mbit/s
Advertised Bandwidth
47.72 Mbit/s
Rate Limit
8.59 Gbit/s
Burst Limit
8.59 Gbit/s
Total Data
951 GB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-09-02 06:00:25

Measured By
4/6 Bandwidth Authorities
Not measured by: faravahar, longclaw
Median Measurement
47.7 Kbit/s
Min / Max
8 bit/s / 47.7 Kbit/s
Deviation
47.7 Kbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0007% of network (21th pctl) | Guard: N/A | Middle: N/A | Exit: 0.0021% (5th pctl)

Uptime and Stability

Uptime Metrics
Current Status
UP 6d 16h 56m ago
Overall Uptime (1M/6M/1Y/5Y)
99.4%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (99.4%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
6d 16h 2m ago (2026-08-26 15:00:00)
Last Seen
2h 2m 54s ago (2026-09-02 05:00:00)
Last Restarted
6d 16h 56m ago (2026-08-26 14:06:16)
Last Changed Address
2026-08-26 15:00:00
[Warning] OVERLOADED — General overload at 2026-09-01 05:00 UTC
General Overload (from /details)
Status
Reported
When
2026-09-01 05:00 UTC (1 days ago)

OOM killer, onionskin queue saturation, or TCP port exhaustion. Flag remains 72h after last event (Tor spec 328).

File Descriptor Exhaustion (from /bandwidth)
Status
Not Reported
Rate Limits (from /bandwidth)

No rate limit data from /bandwidth endpoint.

Recommendations
  • Check CPU/memory: htop
  • Review MaxMemInQueues in torrc

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-09-01 22:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
contact info is ardbarkardvark @proton.me
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
CB8A6A9076665C12340431A105EAB69CA2042C1F (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. 16.2s, 35th percentile)
Query Domain
d780dc80b7994decbbafde95dec6525e.cb8a6a90.tor.exit.validator.1aeo.com
DNS Result
Resolved to 64.65.4.1
Cross-Validation
4/4 instances succeeded
First Hop
corae (US) 99093AA9168907829FF63C1F619C51107DC137A4
Exit Address Used
113.20.28.236
Per-Instance Results
Cross Validation Attempt 1: Success, 18.7s (cv1_w4)
Cross Validation Attempt 2: Success, 10.1s (cv2_w4)
Cross Validation Attempt 3: Success, 17.2s (cv3_w4)
Cross Validation Attempt 4: Success, 18.7s (cv4_w4)
Tested: 2026-09-01 19:21:57 UTC
Source: exitdnshealth.1aeo.com
IPv4 Exit Policy Summary
reject: 
  25
  465
  587
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 113.20.28.236:*
reject *:25
reject *:465
reject *:587
accept *:*

Last fetch was at Wed, 02 Sep 2026 07:02:37 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-09-02 06:00:25).

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, Stable, HSDir, Exit 47.7 Mbit/s | 816.0 Kbit/s 47.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 6.6d | 8d 6.6d | 14.0d 6.7d | 6.4d 100.0% | 98.0% 6.6d | 1.0d 2026-09-01 21:18:30 47.7 Kbit/s
dannenberg (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Stable, Exit 47.7 Mbit/s | 816.0 Kbit/s 47.7 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 6.6d | 8d 6.6d | 15.6d 6.7d | 9.9d 100.0% | 98.0% 6.6d | 1.0d 2026-09-01 21:18:30 8 bit/s
dizum (NL) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Exit 47.7 Mbit/s | 816.0 Kbit/s 47.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.3% | 98% 6.1d | 8d 3.2d | 14.2d 6.7d | 6.9d 99.3% | 98.0% 6.1d | 1.0d 2026-09-01 21:18:30 47.7 Kbit/s
faravahar (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 47.7 Mbit/s | 816.0 Kbit/s 47.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.3% | 98% 6.1d | 8d 3.2d | 15.6d 6.7d | 6.5d 99.3% | 98.0% 6.1d | 1.0d 2026-09-01 21:18:30 47.7 Kbit/s
gabelmoo (DE) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 47.7 Mbit/s | 816.0 Kbit/s 47.7 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 99.3% | 98% 6.1d | 8d 3.2d | 15.7d 6.7d | 6.3d 99.3% | 98.0% 6.1d | 1.0d 2026-09-01 21:18:30 11.2 Kbit/s
longclaw (US) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Exit 47.7 Mbit/s | 816.0 Kbit/s 47.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.3% | 98% 5.8d | 8d 3.1d | 17.6d 6.7d | 6.3d 99.3% | 98.0% 5.8d | 1.0d 2026-09-01 21:18:30 47.7 Kbit/s
maatuska (SE) Yes Yes Yes — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 47.7 Mbit/s | 816.0 Kbit/s 47.7 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 6.6d | 8d 6.6d | 11.9d 6.7d | 6.8d 100.0% | 98.0% 6.6d | 1.0d 2026-09-01 21:18:30 47.7 Kbit/s
moria1 (US) Yes Yes Yes — Y Yes Valid, V2Dir, Fast, Exit 47.7 Mbit/s | 8.4 Mbit/s 47.7 Mbit/s | 200.0 Mbit/s OR 16.0 Mbit/s 0.0% | 98% 0.0d | 8d 0.0d | 5986.6d 6.7d | 6.5d 0.0% | 98.0% 0.0d | 9.9d 2026-09-01 21:18:30 20.8 Kbit/s
tor26 (AT) Yes Yes Yes — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Exit 47.7 Mbit/s | 816.0 Kbit/s 47.7 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 6.6d | 8d 6.6d | 15.6d 6.7d | 6.9d 100.0% | 98.0% 6.6d | 1.0d 2026-09-01 21:18:30 18.4 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). 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.