Skip to content
Pingwell

Changelog

What shipped, newest first.

  1. A redesigned control panel

    A new Overview with your fleet’s uptime and response times, a first-run checklist, and ⌘K to jump anywhere or create anything. Every screen moved onto one design system with light and dark themes, and an accessibility pass took each one to a full Lighthouse accessibility score.

  2. Status pages

    Status pages that follow your monitors and heartbeats, with incidents and scheduled maintenance. They are published to the edge, so they stay up when your servers don’t. Pro and Unlimited add password-protected pages and pages on your own domain.

  3. Alerting

    Alerts go to email, Slack, Discord, Telegram and signed webhooks, and each monitor and heartbeat picks its channels. Degraded and late wait two minutes and go only if still true, recoveries reach only the channels that heard of the problem, and failed deliveries are retried and listed on the channel’s page.

  4. Uptime monitors

    HTTP and TCP monitors, checked from up to eight regions. HTTP checks take a method, the status codes you expect, headers, a body, a timeout and a keyword that must or must not appear. A failure is checked again from up to two more regions before it counts, and each monitor keeps its response times per region.

  5. Heartbeats

    Cron jobs and workers can now report in. Each heartbeat has a ping URL with start, fail and exit-code variants, a period and a grace. A heartbeat goes late when a ping is overdue and down when the grace runs out too, and a failed run keeps the output it sent.