---
title: "HitKeep 2.3.1: Clearer System Status For Backups, Workers, And Rejected Traffic | HitKeep"
description: "HitKeep 2.3.1 improves System Status visibility for backup worker runs, degraded worker health, spam and rejected traffic counters, and managed cloud status links."
canonical: "https://hitkeep.com/blog/hitkeep-2-3-1/"
---

[← All posts](https://hitkeep.com/blog/)

# HitKeep 2.3.1: Clearer System Status For Backups, Workers, And Rejected Traffic

Published April 30, 2026·[Pascale Beier, HitKeep maintainer](https://github.com/pascalebeier)·2 min read

HitKeep 2.3.1 tightens the operational visibility added in 2.3.0. It is a small patch release for instance owners and cloud operators who rely on System Status to answer a simple question: is the instance healthy right now?

The release does not add a new analytics surface. It makes existing status data clearer for backups, worker connectivity, spam filtering, rejected ingest requests, and managed cloud operations.

## What changed

- **Backup worker status:** System Status now reports backup success, failures, recent failure count, last error, and next run time from the live backup worker.
- **Worker health:** leader instances now surface degraded NSQ worker connectivity instead of looking healthy when the producer is unavailable or failing.
- **Spam and rejection counters:** dropped spam hits, dropped spam events, rejected pageview ingest requests, rejected event ingest requests, and rejected AI fetch requests now increment system counters.
- **Managed cloud status link:** managed cloud admin settings now link directly to [status.hitkeep.com](https://status.hitkeep.com/) for hosted incident status.
- **Maintenance refreshes:** the release also includes Go dependency updates and refreshed dashboard screenshots.

![HitKeep System Status page showing health, runtime, enabled features, storage, tenant databases, and refreshable status cards](https://hitkeep.com/_astro/admin-system-status.C40SWcBN_ZkQaFi.webp)

HitKeep 2.3.1 makes the System Status data behind this view more complete for operational checks.

## Upgrade guidance

All 2.3.0 operators should upgrade to 2.3.1. The update is especially useful for:

- managed cloud deployments
- instances using automatic S3 or filesystem backups
- high-traffic self-hosted instances where rejected or spam traffic should be visible
- clustered deployments where worker health needs to be explicit

Use the normal release artifacts from GitHub. There are no extra migration steps for this patch.

## Read more

- [System Status and Settings](https://hitkeep.com/guides/admin/system-administration/)
- [Bot and Spam Filtering](https://hitkeep.com/guides/tracking/spam-filtering/)
- [HitKeep 2.3.0 release post](https://hitkeep.com/blog/hitkeep-2-3-0/)
- [Changelog](https://hitkeep.com/changelog/)
- [GitHub Release v2.3.1](https://github.com/PascaleBeier/hitkeep/releases/tag/v2.3.1)

Managed option

## Run HitKeep without the ops burden.

HitKeep Cloud runs the same single binary in region-pinned EU or US infrastructure, with managed updates and backups.

[Start free in HitKeep Cloud](https://cloud.hitkeep.eu/signup?utm_source=hitkeep_docs&utm_medium=website&utm_campaign=cloud_signup&utm_content=content_cta&plan=free&billing=monthly)[Self-host instead](https://hitkeep.com/guides/installation/)

[← OlderHitKeep 2.3.0: MCP, WordPress, More Events, Installation & Activation Center](https://hitkeep.com/blog/hitkeep-2-3-0/)[Newer →HitKeep 2.4.0: Imports, Search Console, MCP Reporting, Server-Side Ingest, And Dutch Localization](https://hitkeep.com/blog/hitkeep-2-4-0/)