View Relay "GandhiRoute"

Fingerprint: 7FCF828D8AA7932107EEFE00166A93260F8A4906 | Family: 1 relay | LongRouteToFreedom | AS14061 | India | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
4/7 BW Auths Measured 3144 bit/s Median
Stability
Not Overloaded | UP 12h 15m 1s ago
Reachability
IPv4: 9/9 (Directory Auths)
BW Weight
0.00% of Network | 3 Mbit/s Observed By Relay
Version
0.4.9.8 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.4 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 3.7 days is below 8 days requirement (4.3 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.
  • 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
134.209.157.172:9100
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
India India
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS14061
AS Name
DigitalOcean, LLC (BGP.tools)
AS Rarity
Rare (score: 2/5, 0.49% consensus weight, 61 operators)

Current Flags (3): Running, Valid, V2Dir
Eligible Flags (3): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 3/9 | Stable: 0/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) 3.3 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.7d (0/9 DA above threshold)
Min/Max: 3.7d / 3.7d (9/9 DA, Voting / Total Eligible)
≥20.1d - 51.5d (varies) (≥5/9 DA)
[Stricter] moria1: ≥334.0d
Uptime Below (0/9 DA) 0.5d (R) ≥12.4d - 12.8d (varies) (≥5/9 DA)
HSDir Prereq: Fast Below (3/9 DA) 3/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 (0/9 DA) 0/9 DA assigned Stable ≥20.1d - 51.5d (varies) (≥5/9 DA)
[Stricter] moria1: ≥334.0d
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) Majority: 100.0% (9/9 DA) ≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 3.7d (0/9 DA above threshold)
Min/Max: 3.1d / 3.7d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.8d
Guard Prereq: Fast Below (3/9 DA) 3/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 (0/9 DA) 0/9 DA assigned Stable ≥20.1d - 51.5d (varies) (≥5/9 DA)
[Stricter] moria1: ≥334.0d
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) Majority: 100.0% (9/9 DA) ≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 4.3 more days) Median: 3.7d (0/9 DA above threshold)
Min/Max: 3.1d / 3.7d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 3.3 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-328.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-05-25 12:15:04).

Capacity (Relay Reported)
Observed Bandwidth
3.26 Mbit/s
Advertised Bandwidth
3.15 Mbit/s
Rate Limit
3.15 Mbit/s
Burst Limit
6.29 Mbit/s
Total Data
756 MB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-05-25 12:15:04

Measured By
4/7 Bandwidth Authorities
Not measured by: bastet, dannenberg, moria1
Median Measurement
3144 bit/s
Min / Max
392 bit/s / 3144 bit/s
Deviation
2752 bit/s [Warning] High variation
Network Participation: Consensus Weight: 0.0000% of network (3th pctl) | Guard: N/A | Middle: 0.0001% (3th pctl) | Exit: N/A

Uptime Metrics
Current Status
UP 12h 15m 1s ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
Matches Overall Uptime (0.0%/0.0%/0.0%/0.0%)
Hibernating
No
Timestamps
First Seen
3d 18h 15m ago (2026-05-21 18:00:00)
Last Seen
1h 15m 49s ago (2026-05-25 11:00:00)
Last Restarted
12h 15m 1s ago (2026-05-25 00:00:48)
Last Changed Address
2026-05-21 18:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator Identity

Source: AROI Validation API — 2026-05-25 05:00 UTC

AROI Domain (?)
Not specified
Operator Validation
Unvalidated
This Relay
N/A (no AROI configured)
Contact
LongRouteToFreedom
Family Configuration
Family Support
None — No family membership configured
Happy Families (family-cert)
Effective Members: 0
none
MyFamily (legacy declarations)
Effective Member: 1
7FCF828D8AA7932107EEFE00166A93260F8A4906 (this relay)
Alleged Members: 0
none
Indirect Members: 0
none

Platform
Linux — Tor 0.4.9.8 on Linux
Version
0.4.9.8Recommended
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 Mon, 25 May 2026 12:15:48 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-05-25 12:15:04).

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 3.3 Mbit/s | 816.0 Kbit/s 3.3 Mbit/s | 232.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.7d | 8d 3.7d | 50.8d 0.5d | 12.4d 100.0% | 98.0% 3.7d | 1.0d 2026-05-25 00:00:55 3144 bit/s
dannenberg (DE) Yes Yes No Y Yes Running, Valid, V2Dir, Fast 3.3 Mbit/s | 816.0 Kbit/s 3.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.7d | 8d 3.7d | 44.7d 0.5d | 12.8d 100.0% | 98.0% 3.7d | 1.0d 2026-05-25 00:00:55 3144 bit/s
dizum (NL) Yes Yes No N Yes Running, Valid, V2Dir, Fast 3.3 Mbit/s | 816.0 Kbit/s 3.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.7d | 8d 3.7d | 20.1d 0.5d | 12.8d 100.0% | 98.0% 3.7d | 1.0d 2026-05-25 00:00:55 3144 bit/s
faravahar (US) Yes Yes No N Yes Running, Valid, V2Dir, Fast 3.3 Mbit/s | 816.0 Kbit/s 3.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.7d | 8d 3.7d | 51.5d 0.5d | 12.9d 100.0% | 98.0% 3.7d | 1.0d 2026-05-25 00:00:55 3144 bit/s
gabelmoo (DE) Yes Yes No Y Yes Running, Valid, V2Dir 3.3 Mbit/s | 816.0 Kbit/s 3.3 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.7d | 8d 3.7d | 52.1d 0.5d | 13.1d 100.0% | 98.0% 3.7d | 1.0d 2026-05-25 00:00:55 400 bit/s
longclaw (US) Yes Yes No Y Yes Running, Valid, V2Dir 3.3 Mbit/s | 816.0 Kbit/s 3.3 Mbit/s | 248.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.7d | 8d 3.7d | 58.9d 0.5d | 12.8d 100.0% | 98.0% 3.7d | 1.0d 2026-05-25 00:00:55 568 bit/s
maatuska (SE) Yes Yes No Y Yes Running, Valid, V2Dir 3.3 Mbit/s | 816.0 Kbit/s 3.3 Mbit/s | 328.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.7d | 8d 3.7d | 22.9d 0.5d | 12.7d 100.0% | 98.0% 3.7d | 1.0d 2026-05-25 00:00:55 392 bit/s
moria1 (US) Yes Yes No Y Yes Running, Valid, V2Dir 3.3 Mbit/s | 8.4 Mbit/s 3.3 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.1d | 8d 3.7d | 334.0d 0.5d | 13.2d 100.0% | 98.0% 3.1d | 9.8d 2026-05-25 00:00:55 3144 bit/s
tor26 (AT) Yes Yes No Y Yes Running, Valid, V2Dir 3.3 Mbit/s | 816.0 Kbit/s 3.3 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 3.7d | 8d 3.7d | 53.7d 0.5d | 13.1d 100.0% | 98.0% 3.7d | 1.0d 2026-05-25 00:00:55 408 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.