View Relay "PingMeRelay232"
Fingerprint: B92BAD1AFF15474F5CFC3D7F6E1F0F0678FD8436 |
Family: 3 relays
|
info@pingme.ovh |
AS1267
|
Italy
|
Linux
- Consensus
- In Consensus (7/7 Directory Auths)
- BW Verified
- 2/6 BW Auths Measured
- Stability
- Not Overloaded | UP 13h 35m 38s ago
- Reachability
- IPv4: 7/7 (Directory Auths)
- BW Weight
- 0 Kbit/s Observed By Relay
- Version
- 0.4.9.11 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: Time Known below threshold
: Time Known 0.5 days is below 8 days requirement (7.5 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. -
HSDir: Time Known below threshold
: Time Known 12.7 hours below 25 hours (dir-spec default)
Suggestion: Most authorities use 25 hours for HSDir TK. moria1 uses ~10 days. Keep running stably. -
Low bandwidth authority measurements
: Only 2/6 bandwidth authorities measured this relay. Minimum 3 measurements needed for accurate consensus weight.
Suggestion: Low measurement count can indicate connectivity issues. Check: 1) Relay is reachable from multiple geographic locations, 2) ORPort accepts connections from bandwidth scanners, 3) RelayBandwidthRate in torrc matches actual capacity. New relays may take 1-2 days to be measured by all authorities.
Addresses
- OR Address
- 151.59.115.113:9002
Reachability (Directory Authorities)
- IPv4
- 7/7
Location
- Country
-
Italy
- Interactive Map
- View in RouteFluxMap
Eligible Flags (3):
Running: 7/7 | Valid: 7/7 | V2Dir: 7/7 | Fast: 0/7 | Stable: 0/7 | HSDir: 0/7 | Guard: 0/7 | Exit: 0/7
Eligibility Flag Vote Details
| Flag | Metric | Status | Relay Value | Threshold Required |
|---|---|---|---|---|
| Running | IPv4 Reachability | Meets (7/7 DA) | 7/7 authorities reached relay | ≥4/7 DA ORPort reachable |
| Valid | Descriptor | Meets (7/7 DA) | 7/7 authorities assigned Valid | Not blacklisted + valid descriptor (≥4/7 DA) |
| V2Dir | DirPort Available | Meets (7/7 DA) | Tunnelled: Yes (no DirPort) (R) | Tunnelled directory via ORPort or DirPort (≥4/7 DA) |
| Fast | Speed | Below (0/7 DA) | 0 bit/s (R) | ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Stable | MTBF | Below (0/7 DA) | Median: 0.5d (0/7 DA above threshold) Min/Max: 0.5d / 0.5d (7/7 DA, Voting / Total Eligible) |
≥9.3d - 19.8d (varies) (≥4/7 DA) [Stricter] moria1: ≥7800.1d |
| Uptime | Below (0/7 DA) | 0.6d (R) | ≥4.1d - 4.1d (varies) (≥4/7 DA) | |
| HSDir | Prereq: Fast | Below (0/7 DA) | 0/7 DA assigned Fast | ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Below (0/7 DA) | 0/7 DA assigned Stable | ≥9.3d - 19.8d (varies) (≥4/7 DA) [Stricter] moria1: ≥7800.1d |
|
| Prereq: V2Dir | Meets (7/7 DA) | 7/7 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥4/7 DA) | |
| WFU | Meets (7/7 DA) | Majority: 100.0% (7/7 DA) | ≥98.0% (≥4/7 DA) | |
| Time Known | Below (0/7 DA) | Median: 0.5d (0/7 DA above threshold) Min/Max: 0.5d / 0.5d (7/7 DA, Voting / Total Eligible) |
≥1.0d (most) (≥4/7 DA) [Stricter] moria1: ≥9.9d |
|
| Guard | Prereq: Fast | Below (0/7 DA) | 0/7 DA assigned Fast | ≥800.0 Kbit/s (Tor spec minimum) OR top 7/8 (≥4/7 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Below (0/7 DA) | 0/7 DA assigned Stable | ≥9.3d - 19.8d (varies) (≥4/7 DA) [Stricter] moria1: ≥7800.1d |
|
| Prereq: V2Dir | Meets (7/7 DA) | 7/7 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥4/7 DA) | |
| WFU | Meets (7/7 DA) | Majority: 100.0% (7/7 DA) | ≥98% (≥4/7 DA) | |
| Time Known | Below (0/7 DA) (need 7.5 more days) | Median: 0.5d (0/7 DA above threshold) Min/Max: 0.5d / 0.5d (7/7 DA, Voting / Total Eligible) |
≥8 days (≥4/7 DA) | |
| Bandwidth | Below (0/7 DA) | 0 bit/s (R) | ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-288.0 Mbit/s (≥4/7 DA) | |
| Exit | Exit Policy | Below (0/7 DA) | Port 80: No | Port 443: No (R) | Allows ≥1 /8 on ports 80 AND 443 (≥4/7 DA) |
(DA) = Dir. Auth. Measured |
(R) = Relay Reported
Data from Tor CollecTor (authority votes, fetched 2026-07-14 08:45:05).
Capacity (Relay Reported)
- Observed Bandwidth
- 0.00 Kbit/s
- Advertised Bandwidth
- Unknown
- Rate Limit
- 8.59 Gbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
- N/A
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-07-14 08:45:05
- Measured By
-
2/6
Bandwidth Authorities
Not measured by: bastet, faravahar, moria1, tor26 - Median Measurement
- 0 bit/s
- Min / Max
- 0 bit/s / 8 bit/s
Network Participation:
Consensus Weight:
N/A
|
Guard:
N/A |
Middle:
N/A |
Exit:
N/A
Uptime Metrics
- Current Status
- UP 13h 35m 38s 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
- 12h 45m 41s ago (2026-07-13 20:00:00)
- Last Seen
- 1h 45m 41s ago (2026-07-14 07:00:00)
- Last Restarted
- 13h 35m 38s ago (2026-07-13 19:10:03)
- Last Changed Address
- 2026-07-13 20:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
Operator Identity
Source: AROI Validation API — 2026-07-14 01:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- info@pingme.ovh
Family Configuration
- Family Support
- MyFamily Only (3) — Legacy only. Consider migrating to Happy Families. | View Full Family (3)
Happy Families (family-cert)
- Effective Members: 0
- none
MyFamily (legacy declarations)
- Effective Members: 3
3D36D247C2E08941B16C7BB046ADE0B2F701A0F4 B92BAD1AFF15474F5CFC3D7F6E1F0F0678FD8436 (this relay) F33675032858D3726D696F7CAA639DF37FBF1F42
- Alleged Members: 0
- none
- Indirect Members: 0
- none
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Tue, 14 Jul 2026 08:45:40 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-07-14 08:45: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 (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 | 0 bit/s | 816.0 Kbit/s | 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 100.0% | 98% | 0.5d | 8d | 0.5d | 29.3d | 0.6d | 4.2d | 100.0% | 98.0% | 0.5d | 1.0d | 2026-07-13 19:10:19 | — |
| dannenberg (DE) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir | 0 bit/s | 816.0 Kbit/s | 0 bit/s | 248.0 Mbit/s OR 16.0 Mbit/s | 100.0% | 98% | 0.5d | 8d | 0.5d | 9.3d | 0.6d | 4.1d | 100.0% | 98.0% | 0.5d | 1.0d | 2026-07-13 19:10:19 | 8 bit/s |
| dizum (NL) | Yes | Yes | No | — | N | Yes | Running, Valid, V2Dir | 0 bit/s | 816.0 Kbit/s | 0 bit/s | 80.0 Mbit/s OR 16.0 Mbit/s | 100.0% | 98% | 0.5d | 8d | 0.5d | 18.2d | 0.6d | 4.1d | 100.0% | 98.0% | 0.5d | 1.0d | 2026-07-13 19:10:19 | — |
| faravahar (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir | 0 bit/s | 816.0 Kbit/s | 0 bit/s | 288.0 Mbit/s OR 16.0 Mbit/s | 100.0% | 98% | 0.5d | 8d | 0.5d | 16.0d | 0.6d | 4.1d | 100.0% | 98.0% | 0.5d | 1.0d | 2026-07-13 19:10:19 | — |
| maatuska (SE) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir | 0 bit/s | 816.0 Kbit/s | 0 bit/s | 280.0 Mbit/s OR 16.0 Mbit/s | 100.0% | 98% | 0.5d | 8d | 0.5d | 19.8d | 0.6d | 4.1d | 100.0% | 98.0% | 0.5d | 1.0d | 2026-07-13 19:10:19 | 8 bit/s |
| moria1 (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir | 0 bit/s | 8.4 Mbit/s | 0 bit/s | 232.0 Mbit/s OR 16.0 Mbit/s | 100.0% | 98% | 0.5d | 8d | 0.5d | 7800.1d | 0.6d | 4.1d | 100.0% | 98.0% | 0.5d | 9.9d | 2026-07-13 19:10:19 | — |
| tor26 (AT) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir | 0 bit/s | 816.0 Kbit/s | 0 bit/s | 272.0 Mbit/s OR 16.0 Mbit/s | 100.0% | 98% | 0.5d | 8d | 0.5d | 28.6d | 0.6d | 4.1d | 100.0% | 98.0% | 0.5d | 1.0d | 2026-07-13 19:10:19 | — |
— = 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.
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.
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.