View Relay "Caramelo"
Fingerprint: DE15A1432DFB127B49F4C6FD9D48771683732995 |
Family: 16 relays
|
gus@riseup.net |
AS136258
|
Brazil
|
Linux
- Consensus
- In Consensus (9/9 Directory Auths)
- BW Verified
- 5/7 BW Auths Measured 2 Mbit/s Median
- Stability
- Not Overloaded | UP 6d 2h 50m ago | UP 100% (1M)
- Reachability
- IPv4: 9/9 | v6: None configured(Directory Auths)
- BW Weight
- 0.00% of Network | 12 Mbit/s Observed By Relay
- Version
- 0.4.9.15 Recommended
Issues Detected:
-
Guard: bandwidth below threshold
: 0/9 authorities credit this relay with enough bandwidth for Guard (5 needed): at least 16.8 Mbit/s (AuthDirGuardBWGuarantee) or a place in their top 25% (80.0 Mbit/s – 272.0 Mbit/s). bastet, dannenberg, gabelmoo, moria1 and tor26 measured this relay at 880.0 Kbit/s – 3.8 Mbit/s. dizum, faravahar, longclaw and maatuska used the relay-reported 12.6 Mbit/s.
Suggestion: Guard requires a bandwidth of at least AuthDirGuardBWGuarantee (16.8 Mbit/s by default) or one in the top 25% of relays, judged by each authority the same way as for Fast. To increase bandwidth: 1) Ensure adequate upstream capacity, 2) Check RelayBandwidthRate/RelayBandwidthBurst in torrc, 3) Monitor with Nyx. -
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
- 109.104.155.20:9001
Reachability (Directory Authorities)
- IPv4
- 9/9
- IPv6
- None configured
Location
- Country
-
Brazil
- Interactive Map
- View in RouteFluxMap
Eligible Flags (6):
Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 8/9 | Stable: 8/9 | HSDir: 7/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 | Partial (8/9 DA) | 880.0 Kbit/s – 3.8 Mbit/s (5 DA measured) 12.6 Mbit/s (4 DA relay-reported) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Stable | MTBF | Partial (6/9 DA) | Median: 9.0d (4/9 DA above threshold) Min/Max: 1.8d / 12492.5d (9/9 DA, Voting / Total Eligible) |
≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
| Uptime | Meets (9/9 DA) | 6.1d (R) | ≥5.2d - 5.3d (varies) (≥5/9 DA) | |
| HSDir | Prereq: Fast | Meets (8/9 DA) | 8/9 DA assigned Fast 880.0 Kbit/s – 3.8 Mbit/s (5 DA measured) 12.6 Mbit/s (4 DA relay-reported) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Meets (8/9 DA) | 8/9 DA assigned Stable | ≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| Uptime | Meets (9/9 DA) | 6.1d (R) | ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA) [Stricter] moria1: ≥98% WFU and ≥9.8d Time Known |
|
| Guard | Prereq: Fast | Meets (8/9 DA) | 8/9 DA assigned Fast 880.0 Kbit/s – 3.8 Mbit/s (5 DA measured) 12.6 Mbit/s (4 DA relay-reported) |
≥816.0 Kbit/s (AuthDirFastGuarantee, or the top-7/8 cutoff if lower) (≥5/9 DA) [Stricter] moria1: ≥8.4 Mbit/s |
| Prereq: Stable | Meets (8/9 DA) | 8/9 DA assigned Stable | ≥2.4d - 9.3d (varies) (≥5/9 DA) [Stricter] moria1: ≥7607.5d |
|
| Prereq: V2Dir | Meets (9/9 DA) | 9/9 DA assigned V2Dir | Tunnelled directory via ORPort or DirPort (≥5/9 DA) | |
| WFU | Partial (7/9 DA) | Median: 99.6% (7/9 DA above threshold) Min/Max: 96.1% / 100.0% (9/9 DA, Voting / Total Eligible) |
≥98%; dizum: ≥97.84099999999999% (≥5/9 DA) | |
| Time Known | Meets (9/9 DA) | Median: 16.9d (9/9 DA above threshold) Min/Max: 9.6d / 93.9d (9/9 DA, Voting / Total Eligible) |
≥8 days (≥5/9 DA) | |
| Bandwidth | Below (0/9 DA) | 880.0 Kbit/s – 3.8 Mbit/s (5 DA measured) 12.6 Mbit/s (4 DA relay-reported) |
≥16.8 Mbit/s (AuthDirGuardBWGuarantee) OR top 25% (≥80.0 Mbit/s-272.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-11-04 12:45:10).
Capacity (Relay Reported)
- Observed Bandwidth
- 12.61 Mbit/s
- Advertised Bandwidth
- 12.61 Mbit/s
- Rate Limit
- 8.59 Gbit/s
- Burst Limit
- 8.59 Gbit/s
- Total Data
-
69 TB
(5 years)
1mo: 1.7 TB | 6mo: 14 TB | 1y: 16 TB | 5y: 69 TB
Measurement (Directory Authority Verified)
Source: CollecTor — fetched 2026-11-04 12:45:10
- Measured By
-
5/7
Bandwidth Authorities
Not measured by: faravahar, longclaw - Consensus Weight
- 2.5 Mbit/s (median of 5 measurements)
- Measured Min / Max
- 880.0 Kbit/s / 3.8 Mbit/s
- Deviation
- 3.0 Mbit/s [Warning] High variation
Network Participation:
Consensus Weight:
0.0002% of network
(9th pctl)
|
Guard:
N/A |
Middle:
0.0005% (11th pctl) |
Exit:
N/A
History
Uptime Metrics
- Current Status
- UP 6d 2h 50m ago
- Overall Uptime (1M/6M/1Y/5Y)
- 100.0%/99.8%/99.9%/99.1%
- Flag Uptime (1M/6M/1Y/5Y)
- 99.9%/—/—/—
- Hibernating
- No
Timestamps
- First Seen
- 3y 3mo 1w ago (2023-07-27 00:00:00)
- Last Seen
- 2h 15m 38s ago (2026-11-04 11:00:00)
- Last Restarted
- 6d 2h 50m ago (2026-10-29 10:25:09)
- Last Changed Address
- 2026-04-06 23:00:00
Overload Status:
Not Overloaded — No overload conditions reported.
Evaluated 2026-11-04 13:15 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 19s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 5h 30m ago).
General Overload (from /details)
- Status
- No general overload report in available data
File Descriptor Exhaustion (from /bandwidth)
- Status
- No file-descriptor exhaustion report in available data
Rate Limits (from /bandwidth)
- Status
- No rate-limit report in available data
- Rate Limit
- —
- Burst Limit
- —
- Write counter
- —
- Read counter
- —
About these reports and MetricsPort
Allium’s eligibility windows are applied to the reported timestamps: 72 hours for general overload and file-descriptor exhaustion, 24 hours for a rate-limit hit. A report at the cutoff is historical. An older report can remain visible after Onionoo or Allium’s cache still has it. The cutoff does not prove the relay recovered at that moment. Allium caches the bandwidth document for 12 hours by default. The snapshot time is when Onionoo published that document. It is not the relay’s event time, and it is not necessarily the extra-info publication time. Cache age is how old Allium’s copy is.
MetricsPort counters are cumulative. Compare samples, and account for process restarts. A nonzero total alone does not show ongoing activity. Gauges describe current values. An unavailable metric is unknown, not zero. Allium does not have this relay’s MetricsPort readings and does not invent them.
The port below is an example for an endpoint you have already configured. MetricsPort must be enabled with restricted access and must not be exposed publicly. Setup stays in the Tor overload troubleshooting guide.
curl http://127.0.0.1:9035/metrics
History
Operator Identity
Source: AROI Validation API — 2026-11-04 04:00 UTC
- AROI Domain (?)
- Not specified
- Operator Validation
- Unvalidated
- This Relay
- N/A (no AROI configured)
- Contact
- gus@riseup.net
Family Configuration
- Family Support
- Both — Happy Families (20 / 100%) and MyFamily (0 / 0%) | View Full Family (16)
Happy Families (family-cert)
- Effective Members: 20
028BEF4A81578286BAA1352C73E4609B9915C687 308A2C8C276357C85D8060B9679881970D072CD4 50E9EF9E3B8BC9F4D4DA42533CB14897AB84B72F 531B3B0391A92F08376A4D5FAFAAC04009690FD1 58FE6772343FF6CD9E53D8B040A2CE495808E93D 6CF51BBB8E5B29DC6F6A225E1F3331414E6C38C8 70B0FD26318C6058D363059C69CAD9CE9CA587C1 73D5045F4AE50B224CABDADC339B5D101CF5A465 743EEE7D2CA078A8F30DDD1851C2142A156A4A83 83F02FD5FEA0B87A6FB18EEC52E3006766E1E92E 94330168CD85E5613C624FE462EC434B39221148 9C60AB34A7D8D5CA37DC9833F07E6EE104B5CC18 9E47303453F961132C2A59D2966F5A6EFA13B6A5 B158EB875A0729511607E307C1D8F27185547202 B9A1431A055F3E5A77AB123797D616407C5C15EC C6B6F625CF68D3884D5895E0C7A399ECF0C04CA8 D14B58EACE3EC7D1B367C881B85815B9E985BCE7 D2C61D214916E96DBD2E5105EA8FA002DC36ABDF DE15A1432DFB127B49F4C6FD9D48771683732995 (this relay) F439D39E25D3B5B042F7FEA554E384A83D21456D
MyFamily (legacy declarations)
- Effective Members: 0
- none
- Alleged Members: 13
-
(they don't list you back)
00E89DDEF944B42FD652F80C2480D5E20DF13194 (not in the network) 0EDB953238918AAED075123174053E85A3D711D5 (not in the network) 1DA888D47E43EDFCC60CBC0E1FDF0C8A43D64343 (not in the network) 32361A1EFDF684DAEDC8CA64843767A395F9EACE (not in the network) 4DB0490A0420809A8149E778BBAC8F1E9349D9EC (not in the network) 568E434F725B7828D17EF2B33C2F5CC84F18FCE3 (not in the network) B166FEAE2396CD3A4B94C7CF06D1539F172BA40F (not in the network) B4DBA14670B5F90B3565DFE7F6E29173489995C5 (not in the network) D17EF219FD037CE9338345E120F6A0DC519EBA1D (not in the network) D234FB04EC8CA6A7F5AC617140F9E0394C34A956 (not in the network) E9EE09B4AD43BB44EF6D328566F928F5818BC287 (not in the network) F4BDEDA20CE687FAC9387DA80224F5463947D83B (not in the network) FED2F5D81CCA06698E540A42038CB3D6AEF747C2 (not in the network)
- Indirect Members: 0
- none
DNS Health
Not an exit relay — DNS health testing does not apply.Last fetch was at Wed, 04 Nov 2026 13:15:37 GMT.
Data from Tor CollecTor (authority votes, fetched 2026-11-04 12:45:10).
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 (BW|T) | Guard BW (BW|Threshold) | Guard WFU (M|T) | Guard TK (M|T) | Stable MTBF (M|T) | Stable Uptime (Relay|T) | Desc Published | Cons Wt (Authority) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| bastet (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir | 2.3 Mbit/s (M) | 816.0 Kbit/s | 2.3 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 99.4% | 98% | 16.8d | 8d | 6.5d | 8.4d | 6.1d | 5.2d | 2026-11-04 05:25:15 | 2.3 Mbit/s (M) |
| dannenberg (DE) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir | 2.5 Mbit/s (M) | 816.0 Kbit/s | 2.5 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 93.9d | 8d | 93.9d | 9.3d | 6.1d | 5.3d | 2026-11-04 05:25:15 | 2.5 Mbit/s (M) |
| dizum (NL) | Yes | Yes | No | — | N | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir | 12.6 Mbit/s (R) | 816.0 Kbit/s | 12.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 96.1% | 98% | 15.4d | 8d | 9.0d | 6.7d | 6.1d | 5.3d | 2026-11-04 05:25:15 | 12.6 Mbit/s (R) |
| faravahar (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir | 12.6 Mbit/s (R) | 816.0 Kbit/s | 12.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.8% | 98% | 20.6d | 8d | 8.7d | 6.5d | 6.1d | 5.3d | 2026-11-04 05:25:15 | 12.6 Mbit/s (R) |
| gabelmoo (DE) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir | 3.8 Mbit/s (M) | 816.0 Kbit/s | 3.8 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s | 99.6% | 98% | 18.1d | 8d | 8.2d | 10.8d | 6.1d | 5.3d | 2026-11-04 05:25:15 | 3.8 Mbit/s (M) |
| longclaw (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir | 12.6 Mbit/s (R) | 816.0 Kbit/s | 12.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 99.9% | 98% | 16.9d | 8d | 11.3d | 10.9d | 6.1d | 5.3d | 2026-11-04 05:25:15 | 12.6 Mbit/s (R) |
| maatuska (SE) | Yes | Yes | No | — | N | Yes | Running, Valid, V2Dir, Fast | 12.6 Mbit/s (R) | 816.0 Kbit/s | 12.6 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s | 97.99% | 98% | 13.0d | 8d | 1.8d | 2.4d | 6.1d | 5.3d | 2026-11-04 05:25:15 | 12.6 Mbit/s (R) |
| moria1 (US) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Stable | 3.0 Mbit/s (M) | 8.4 Mbit/s | 3.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s | 99.3% | 98% | 9.6d | 8d | 12492.5d | 7607.5d | 6.1d | 5.3d | 2026-11-04 05:25:15 | 3.0 Mbit/s (M) |
| tor26 (AT) | Yes | Yes | No | — | Y | Yes | Running, Valid, V2Dir, Fast, Stable, HSDir | 880.0 Kbit/s (M) | 816.0 Kbit/s | 880.0 Kbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s | 100.0% | 98% | 45.9d | 8d | 45.0d | 10.6d | 6.1d | 5.3d | 2026-11-04 05:25:15 | 880.0 Kbit/s (M) |
N/T = this authority does not test IPv6 • — = not in this vote • Format: relay value | authority threshold • WFU = Weighted Fractional Uptime • TK = Time Known • Bandwidth source: (M) bandwidth-scanner measurement, (R) relay-reported, (U) unmeasured, counted as 0
Bandwidth Values Explained:
Measured (M) = An authority's bandwidth-scanner measurement of your relay (
Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (
Not published = The authority has no measurement of your relay in its vote and ignores relay-reported bandwidth, yet it voted Fast or its vote has no measurements at all: it judges your relay by a measurement kept from an earlier bandwidth file (0 if none), which its vote doesn't show.
Why different? A low measurement means the bandwidth scanners see your relay underperforming compared with other relays that report a similar speed. Votes list both values in kilobytes per second. Rules: Assigning flags in a vote, Computing a consensus.
Measured (M) = An authority's bandwidth-scanner measurement of your relay (
Measured= in its vote). An authority that has one uses it for the Fast and Guard flags, and the consensus weight is the median of these measurements when 3 or more authorities have one.Relay-reported (R) = The bandwidth your relay advertises: the lower of its observed bandwidth and its rate limit, capped at 10 MB/s (
Bandwidth= in every vote). An authority without a measurement uses it for flags, unless it has measurements for enough other relays (ignoring-advertised-bws=1); then your relay counts as 0 (U). It sets the consensus weight only when fewer than 3 authorities measured the relay, capped at 20 KB/s (maxunmeasuredbw) while 3 or more authorities publish measurements.Not published = The authority has no measurement of your relay in its vote and ignores relay-reported bandwidth, yet it voted Fast or its vote has no measurements at all: it judges your relay by a measurement kept from an earlier bandwidth file (0 if none), which its vote doesn't show.
Why different? A low measurement means the bandwidth scanners see your relay underperforming compared with other relays that report a similar speed. Votes list both values in kilobytes per second. Rules: Assigning flags in a vote, Computing a consensus.
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.