What we shipped in Uptimecheck, newest first: new features, improvements, fixes and security updates to monitoring, alerts and status pages.
Every status page now has a history page at /s/<name>/history. It lists the incidents you wrote, with all their updates and impact, and the outages our checks detected, with their incident report.
Incidents are grouped by month in UTC, 20 to a page, and go back as far as your plan keeps history.
When you report an incident, you can now set Degraded performance, Partial outage or Major outage for each component it affects. The status page, badge, widget and summary.json show the worse of your choice and what our checks see, so a confirmed outage is never hidden.
The REST API and the MCP server take the same impacts.
Maintenance windows that haven’t ended can now be edited, and so can recurring series. A window that is running keeps its start, and a series changes from its next window on.
Subscribers who were told about a window get a “Maintenance moved” notice with the new and the old time, in all 9 status page languages. The REST API can change windows too, and the MCP server can list and update them.
A new monitor now offers to send a test alert until one of your channels has delivered one, and the getting-started checklist has a “Send yourself a test alert” step. It is the quickest way to know an alert will reach you before the first real outage does.
A new free tool at /tools/uptime-calculator/ turns an SLA into allowed downtime per day, week, month, quarter and year, or turns your downtime into an uptime percentage. 99.9% allows 43m 49s of downtime a month. Every result has its own link to share, and it works without JavaScript.
Read more: What Does 99.9% Uptime Mean? SLA Downtime Explained
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.
Next to email and password, email links and Google, you can now sign in with GitHub. A sign-in through GitHub or Google only works when that provider has confirmed your email address.
Domain monitors now look up your own mail servers, the addresses in your SPF record and your MX hosts, in SpamCop, PSBL and UCEPROTECT level 1. When one is listed, you get an alert through your usual channels.
Incidents now explain the likely cause in plain words, worked out from the failing response by fixed rules. You see it on the incident page and in the monitor’s incident box, and as a line in the alert when the cause is clear.
Alerts can now go out by SMS to phone numbers in the EU/EEA, the UK and Switzerland. Professional includes 50 SMS credits a month and Business 200. On any plan you can buy packs of 100 credits for €12 or 500 for €50.
app.uptimecheck.com is now our own app, built and hosted in Stockholm: ten monitor types, incidents with evidence, on-call schedules, status pages with cookie-free visitor statistics, and client dashboards, at fixed prices in euros.
Try every feature in the live demo, a made-up shop called Nordhem with 90 days of history, without signing up.
Set up your first monitor in under a minute, or look around the live demo first.
14-day free trial · No credit card required
With your OK, Google Analytics and Microsoft Clarity show us which pages help and where visitors get stuck. They set cookies for up to 13 months. Without your OK, neither of them runs. You can change your mind at any time under Cookie settings at the bottom of the page. Privacy policy