Updates

Every release, in plain language.

Dated, versioned, no jargon. Every release of Monitrova, in plain language — what changed for you, not the migration filenames.

  1. v1.40.0 Plans UX

    Pay in your currency — USD, GBP or EUR

    Not everyone wants to pay in euros. You can now see prices and pay in US dollars or British pounds as well as euros. We pick the right currency for you automatically based on where you are, and you can switch any time — and at checkout your card is billed in the currency you chose.

    • Prices in your currency. The pricing page and your billing page now show plans in euros, US dollars or British pounds — chosen automatically from your location, with a switcher if you’d prefer a different one.
    • Checkout charges in that currency. When you upgrade, you’re billed in the currency you were shown — no surprise euro conversion on your statement.
    • Existing subscriptions are unchanged. If you’re already on a paid plan, your currency and price stay exactly as they are — this only affects new sign-ups.
  2. v1.39.0 UX Monitoring

    New: share your free-tool results

    Run a free check and you can now share the result. A new “Share this result” button turns any check — uptime, response time, SSL, homepage, WordPress, WooCommerce or website growth — into a public link with a social-preview image, plus a small status badge you can embed on your own site. Sharing is always your choice: nothing is made public unless you click share.

    • Share any result. After running a check on one of the free tools, click Share this result to get a public link — with a ready-made social-preview image — that you can post anywhere. It’s opt-in: we only save a result when you choose to share it.
    • Embeddable status badge. Every shared result comes with a small badge (like the ones on software projects) you can paste into your own site or README to show its status at a glance.
    • Two new guides for choosing a monitor. A plain-English roundup of the best free uptime monitors, and a guide to monitoring WooCommerce checkout — because a homepage being “up” doesn’t mean checkout works.
  3. v1.38.0 Monitoring API

    New: check and monitor your API endpoints

    A new free API Endpoint Checker lets you send a request — with the method, headers and body you choose — and check the response against your own conditions: the status code, how fast it answered, text in the body, and a value at a JSON field. And you can now add an API endpoint as a monitor, so Monitrova keeps checking it on a schedule and alerts you the moment it stops responding the way it should.

    • Free API Endpoint Checker. At monitrova.com/tools/api-endpoint-checker: pick the method (GET, POST, PUT, PATCH, DELETE…), add headers and a body, and set pass conditions — expected status code, max response time, body-contains text, and a JSON field path (optionally equal to a value). No login needed.
    • API endpoint monitoring. On Add site, choose “API endpoint” as the monitor type to send your request on a schedule and have those same conditions decide whether it’s healthy — with the incidents, email/webhook alerts and uptime history you already get for websites.
    • Alerts that mean something. A monitor goes down when a condition actually fails — and the alert tells you which one (for example, “Expected HTTP 200, got 503”), so you know what broke, not just that something did. Two new help guides walk through both.
  4. v1.36.0 Site Agent Security WordPress

    Spot outdated plugins and known vulnerabilities

    The WordPress Site Agent now reports which plugins, themes and WordPress core have updates waiting — and Monitrova checks your installed software against a public vulnerability database, so you find out when something on your site has a known security issue (CVE), including abandoned plugins with no fix.

    • Updates at a glance. The site’s agent page now lists pending plugin, theme and core updates, so you can see which sites are running outdated software.
    • Known vulnerabilities flagged. Installed plugins/themes/core are matched against a public CVE database. Findings show on the agent page, as a badge on your sites list, and in your daily tasks — with severity, fix version and a link to the CVE.
    • Email alerts, without the noise. You’re emailed when a new high or critical vulnerability appears. The first check of each site quietly records what’s already there, so turning the feature on never floods your inbox.
  5. v1.35.0 UX Updates

    Help guides for your account & monitoring

    The Help Center now covers the logged-in side of Monitrova too — getting started, the dashboard, adding a site, incidents, alerts and quiet hours, monthly reports, the WordPress Site Agent and plans. In English and Spanish.

    • 10 new guides for members. Step-by-step help for setting up and running your monitoring, browsable at monitrova.com/help.
    • Every state explained. What incident states, alert types, quiet hours and the second-location re-check actually do — so you know exactly why (and when) Monitrova emails you.
  6. v1.34.0 UX Updates

    New: a Help Center for our free tools

    We've added a Help Center with a clear guide for every free tool — what it does, how to use it, and what each result and error means, in plain English. Available in English and Spanish.

    • A guide for every tool. Step-by-step help for all seven free tools, with a "what the results mean" table and every error explained, at monitrova.com/help.
    • Know what to do next. Each guide turns the result bands and error messages — "Blocked", "WordPress not detected", a broken checkout — into plain-English explanations, so a confusing result becomes a clear next step.
  7. v1.33.0 Updates Pipeline

    More reliable update emails

    A behind-the-scenes fix to the emails we send when there are new product updates. Some subscribers had received the same update email twice — that is fixed, and delivery is now more resilient when our email provider is under load, so each update reaches you exactly once.

    • No more duplicate update emails. A timing issue could send the same update-digest email to a subscriber twice. Sends are now serialised end to end, so you get each update once.
    • Steadier delivery under load. When our email provider hits a temporary sending limit, the queue now pauses and resumes automatically instead of failing — so large sends finish cleanly rather than dropping recipients.
  8. v1.32.0 Monitoring Updates

    New free tool: Response Time Checker

    A site can be online and still feel slow. Check how fast your website responds from Europe and the US — total time, time to first byte, DNS/TCP/TLS breakdown, redirect delay and a Fast/OK/Slow rating — in seconds, with no login.

    • Free Response Time Checker. Paste your URL and see how fast it responds, region by region, at monitrova.com/tools/response-time-checker.
    • See where the time goes. Total response time plus time to first byte and a DNS/TCP/TLS breakdown, a regional comparison, and clear warnings for slow responses, too many redirects or an HTTPS→HTTP downgrade.
    • Now on your monitored sites too. If you have an account, your uptime checks now record time to first byte as well — on the recent-checks table and the response-time chart — so you can tell a slow backend from a slow transfer.
  9. v1.31.0 WooCommerce WordPress Monitoring

    New free tool: WooCommerce Checkout Health Check

    Check whether your WooCommerce shop, cart and checkout pages are reachable, secure and free from obvious public errors — in seconds, with no login. It is a safe, public check: it never places orders, submits forms or tests payments.

    • Free WooCommerce Checkout Health Check. Paste your store URL and get a Healthy / Warning / Critical read on your shop, cart and checkout pages at monitrova.com/tools/woocommerce-checkout-health-check.
    • Catches real checkout risks. Spots checkout pages that aren’t on HTTPS, are noindexed, blank, in maintenance mode, showing backend or payment-gateway errors, an unrendered checkout shortcode, or redirecting unexpectedly — plus SSL and slow-response context.
    • Then go deeper for free. A public check only sees the outside. Connect Monitrova Site Agent to track checkout fatals, payment errors, failed orders and plugin changes from inside WordPress.
    • Plus: deeper checkout monitoring from inside WordPress. The Monitrova Site Agent (v0.2.17) now also catches a checkout with no available payment method for the cart, a noindexed checkout page, and a checkout page missing its form. Update the plugin from your WordPress dashboard to get them.
  10. v1.30.0 Privacy Updates

    Understanding where new sign-ups come from — privately, and only with your consent

    To keep improving Monitrova we need a clear picture of which channels — search, ads, newsletters, referrals — actually help people find us. We now record that acquisition signal at sign-up, but only after you accept cookies, and always as first-party data we never share with anyone else.

    • Consent first. Nothing is recorded until you accept cookies — the same choice that controls our analytics. Decline, and no acquisition data is stored at all.
    • First-party and private. We capture the campaign or referrer that brought you in — never sold or shared with third parties — purely so we can invest in the channels that genuinely help people discover Monitrova.
  11. v1.29.0 WordPress Monitoring Security Alerts

    Three new free website tools — SSL, homepage health and WordPress checks

    We added three more free, no-login tools so you can spot common website problems in seconds — when your SSL certificate expires, whether your homepage is healthy, and how your WordPress site looks from the outside. Behind the scenes we also made sure your alert and account emails are never lost to a temporary sending limit.

    • Free SSL Expiry Checker. Check when your certificate expires and whether it's valid — expiry date, days remaining, issuer and hostname match — at monitrova.com/tools/ssl-expiry-checker.
    • Free Homepage Health Checker. See whether your homepage is loading properly and free of common problems — slow responses, missing titles, noindex tags, blank pages and backend errors — at /tools/homepage-health-checker.
    • Free WordPress Site Check. A safe, non-aggressive look at public WordPress health signals — exposed version, XML-RPC, security headers, SSL and homepage health — at /tools/wordpress-site-check.
    • Emails that don't get lost. If our email provider hits a temporary sending limit, your alerts and account emails are now queued and delivered automatically once it clears — instead of being dropped.
  12. v1.28.0 Privacy Updates

    Improving our free tools — without storing the sites you check

    We added detailed, privacy-safe analytics behind the Free Uptime Checker and Website Growth Check, so we can see which tools help people most and keep making them better. We record what a check found — never the website address you entered.

    • Better tools over time. We can now see how each free tool is used and what it tends to find, so we invest in the ones that genuinely help.
    • Private by design. We store the outcome of a check — up or down, your score, the type of issue — but never the URL you typed in.
  13. v1.27.0 Updates Alerts

    Subscribe once, get our updates by email — plus an RSS feed

    If you subscribe on our updates page, you'll now automatically get a short email whenever we ship something new. We also added an RSS feed so you can follow updates in your reader or pipe them anywhere.

    • Update emails that just work. Subscribe on this page and we'll email you a digest whenever there's something new — no more checking back manually. Unsubscribe any time.
    • RSS feed. Follow along at monitrova.com/updates/feed.xml in any reader, or connect it to your own tools.
  14. v1.26.0 WordPress Alerts

    Get emailed the moment WordPress hits an error

    If you use Site Agent, Monitrova now emails you as soon as your WordPress site reports an error — a fatal crash, a broken checkout, a payment failure — so you don't have to keep checking the timeline.

    • Know right away. When Site Agent detects an error or critical event, you get an email with the error message, the file and line, and a link straight to the timeline.
    • No inbox flooding. The same error repeating only emails you once a day; a different error still alerts. Critical errors come through even during quiet hours, while normal errors respect them.
    • Nothing to set up. It uses your existing alert email and language. Requires a plan with Site Agent connected.
  15. v1.25.1 Monitoring Accuracy

    Our free website checker now sees through bot protection

    Some sites block automated checkers behind Cloudflare or a firewall. The free Website Growth Check now checks those sites from a second location instead of giving up — and tells you when it did.

    • Fewer dead ends. If a site blocks our usual check, we now retry from a second, independent network so you still get a score and suggestions.
    • Honest results. When we fall back, we show a note that some results may be limited or differ from what a browser sees — and if a site blocks every route, we say so plainly rather than guessing.
  16. v1.25.0 Monitoring Site

    New free tool: score your website and see what to improve

    Our new free Website Growth Check gives any site a 0–100 score and the top things to fix — SEO, speed, SSL and common errors — in seconds, no signup.

    • Instant score, no signup. Paste any URL and get a 0–100 growth score with a clear verdict, plus the status code, response time and redirect count. Try it at monitrova.com/tools/website-growth-check.
    • The top things to improve. We check your homepage the way a visitor or search engine sees it — title, meta description, headings, canonical, noindex, robots.txt, sitemap, speed and server errors — and show the highest-impact fixes first.
    • Then let Monitrova do it daily. A one-off check is a snapshot. Create a free account and your dashboard's Daily Website Tasks keep telling you what to fix next.
  17. v1.24.0 Monitoring Site

    New: Daily Website Tasks tell you what to fix or improve next

    Monitrova already checks whether your website is working. Daily Website Tasks turn that into a clear, prioritised to-do list for each of your sites — based on your real monitoring data, not generic advice.

    • Prioritised, practical tasks. See exactly what to improve next — a missing meta description, an expiring SSL certificate, a slow homepage, a stray noindex tag, a recent error — each with a plain-English fix. Find it under Daily tasks in your dashboard.
    • Straight from your real data. Tasks come from your own uptime, SSL, homepage and — on plans with Site Agent — WordPress checks. Mark them complete or dismiss them, and the list refreshes automatically as things change.
    • Free and paid. Every account gets a daily task to act on; paid plans unlock tasks for all your sites, plus filtering, history and Site Agent-powered suggestions.
  18. v1.23.1 Monitoring Privacy

    A home for our free tools — plus a clearer cookie policy

    We added a “Free tools” menu to the site so our free, no-signup tools are easy to find in one place — starting with the Uptime Checker, with more on the way. We also refreshed our cookie policy so it accurately describes the analytics we use.

    • New “Free tools” menu. A new Free tools page lists every free, no-login tool in one place. First up is the Uptime Checker — and it’s built to grow as we add more.
    • More tools coming. We’re building more free diagnostics to help you check and fix your site. Want round-the-clock monitoring with instant alerts? A free Monitrova account does that automatically.
    • Clearer cookie policy. We updated our cookie policy to spell out that Google Analytics now runs on both the marketing site and the app — only after you accept analytics cookies. No advertising cookies, no cross-site tracking.
  19. v1.22.0 Monitoring Site

    New free tool: check if any website is online right now

    We launched a free Uptime Checker. Paste any website address and see, in seconds, whether it’s online — checked from both Europe and the US — with the status code, response time and the full redirect chain. No account needed.

    • Instant check, no signup. Enter a URL and get its live status, HTTP status code and response time straight away. Try it at monitrova.com/tools/uptime-checker.
    • Europe & US, with detail. We check from two regions so you can spot location-specific outages, and show the redirect chain, final URL and a plain-English reason when a site is down (DNS, timeout, SSL, bot protection, server error…).
    • Then monitor it for real. A one-off check is just a snapshot. Create a free Monitrova account and we’ll keep watching the site and alert you the moment it goes down.
  20. v1.21.2 Privacy UX

    A cookie-consent choice now lives in the app, not just the website

    Our cookie-consent banner used to appear only on the marketing site. Now the app — where you sign in, verify your email and manage billing — asks the same way. Analytics cookies load only if you accept, across every part of Monitrova.

    • Consent on the app too. When you create an account, verify your email or change a plan, you’ll see the same Accept / Decline choice the main site uses. Decline and no analytics cookies are set.
    • Your choice is remembered. Once you pick, the banner stays out of your way for a year, and analytics only loads after you accept — matching how the marketing site already works.
  21. v1.21.1 Site Agent UX

    Your Site Agent timeline now shows every event

    A fix for the per-site Site Agent timeline: when you pick a time range like “Last 24 hours” you now see every event in that window, with paging — not just the most recent few hundred. On busy sites the older part of the day (including WooCommerce orders and login activity) could previously drop off the bottom.

    • Nothing gets cut off. Time ranges now page through every event in the window (100 per page) with First / Previous / Next / Last, and a “Showing 101–200 of 412” counter so you know where you are.
    • Filters stick. Paging keeps your selected range, severity and event-type filters — so you can jump straight to, say, every WooCommerce order or failed login in the last week.
  22. v1.21.0 Site Agent Security

    Know who logs in — and see your WooCommerce orders

    The Monitrova Site Agent — our free WordPress plugin — now keeps a proper security log and shows your store activity. Update to v0.2.16 to see successful and failed logins, password resets and changes, and every WooCommerce order as it comes in, right on the site’s Agent timeline.

    • Login & password activity. Every successful login (for all users, with admins flagged), every failed attempt (with the username that was tried), and password resets and changes now appear on the timeline. IP addresses follow your existing hashing setting.
    • WooCommerce orders, with details. Placed orders now show up with their order number, status, total, items and payment method — on both the classic and block checkouts. No customer names, emails or addresses are sent to Monitrova.
    • On by default, easy to tune. Both are controlled from Settings → Monitrova Site Agent on your site. Update the plugin (or let it auto-update) to v0.2.16 to switch them on.
  23. v1.20.0 Site Agent WordPress

    See your Site Agent at a glance — and where to add it

    The Monitrova Site Agent — our free WordPress plugin — is now far easier to find and check on. Add a WordPress site and we detect it automatically and show a one-click prompt to set it up; and every site now shows whether its agent is connected, plus a flag for any recent issues, right from your sites list and dashboard.

    • WordPress detected? We’ll tell you. When you add a WordPress site, Monitrova spots it and shows a “Set up Site Agent” prompt on the site page — so you can add plugin, theme, core-update and security monitoring in a couple of clicks instead of hunting for it.
    • Connection status at a glance. Each site now shows a small badge when its Site Agent is connected — and an idle or stale marker if it has gone quiet — across your sites list, dashboard and the site detail page.
    • Recent issues, surfaced. If the agent reports a problem (such as a fatal error or a security finding) in the last 48 hours, a chip appears next to the site linking straight to the details.
  24. v1.19.0 Alerts Accuracy

    Fixed: some alerts could arrive twice

    We found and fixed a bug where a “site down” or “recovered” alert could occasionally be sent twice for the same event. If you saw a duplicate alert email recently, that’s why — it’s resolved now, and your alerts will arrive once.

    • What happened. Under certain timing conditions our background checks could briefly run two copies at once, and each sent the same alert. Nothing was ever missed — some alerts were just duplicated.
    • Fixed. Checks now refuse to overlap, so each alert is sent exactly once.
  25. v1.18.0 Accuracy Audit Monitoring

    Your SEO & SSL checks keep working when a site blocks our checker

    Last update we stopped false “down” alerts for sites that block our monitoring IP at their firewall. Now the rest of your checks are covered too: if a site blocks us, your homepage/SEO audit and SSL certificate check automatically run from a second location — so you get the real result instead of a false warning.

    • SEO & homepage audit via the backup. A blocked page used to look like it had no title, a stray “noindex”, or a server error that wasn’t real. Monitrova now re-fetches your actual page from a second network and audits that instead.
    • SSL checks via the backup. If a site blocks our IP at the network level, the certificate expiry/validity check now falls back to the second location too, so you don’t get a spurious SSL warning.
    • Still nothing to change on your end. It all happens on our side. You see the accurate result, and we record which location each check came from.
  26. v1.17.0 Accuracy Alerts Monitoring

    Fewer false ‘site is down’ alerts

    Some websites block automated checkers at their firewall and return an error to us even though the site is perfectly fine for real visitors. Monitrova now double-checks from a second, independent location before alerting — so a site that is only blocking our checker no longer triggers a false “down”.

    • Second-location confirmation. When a check fails, Monitrova re-tests the same address from a different network before deciding the site is down. An alert now only fires when both locations agree it’s unreachable.
    • Nothing to change on your sites. This works entirely on our side — you don’t have to allowlist anything or touch your server or firewall settings.
    • Accurate manual recheck. The “Recheck” button on a site’s page now uses the same two-location logic, so it reflects what your real visitors see rather than whether our checker happens to be blocked.
  27. v1.16.0 Updates UX Admin

    Subscribe to the Monitrova newsletter

    You can now opt in to occasional product news, monitoring tips and reliability advice — and unsubscribe in one click. Newsletter signup is optional everywhere it appears (no pre-ticked boxes), completely separate from monitoring alerts and billing emails, and works whether you have an account or not.

    • Optional opt-in at signup. The register form now has an unchecked “Send me occasional Monitrova updates” checkbox. Tick it once and you’re on the list; leave it alone and we never send you marketing.
    • Signup forms on the marketing site. A simple email-and-button block now sits on the homepage (above the final CTA), on /pricing (below the FAQ) and on this /updates page. Works for guests — no account required to follow along.
    • Manage the newsletter from your account. A new “Monitrova newsletter” toggle joins the existing alerts / digests / account-updates switches at /account/notifications. Tick or untick, save, done.
    • One-click unsubscribe in every email. Every newsletter carries a per-recipient unsubscribe link. Click it once, you’re off the list, and we record the date for our consent logs. Unsubscribing from the newsletter has zero effect on uptime alerts, SSL alerts, monthly reports, billing receipts, password resets or account invites — those keep working exactly as before.
    • Existing users opted in by default. If you already had a Monitrova account before this release, we treated you as subscribed (consent recorded at your original signup date). If you don’t want product newsletters, untick the toggle on /account/notifications and you’re done.
  28. v1.15.4 Site Design About

    New /compare pages, real product screenshots, and a persona-led home page

    Marketing-site refresh. Three things landed: head-to-head comparison pages versus the three legacy uptime monitors prospects most often ask us about (BetterStack, StatusCake, UptimeRobot); real product screenshots replacing the CSS-built “example report” mockups in the hero and dashboard sections; and a new persona section on the home page so visitors can self-identify (freelancer, agency, solo founder) before reading any feature copy. Fully bilingual — all eight comparison pages exist in English and Spanish. No platform code changed; nothing to install or migrate.

    • Compare hub + three head-to-heads. /compare/ is a hub linking to deep comparison pages versus BetterStack, StatusCake and UptimeRobot. Each page covers what they both do, where Monitrova goes further, side-by-side pricing, a “classify” row, and “you’re a good fit if …” / “stick with them if …” cards. EN + ES = eight new pages on the sitemap.
    • Real product screenshots in the hero. The home-page hero now shows an actual Monitrova monthly report rather than a CSS-built mockup of one. The daily-pulse section likewise shows a real dashboard. Both use <picture> with WebP and JPG fallbacks so they stay sharp and load quickly.
    • Persona-led home page. New section under the hero with three personas (freelancer juggling client sites, agency managing 50 properties, solo founder running their own product). Each card has a pull-quote, a plain-English fit description, and a tier hint. The agency tier interpolates live plan data so the “X sites”, cadence and price stay accurate when plans change.
    • Founder photo + plan-driven copy + new FAQ. Wayne’s photo is now on /about. Home-page copy that mentions prices, site counts or check intervals now reads them from /api/plans at render time so it stays accurate without manual edits. The home FAQ gained an eighth entry covering the most-asked question from comparison-page traffic.
  29. v1.15.3 Site Agent WordPress

    Site Agent v0.2.15 — the “Update available” banner stops sticking around after upgrade

    Small WordPress-plugin UX fix. A few people noticed the “Update available” banner in WP admin kept appearing after they’d already upgraded the Site Agent — pointing at the same version the site was already running. Root cause was a stale entry in WordPress’s own update_plugins cache that occasionally survived the standard cleanup (ZIP uploads, object-cache delays). Patched two ways so it self-heals on the next admin pageview.

    • Defensive cleanup on transient rebuild. When the plugin sees that the installed version matches the version on Monitrova, it now also strips its own stale entry from WP’s update cache — not just adding itself to the “up-to-date” list. Means the banner clears whenever WP next refreshes its plugin list.
    • Self-heal on admin pageview. A cheap check on every admin page strips a stale entry the moment you load any admin screen, so you don’t have to wait for the WordPress cache to expire on its own. Only writes when there’s actually something stale — otherwise it’s a no-op.
  30. v1.15.2 Site Agent UX

    Site Agent timeline — defaults to the latest 10 events, with a time-range filter

    The per-site Agent page used to render 100 events on every visit, which gets unwieldy on a busy site. The default is now Latest 10, with a new dropdown to widen to the last 24 hours, 7 days, 30 days, or everything. Small thing, but it keeps the page calm.

    • Latest 10 by default. Most of the time you visit the Agent page to spot-check the most recent activity. Showing 10 first keeps the page snappy and the relevant stuff above the fold. The dropdown widens the window when you actually need the history.
    • A summary line under the card title. “Showing 8 events · last 7 days · filtered” — so you can tell at a glance what range and filters are active without re-reading the dropdowns.
    • Smarter empty state. If you filter to a quiet window and there are no events, the page tells you to widen the range — instead of the previous fallback message suggesting the plugin isn’t installed.
  31. v1.15.1 Site Agent WordPress

    Site Agent v0.2.14 — WordPress core auto-updates now appear on the timeline

    Quiet fix to the WordPress plugin. Before today, a core auto-update on a monitored WordPress site bumped the version field on the next heartbeat snapshot, but never appeared as a discrete “WordPress core updated” event on the timeline. The cause was a subtle PHP gotcha — the in-memory $wp_version global stays stale during the same request that did the upgrade. Now patched two ways for belt-and-braces coverage.

    • The upgrader hook now sees the new version. When the standard WordPress upgrader (manual or auto-update) finishes, the plugin re-reads wp-includes/version.php from disk before comparing, so manual and standard auto-updates fire core_updated immediately.
    • Every heartbeat double-checks. If your host swapped core files at the filesystem level (no WP upgrader involved), or you ran wp core update via WP-CLI in a separate process, or you restored from a backup — the upgrader hook never fires. The heartbeat now compares the stored core version against the live runtime value and emits the event on whichever heartbeat first notices the change. Marked detected_by_heartbeat in the actor field so you can tell which path caught it.
    • No double-fires. When the upgrader hook does its job correctly, it updates the stored value — so the heartbeat sees a match next time and stays quiet. The two paths share one source of truth.
  32. v1.15.0 Site Agent WordPress

    Fire overdue WordPress cron from the Monitrova dashboard — one click, no WP login

    A new Remote actions card on each site’s Agent page. First button: Fire overdue cron now. If a site has accumulated a WP-Cron backlog (a common symptom of misconfigured hosting), you can clear it without logging into WordPress — the plugin picks the command up on its next heartbeat and reports back on the timeline. Lays the groundwork for future remote buttons (run security sweep, run integrity check).

    • Fire overdue cron now. The plugin walks WordPress’s scheduled-event list and runs every overdue hook in the same PHP request, with an 8-second wall-time budget. Recurring events are rescheduled before firing so a slow handler can’t double-trigger. The result lands on your timeline as e.g. “Fired 8 overdue WP-Cron events · 1240 ms”.
    • Delivered on the next heartbeat. Monitrova has no inbound channel into your WordPress install — the plugin polls us. Commands you queue from the dashboard ride along on the next heartbeat reply (within ~15 minutes; sooner on busy sites thanks to v0.2.12’s in-process firing). Once the plugin claims a command, the slot clears, so a command is delivered exactly once.
    • The button greys out while a command is pending. Click once; the badge changes to “Fire cron — queued” until the plugin picks it up. You won’t accidentally queue ten copies during a slow heartbeat window.
    • Requires plugin v0.2.13. Older plugins ignore the new field in the heartbeat reply, so the button silently does nothing until they upgrade. The auto-updater (introduced in v0.2.8) rolls installs forward within ~1 hour of a platform deploy — no manual ZIP install needed.
  33. v1.14.4 Site Agent WordPress

    Site Agent v0.2.12 — cron now wakes itself, no system cron or admin login needed

    Fixes a real WordPress hosting trap: many shared hosts (Imunify360, Comodo, OWASP CRS) block the WP-Cron HTTP loopback as a “vulnerability scanner” pattern. The result on those hosts is that nothing ever fires scheduled events — heartbeats, retries, daily sweeps all stay overdue forever. v0.2.12 stops relying on the loopback entirely.

    • Every WordPress request wakes the cron. Frontend visitor, search crawler, an uptime check from Monitrova itself, anything — the plugin now checks whether any of its own events are overdue and runs them inline in that same PHP process. No HTTP loopback, no system cron, no admin login required.
    • Throttled and time-budgeted. At most one catch-up tick per minute (transient lock), with a hard 4-second wall-time budget per tick. Anything we don’t finish in 4 seconds stays scheduled for the next request to pick up. Worst case for any individual visitor: ~4 s extra latency on one in many pageviews, on the request that catches the tick.
    • Scoped + safe. Only Monitrova’s own scheduled events are fired — other plugins’ cron is untouched. Each handler runs in its own try/catch so a failing event can’t crash the frontend pageview that triggered it. If you HAVE proper system cron configured, it keeps working alongside this — belt + braces.
  34. v1.14.3 Site Agent WordPress Updates

    Site Agent v0.2.11 — “Update available” banner appears within ~1 hour now

    A second WordPress-plugin polish: the auto-updater used to cache its “latest version” check for 12 hours, which occasionally hid a fresh release for up to half a day. The cache layer is gone; WordPress’s own update transient (refreshed roughly hourly) now drives the timing.

    • Faster propagation. Worst-case time between a new Site Agent release going live on Monitrova and the “Update available” banner appearing in an installed site’s WP admin drops from up to ~13 hours to ~1 hour. No setting to change; the new behaviour is automatic from v0.2.11 onwards.
    • Less surprising state. The cache layer occasionally fell out of sync — for example if it happened to refresh while the platform was momentarily on an older version than the installed site. Removing it eliminates a class of “the banner should be there but isn’t” debugging. Installs upgrading from 0.2.8–0.2.10 sweep the legacy cache out automatically on first request after upgrade.
  35. v1.14.2 Site Agent WordPress

    Site Agent v0.2.10 — heartbeat actually runs on schedule now

    A real bug fix on the WordPress plugin: the heartbeat, queue-retry and cron-health WP-Cron events were never actually scheduled on installs ≤ 0.2.9. They only ran when an operator clicked “Send heartbeat now” in the plugin admin. Upgrade to v0.2.10 and they start firing on their normal cadence again — no reactivation needed.

    • Why it happened. Plugin activation runs BEFORE WordPress fires the init hook. The plugin’s custom-schedule filter (for “every 15 min”, “every 5 min” etc.) was only attached during init, so when the activation code tried to schedule those events, WordPress couldn’t resolve the schedule names and silently dropped them. Events on built-in schedules (daily) were unaffected, which is why daily-cadence events were running fine.
    • The fix is self-healing. v0.2.10 attaches the schedule filter at file-load time (works during activation) AND adds a reconcile step that runs on every request, re-scheduling any missing events. So existing installs that were silently broken auto-recover on the first request after upgrade. No manual reactivation, no WP-CLI commands needed.
  36. v1.14.1 Site Agent Security UX

    Security flags get plain-English help, install steps hide when the agent is live

    A round of polish on the per-site Site Agent timeline. The daily security sweep now explains every flag inline (what it means, why it matters, the exact one-line fix), and the install-instructions card disappears once the plugin is actually talking to Monitrova — less clutter for the common case.

    • Plain-English help on security_sweep events. Codes like wp_config_world_readable or file_editor_enabled now expand into a friendly title (e.g. "wp-config.php is world-readable"), a short explanation of why it matters, and the exact fix to copy — chmod 640 wp-config.php, or the DISALLOW_FILE_EDIT wp-config line — right there in the timeline row. Covers wp-config permissions, the file editor, WP_DEBUG_DISPLAY in production, and unsupported PHP.
    • Install-instructions card auto-hides once you're live. The three-step "Connect the WordPress plugin" block used to show on every visit to a site’s Site Agent page. Now it appears only when there’s actually something to do (no token, revoked token, or token never used). Once the agent has authenticated even once, the page leads straight with status, the 24h counter and the timeline.
    • /updates page polish. v1.13.0 was rendering a literal “&mdash;” in its headline; fixed. Recently added tags (Site Agent, WordPress, Plans, Updates, plus the older UX / Design / Onboarding) now have proper coloured tints matching the rest of the site palette.
  37. v1.14.0 Site Agent WordPress Updates

    Site Agent: one-click updates inside WordPress + a calmer timeline

    A round of refinements to the Site Agent plugin shipped in v1.13.0. The plugin now plugs into WordPress's native update flow — the standard "Update available" banner appears on the Plugins page and the one-click upgrader fetches the gated ZIP for you. The timeline also gets a softer middle state and a noisier monitor goes quiet.

    • One-click WordPress-native updates. When a new Site Agent version ships, every installed site sees it as a normal plugin update inside WP admin → Plugins. No more SFTP, no manual ZIP re-uploads. The download still goes through your site’s bearer token, so only your sites can pull updates.
    • New “Idle” agent state. The connection card on each site’s Site Agent page used to flip from green Connected to yellow Stale after 30 minutes — too eager. It now shows a calm grey Idle in the 30 min – 6 h window (heartbeat just running behind) and only escalates to Stale after 6 hours of silence (worth checking on).
    • Quieter performance monitor. The agent no longer fires slow_request or memory_pressure events for cron context — those readings reflect whatever other plugins did in the same cron tick, not anything the Site Agent caused. Genuine cron slowness is still surfaced by the dedicated cron_slow_run event.
    • Polish: mobile layout fixes on the Site Agent page (breadcrumbs wrap cleanly, long URLs no longer push the viewport), "View details" lightbox now shows the full plugin description and changelog, and the agent is tested up to WordPress 7.0.
  38. v1.13.0 Site Agent WordPress Plans

    Site Agent — the WordPress sensor that turns alerts into a timeline

    A new WordPress plugin reports back to Monitrova every plugin update, theme switch, admin login, fatal PHP error, WooCommerce gateway failure, slow request, and security event — so when something breaks, you can see exactly what changed just before it. Available on Starter and above.

    • Install the plugin from Account → Site Agent. Paid plans get a one-click download (it always matches the platform version). Paste the per-site token, click Test connection, and events start flowing within seconds.
    • Every site now has a Site Agent page (open a site → Site Agent button) with a live connection card, a 24-hour severity counter, the latest heartbeat snapshot (WP version, PHP version, theme, WooCommerce status, memory, perf trends), and a filterable timeline of recent events — each rendered as a human sentence like "Plugin updated: WooCommerce v9.4.2 → v9.4.3 by admin@…".
    • What it captures: plugin / theme / core / user changes, fatal PHP errors and debug.log lines, WooCommerce failed orders and gateway errors, performance signals (slow request, memory pressure, slow WP-Cron), security events (failed-login bursts, sensitive option changes, daily wp-config sweep), and optional file integrity diffing against api.wordpress.org checksums — with privacy-conscious defaults (IPs and User-Agents hashed by default, no customer or order detail).
    • Tokens are SHA-256 hashed; the raw secret is shown once on creation and never recoverable. Every ingest request is also verified against the site URL the token was issued for, so a token pasted into the wrong WordPress install can't accidentally feed events into someone else's timeline.
    • On Free: the Site Agent area shows what the plugin would capture and a one-click Upgrade plan button. Existing customers on Starter, Pro and Beta are unchanged — the plugin is included in their plan.
  39. v1.12.0 UX Design

    A consistent look across every page

    The dashboard's clean visual language — coloured status pills, summary cards with tone accents, tidy section headers, ghost-button actions — now runs through every screen of the app, so moving from the dashboard to Sites, Incidents, Alerts, or Reports feels like one app instead of four.

    • Sites page now opens with four summary cards (total / healthy / with warnings / currently down). The site list itself uses the same rounded tag pills as the dashboard, with a real play/pause icon for the active toggle. Empty state explains what to do next.
    • Site detail page (Sites → pick a site) shows the URL, client, tag, and "checked N ago" along the top with consistent icon prefixes. Status appears as a coloured pill with a matching icon (shield-check, warning-triangle, no-signal). All four summary cards (uptime %, response time, SSL days, homepage audit) now carry tone accents that match the dashboard.
    • Incidents, Alerts, and Reports picked up the same treatment — section headings with an icon and underline rule, coloured status pills with inline icons, rounded chips for types and tags, ghost-button actions. The flapping-issue label even gets a tiny lightning bolt.
    • Nothing functional changed — no new pages, no new buttons, no settings to flip. Existing links, forms, filters, and actions all work the same. This is purely a polish release so the app reads as one product.
  40. v1.11.0 Alerts Classification

    Down alerts now tell you why

    When a monitored site goes down, the alert email and the dashboard now name the actual cause — WordPress fatal error, Cloudflare bot challenge, nginx server error — instead of just saying the site "is not responding." If the server returned a useful error message, you see it.

    • Down-alert emails include a new Likely cause line and, when we can identify the message, a short excerpt of what the server returned — usually the exact line of the WordPress / PHP / Laravel error that broke the site.
    • Recognised causes today: WordPress fatal error, WordPress critical error, WordPress can't reach its database, WordPress stuck in maintenance mode, generic PHP fatal, Laravel application exception, Cloudflare bot challenge, Cloudflare origin unreachable (5xx 520-527), nginx 5xx default page, and Apache 5xx default page.
    • The site detail page's Recent uptime checks table now shows the same human-readable cause in the Error column, replacing the cryptic "Expected HTTP 200, got 500.".
    • Forward-only — only failures after the deploy carry the new diagnostic. Historic incidents stay as they were; we never captured the response body for those, so there's nothing to look back at.
  41. v1.10.0 Onboarding UX

    Adding a site is now a single field

    The add-site screen used to ask thirteen things up front. Now it asks one — your homepage URL — and applies sensible defaults to everything else. The full set of options is still there, one click away.

    • Paste your homepage URL, click Add site. Monitrova fills in defaults for timeout, expected HTTP status, SSL expiry warning, and the rest. No more wall of fields between you and your first check.
    • The display name auto-fills from your URLhttps://www.example.com becomes example.com in reports and alerts. Type something else if you prefer; leave it blank otherwise.
    • Power users keep everything: alert routing (per-site email, webhook, sensitivity), monitoring thresholds, SSL/SEO toggles, notes — all behind a "Show advanced settings" disclosure on create, and always visible on edit.
    • The post-add confirmation now sets expectations: "The first check runs within a few minutes — you only hear from us if something breaks." One sentence, no surprises.
  42. v1.9.1 Site Security About

    Marketing site overhaul + public security policy

    A site-wide refresh focused on showing what the product actually does — plus a public security-disclosure policy and a clearer answer to "who built this".

    • The hero now shows a real-looking monthly report card — the same KPIs, incident row, SSL summary, and homepage audit you see post-signup.
    • New "Daily view" section underneath previews the dashboard fleet view, and the no-noise pipeline now renders as a timestamped alert-log feed instead of a generic explainer.
    • Public security disclosure at /.well-known/security.txt and /about#security — 72-hour acknowledgement, 30-day patch target, responsible-disclosure ask.
    • About page now names the developer behind Monitrova (Wayne Tomlinson) and is honest about Mailgun handling outbound email rather than implying a hand-written SMTP transport.
    • Production nginx hardened to stop leaking its version in response headers.
    • Fixed a pre-existing bug where the language switcher in the nav and footer always dropped you on the Spanish home page instead of the Spanish version of the page you were on. Caught during pre-release review.
  43. v1.9.0 Admin Accounts

    Cleaner invitation flow + permanent account deletion

    Two unrelated admin improvements bundled together. The old flow re-used the password-reset machinery for invitations, which was a hack; the new flow is a proper invitation with its own email and setup page.

    • Invited users now get a dedicated welcome email ("You've been invited to Monitrova") with a 14-day setup link.
    • New /invite/{token} setup page replaces the previous password-reset hijack. Same security; clearer copy.
    • Invite and reset tokens are now cross-checked server-side — an invite token can't redeem on the reset page and vice-versa.
    • Admins can now permanently delete soft-deleted accounts with a typed-name confirmation. Audit log entries survive the deletion so admin history outlives the account.
  44. v1.8.0 Crawler Accuracy

    Signed monitoring requests + recheck improvements

    Outbound checks can now be cryptographically signed so Cloudflare (and any web-bot-auth verifier) can confirm a request really came from Monitrova rather than someone faking the User-Agent.

    • New Web Bot Auth support (RFC 9421, Cloudflare-compatible). Every probe carries an Ed25519 signature header set; the public key is served at the standard well-known directory.
    • "Recheck now" on a site now re-runs all three layers — uptime, SSL, and homepage health — not just the uptime probe. A manual recheck genuinely re-evaluates the site.
    • Fixed a partial-render false positive — large pages that omit </body></html> (some WordPress themes, PHP output buffers) are no longer mis-flagged as truncated.
    • Fixed "suspected" incidents being shown as "Resolved" on the site detail page. They now display a proper info-coloured "Suspected" badge.
  45. v1.7.0 Alerts Pipeline

    The no-noise alert pipeline

    The differentiator that gives Monitrova its name. Five mechanisms that decide whether an alert is worth your inbox or your attention — together they prevent the floods that other monitors cause.

    • Two-scan confirmation for non-critical issues. A one-off blip never reaches your inbox; the second scan either confirms (alert fires) or clears it silently.
    • Flap detection & daily digest. When the same problem opens and recovers 3+ times in 24h, individual alerts stop and one daily digest takes over.
    • Recovery suppression. If the original alert was held back, the matching "your site is back up" email is held back too — no notifications for problems you weren't told about.
    • Quiet hours, per account, IANA-timezone aware. Non-critical alerts hold inside the window; site-down and SSL-invalid still go through.
    • Webhook channel. Drop any HTTPS URL into a site's settings; every alert fires a JSON POST alongside the email.
  46. v1.6.0 Classification Monitoring

    Smarter classification — root cause, not symptoms

    When your homepage renders a database error, that's a critical backend incident, not three "missing meta tag" warnings. New classification respects the difference.

    • New backend_error incident type. Database connection errors, PHP fatals, and framework crash pages are now identified as critical backend incidents — the failing SEO checks show as downstream symptoms.
    • Cloudflare bot-challenge detection. A healthy site presented with Cloudflare's anti-bot challenge is no longer reported as "down" — Monitrova surfaces "blocked by bot protection" explicitly.
  47. v1.5.0 Admin Audit

    Admin tooling + cleaner alert audit history

    Foundational improvements to admin tools and the alert-decision audit log. Sets up the bigger pipeline work that shipped a week later.

    • Refined admin tools for account management and lifecycle.
    • Alert log fixes so every send / suppress / defer / summarise decision is captured with its reason, visible alongside email subject, recipient, and provider message ID.

Want to try it?

The free plan covers one site forever. Add a URL and the first uptime check fires within a few minutes.