View Relay "Borrowing"

Fingerprint: 52E81F961139C65FFB702BD1A0D42D76B07332DB | Family: 1 relay | fvckbubble@proton.me | AS26599 | Brazil | Linux

Consensus
In Consensus (9/9 Directory Auths)
BW Verified
0/6 BW Auths Measured 5248 bit/s Median
Stability
Not Overloaded | DOWN 4d 6h 46m ago
Reachability
IPv4: 9/9 (Directory Auths)
BW Weight
0.00% of Network | 5 Mbit/s Observed By Relay
Version
0.4.9.6 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.7 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 2.4 days is below 8 days requirement (5.6 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.
  • Low bandwidth authority measurements : Only 0/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
179.146.60.201:9001
[2804:7f1:6803:52b5:cd70:5e6c:5650:858b]:9001
Reachability (Directory Authorities)
IPv4
9/9
Location
Country
Brazil Brazil
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS26599
AS Name
Unknown
AS Rarity
Legendary (score: 5/5, <0.05% consensus weight, 1 operator)

Current Flags (3): Running, Valid, V2Dir
Eligible Flags (3): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 3/9 | Stable: 4/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
IPv6 Reachability Meets (2/2 DA) 2/2 tested authorities reached relay ≥2/2 tested (majority) (≥2/2 DA)
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) 5.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 (1/9 DA) Median: 2.4d (1/9 DA above threshold)
Min/Max: 0.0d / 20559.1d (9/9 DA, Voting / Total Eligible)
≥38.3d - 62.2d (varies) (≥5/9 DA)
Uptime Below (0/9 DA) 4.1d (R) ≥8.3d - 11.1d (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 (4/9 DA) 4/9 DA assigned Stable ≥38.3d - 62.2d (varies) (≥5/9 DA)
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (4/9 DA) Median: 0.6% (4/9 DA above threshold)
Min/Max: 0.2% / 100.0% (9/9 DA, Voting / Total Eligible)
≥98.0% (≥5/9 DA)
Time Known Meets (8/9 DA) Median: 4.3d (0/9 DA above threshold)
Min/Max: 2.4d / 5.4d (9/9 DA, Voting / Total Eligible)
≥1.0d (most) (≥5/9 DA)
[Stricter] moria1: ≥9.9d
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 (4/9 DA) 4/9 DA assigned Stable ≥38.3d - 62.2d (varies) (≥5/9 DA)
Prereq: V2Dir Meets (9/9 DA) 9/9 DA assigned V2Dir Tunnelled directory via ORPort or DirPort (≥5/9 DA)
WFU Below (4/9 DA) Median: 0.6% (4/9 DA above threshold)
Min/Max: 0.2% / 100.0% (9/9 DA, Voting / Total Eligible)
≥98% (≥5/9 DA)
Time Known Below (0/9 DA) (need 3.7 more days) Median: 4.3d (0/9 DA above threshold)
Min/Max: 2.4d / 5.4d (9/9 DA, Voting / Total Eligible)
≥8 days (≥5/9 DA)
Bandwidth Below (0/9 DA) 5.3 Mbit/s (R) ≥16.0 Mbit/s (Tor spec minimum) OR ≥80.0 Mbit/s-312.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-04-20 10:15:08).

Capacity (Relay Reported)
Observed Bandwidth
5.25 Mbit/s
Advertised Bandwidth
5.25 Mbit/s
Rate Limit
12.58 Mbit/s
Burst Limit
15.73 Mbit/s
Total Data
256 MB (1 month)
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-04-20 10:15:08

Measured By
0/6 Bandwidth Authorities
Not measured by: bastet, gabelmoo, longclaw, maatuska, moria1, tor26
Median Measurement
5248 bit/s
Min / Max
5248 bit/s / 5248 bit/s
Network Participation: Consensus Weight: 0.0000% of network (3th pctl) | Guard: N/A | Middle: N/A | Exit: N/A

