View Contact example.com Details

📋 Contact & Network Overview

  • AROI: example.com⚠ Misconfigured
    • 1 relay, 0% valid, 100% v3
  • Contact: email:your-email[]example.com pgp:YOUR_PGP_FINGERPRINT url:https://example.com proof:uri-familyid-ed25519 ciissversion:3
  • Hash: 5181ccd767c27550e55c47d364f63829
  • Countries: Germany Germany (1)
Network Summary:
  • Bandwidth Capacity: ~13.98 Mbit/s (13.98 Mbit/s middle)
  • Total Data Transferred: 19 GB
  • Network Influence: 0.00% of overall consensus weight (0.01% middle)
  • Network Position: Middle-only (1 total relay, 1 middle)

📊 Operator Intelligence

  • Network Diversity: Great, 1 network (epic)
  • Geographic Diversity: Poor, 1 country
  • Infrastructure Diversity: Poor, 1 platform
  • Bandwidth Capacity Measurements: 1/1 relays measured by authorities
  • Performance Insights: Overall CW/BW: 973. -23% lower than 1267 network average. 52th percentile with 922 median.
  • Operational Maturity: Operating since 2026-06-20 (all deployed together)
  • Version Compliance: All, 1 (100%) compliant
    • Version Status: All, 1 (100%) recommended
  • Family Support: 1 None (100%)

⏰ Relay Reliability

  • Overall Uptime: 30d 89.7% (1 relays)
    • ✅ No statistical outliers detected - consistent performance across all relays
  • 🚨 Offline (1): 1 middle (100.0% of observed traffic)
    • Impact: 13.98 Mbit/s (100.0% of 13.98 Mbit/s) and 0.001% (100.0% of 0.00%) consensus weight
Reliability data available for 1/1 relays, from 2026-06-27 04:00:00 UTC

🏷️ Flag Reliability

Flag-specific uptime percentages (1M):
⚡ Fast Relay: 88.9%
🟢 Running Operation: 89.7%
📁 Directory Services: 89.7%
Excellent (>99%), Below average (<μ of network), Poor (≥2σ from network μ) , from 2026-06-27 04:00:00 UTC

🚀 Flag Bandwidth Performance

Flag-specific bandwidth averages:
No flag bandwidth data available for this operator.
High performance (>1.5x μ), Below average (<μ of network), Poor (≥2σ from network μ)

Last updated: Sat, 27 Jun 2026 06:45:40 GMT. Refreshed every 30 minutes from the Tor directory authorities via Tor Project's onionoo API.

⏳ PENDING ONIONOO REFRESH (1)

Nickname BW Cap (13.98 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
⏳ v3 MyTorGuardRelay 13.98 Mbit/s   ✓ 19 GB DOWN 5h 45m 41s ago 89.7%/0.0%/0.0%/0.0% 88.9%/—/—/— 171.22.172.65 FastRunningV2DirValid NA None Germany DE AS49683 MASSIVEGRID LTD Linux 6d 18h 46m ago 4d 8h 20m ago
⏳ WAITING FOR ONIONOO TO REFRESH

These relays declared ciissversion:3 but Onionoo hasn't picked up family_ids yet. This is transient — Onionoo refreshes hourly; expect resolution within 24 hours of restarting Tor with the happy-family directive.

Validation data last updated: 2026-06-26 23:00 UTC

  • MyTorGuardRelay v3 • URI-FamilyID: Relay has no family_ids in Onionoo, cannot verify ciissversion:3 proof • Proof: uri-familyid-ed25519 • FP: E5465365CD56FA289A30E8826586D20C2A5CBE28
    💡 Fix: Run 'tor --keygen-family <file>' on the relay, configure Tor's happy-family directive to use <file>.secret_family_key, restart, and wait for Onionoo to refresh (typically < 24h).
    📋 Paste: curl "https://onionoo.torproject.org/details?lookup=E5465365CD56FA289A30E8826586D20C2A5CBE28&fields=family_ids" | jq # should show your .public_family_id within 24h of restarting Tor

💡 No action needed if you recently changed torrc; wait < 24h. If still pending after 24h: verify FamilyId line in torrc and that .secret_family_key is in Tor KeyDir.
📖 See the AROI Specification for guidance.

⚠ MISCONFIGURED RELAYS (1)

Nickname BW Cap (13.98 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
⚠ MyTorGuardRelay 13.98 Mbit/s   ✓ 19 GB DOWN 5h 45m 41s ago 89.7%/0.0%/0.0%/0.0% 88.9%/—/—/— 171.22.172.65 FastRunningV2DirValid NA None Germany DE AS49683 MASSIVEGRID LTD Linux 6d 18h 46m ago 4d 8h 20m ago
⚠️ MISCONFIGURED RELAY DETAILS

These relays have AROI configured but validation failed due to errors.

Validation data last updated: 2026-06-26 23:00 UTC

  • MyTorGuardRelay v3 • URI-FamilyID: Relay has no family_ids in Onionoo, cannot verify ciissversion:3 proof • Proof: uri-familyid-ed25519 • FP: E5465365CD56FA289A30E8826586D20C2A5CBE28
    💡 Fix: Run 'tor --keygen-family <file>' on the relay, configure Tor's happy-family directive to use <file>.secret_family_key, restart, and wait for Onionoo to refresh (typically < 24h).
    📋 Paste: curl "https://onionoo.torproject.org/details?lookup=E5465365CD56FA289A30E8826586D20C2A5CBE28&fields=family_ids" | jq # should show your .public_family_id within 24h of restarting Tor

💡 Fix: Check DNS records, renew SSL certificates, or verify server connectivity.
📖 See the AROI Specification for guidance.