What we shipped in Uptimecheck, newest first: new features, improvements, fixes and security updates to monitoring, alerts and status pages.
The HTTP headers checker shows the response headers of any URL, judges six security headers and shows where the time went. The open port checker tells you whether a port on a host answers from the internet.
SMS alerts now work on every paid plan. Start has no monthly credits, so it sends with credits you buy; Professional still includes 50 a month and Business 200. Packs work on any plan: 100 credits for €12, as before, and 500 for €55. The 500 pack cost €50 until now. Prices exclude VAT.
A workspace now sends at most 100 SMS in any 24 hours, alerts and tests together, so a flapping monitor can’t run through your credits. Past the limit nothing is sent and no credit is used, the incident timeline says why, and the workspace owners get an email, at most once a day.
The new integrations section has a page for each of the 13 alert channels, from Slack and Microsoft Teams to SMS, ntfy and webhooks, and one for the MCP server. Each page shows what an alert looks like there, how to connect it and which help articles go with it.
Setting up a new workspace now takes four steps with a progress indicator: workspace, first check, alerts and status page. The first check runs while you watch and shows the status, the response time split into DNS, connect, TLS, server and download, and the certificate. Then you send yourself a test alert at the email address you signed up with, and, if you want one, publish a status page for your monitors in one click.
Every step can be skipped. Progress is saved with the workspace, so Continue setup on the overview picks up where you left off.
“Get alerted” on our Is it down? pages and “Monitor this …” in our free tools now also work when you already have an account. They open a new monitor with the service’s status page, the website, the domain or the DNS record already filled in. If you are new, the sign-up page says what we will start watching, for example “After sign-up we start watching ChatGPT.”
Our free tools now include an HTTP status code reference, with a page for each of 72 codes and what an uptime monitor makes of it, a downtime cost calculator and a status update generator that drafts incident updates for every stage, from Investigating to Resolved.
Read more: HTTP Status Codes Cheat Sheet for Website Monitoring
We updated the web framework that app.uptimecheck.com runs on to a patched release. It closes three recently published vulnerabilities in that framework. Nothing changes in how the app works, and you don’t need to do anything.
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.
We checked every alert channel against the service’s own API. A monitor name or message can no longer trigger @channel or @everyone mentions in Slack, Discord, Google Chat or Mattermost, and each service’s length limits are respected.
A channel that fails for good, such as a deleted webhook, stops retrying at once and shows a clear reason, and a service asking us to slow down (Retry-After) is listened to. Webhook payloads now include the monitor’s ID and the incident.
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.
Choose a plan and monthly or yearly billing on our pricing page, and sign-up now remembers it. The app shows your choice when you sign up, and Billing preselects that plan and interval when you are ready to subscribe. The 14-day trial is the same as before.
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.
Alert emails now name the cause correctly, for example “answered with an error” for an HTTP 503, and expired certificates and domains say that they have expired. Each address gets its own message, so recipients don’t see each other, and the unsubscribe link in a client report is signed for its recipient.
New workspaces get a few getting-started emails, which you can turn off under Account. Trial and billing notices always arrive.
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
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
We measure how the site is used with Google Analytics and Microsoft Clarity, to make it better. They don’t tell us who you are, and we run no ads. You can turn statistics off here, or at any time under Cookie settings at the bottom of every page. Privacy policy