Pulse - Public Status Page

When a node goes down, customers look for a status page. If you do not have one, they open tickets instead. Pulse publishes node up/down, overall health and per-node load to a public page served by your own panel — no separate service to run, no extra host to pay for.

DEMO: http://5.10.220.249/extensions/pulse

The page lives at /extensions/pulse on your panel. Point status.yourdomain at it and you have a status page on your own domain in a couple of minutes.

WHAT YOU CONTROL

• Which nodes are published — a whitelist, so nodes you would rather not show stay invisible
• Optional grouping, so several nodes appear as one service line (“EU Servers”, “Web”) instead of raw node names
• An incident banner with a level, a title and a message, for when something is going on and you want to say so before the tickets arrive
• Branding: page title, description, accent colour, an optional logo and a footer line
• Refresh interval
• A master switch that takes the page offline entirely

WHAT IS PUBLISHED

Only the nodes you ticked, and only display values: the name you gave the node, whether it is up, and load as a percentage. Node FQDNs, IP addresses, ports, tokens and server counts are never in the page or in the JSON behind it. The same data is available at /extensions/pulse/status.json if you want to drive something else with it.

**SUPPORT: https://t.me/whoisfazil

• Fully supported. Missing something, or have an idea for it? Tell me — feature requests are welcome. Run into a problem? Message me on Telegram and I will get you a fix.

• Rate the product however you see fit, but if something is broken please tell me about it directly too — a review alone does not tell me what went wrong on your setup, and I cannot fix what I do not know about.**

Requires Pterodactyl with Blueprint.