Aloita ilmainen kokeilu

Mitä me julkaistu.

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

lokakuu 2026

  1. Parannettu , linkki tähän merkintään

    Tekstiviestihälytykset kaikissa maksullisissa paketeissa ja päiväraja

    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.

    Lue lisää: How to add alert channels

  3. Uusi , linkki tähän merkintään

    Uusi käyttöönotto: ensimmäinen tarkistus livenä, testihälytys ja tilasivu

    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.

    Lue lisää: How to add your first monitor

  4. Parannettu , linkki tähän merkintään

    Sivustomme linkit avaavat valmiiksi täytetyn valvonnan

    “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.”

    Lue lisää: Third-party monitoring

  6. Tietoturva , linkki tähän merkintään

    Tietoturvapäivitys verkkosovellukseen

    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.

  8. Tietoturva , linkki tähän merkintään

    Hälytysintegraatioita on vahvistettu

    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.

    Lue lisää: Alerts and notifications

  9. Uusi , linkki tähän merkintään

    Komponenttikohtainen vaikutus tilapäivityksissä

    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.

    Lue lisää: How to post status updates and reach subscribers

  10. Uusi , linkki tähän merkintään

    Muokkaa huoltoikkunoita

    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.

    Lue lisää: How to schedule a maintenance window

  13. Parannettu , linkki tähän merkintään

    Selkeämmät hälytys- ja raporttisähköpostit

    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.

    Lue lisää: How to get uptime email reports

  15. Uusi , linkki tähän merkintään

    Näe, kun hälytyskanava lakkaa toimittamasta hälytyksiä

    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.

    Lue lisää: Alerts and notifications

Seuraa tilannetta Jokainen muutos päätyy syötteeseemme heti julkaisun yhteydessä.

Katkot ovat menneisyyttä.

Luo ensimmäinen valvontasi alle minuutissa – tai tutustu ensin live-demoon.

Aloita ilmainen kokeilu Vertaa paketteja

14 päivän ilmainen kokeilu · Sen jälkeen ilmainen 5 valvonnalle · Ei luottokorttia