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. See when an alert channel stops delivering

    Every alert channel now shows whether its alerts arrived over the last 30 days. A failed alert is retried five times over about 40 minutes. After that the channel shows Not delivering with the reason: at the top of the overview, on the monitors that use it and in the weekly report.

    Fix the channel and press Send test. A test that gets through clears the warning.

    Read more: Alerts and notifications

  2. 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

  3. Stricter checks on private network addresses

    Monitors and our free website checker refuse addresses that point into private networks or a cloud provider’s metadata service. We closed a gap where one way of writing an IPv6 address could get past that check.

  4. 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

  5. A new overview, and a shorter menu

    The workspace overview now opens with one sentence about where things stand. Below it: Needs you now, with Acknowledge buttons; Worth a look, for things like a certificate about to expire; your services with response times against last week; and the week’s uptime. The services you depend on are listed under Your providers and don’t count toward your own uptime.

    The menu is shorter too: Monitoring holds Overview, Monitors and Incidents, and Reports and Maintenance sit under Workspace.

    Read more: How to try Uptimecheck without signing up

  6. Paused time and gaps no longer count as uptime

    Time when a monitor was paused, when a workspace wasn’t active, or when our checks didn’t run is no longer counted as up. It shows as gray “no data” instead: in the app, on status pages, in client reports and emails, and in the API and MCP server.

    Read more: Uptime monitoring

  7. Status pages update at once, and templates for status updates

    A status page now changes the moment an incident opens or closes, and notices to subscribers are sent again if a first try fails.

    Save the updates you write often as templates for the workspace and pick one from the Templates menu when you post. {components} is replaced with the components you chose.

    Read more: Status pages

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.

14-day free trial · Then free on 5 monitors · No credit card