View Contact tincan-relay.github.io Details

📋 Contact & Network Overview

  • AROI: tincan-relay.github.io✓ Validated
  • Vanity URL: https://metrics.1aeo.com/tincan-relay.github.io/
  • ContactInfo variants: 2 distinct ContactInfo strings across this operator's 2 relays (grouped by AROI domain).
    • 1 relay v2 uri-rsa
      email:tincan.tor[]proton.me url:tincan-relay.github.io proof:uri-rsa ciissversion:2
    • 1 relay v2 uri-rsa
      email:tincan.tor[]proton.me url:tincan-relay.github.io proof:uri-rsa ciissversion:2 uplinkbw:1000 trafficacct:unmetered cpu:Ryzen-9-9900X memory:31488 virtualization:baremetal os:linuxmint/22.3
  • Hash: 1576031e1bf1b771766464ddb52fea2f
  • Countries: Finland Finland (2)
Network Summary:
  • Bandwidth Capacity: ~294.33 Mbit/s (294.33 Mbit/s middle)
  • Total Data Transferred: 39 TB
  • Network Influence: 0.02% of overall consensus weight (0.14% middle)
  • Network Position: Middle-only (2 total relays, 2 middles)

📊 Operator Intelligence

  • Network Diversity: Great, 1 network (legendary)
  • Geographic Diversity: Poor, 1 country (2 relays)
  • Infrastructure Diversity: Poor, 1 platform
  • Bandwidth Capacity Measurements: 1/2 relays measured by authorities
  • Performance Insights: Overall CW/BW: 1196. -4% lower than 1246 network average. 67th percentile with 849 median.
  • Operational Maturity: Operating since 2026-08-04 (expanded through 2026-09-15)
  • Version Compliance: All, 2 (100%) compliant
    • Version Status: All, 2 (100%) recommended
  • Family Support: 2 None (100%)

🚀 Bandwidth Reliability

Operator Performance:
  • Average Relay Throughput: 6mo 41.35 Mbit/s avg (1 relays)
    • No bandwidth outliers detected
  • Performance Analysis (6mo):
    • Stability: Great (Coefficient of Variation: 0.0% = 0.00 Kbit/s σ / 41.35 Mbit/s μ)
Network Comparison:
  • Network Position: Top 50% (50th-75th percentile)
  • Network Contribution: 6mo 41.35 Mbit/s avg (44 days)
Bandwidth Stability: Great (Top 25% most stable), Good (25-50% most stable), Variable (25-50% most stable), Extreme (Bottom 10% most variable)
Reliability data available for 1/2 relays, from 2026-09-20 09:00:00 UTC

⏰ Relay Reliability

  • Overall Uptime: 30d 96.2% (1 relays), 6mo 97.5% (1 relays)
    • ✅ No statistical outliers detected - consistent performance across all relays
    • Network Uptime (6mo): 5th Pct: 86%, Operator: 97%, 25th Pct: 98%, 50th Pct: 99%, 75th Pct: 100%, 90th Pct: 100%, 95th Pct: 100%, 99th Pct: 100%
  • 🚨 Offline (1): 1 middle (0.0% of observed traffic)
    • Impact: 0.00 Mbit/s (0.0% of 294.33 Mbit/s) and 0.000% (0.0% of 0.02%) consensus weight
Reliability data available for 1/2 relays, from 2026-09-20 09:00:00 UTC

🏷️ Flag Reliability

Flag-specific uptime percentages (1M/6M):
🛡️ Stable Operation: 96.2% / 97.2%
⚡ Fast Relay: 96.2% / 97.3%
🟢 Running Operation: 96.2% / 97.5%
📁 Directory Services: 96.2% / 97.5%
Excellent (>99%), Below average (<μ of network), Poor (≥2σ from network μ) , from 2026-09-20 09:00:00 UTC

🚀 Flag Bandwidth Performance

Flag-specific bandwidth averages (6M):
⚡ Fast Relay: 41.35 Mbit/s
🟢 Running: 41.35 Mbit/s
🎯 Stable Relay: 41.35 Mbit/s
📋 Version 2 Directory: 41.35 Mbit/s
High performance (>1.5x μ), Below average (<μ of network), Poor (≥2σ from network μ)

Last updated: Sun, 20 Sep 2026 10:15:54 GMT. Refreshed every 30 minutes from the Tor directory authorities via Tor Project's onionoo API.

💡 Want to upgrade to ciissversion:3?

All 2 of your relays validate cleanly on CIISS v2 (RSA fingerprint proofs). The new CIISS v3 spec replaces per-relay RSA proofs with a single shared ed25519 family-id proof — same url, one published file for the whole family.

To migrate, change torrc ContactInfo to:

ciissversion:3 url:tincan-relay.github.io proof:uri-familyid-ed25519

And on a secure host, generate the happy-family key:

tor --keygen-family /path/to/myfamily # then deploy myfamily.secret_family_key to every relay's KeyDir

Publish .public_family_id at /.well-known/tor-relay/ed25519-family-id.txt. Allow ~24h after restarting Tor for Onionoo to refresh family_ids. Full guide: aroivalidator setup guide.

✓ VALIDATED RELAYS (1)

Nickname BW Cap (294.33 Mbit/s) Total Data Uptime/Downtime Uptime (1M/6M/1Y/5Y) Flag Uptime (1M/6M/1Y/5Y) IPv4 Flags DNS Family Country AS Number AS Name Platform First Seen Last Restarted
TinCan 294.33 Mbit/s    39 TB UP 1d 14h 49m ago 96.2%/97.5%/0.0%/0.0% —/97.3%/—/— 77.234.125.150 FastRunningStableV2DirValid NA None Finland FI AS42885 Paraisten Puhelin Oy Linux 1mo 2w 2d ago 1d 14h 50m ago

🚫 UNAUTHORIZED RELAYS (1)

Nickname BW Cap (294.33 Mbit/s) Total Data Uptime/Downtime Uptime (1M/6M/1Y/5Y) Flag Uptime (1M/6M/1Y/5Y) IPv4 Flags DNS Family Country AS Number AS Name Platform First Seen Last Restarted
🚫 TinCan 0.00 Kbit/s    N/A DOWN 4d 18h 15m ago 0.0%/0.0%/0.0%/0.0% N/A 77.234.125.150 RunningV2DirValid NA None Finland FI AS42885 Paraisten Puhelin Oy Linux 4d 18h 16m ago 4d 18h 38m ago
🚫 UNAUTHORIZED RELAY DETAILS

These relays claim this domain but their fingerprints are NOT in the AROI proof file. This could be someone falsely claiming your domain.

Validation data last updated: 2026-09-20 02:00 UTC

  • TinCan v2 URI-RSA: Fingerprint not found at tincan-relay.github.io • Proof: uri-rsa • FP: A8B85E0C355563D9BCB1A4CBC3AA76AF3BD23BEB
    📋 Paste: curl https://tincan-relay.github.io/.well-known/tor-relay/rsa-fingerprint.txt # must contain this relay's 40-char fingerprint A8B85E0C355563D9BCB1A4CBC3AA76AF3BD23BEB

💡 If this is YOUR relay: Add the fingerprint to your AROI proof file.
📖 See the AROI Specification for guidance.