View Contact tor.redlabsdevelopment.de Details

📋 Contact & Network Overview

  • AROI: tor.redlabsdevelopment.de⚠ Misconfigured
    • 1 relay, 0% valid, 100% v3
  • Contact: email:tor[]redlabsdevelopment.de url:https://tor.redlabsdevelopment.de proof:uri-familyid-ed25519 offlinemasterkey:y ciissversion:3 pgp:B549C91B7C50E91C8FEDEEFA45D5AE6A61D54573
  • Hash: ad127ec2606eb9fe1a534b4c364c37ef
  • Countries: Germany Germany (1)
Network Summary:
  • Bandwidth Capacity: ~22.08 Mbit/s (22.08 Mbit/s middle)
  • Total Data Transferred: 724 GB
  • Network Influence: 0.00% of overall consensus weight (0.00% middle)
  • Network Position: Middle-only (1 total relay, 1 middle)

📊 Operator Intelligence

  • Network Diversity: Great, 1 network (rare)
  • Geographic Diversity: Poor, 1 country (1 relay)
  • Infrastructure Diversity: Poor, 1 platform
  • Bandwidth Capacity Measurements: 1/1 relays measured by authorities
  • Performance Insights: Overall CW/BW: 435. -65% lower than 1241 network average. 20th percentile with 836 median.
  • Operational Maturity: Operating since 2026-06-26 (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 90.5% (1 relays)
    • ✅ No statistical outliers detected - consistent performance across all relays
  • Offline: 0 relays
Reliability data available for 1/1 relays, from 2026-07-18 23:00:00 UTC

🏷️ Flag Reliability

Flag-specific uptime percentages (1M):
🛡️ Stable Operation: 63.2%
⚡ Fast Relay: 90.4%
🟢 Running Operation: 90.5%
📁 Directory Services: 90.5%
Excellent (>99%), Below average (<μ of network), Poor (≥2σ from network μ) , from 2026-07-18 23: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: Sun, 19 Jul 2026 13:01:45 GMT. Refreshed every 30 minutes from the Tor directory authorities via Tor Project's onionoo API.

⏳ PENDING ONIONOO REFRESH (1)

Nickname BW Cap (22.08 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 TorHostingByRedLabs 22.08 Mbit/s   ✓ 724 GB UP 1d 13h 9m ago 90.5%/0.0%/0.0%/0.0% Match 93.244.234.239 FastRunningStableV2DirValid NA None Germany DE AS3320 Deutsche Telekom AG Linux 3w 1d 21h ago 1d 13h 15m 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-07-19 05:00 UTC

  • TorHostingByRedLabs v3 • URI-FamilyID: Relay has no family_ids in Onionoo, cannot verify ciissversion:3 proof • Proof: uri-familyid-ed25519 • FP: 83138B649C7138AAD7633E4B1B0A8FB2F58B7E9B
    💡 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=83138B649C7138AAD7633E4B1B0A8FB2F58B7E9B&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 (22.08 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
⚠ TorHostingByRedLabs 22.08 Mbit/s   ✓ 724 GB UP 1d 13h 9m ago 90.5%/0.0%/0.0%/0.0% Match 93.244.234.239 FastRunningStableV2DirValid NA None Germany DE AS3320 Deutsche Telekom AG Linux 3w 1d 21h ago 1d 13h 15m ago
⚠️ MISCONFIGURED RELAY DETAILS

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

Validation data last updated: 2026-07-19 05:00 UTC

  • TorHostingByRedLabs v3 • URI-FamilyID: Relay has no family_ids in Onionoo, cannot verify ciissversion:3 proof • Proof: uri-familyid-ed25519 • FP: 83138B649C7138AAD7633E4B1B0A8FB2F58B7E9B
    💡 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=83138B649C7138AAD7633E4B1B0A8FB2F58B7E9B&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.