Start free trial

What we shipped.

What we shipped in Uptimecheck, newest first: new features, improvements, fixes and security updates to monitoring, alerts and status pages.

October 2026

  1. Fixed , link to this entry

    A closing notice when maintenance, pausing or deleting ends an incident

    An incident that ended because a maintenance window started, or because someone paused, changed the address of or deleted a monitor that was down, used to close silently. Slack and email never heard it was over, and the PagerDuty incident stayed open.

    Now every channel that got the down alert gets a notice that says why the incident closed, and PagerDuty resolves it.

    Read more: How to connect PagerDuty, Google Chat, ntfy and more

  2. Fixed , link to this entry

    No false alerts for cron jobs and servers after a gap in our checks

    When our own monitoring had a gap, cron job and server monitors could alert as soon as it ended. They now pause during the gap and start their clock again when it ends.

    Alerts also go out six at a time instead of one by one, so a single slow webhook can no longer hold up the rest.

    Read more: Cron job monitoring

Follow along Every change lands in our feed as it ships.

Downtime is obsolete.

Set up your first monitor in under a minute, or look around the live demo first.

Start free trial Compare plans

14-day free trial · No credit card required