View Relay "0x1ea7deadbeef"

Fingerprint: F475E5987E44A2B7B143A2BEE3F8128EEFD7E5A3 | Family: 1 relay | <1ea7deadbeef AT posteo dot net> | AS197540 | Germany | Linux

Health Status

Consensus
In Consensus (9/9 Directory Auths)
Flags
Running, Valid, V2Dir, Fast, Stable, HSDir, Guard (7)
BW Verified
5/7 BW Auths Measured 264 Mbit/s Median
Stability
Overloaded | UP 6d 11h 13m ago | UP 99% (1M)
Reachability
IPv4: 9/9 | v6: 8/8(Directory Auths)
First Seen
8y 1mo 1w ago
BW Weight
0.02% of Network | 162 Mbit/s Observed By Relay
Version
0.4.9.15 Recommended
Issues Detected:
  • Write Bandwidth Limit Hit : Write rate-limit counter is 3,628 (configured rate 167.77 Mbit/s). Read and write counters increment at most once per minute per direction. They are not a count of blocked connections, the duration of throttling, or necessarily the number of events in the last 24 hours.
    Suggestion: Inspect BandwidthRate and BandwidthBurst (the values reported with this hit), any relay-specific caps such as RelayBandwidthRate and RelayBandwidthBurst, the intended bandwidth budget, and actual uplink headroom. A rate-limit report is not evidence of ISP throttling. After checking that evidence and the capacity you meant to offer, review whether those limits should change. MetricsPort: tor_relay_load_global_rate_limit_reached_total{side="read"} and {side="write"}. Increases indicate additional global token-bucket limit events.
  • Read Bandwidth Limit Hit : Read rate-limit counter is 4 (configured rate 167.77 Mbit/s). Read and write counters increment at most once per minute per direction. They are not a count of blocked connections, the duration of throttling, or necessarily the number of events in the last 24 hours.
    Suggestion: Inspect BandwidthRate and BandwidthBurst (the values reported with this hit), any relay-specific caps such as RelayBandwidthRate and RelayBandwidthBurst, the intended bandwidth budget, and actual uplink headroom. A rate-limit report is not evidence of ISP throttling. After checking that evidence and the capacity you meant to offer, review whether those limits should change. MetricsPort: tor_relay_load_global_rate_limit_reached_total{side="read"} and {side="write"}. Increases indicate additional global token-bucket limit events.
Notes:
  • Rate Limit Configuration: Configured limits: Rate=167.77 Mbit/s, Burst=25 MB. Counters: Write=3,628, Read=4. These values are BandwidthRate and BandwidthBurst from the extra-info descriptor. RelayBandwidthRate and RelayBandwidthBurst are additional torrc caps, not the names of these values. Burst is a quantity of bytes.
    Suggestion: Inspect BandwidthRate and BandwidthBurst (the values reported with this hit), any relay-specific caps such as RelayBandwidthRate and RelayBandwidthBurst, the intended bandwidth budget, and actual uplink headroom. A rate-limit report is not evidence of ISP throttling. After checking that evidence and the capacity you meant to offer, review whether those limits should change. MetricsPort: tor_relay_load_global_rate_limit_reached_total{side=&quot;read&quot;} and {side=&quot;write&quot;}. Increases indicate additional global token-bucket limit events.

Connectivity and Location

Addresses
OR Address
tor-exit-node.1ea7deadbeef.de
45.90.4.235:9001
[2a03:4000:58:7d:de1:ea7:dead:beef]:9090
Reachability (Directory Authorities)
IPv4
9/9
IPv6
8/8 (1 don't test)
Location
Country
Germany Germany
Interactive Map
View in RouteFluxMap
Autonomous System
AS Number
AS197540
AS Name
netcup GmbH (BGP.tools)
AS Rarity
Common (score: 0/5, 3.93% consensus weight, 174 operators)

Flags and Eligibility

Current Flags (7): Running, Valid, V2Dir, Fast, Stable, HSDir, Guard
Eligible Flags (7): Running: 9/9 | Valid: 9/9 | V2Dir: 9/9 | Fast: 9/9 | Stable: 9/9 | HSDir: 9/9 | Guard: 9/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 (8/8 DA) 8/8 tested authorities reached relay ≥5/8 tested (majority) (≥5/8 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) 184.0 Mbit/s – 312.0 Mbit/s (5 DA measured)
80.0 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 (7/9 DA) Median: 19.5d (6/9 DA above threshold)
Min/Max: 3.4d / 2142.5d (9/9 DA, Voting / Total Eligible)		 ≥2.3d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.9d
Uptime Meets (9/9 DA) 6.5d (R) ≥5.2d - 5.3d (varies) (≥5/9 DA)
HSDir Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
184.0 Mbit/s – 312.0 Mbit/s (5 DA measured)
80.0 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 (9/9 DA) 9/9 DA assigned Stable ≥2.3d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.9d
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.5d (R) ≥96h as each authority sees it (MinUptimeHidServDirectoryV2) (≥5/9 DA)
[Stricter] moria1: ≥98% WFU and ≥9.8d Time Known
Guard Prereq: Fast Meets (9/9 DA) 9/9 DA assigned Fast
184.0 Mbit/s – 312.0 Mbit/s (5 DA measured)
80.0 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 (9/9 DA) 9/9 DA assigned Stable ≥2.3d - 9.3d (varies) (≥5/9 DA)
[Stricter] moria1: ≥7607.9d
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) Median: 99.9% (9/9 DA above threshold)
Min/Max: 98.5% / 100.0% (9/9 DA, Voting / Total Eligible)		 ≥98%; dizum: ≥97.774% (≥5/9 DA)
Time Known Meets (9/9 DA) Median: 21.7d (9/9 DA above threshold)
Min/Max: 9.9d / 31.2d (9/9 DA, Voting / Total Eligible)		 ≥8 days (≥5/9 DA)
Bandwidth Meets (9/9 DA) 184.0 Mbit/s – 312.0 Mbit/s (5 DA measured)
80.0 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 11:15:19).

