LoggerBot Status
Real-time monitoring of LoggerBot's systems and services
Over a few hours the bot and dashboard restarted repeatedly when the hosting instance ran out of memory, causing brief gaps in logging and dashboard availability. LoggerBot was moved to a larger instance and has been stable since.
Affected components
Some servers saw their logging channels and other settings roll back to a previous state. Three separate causes were identified and fixed: saves are now written atomically, the shared settings store can no longer be replaced by a stale in-memory copy, and a background task no longer holds an outdated snapshot across its run.
Affected components
Kick events did not generate a log embed because a required gateway option was missing. The option was enabled and kick logging works again.
Affected components
The settings store was overwritten, wiping per-server configuration, Pro license records and staff roles. Server configuration was restored from backups over the following days and the Pro licensing system was rebuilt. Timestamped backups now run every 15 minutes.
Affected components