View Relay "JGWeb3Relay"

Fingerprint: 2E2BDE9DAEDDC18C536E72E396AB9C0653827D49 | Family: 1 relay | AS4764 | Australia | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
5/7 BW Auths Measured 2 Mbit/s Median
Stability
Not Overloaded | UP 1w 1d 21h ago | UP 99% (1M)
Reachability
IPv4: 9/9 (Directory Auths)
BW Weight
0.00% of Network | 18 Mbit/s Observed By Relay
Version
0.4.9.14 Recommended
Issues Detected:
  • Guard: bandwidth below threshold : 3/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 – 280.0 Mbit/s). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 2.2 Mbit/s – 11.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.
  • HSDir: uptime below 96 hours : Only 4/9 authorities voted HSDir, though this relay has Fast, Stable and V2Dir
    Suggestion: HSDir needs 96 hours of uptime as each authority sees it (MinUptimeHidServDirectoryV2): the time since your relay restarted, or since that authority last failed to reach it if that is shorter. Keep the relay running and reachable.
  • 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.

Addresses
OR Address
119-17-139-248.77118b.mel.static.aussiebb.net
119.17.139.248:9003
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Australia Australia
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS4764
AS Name
Aussie Fibre Pty Ltd (BGP.tools)
AS Rarity
Legendary (score: 4/5, <0.05% consensus weight, 7 operators)

Current Flags (5): Running, Valid, V2Dir, Fast, Stable
Eligible Flags (5): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 9/9 | HSDir: 4/9 | Guard: 3/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) 2.2 Mbit/s – 11.2 Mbit/s (5 DA measured)
18.0 Mbit/s (3 DA relay-reported)
faravahar: not published
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Stable MTBF Partial (8/9 DA) Median: 9.5d (9/9 DA above threshold)
Min/Max: 9.4d / 9881.9d (9/9 DA, Voting / Total Eligible)
≥6.2d - 8.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10253.2d
Uptime Meets (9/9 DA) 8.9d (R) ≥5.8d - 5.8d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
2.2 Mbit/s – 11.2 Mbit/s (5 DA measured)
18.0 Mbit/s (3 DA relay-reported)
faravahar: not published
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (9/9 DA) 9/9 DA assigned Stable ≥6.2d - 8.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10253.2d
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
Uptime Below (4/9 DA) 8.9d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.9d Time Known
Guard Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
2.2 Mbit/s – 11.2 Mbit/s (5 DA measured)
18.0 Mbit/s (3 DA relay-reported)
faravahar: not published
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA)
[Stricter] moria1: ≥8.4 Mbit/s
Prereq: Stable Meets (9/9 DA) 9/9 DA assigned Stable ≥6.2d - 8.9d (varies) (≥5/9 DA)
[Stricter] moria1: ≥10253.2d
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) Median: 99.7% (9/9 DA above threshold)
Min/Max: 99.4% / 99.7% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 18.2d (9/9 DA above threshold)
Min/Max: 9.8d / 18.2d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Below (3/9 DA) 2.2 Mbit/s – 11.2 Mbit/s (5 DA measured)
18.0 Mbit/s (3 DA relay-reported)
faravahar: not published
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-280.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-10-18 17:15:05).

Capacity (Relay Reported)
Observed Bandwidth
18.05 Mbit/s
Advertised Bandwidth
18.05 Mbit/s
Rate Limit
94.37 Mbit/s
Burst Limit
99.61 Mbit/s
Total Data
7.0 TB (6 months)
1mo: 4.9 TB | 6mo: 7.0 TB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-10-18 17:15:05

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight
2.7 Mbit/s (median of 5 measurements)
Measured Min / Max
2.2 Mbit/s / 11.2 Mbit/s
Deviation
9.0 Mbit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0002% of network (8th pctl) | Guard: N/A | Middle: 0.0005% (12th pctl) | Exit: N/A
History
Throughput and write/read, last 6 months Throughput and write/read, last 30 days
1M 6M

