The offline alert

The offline alert is the simplest and most important alert. It tells you when your server has stopped responding for long enough that it is likely down, not just momentarily unreachable.

What triggers it

The alert fires when clan.me has not received a heartbeat from your plugin for about 3 minutes. Since the plugin sends a heartbeat every 60 seconds by default, that means roughly three missed heartbeats in a row before the alert sends. The delay is intentional: brief network blips and quick restarts usually recover within a heartbeat or two, so waiting a few cycles avoids alerting on planned restarts and transient connectivity issues.

A missed heartbeat vs going offline

A single missed heartbeat is not an alert. clan.me waits for about 3 minutes of silence before sending the offline alert, and if the silence continues to 5 minutes your server's status flips to "offline" on its public page and dashboard. Brief gaps are expected and do not trigger a notification.

If your server restarts frequently, you may want to suppress the offline alert during known maintenance windows. This is available from the Alerts settings in your dashboard: set a maintenance window and alerts will be paused for that period.

What the alert contains

The email includes the context from the last successful heartbeat before the server went silent:

• Last known TPS and MSPT
• Last known player count and player list
• Last known heap usage
• Time since last heartbeat

The last-known TPS and memory values are useful for diagnosing whether the server crashed under load, with low TPS or high memory just before going silent, or stopped unexpectedly while performing normally, which suggests an external cause like a host issue or a scheduled task killing the process.