Changelog.

What changed in Monitive, newest first.

Subscribe by RSS Older Monitive? See the Classic changelog.

The Monitive sign-in page with GitHub, Google and Microsoft buttons

Sign in with Microsoft

Microsoft joins GitHub, Google, and email on the sign-in page. Use your work account; your name comes with it. Every email we send also has a new, cleaner layout.

New

  • Alerts, recoveries, and account emails share one layout. Each alert says what is down, since when, and links to the monitor.
    Alerts
  • The monitors list marks flapping monitors.
    App
  • Paused monitors show when they were paused.
    App
  • Your account page shows your plan and its limits.
    App
  • Sign-in tells you when your company’s domain already has an account.
    App

Improvements

  • Alerts wait 2 minutes before sending, to filter out blips. How alerting works →
    Alerts
  • Email alerts allow up to 1,000 a day, and the owner hears from us before the cap. Alert limits →
    Alerts
  • New accounts start with the owner as the email recipient, so the first alert always lands somewhere.
    Alerts
  • Delete and pause dialogs now name exactly what they affect.
    App
  • You stay signed in for 30 days, even while we deploy.
    App
  • Your name and initials come from your sign-in provider.
    App
  • All 13 public pages moved to the new design. Status pages →
    Status pages

Fixes

  • Signing out ends the session on our side too, not only in your browser.
    App
  • The public incident feed shows each monitor’s host only, never the full address.
    Status pages

The new Monitive homepage, with a URL field under the headline

A new homepage

monitive.com has a new front page. Paste a URL, sign in, and your first check runs right away. See it →

New

  • TCP port monitors accept 8 common ports, from SSH to PostgreSQL. Read the docs →
    Checks
  • HTTP checks report the final address after following redirects.
    Checks
  • API keys show when they were last used.
    API
  • Recovery emails say how long the monitor was down.
    Alerts

Improvements

  • The monitors list loads uptime for every monitor in one request, so it opens faster.
    App
  • If you used the older Monitive, signing in takes you to app.monitive.com.
    App
  • Times show in your browser’s time zone.
    App
  • Status pages load faster on slow mobile connections.
    Status pages
  • The API explains which field is wrong when a monitor URL isn’t valid.
    API

Fixes

  • A check interval shorter than your plan allows is rejected when you save, not later.
    Checks

Incidents tell the whole story

The app, alerts, and status pages now carry the Monitive name. Incidents now keep the full story from first failure to recovery.

New

  • The incidents list groups outages by day with filters, summaries, causes, and burst details.
    App
  • Incident details show the full timeline, regions, alert counts, recovery evidence, flapping, and maintenance.
    App
  • You can acknowledge an outage through the API or a signed alert link.
    Alerts
  • The API and MCP are available at api.monitive.com.
    API

Improvements

  • Test alerts are labeled previews of a real down alert for one of your monitors.
    Alerts
  • API keys show a warning when they are more than six months old.
    API
  • Uptime report emails fit phone screens.
    Alerts
  • The sign-in pages use the Monitive design and clearer choices.
    App

Fixes

  • Pausing a monitor resolves its open incident and stops paused time counting as downtime.
    Checks
  • Incident duration starts at the first failed check while keeping the later confirmation time.
    Checks
  • Create and edit dialogs scroll on large phones in landscape.
    App
  • Missing TCP timing values show a dash instead of an invalid number.
    App

Keyword checks and a clearer dashboard

The dashboard puts the signal first. Status, uptime, latency, alerts, and the latest check are easier to scan, with deeper details one step away.

New

  • Keyword is a monitor type in the form for checking that a response contains required text.
    Checks
  • The monitor detail page can preview the exact alert payload that integrations receive.
    Alerts

Improvements

  • The sidebar, monitor list, and monitor details use a clearer Monitive layout.
    App
  • Monitor and incident links use short stable references.
    App
  • Status pages show one timestamp and a plain reason for every outage, with seconds when they matter.
    Status pages
  • Durations leave off a trailing zero unit.
    App

Fixes

  • A monitor created while its target is down sends the expected outage alert.
    Alerts
  • The app reports an invalid empty API response instead of crashing the monitor list.
    App

Teams, Slack, and PagerDuty

Bring the people and tools that share the call. Monitive now covers team access, richer HTTP checks, scheduled quiet time, and three new ways to receive a report or alert.

New

  • HTTP monitors can send a custom method, body, headers, and timeout.
    Checks
  • Weekly and monthly uptime reports can arrive by email.
    Alerts
  • Slack recipients send alerts through an incoming webhook.
    Alerts
  • PagerDuty recipients open and resolve incidents through the Events API.
    Alerts
  • Maintenance windows silence alerts while checks and incident history continue.
    Checks
  • You can invite teammates, assign roles, and switch between accounts.
    App

Improvements

  • Public status pages have a cleaner layout that works on phones.
    Status pages

