View Relay "aRC0C7"

Fingerprint: D8F3B0A19A71FA8BACEC4B36E0A8645EEFF01E6F | Family: 1 relay | AS31898 | United States of America | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir (3)
BW Verified
0/7 BW Auths Measured 5128 bit/s Median
Stability
Overloaded | UP 2d 20h 6m ago | UP 18% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
First Seen
4y 8mo 2d ago
BW Weight
0.00% of Network | 5 Mbit/s Observed By Relay
Version
0.4.9.11 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: bandwidth below threshold : Observed bandwidth 0.6 MB/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 5.6 days is below 8 days requirement (2.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.
  • Low bandwidth authority measurements : Only 0/7 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
    Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.
  • Write Bandwidth Limit Hit : Write rate limit (25 Mbit/s) was hit 3,230 times. Relay is throttling outbound traffic.
    Suggestion: Increase RelayBandwidthRate and RelayBandwidthBurst in torrc if your connection has more upload capacity.
Notes:
  • Rate Limit Configuration: Configured limits: Rate=25 Mbit/s, Burst=9 Gbit/s. Limits hit: Write=3,230, Read=0.

Connectivity and Location

Addresses
OR Address
132.145.62.236:1234
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
United States of America United States of America
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS31898
AS Name
Oracle Corporation (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.29% consensus weight, 108 operators)

Flags and Eligibility

Current Flags (3): Running, Valid, V2Dir
Eligible Flags (3): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 4/9 | Stable: 4/9 | HSDir: 0/9 | Guard: 0/9 | Exit: 0/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) 5.1 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.5d (0/9 DA above threshold)
Min/Max: 0.2d / 5.6d (9/9 DA, Voting / Total Eligible)		 ≥10.1d - 48.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥1364.1d
Uptime Below (0/9 DA) 2.8d (R) ≥4.3d - 5.2d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (4/9 DA) 4/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 ≥10.1d - 48.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥1364.1d
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% (6/9 DA)
Min/Med/Max: 79.9% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98.0% (≥5/9 DA)
Time Known Meets (7/9 DA) Median: 5.6d (0/9 DA above threshold)
Min/Max: 0.2d / 5.6d (9/9 DA, Voting / Total Eligible)		 ≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Below (4/9 DA) 4/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 ≥10.1d - 48.4d (varies) (≥5/9 DA)
[Stricter] moria1: ≥1364.1d
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% (6/9 DA)
Min/Med/Max: 79.9% / 100.0% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 2.4 more days) Median: 5.6d (0/9 DA above threshold)
Min/Max: 0.2d / 5.6d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 5.1 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 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-07-03 03:02:32).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
5.13 Mbit/s
Advertised Bandwidth
5.13 Mbit/s
Rate Limit
25.17 Mbit/s
Burst Limit
8.59 Gbit/s
Total Data
210 TB (5 years)
1mo: 2.0 TB | 6mo: 2.0 TB | 1y: 2.0 TB | 5y: 210 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-07-03 03:02:32

Measured By
0/7 Bandwidth Authorities
Not measured by: bastet, dannenberg, gabelmoo, longclaw, maatuska, moria1, tor26
Median Measurement
5128 bit/s
Min / Max
5128 bit/s / 5128 bit/s
Network Participation: Consensus Weight: 0.0000% of network (4th pctl) | Guard: N/A | Middle: 0.0000% (3th pctl) | Exit: N/A

Uptime and Stability

Uptime Metrics
Current Status
UP 2d 20h 6m ago
Overall Uptime (1M/6M/1Y/5Y)
18.2%/3.0%/1.2%/52.2%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (18.2%/3.0%/1.2%/52.2%)
Hibernating
No
Timestamps
First Seen
4y 8mo 2d ago (2021-11-04 00:00:00)
Last Seen
2h 11m 26s ago (2026-07-03 01:00:00)
Last Restarted
2d 20h 6m ago (2026-06-30 07:05:20)
Last Changed Address
2026-06-27 13:00:00
[Warning] OVERLOADED — Rate limits hit W:3230 R:0 (limit: 25 Mbit/s)
General Overload (from /details)
Status
Not Reported

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)
Rate Limit
25.17 Mbit/s
Burst Limit
8.59 Gbit/s
Write Limit Hit
3,230 times
Read Limit Hit
0 times
Last Reported
14 hours ago
Recommendations
  • Consider increasing RelayBandwidthRate
  • Check if ISP is throttling traffic

Operator and Family

Operator Identity

Source: AROI Validation API — 2026-07-02 19:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
none
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1 
D8F3B0A19A71FA8BACEC4B36E0A8645EEFF01E6F (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
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 Fri, 03 Jul 2026 03:11:23 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-07-03 03:02:32).

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 No — Y Yes Running, Valid, V2Dir, Fast, Stable 5.1 Mbit/s | 816.0 Kbit/s 5.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.6d | 8d 5.6d | 48.4d 2.8d | 5.1d 100.0% | 98.0% 5.6d | 1.0d 2026-07-02 13:06:29 5128 bit/s
dannenberg (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast 5.1 Mbit/s | 816.0 Kbit/s 5.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 0.2d | 8d 0.2d | 10.1d 2.8d | 5.2d 100.0% | 98.0% 0.2d | 1.0d 2026-07-02 13:06:29 5128 bit/s
dizum (NL) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 5.1 Mbit/s | 816.0 Kbit/s 5.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 99.7% | 98% 5.6d | 8d 3.5d | 25.9d 2.8d | 5.2d 99.7% | 98.0% 5.6d | 1.0d 2026-07-02 13:06:29 5128 bit/s
faravahar (US) Yes Yes No — N Yes Running, Valid, V2Dir, Fast 5.1 Mbit/s | 816.0 Kbit/s 5.1 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 79.9% | 98% 5.2d | 8d 2.2d | 28.4d 2.8d | 5.2d 79.9% | 98.0% 5.2d | 1.0d 2026-07-02 13:06:29 5128 bit/s
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, V2Dir 5.1 Mbit/s | 816.0 Kbit/s 5.1 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.4d | 8d 2.4d | 60.1d 2.8d | 4.3d 100.0% | 98.0% 2.4d | 1.0d 2026-06-29 20:07:20 5128 bit/s
longclaw (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Stable 5.1 Mbit/s | 816.0 Kbit/s 5.1 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.6d | 8d 5.6d | 57.2d 2.8d | 5.4d 100.0% | 98.0% 5.6d | 1.0d 2026-07-02 13:06:29 5128 bit/s
maatuska (SE) Yes Yes No — Y Yes Running, Valid, V2Dir, Stable 5.1 Mbit/s | 816.0 Kbit/s 5.1 Mbit/s | 304.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.6d | 8d 5.6d | 30.6d 2.8d | 5.3d 100.0% | 98.0% 5.6d | 1.0d 2026-07-02 13:06:29 5128 bit/s
moria1 (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Stable 5.1 Mbit/s | 8.4 Mbit/s 5.1 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 4.2d | 8d 5.6d | 1364.1d 2.8d | 5.4d 100.0% | 98.0% 4.2d | 9.8d 2026-07-02 13:06:29 5128 bit/s
tor26 (AT) Yes Yes No — Y Yes Running, Valid, V2Dir 5.1 Mbit/s | 816.0 Kbit/s 5.1 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 99.5% | 98% 5.6d | 8d 3.5d | 53.1d 2.8d | 5.4d 99.5% | 98.0% 5.6d | 1.0d 2026-07-02 13:06:29 5128 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.