Bandwidth Metrics

Capacity (Relay Reported)
Observed Bandwidth
162.77 Mbit/s
Advertised Bandwidth
162.77 Mbit/s
Rate Limit
167.77 Mbit/s
Burst Limit
201.33 Mbit/s
Total Data
3.5 PB (5 years)
1mo: 81 TB | 6mo: 465 TB | 1y: 882 TB | 5y: 3.5 PB
Measurement (Directory Authority Verified)

Source: CollecTor — fetched 2026-11-04 11:15:19

Measured By
5/7 Bandwidth Authorities
Not measured by: faravahar, longclaw
Consensus Weight
264.0 Mbit/s (median of 5 measurements)
Measured Min / Max
184.0 Mbit/s / 312.0 Mbit/s
Network Participation: Consensus Weight: 0.0167% of network (79th pctl) | Guard: 0.0350% (70th pctl) | Middle: 0.0132% (72th pctl) | Exit: N/A
History
Throughput and write/read, last 6 months Throughput and write/read, last year Throughput and write/read, last 5 years Throughput and write/read, last 30 days
1M 6M 1Y 5Y

Uptime and Stability

Uptime Metrics
Current Status
UP 6d 11h 13m ago
Overall Uptime (1M/6M/1Y/5Y)
99.7%/99.8%/99.9%/99.8%
Flag Uptime (1M/6M/1Y/5Y)
—/—/—/99.4%
Hibernating
No
Timestamps
First Seen
8y 1mo 1w ago (2018-09-28 20:00:00)
Last Seen
1h 15m 40s ago (2026-11-04 11:00:00)
Last Restarted
6d 11h 13m ago (2026-10-29 01:02:31)
Last Changed Address
2026-04-06 23:00:00
[Warning] OVERLOADED — Rate limits hit W:3,628 R:4 (limit: 167.77 Mbit/s)

Evaluated 2026-11-04 12:15 UTC. /details snapshot 2026-11-04 11:00:00 UTC (cached 25s ago). /bandwidth snapshot 2026-11-04 05:00:00 UTC (cached 4h 30m ago).

Reported timestamps use hour precision, so the displayed minute is not an exact incident time.

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
Reported
Rate Limit
167.77 Mbit/s
Burst Limit
25 MB
Write counter
3,628
Read counter
4
Reported
2026-11-03 23:00 UTC (13 hours ago)

Read and write counters increment at most once per minute per direction. They are not a count of blocked connections, the duration of throttling, or necessarily the number of events in the last 24 hours. Rate is BandwidthRate and follows this site’s bits/bytes setting. Burst is BandwidthBurst, already a byte quantity. RelayBandwidthRate and RelayBandwidthBurst are extra torrc caps, not the names of these values. A hit stays eligible for 24 hours.

What to check
  • Configured bandwidth limits
    Inspect BandwidthRate and BandwidthBurst (the values reported with this hit), any relay-specific caps such as RelayBandwidthRate and RelayBandwidthBurst, the intended bandwidth budget, and actual uplink headroom. A rate-limit report is not evidence of ISP throttling. After checking that evidence and the capacity you meant to offer, review whether those limits should change.
    MetricsPort: tor_relay_load_global_rate_limit_reached_total{side="read"} and {side="write"} — Increases indicate additional global token-bucket limit events.
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
Uptime, last 6 months Uptime, last year Uptime, last 5 years Uptime, last 30 days
1M 6M 1Y 5Y

Operator and Family

Operator Identity

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

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

Software and Version