Uptime Metrics
Current Status
UP 1w 1d 21h ago
Overall Uptime (1M/6M/1Y/5Y)
99.5%/99.7%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (99.5%/99.7%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
1mo 2w 1d ago (2026-09-03 11:00:00)
Last Seen
1h 45m 39s ago (2026-10-18 16:00:00)
Last Restarted
1w 1d 21h ago (2026-10-09 20:00:28)
Last Changed Address
2026-09-03 11:00:00
Overload Status: Not Overloaded — No overload conditions reported.
History
Uptime, last 6 months Uptime, last 30 days
1M 6M

Operator Identity

Source: AROI Validation API — 2026-10-18 09: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
2E2BDE9DAEDDC18C536E72E396AB9C0653827D49 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

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

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 Sun, 18 Oct 2026 17:45:38 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-10-18 17:15:05).

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 (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 Running, Valid, V2Dir, Fast, Stable 11.2 Mbit/s (M) | 816.0 Kbit/s 11.2 Mbit/s (M) | 184.0 Mbit/s OR 16.8 Mbit/s 99.7% | 98% 18.2d | 8d 9.5d | 8.9d 8.9d | 5.8d 2026-10-18 15:40:10 11.2 Mbit/s (M)
dannenberg (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable 2.2 Mbit/s (M) | 816.0 Kbit/s 2.2 Mbit/s (M) | 280.0 Mbit/s OR 16.8 Mbit/s 99.7% | 98% 18.2d | 8d 9.5d | 6.2d 8.9d | 6.2d 2026-10-18 15:40:10 2.2 Mbit/s (M)
dizum (NL) Yes Yes No — N Yes Running, Valid, V2Dir, Fast, Stable, Guard 18.0 Mbit/s (R) | 816.0 Kbit/s 18.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.7% | 98% 18.2d | 8d 9.5d | 8.8d 8.9d | 5.8d 2026-10-18 15:40:10 18.0 Mbit/s (R)
faravahar (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable not published | 816.0 Kbit/s not published | 264.0 Mbit/s OR 16.8 Mbit/s 99.7% | 98% 18.2d | 8d 9.5d | 9.3d 8.9d | 6.4d 2026-10-18 15:40:10 18.0 Mbit/s (R)
gabelmoo (DE) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir 2.6 Mbit/s (M) | 816.0 Kbit/s 2.6 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s 99.7% | 98% 18.2d | 8d 9.5d | 8.9d 8.9d | 6.0d 2026-10-18 15:40:10 2.6 Mbit/s (M)
longclaw (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 18.0 Mbit/s (R) | 816.0 Kbit/s 18.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.7% | 98% 17.7d | 8d 9.4d | 9.1d 8.9d | 5.8d 2026-10-18 15:40:10 18.0 Mbit/s (R)
maatuska (SE) Yes Yes No — N Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 18.0 Mbit/s (R) | 816.0 Kbit/s 18.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.7% | 98% 18.2d | 8d 9.5d | 8.8d 8.9d | 5.8d 2026-10-18 15:40:10 18.0 Mbit/s (R)
moria1 (US) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable 10.4 Mbit/s (M) | 8.4 Mbit/s 10.4 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 99.4% | 98% 9.8d | 8d 9881.9d | 10253.2d 8.9d | 5.8d 2026-10-18 15:40:10 10.4 Mbit/s (M)
tor26 (AT) Yes Yes No — Y Yes Running, Valid, V2Dir, Fast, Stable, HSDir 2.7 Mbit/s (M) | 816.0 Kbit/s 2.7 Mbit/s (M) | 264.0 Mbit/s OR 16.8 Mbit/s 99.6% | 98% 17.7d | 8d 9.4d | 9.2d 8.9d | 6.3d 2026-10-18 15:40:10 2.7 Mbit/s (M)

— = not tested/available • 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.