Put a public status page on a Pingstack subdomain like acme.pingstackhosted.com, or on a hostname you own like status.example.com. Subdomains work right away. For your own domain, add a TXT record and a CNAME, and Pingstack checks them for you every few minutes. Available on Pro, Team and Business. Status pages
What's new
Add Pingstack's bot to your Discord server and send incident alerts, recoveries and weekly summaries to the channels you choose. Available on every plan. Discord
Report failed jobs and track run times
Heartbeat checks now accept a failure signal at /fail, so a job that knows it failed opens an incident right away instead of waiting for its deadline. Send /start when a job begins to see how long each run took, and spot failed runs in red in the check's recent results. Cron job monitoring
Post incident alerts and recoveries as cards in a Microsoft Teams channel, using a Teams Workflows webhook with no app to install. Available on every plan. Microsoft Teams
Choose incident severity and priority
Choose PagerDuty severity and Jira Service Management priority separately for down, late and degraded checks. That way alerts land at the level your team already uses.
Pingstack now sends incidents to Jira Service Management, adds updates as a check's status changes, and closes the alert when the check recovers. Available on Team and Business plans.
Open a Jira issue for each incident, add comments as it changes, and move it to a status such as Done when the check recovers. Pick the project, issue type and recovery status from your own Jira instead of typing them. Available on Team and Business plans. Jira tickets
Pingstack now sends incidents to PagerDuty and keeps updating the same alert as a check's status changes. The alert resolves on its own when the check recovers. Available on Team and Business plans.
Start Zaps when checks go down or incidents open, and let Zaps send heartbeats, pause checks or post incident updates. Connect it from the Zapier card on the Channels page, on every plan. Zapier
Simpler API key management
All your API access now lives under one set of API keys. MCP connections you approved in the browser get their own list, and you can review or disconnect them from MCP Connections.