This briefing has not refreshed recently, so what you see may be out of date.
✓Healthy
Everything is operating normally.
7 of 7 services are healthy and mirrored; 7 of 7 fleet nodes are reporting; 3 of 3 backups are on schedule. 3 items to watch.
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.
Each node continuously compares its nftables firewall with CrowdSec's ban decisions and repairs any mismatch: 190 mismatches were detected and 190 repaired in the last 24 hours.
Backups and recovery
Node
Last backup
Verification
Restore test
Triton
✓2.3 h ago5.28 GB, about every 8 h
✓Verified 18 h agofull data check 9 d ago
✓Passed 9 d ago11 passed
Ares
✓6.3 h ago1.23 GB, about every 8 h
–
–
Zephyrus
✓12 h ago782 MB, about every 12 h
✓Verified 18 h agofull data check 9 d ago
✓Passed 9 d ago11 passed
Verification checks repository integrity. A restore test restores a backup and checks its hashes and contents. A dash means that check is not set up for the node yet.
Software updates
2updates availableplus 3 held back, waiting on upstream
2patch and minoroldest released 22 h ago
0major, breakingneed a planned migration
Renovate checks container and chart versions against upstream releases (last scan ). Updates are reviewed and merged by hand. Package names are deliberately not published.
Change delivery
GitOps
✓ Healthy3 of 3 clusters reconciled
0failing now
15 minsince the last change
✓Ares✓Triton✓Zephyrus
Flux reconciles each cluster from its Git repository. Failing now counts resources that were not ready at the last check (last check ).
CI
✓ Green5 of 5 repos green on main
97%pass rate, 239 runs in 7 days
15 smedian run on main
Pushes and pull requests across my private repositories. The pass rate leaves out cancelled runs, and only the default branch decides whether CI is failing. Last run .
Engineering activity
30of 30 days active
Commits across my repositories, last 30 days. The pale bar is today so far, as of 1:50 PM. Over the last year: 249 of 364 days.