Lantern
Service Status & Diagnostics
Updating...
Analyzing…
Fetching latest service data
Uptime --%
Latency --
Overall Uptime
--%
Last 7 days average
Active Incidents
--
Services currently down or degraded
Avg Response
--
Across the last 30 checks per service
Services 0
⌘K
Source
Status
Service Name UP
Service Group
Organize services into stacks (e.g. media, networking)
Maintenance Mode
Suppress alerts and mark as under maintenance
TimeStatusMessage
Dashboard Settings
Default
Renames and re-logos the header on this dashboard and the public status page. Leave a field blank to keep Lantern's default. Custom domains are handled by your reverse proxy, not here.
Hex color. Only a default — anyone who has picked their own accent above keeps it.
Pins a notice to the top of this dashboard and the public status page. Anyone can read it, no sign-in needed. Publishing replaces whatever is currently showing.
Download a consistent snapshot of the full database (all services, history, settings, and webhook configs). See the README for how to restore it.
Only needed if LANTERN_AUTH_TOKEN or basic auth is configured on the server. Stored in this browser only, sent as an Authorization header on admin actions (maintenance, groups, webhooks, monitors, Docker controls).
Discord, Telegram, Gotify and generic endpoints for status-change notifications.
Silence or batch every service's notifications during a daily window, instead of each status change firing immediately. Independent of per-service maintenance mode.
No deliveries yet.
Optional: have Lantern check a service itself (HTTP, TCP, or ping) on a schedule, instead of waiting for it to push its own status.
No active monitors configured.
Owner runs the install and manages accounts. Admin can do everything except manage accounts. Viewer can only look — no changes, and no access to backups, webhook URLs, config export or the audit log.
Loading…
Diagnostics
Filter: