This briefing has not refreshed recently, so what you see may be out of date.
✓Healthy
Everything is operating normally.
6 of 6 services are healthy and mirrored; 7 of 7 fleet nodes are reporting; the last backup finished 6.8 hours ago.
A self-hosted, multi-node platform: every public service runs on a primary and a mirror behind automatic DNS failover, FluxCD keeps configuration in line with its Git repository, each node repairs any drift between its nftables firewall and CrowdSec's ban decisions, and a decision engine escalates repeat offenders from the shared threat feed to 24-hour and then 14-day bans across the whole fleet. This page is generated from the platform's own APIs and explains, in one place, what is running and what changed.
Services healthy
6/6
all with a live mirror and DNS failover
Fleet nodes reporting
7/7
263 active bans, ban lists in sync
Since last backup
6.8 h
Triton · 5.27 GB · 35.28 s · 12/12 recent runs ok
Bans yesterday
252
a typical day (median 169)
Firewall self-heal, 24h
100%
200 drifts detected, 0 unresolved
What changed last 7 days
Tracking began . Nothing has changed since.
Needs attention
✓ Nothing needs attention.
Services
Service
Primary
Mirror
Serving
Threatsthreats.beane.me
✓Up
✓Up
Primary
Intelintel.beane.me
✓Up
✓Up
Primary
Backupsbackups.beane.me
✓Up
✓Up
Primary
Observeobserve.beane.me
✓Up
✓Up
Primary
Vulnvuln.beane.me
✓Up
✓Up
Primary
Portfoliobeane.me
✓Up
✓Up
Primary
Each service runs on a primary and a mirror; DNS moves to the mirror automatically if the primary fails.
Threat picture
The 25 most recent distinct threats from CrowdSec, reaching back 7.7 h, seen by 6 nodes. Severity reflects the techniques a source attempted.
By severity
Critical7
High8
Low10
By technique (MITRE ATT&CK)
Exploit public-facing application T119015
Active scanning T159511
Ingress tool transfer T11053
Command & scripting interpreter T10593
1 group of sources share a network block, which usually means one actor.
Bans per day, last 30 days
The tallest bar is clipped so normal days stay readable. The line marks the median day (169). The pale bar is today, still in progress.
View as table
Date
Bans
Oct 6
146 (so far)
Oct 5
252
Oct 4
246
Oct 3
113
Oct 2
238
Oct 1
269
Sep 30
205
Sep 29
179
Sep 28
104
Sep 27
156
Sep 26
128
Sep 25
159
Sep 24
107
Sep 23
345
Sep 22
334
Sep 21
306
Sep 20
339
Sep 19
112
Sep 18
200
Sep 17
234
Sep 16
189
Sep 15
49,564
Sep 14
67
Sep 13
136
Sep 12
146
Sep 11
158
Sep 10
73
Sep 9
107
Sep 8
64
Sep 7
171
Decision engine, active now
14-day ban250
24-hour ban21
Watching189
New in the last 24 hours: 10 14-day bans, 21 24-hour bans, 20 watching.
Most common reasons, last 24 hours
Single node only30
Low scenario volume19
High severity single node17
Fleet
Ares✓Healthy · seen 15 min ago
Argus✓Healthy · seen 20 min ago
Hermes✓Healthy · seen 15 min ago
Iris✓Healthy · seen 19 min ago
Triton✓Healthy · seen 23 min ago
Vault✓Healthy · seen 16 min ago
Zephyrus✓Healthy · seen 16 min ago
Each node continuously compares its nftables firewall with CrowdSec's ban decisions and repairs any mismatch: 200 mismatches were detected and 200 repaired in the last 24 hours.