Uptime Metrics
Current Status
DOWN 4d 6h 46m ago
Overall Uptime (1M/6M/1Y/5Y)
0.0%/0.0%/0.0%/0.0%
Flag Uptime (1M/6M/1Y/5Y)
N/A
Hibernating
No
Timestamps
First Seen
4d 6h 46m ago (2026-04-16 04:00:00)
Last Seen
4d 6h 46m ago (2026-04-16 04:00:00)
Last Restarted
4d 1h 17m ago (2026-04-16 09:29:22)
Last Changed Address
2026-04-16 04:00:00
Overload Status: Not Overloaded — No overload conditions reported.

Operator Identity

Source: AROI Validation API — 2026-04-20 03:00 UTC

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

Platform
Linux — Tor 0.4.9.6 on Linux
Version
0.4.9.6Recommended
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, 20 Apr 2026 10:46:38 GMT.

Data from Tor CollecTor (authority votes, fetched 2026-04-20 10:15:08).

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 5.3 Mbit/s | 816.0 Kbit/s 5.3 Mbit/s | 200.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 2.4d | 8d 2.4d | 62.2d 4.1d | 8.3d 100.0% | 98.0% 2.4d | 1.0d 2026-04-17 09:08:39 5248 bit/s
dannenberg (DE) Yes Yes No N Yes Valid, V2Dir, Fast 5.3 Mbit/s | 816.0 Kbit/s 5.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 0.5% | 98% 4.3d | 8d 0.0d | 38.3d 4.1d | 11.1d 0.5% | 98.0% 4.3d | 1.0d 2026-04-20 06:40:15 5248 bit/s
dizum (NL) Yes Yes No N Yes Running, Valid, V2Dir, Fast, Stable 5.3 Mbit/s | 816.0 Kbit/s 5.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.4d | 8d 5.4d | 40.3d 4.1d | 11.1d 100.0% | 98.0% 5.4d | 1.0d 2026-04-20 09:41:16 5248 bit/s
faravahar (US) Yes Yes No N Yes Running, Valid, V2Dir, Fast, Stable 5.3 Mbit/s | 816.0 Kbit/s 5.3 Mbit/s | 80.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.4d | 8d 5.4d | 61.2d 4.1d | 11.1d 100.0% | 98.0% 5.4d | 1.0d 2026-04-20 09:41:16 5248 bit/s
gabelmoo (DE) Yes Yes No Y Yes Valid, V2Dir 5.3 Mbit/s | 816.0 Kbit/s 5.3 Mbit/s | 296.0 Mbit/s OR 16.0 Mbit/s 0.2% | 98% 4.3d | 8d 0.0d | 63.0d 4.1d | 11.1d 0.2% | 98.0% 4.3d | 1.0d 2026-04-20 06:40:15 5248 bit/s
longclaw (US) Yes Yes No Y Yes Valid, V2Dir 5.3 Mbit/s | 816.0 Kbit/s 5.3 Mbit/s | 240.0 Mbit/s OR 16.0 Mbit/s 0.5% | 98% 4.3d | 8d 0.0d | 62.3d 4.1d | 11.1d 0.5% | 98.0% 4.3d | 1.0d 2026-04-20 06:40:15 5248 bit/s
maatuska (SE) Yes Yes No Y Yes Valid, V2Dir 5.3 Mbit/s | 816.0 Kbit/s 5.3 Mbit/s | 312.0 Mbit/s OR 16.0 Mbit/s 0.6% | 98% 3.3d | 8d 0.0d | 61.4d 4.1d | 10.2d 0.6% | 98.0% 3.3d | 1.0d 2026-04-19 07:10:34 5248 bit/s
moria1 (US) Yes Yes No Y Yes Valid, V2Dir, Stable 5.3 Mbit/s | 8.4 Mbit/s 5.3 Mbit/s | 216.0 Mbit/s OR 16.0 Mbit/s 0.6% | 98% 3.4d | 8d 20559.1d | 303.7d 4.1d | 11.0d 0.6% | 98.0% 3.4d | 9.9d 2026-04-20 03:38:15 5248 bit/s
tor26 (AT) Yes Yes No Y Yes Running, Valid, V2Dir, Stable 5.3 Mbit/s | 816.0 Kbit/s 5.3 Mbit/s | 288.0 Mbit/s OR 16.0 Mbit/s 100.0% | 98% 5.4d | 8d 5.4d | 63.2d 4.1d | 11.1d 100.0% | 98.0% 5.4d | 1.0d 2026-04-20 09:41:16 5248 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.