Free status pages

Give any monitor a public window. One switch publishes its current state, recent incidents, a feed, and a badge you can place elsewhere.

New

  • Each monitor can publish a status page with incident feeds and an embeddable uptime badge.
    Status pages

Improvements

  • Signing in or out in one browser tab updates the other tabs.
    App
  • Recipient, monitor, and settings screens link to the matching Monitive guides.
    App
  • A first GitHub or Google sign-in joins the account that already owns the same verified email.
    App
  • Delivery history supports recipient filters and cursor paging.
    API

Email, Google, and alert recipients

There are more ways in and more ways to hear about trouble. Sign in without GitHub, then decide exactly where each monitor should speak.

New

  • You can sign in with Google or with an email link or code.
    App
  • Alert recipients live at account level and can be attached while you create a monitor.
    Alerts
  • Email recipients receive outage and recovery messages with the downtime included.
    Alerts
  • Each monitor can delay a down alert separately for each recipient.
    Alerts
  • You can create and edit TCP monitors in the dashboard.
    App

Improvements

  • Monitors, incidents, recipients, API keys, usage, and incident feeds work comfortably on phones.
    App
  • Monitors with no alert recipient are clearly marked in the list.
    Alerts

Fixes

  • Public incident feeds show ongoing incidents instead of an error.
    App
  • The incidents page shows an error when its request fails instead of claiming that all is clear.
    App
  • Creating a monitor succeeds even when its first check times out.
    Checks

TCP and ping checks

Not everything speaks HTTP. Monitive can now watch a service port or ask a host for a simple sign of life.

New

  • The API and MCP can create TCP monitors for supported service ports.
    Checks
  • The API and MCP can create ping monitors and report packet loss.
    Checks
  • The Usage screen shows yesterday’s check, incident, and webhook totals.
    App

Fixes

  • Monitive rejects a check type it cannot run when you save the monitor, instead of creating a monitor that never checks.
    API

History that holds up

Long outages and overlapping edits should not bend the record. This release keeps history and monitor changes steady under the awkward cases.

Fixes

  • A long outage stays in history until 30 days after it recovers.
    App
  • A confirmed down monitor reports 0% uptime instead of 100% when an incident row is missing.
    Checks
  • Concurrent monitor edits preserve both changes instead of silently overwriting one.
    API
  • Usage windows stay on the correct UTC dates in every database time zone.
    API

Thirty days of latency

A green check is only half the story. Monitive now draws the last 30 days of latency beside uptime, so slow days stand out.

New

  • Monitor details show a 30-day latency chart with daily ranges, averages, and uptime.
    App

Improvements

  • Monitor details put status, uptime, latency, the latest check, evidence, and actions into one clear layout.
    App
  • The app has a proper Monitive mark and favicon.
    App
  • Body text is larger across the app for more comfortable reading.
    App

Webhook replies in view

When a webhook talks back, Monitive keeps the answer. Open its delivery log to see what the receiving service returned.

New

  • The webhook delivery log shows the response body returned by the receiving service.
    Alerts

Improvements

  • Delivery history keeps the monitor name and address from when the event was sent, even after an edit.
    Alerts

Alerts in your browser

Monitive can tap you on the shoulder without an inbox. Turn on browser notifications, and keep the monitor list close on any screen.

New

  • Your current browser can receive outage and recovery notifications.
    Alerts
  • Each monitor has a 30-day daily uptime view backed by measured checks and incidents.
    App
  • Platform announcements are available as an Atom feed.
    API

Improvements

  • The navigation and monitor list fit phone screens and touch controls.
    App
  • REST responses show the rate limit, remaining requests, and reset time.
    API

Fixes

  • Days with no checks appear as no data, and paused or suspended time no longer looks like uptime.
    App

Meet Monitive through MCP

Your tools can talk to Monitive too. Connect an MCP client, ask about your monitors, or create one without leaving the conversation.

New

  • MCP clients can list, inspect, create, update, and delete monitors, read incidents, and check account usage.
    MCP
  • MCP clients can connect through a browser sign-in flow or with an existing API key.
    MCP
  • A new HTTP monitor runs its first check before the create request returns.
    Checks

Where it started

The first release of the new Monitive, the one you use today. Sign in with GitHub, add an HTTP monitor, and watch the first checks arrive.

New

  • Monitive checks your HTTP sites and confirms failures across regions before opening an incident.
    Checks
  • Signed webhooks send outage and recovery events, retry failures, and keep a delivery log.
    Alerts
  • Monitor status and check evidence update live without a page reload.
    App

Improvements

  • You can edit or delete a monitor from either its list row or detail page.
    App
  • HTTP monitors accept a specific expected status from 200 through 599.
    Checks

Fixes

  • Recoveries close the active outage instead of appearing as another open incident.
    App

Older updates →