Platform
Linux — Tor 0.4.9.15 on Linux
Version
0.4.9.15 — Recommended
Version Status
Recommended

Exit Health & Policy

DNS Health
Not an exit relay — DNS health testing does not apply.
IPv4 Exit Policy Summary
accept: 
  23
  43
  53
  88
  110
  143
  194
  220
  464
  531
  543-544
  563
  902-904
  989-995
  1194
  1220
  1293
  1500
  1533
  1677
  1723
  4321
  5222-5223
  5228
  5900
  6660-6669
  6679
  6697
  8082
  8332-8333
  9418
  10000
  11371
  14265
  50002
IPv6 Exit Policy Summary
accept: 
  23
  43
  53
  88
  110
  143
  194
  220
  464
  531
  543-544
  563
  902-904
  989-995
  1194
  1220
  1293
  1500
  1533
  1677
  1723
  4321
  5222-5223
  5228
  5900
  6660-6669
  6679
  6697
  8008
  8332-8333
  9418
  10000
  11371
  14265
  50002
Full Exit Policy
reject 0.0.0.0/8:*
reject 169.254.0.0/16:*
reject 127.0.0.0/8:*
reject 192.168.0.0/16:*
reject 10.0.0.0/8:*
reject 172.16.0.0/12:*
reject 45.90.4.235:*
accept *:23
accept *:43
accept *:53
accept *:88
accept *:110
accept *:143
accept *:194
accept *:220
accept *:464
accept *:531
accept *:543-544
accept *:563
accept *:902-904
accept *:989-995
accept *:1194
accept *:1220
accept *:1293
accept *:1500
accept *:1533
accept *:1677
accept *:1723
accept *:4321
accept *:5222-5223
accept *:5228
accept *:5900
accept *:6660-6669
accept *:6679
accept *:6697
accept *:8082
accept *:8332-8333
accept *:9418
accept *:10000
accept *:11371
accept *:50002
accept *:14265
reject *:*

Last fetch was at Wed, 04 Nov 2026 12:15:39 GMT.

Consensus Evaluation

Data from Tor CollecTor (authority votes, fetched 2026-11-04 11:15:19).

Per-Authority Details

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 v6 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 Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 184.0 Mbit/s (M) | 816.0 Kbit/s 184.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 99.8% | 98% 19.0d | 8d 13.7d | 8.4d 6.5d | 5.2d 2026-11-04 01:02:52 184.0 Mbit/s (M)
dannenberg (DE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 312.0 Mbit/s (M) | 816.0 Kbit/s 312.0 Mbit/s (M) | 272.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 30.3d | 8d 19.5d | 9.3d 6.5d | 5.3d 2026-11-04 01:02:52 312.0 Mbit/s (M)
dizum (NL) Yes Yes No — N Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 98.5% | 98% 19.2d | 8d 6.3d | 6.7d 6.5d | 5.3d 2026-11-04 01:02:52 80.0 Mbit/s (R)
faravahar (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.9% | 98% 21.7d | 8d 8.7d | 6.5d 6.5d | 5.3d 2026-11-04 01:02:52 80.0 Mbit/s (R)
gabelmoo (DE) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 272.0 Mbit/s (M) | 816.0 Kbit/s 272.0 Mbit/s (M) | 248.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 31.2d | 8d 27.9d | 10.7d 6.5d | 5.3d 2026-11-04 01:02:52 272.0 Mbit/s (M)
longclaw (US) Yes Yes No — Y Yes N/T Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 31.1d | 8d 27.9d | 10.9d 6.5d | 5.3d 2026-11-04 01:02:52 80.0 Mbit/s (R)
maatuska (SE) Yes Yes No — N Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 80.0 Mbit/s (R) | 816.0 Kbit/s 80.0 Mbit/s (R) | 80.0 Mbit/s OR 16.8 Mbit/s 99.1% | 98% 20.0d | 8d 3.4d | 2.3d 6.5d | 5.3d 2026-11-04 01:02:52 80.0 Mbit/s (R)
moria1 (US) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 208.0 Mbit/s (M) | 8.4 Mbit/s 208.0 Mbit/s (M) | 192.0 Mbit/s OR 16.8 Mbit/s 99.9% | 98% 9.9d | 8d 2142.5d | 7607.9d 6.5d | 5.3d 2026-11-04 01:02:52 208.0 Mbit/s (M)
tor26 (AT) Yes Yes No — Y Yes Yes Running, Valid, V2Dir, Fast, Stable, HSDir, Guard 264.0 Mbit/s (M) | 816.0 Kbit/s 264.0 Mbit/s (M) | 256.0 Mbit/s OR 16.8 Mbit/s 100.0% | 98% 31.1d | 8d 27.9d | 10.6d 6.5d | 5.3d 2026-11-04 01:02:52 264.0 Mbit/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 (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.