Every release,
in the open.

• FixWhen a domain is transferred between registrars and the old registrar was serving a parking page, the old IP addresses can linger in some recursive DNS caches for hours. Our check nodes could end up resolving the now-restored domain to the stale parking IP and reporting it as DOWN even though the site was actually serving normally everywhere else. Each parking detection is now independently verified against an authoritative DNS lookup before we open an incident, so transient resolver-cache lag after a registrar transfer no longer triggers a spurious outage.

• FixInternal reliability fix. No customer-facing changes.

• FixInternal build reliability fix. No customer-facing changes.

• FixServer-level outage detection no longer misses sustained spikes whose underlying signals briefly dip into the noise-suppression range. Real prolonged outages now produce a single accurate DEGRADED notification once the threshold is crossed, instead of being silently absorbed.

• FixServer-level "back online" alerts now respect the configured alert cooldown. Previously a server with a brief metrics blip could send the same "back online" message every minute until the metrics fully stabilized. Now it sends one summary recovery notification and waits out the cooldown.

• FixInternal build reliability fix. No customer-facing changes.

Improved how Visual Sentinel groups alerts when several monitors on the same server fail or recover in waves.

• FixLarge shared servers now group smaller partial outages into one server-level alert instead of sending repeated individual monitor alerts.
• FixServer-level recovery alerts now wait for a short quiet period, preventing outage/recovery notification loops while a server is still flapping.

• FixThe free status-check tool at /tools/status no longer crashes on browsers that have auto-translate enabled. The page now stays in English regardless of browser language so the live status indicator renders reliably for every visitor.
• FixCleaned up internal alert noise when an account is removed while the user still has a session open elsewhere. No user-visible behavior change.

• FixInternal build reliability fix. No customer-facing changes.

Refinements to how we attribute marketing conversions, so the team can measure which channels are bringing in real customers more accurately. No customer-facing UI changes.

• ImprovedStrengthened conversion tracking across the signup and checkout flow, with appropriate handling for visitors covered by GDPR and CCPA consent rules.

Multi-region monitors now show each region's uptime separately on the monitor detail page, so you can immediately see when a single region is failing instead of a confusing aggregate that could read 50% with no obvious explanation. The headline uptime number is also recalculated as the mean across regions, which fixes cases where one healthy region was masking a 100% failure in another.

• FixMulti-region monitors no longer report a misleading aggregate uptime when one region is consistently failing. Each region's uptime is now calculated and shown independently, and the overall figure is the mean of those.
• NewNew "Uptime by Region" card on the monitor detail page shows each location's uptime over the selected time range, with color-coded thresholds. If one region is at 0% it usually means the target is responding differently to that location (different status code, or geo-blocking).
• ImprovedConcurrent checks from different regions no longer race each other when updating a monitor's stats. Per-region check data is now persisted reliably even under heavy concurrent load.

Server load alerts are smarter about when to fire. A common false-positive pattern (high load average with low CPU usage, typical inside Linux containers and I/O-heavy workloads) is now correctly recognised as non-actionable and suppressed. Critical-tier load spikes still fire regardless of CPU so real incidents are not missed. The notification channel hint and load average tooltip on the server configuration dialog were also clarified.

• FixServer load alerts no longer fire for the common pattern of high load average with low CPU usage (typical of I/O-bound or containerized workloads). Critical-tier load spikes still fire as before.
• ImprovedClearer tooltip text on the server alert configuration dialog explaining when load alerts fire and where notifications get routed.

Internal-only fix for a regression in our continuous integration test suite. No customer-facing change.

• FixInternal build reliability fix.

When you accept an invitation to an existing organization, you now land directly on the dashboard. Previously, invited users were sent through the first-monitor setup wizard, even though the inviting organization already had monitors, channels, and a plan configured.

• FixInvited teammates joining an existing organization now skip the first-monitor setup wizard and land directly on the dashboard.

When a teammate accepted an invitation by signing up with Google or GitHub, the app was previously creating an extra empty workspace for them in addition to joining the inviting organization. They now land directly in the inviting organization with the correct role, no extra workspace.

• FixInvited teammates signing up with Google or GitHub no longer end up with an extra empty workspace in their account switcher.

Internal-only: we can now see why a signup or social login attempt did or did not complete, instead of only seeing the successes. No customer-facing change.

• ImprovedInternal telemetry improvements for the signup and social-login flow.

Public pages were loading two session-replay vendors. We removed Microsoft Clarity and kept the higher-quality one. Side effect: a known JavaScript error class disappears, public pages load slightly faster, and the cookie consent surface is simpler.

• ImprovedPublic pages now load one fewer third-party script for slightly faster first paint.
• FixResolved a recurring JavaScript error class that was firing on the homepage, sign-in, and status-page tools.
• ImprovedUpdated Privacy and Cookies pages to reflect the simplified vendor list.

Internal error monitoring no longer logs or forwards outgoing webhook URLs when paging engineering. No customer-facing change.

• SecurityEnhanced security hardening.

Internal log-level tuning so the engineering channel only pages on platform issues, not on customer-side connection failures that are already handled by the existing alert pipeline. No change to customer-facing alerts or check behavior.

• ImprovedInternal alerting noise reduction (no change to customer alerts).

When you click a notification from one organization while currently working in another, the dashboard now switches you to the correct organization automatically and lands you directly on the monitor, server, or incident the notification was about. No more 404, switch organization manually, then re-navigate.

• ImprovedNotification clicks across organizations now auto-switch you to the right organization and land you on the right page.

The AI-agent markdown rendering now leads with our actual differentiators (smart-alert clustering, Cloudflare integration, 15-minute visual regression, privacy-first status pages) instead of a generic feature list. Also fixed a delivery quirk where the homepage markdown was returning HTML when the prerender cache won the race against content negotiation.

• ImprovedAI-agent markdown rendering of public pages now actively pitches what makes us different rather than listing features.
• FixMarkdown rendering now reliably returns markdown for prerendered routes including the homepage.

Hotfix to the AI-agent markdown rendering shipped in the previous release: the homepage path now correctly returns markdown when requested with Accept: text/markdown.

• FixMarkdown rendering for AI agents now works on the homepage too (was returning HTML in 2.40.16).

Public marketing pages now also serve a clean markdown rendering when an AI agent or LLM tool requests it via the standard Accept: text/markdown header. Browsers continue to get the regular HTML view. Helps AI search engines and assistants ingest and cite Visual Sentinel content with higher fidelity.

• ImprovedPublic pages now respond with a clean markdown version when AI agents request it via Accept: text/markdown.

Fixed an intermittent rendering glitch on the homepage that some visitors were seeing on first load. Locked the live status pages against in-browser auto-translation that was causing the same glitch. Added our LinkedIn, Facebook, and Instagram presence to the footer and to our brand metadata so AI search engines can find them. Internal telemetry improvements for our signup funnel.

• FixResolved an intermittent rendering glitch on the homepage and live status pages.
• ImprovedAdded LinkedIn, Facebook, and Instagram links in the footer; expanded brand metadata for AI search visibility.
• ImprovedImproved internal funnel telemetry to better understand signup flow on different browsers.

The 29-day SSL expiry tier was retired across the dashboard because it fired during the typical certificate auto-renewal window (most customers got paged about a renewal that completed uneventfully). Existing monitors using the 29-day tier are migrated to the 20-day tier instead, which fires after auto-renewal would have completed and a real problem is more likely.

• ImprovedSSL expiry alerts no longer fire 29 days out by default. Replaced with a 20-day tier that fires after the typical auto-renewal window.
• ImprovedExisting monitors set to the 29-day tier are migrated to 20 days. All other custom tiers preserved.

Visual Monitoring now defaults to one capture per hour for new monitors, with a 15-minute minimum if you want it more frequent. Same alert quality, less noise, and lower load on the sites being monitored. Internal alerting noise from already-handled customer-side timeouts has also been reduced (your DOWN alerts are unchanged).

• ImprovedVisual Monitoring captures now default to once per hour for new monitors. Existing monitors keep their current cadence.
• ImprovedVisual Monitoring minimum is now 15 minutes (raised from 5).
• ImprovedInternal alert pipeline now distinguishes customer-side request timeouts from check infrastructure issues.

Tightened the check infrastructure trust model so a brief network blip on a check node no longer wakes you with a "site down" alert when your site is actually fine.

• FixShort-lived check infrastructure blips no longer trigger false-positive DOWN alerts.

Bulk actions on the alert settings page and the monitor list (linking monitors to a server) now apply to every selected monitor instead of silently failing on accounts with many monitors. The action cap now matches what the page can display.

• FixBulk alert and bulk server-linking actions now apply to every selected monitor.

Filtered out noise from a third-party library that cannot generate IDs on certain privacy-hardened browsers. No customer-facing behavior change.

• FixInternal error tracker filters a noisy false-positive class.

Sign-in via Google or GitHub now recovers automatically from a slow upstream call and gives up quickly with a clear retry path instead of leaving you waiting.

• ImprovedGoogle and GitHub sign-in is more resilient to slow third-party calls.

When you invite a teammate and they sign up directly (rather than clicking the invite link), they now land straight inside your organization with their assigned role. No detour, no orphan personal workspace, no extra step.

• ImprovedInvited teammates who sign up at the login page are added to your organization automatically.

Daily, weekly, and monthly digest reports now load several times faster, especially for accounts with many monitors. On quiet periods with no incidents, the report is generated instantly without waiting on analyst commentary.

• ImprovedDigest reports load much faster.
• ImprovedQuiet uneventful periods skip the analyst commentary step.

Loading Cloudflare zones for the first time after the cache refreshes is now several times faster, especially for large accounts.

• ImprovedCloudflare zone list loads faster on cache miss.

Fixed an internal build configuration so new releases can deploy. No customer-facing behavior change.

• FixInternal build pipeline hotfix.

Aligned a few internal compliance tests with the new in-app trial offer plumbing. No customer-facing behavior change.

• FixInternal test suite hotfix.

Tightened internal copy to match our style guide. No customer-facing behavior change.

• FixInternal build pipeline hotfix.

If your trial paused some of your monitors, the Monitors page now shows a quick way to bring them all back. Card required, no charge until day 10. Cancel anytime.

• NewOne-click reactivation for monitors paused after a trial.

Customers with several hundred monitors will now see all of them on the alert settings page. Previously the list quietly stopped at the first 500.

• FixAlert settings now loads every monitor in your account.

A locked feature now offers a 10-day trial right where you are, with one click instead of a trip to the pricing page. Card required. No charge until day 10. Cancel anytime.

• NewStart a 10-day free trial directly from any locked feature.
• ImprovedClearer in-app prompts when you bump into a paid feature.

Cleaner error tracking and clearer billing alerts on our end. No customer-facing behavior changes.

• ImprovedInternal monitoring polish.

Tightened how AI-generated incident summaries handle data from monitored services. No customer-facing changes for normal monitors and incidents.

• SecurityEnhanced security hardening.

Tightened how links are rendered inside chat replies and blog content. No customer-facing behavior changes for normal links.

• SecurityEnhanced security hardening.

Profile picture uploads now go through additional safety checks and are converted to a single canonical format. Existing profile pictures are unchanged.

• SecurityEnhanced security hardening.

Improved how the site refreshes its global content cache after each release. Fixes occasional rendering glitches that some visitors hit immediately after a new version goes live.

• FixPages now refresh promptly after each release.

Strengthened password requirements on the password reset and change forms (the same complexity rule that applies at signup now applies everywhere). Internal error reporting no longer includes raw email addresses or URL query strings.

• SecurityEnhanced security hardening.

Tightened authentication on internal agent endpoints. No customer-facing behavior changes.

• SecurityEnhanced security hardening.

Tightened how outgoing webhook requests are validated. No customer-facing behavior changes for legitimate webhooks.

• SecurityEnhanced security hardening.

Tightened verification on links inside our outbound emails. No customer-facing behavior changes.

• SecurityEnhanced security hardening.

Updated several internal libraries to their latest patched versions. No customer-facing behavior changes.

• SecurityEnhanced security hardening.

Tightened the boundary between customer status-page custom domains and the rest of the application. No customer-facing behavior changes.

• SecurityEnhanced security hardening.

Replaced a flaky external lookup with a faster built-in equivalent. No user-visible changes.

• FixFaster, more reliable internal session enrichment. No customer-facing behavior changes.

If you have many monitors on the same hosting (even without explicitly grouping them), a shared infrastructure event would previously page you for every site at once. We now spot the pattern automatically and consolidate to one informative alert.

• ImprovedWhen several of your monitors that share the same internet address fail at the same time, we now collapse the notifications into one alert that names the shared address. The per-monitor incidents still appear on your dashboard, but you stop getting flooded.
• ImprovedDetection is automatic and per-account: even if monitors share a public CDN address with someone else, the alert grouping never crosses account boundaries.

When many of your monitors share infrastructure that goes wobbly, we already fold the failure alerts into one summary. We now do the same for slow-response alerts so you stop getting a flood of "responding slowly" notifications during a shared-host event.

• ImprovedSlow-response alerts are folded into the main outage summary when many monitors on the same hosting are slowing down at once. The per-monitor incident still appears on your dashboard so nothing is hidden, but you get one consolidated alert instead of dozens.

Hotfix for an internal background process. No user-visible changes.

• FixResolved a background error that prevented one of our internal correlation checks from running. No customer-facing behavior changes.

Performance and observability follow-ups based on real user data from the previous release.

• ImprovedVisual monitoring page is dramatically faster. Layout no longer shifts while content loads, clicks respond instantly, and large accounts load progressively instead of all at once.
• FixInternal error tracking now captures real stack traces instead of opaque "Script error." messages, so we can fix issues faster.

Foundational changes to how we decide when to wake you up. When our checking infrastructure is itself unstable, we now hold customer alerts until we can confirm the issue is on the monitored site, not on our side. Phase 1 of a multi-step rollout.

• ImprovedInternal trust signals so we can tell "our infrastructure is having a moment" apart from "your site is actually down." First customer-visible benefit lands in a follow-up release.
• ImprovedResponse-time charts no longer get ruined by a single slow check. One outlier used to stretch the Y-axis so far that the typical-case variation became a flat line. Charts now resist outliers while still showing the spike if you hover.

Small follow-up to the previous release. No user-visible changes.

• FixQuieter handling of malformed requests to public endpoints. No customer-visible behavior change.

Small follow-up to the previous release. No user-visible changes.

• FixInternal observability instrumentation now activates correctly in production. No customer-visible behavior change.

Internal improvements to product analytics and a small piece of preparation work for an upcoming payment-method addition. No user-visible changes in this release.

• ImprovedImproved internal analytics so the team can better understand how new visitors interact with the site and where the experience falls short. Existing privacy controls (consent banner, region-based opt-out) apply unchanged.
• ImprovedGroundwork for an additional payment method at checkout. The new option will appear automatically once the rollout is complete; no action needed on your side.

When dozens of your monitors fail at once because a shared origin server has a brief outage, you now get exactly one server-level alert naming the affected server, the count of impacted sites, and a sample of which ones. The individual monitor incidents are nested under that one parent incident on your dashboard, so the audit trail stays complete. A 30-second deferral on linked-monitor notifications gives the system time to recognize a cluster pattern before any noise reaches your channels. The full-feature trial offer also no longer auto-starts the moment you pick the Free plan.

• ImprovedServer-level alert aggregation. If your monitors are linked to a Server, and many of those monitors fail together within a short window, you receive ONE alert for that server. Per-monitor incidents are nested under one parent server incident on your dashboard, so you can see the full picture in one place. Recovery works the same way: one server-level recovery message instead of dozens.
• ImprovedWhen the system has direct evidence of server state (via the optional server agent script), the alert message says clearly whether the server itself appears offline, OR whether the server is responding but the hosted sites are unreachable (a network or app-level issue). Two different problem shapes, two different message framings.
• ImprovedPer-channel notification cap as a final-line safety net. Each integration channel (Discord, Slack, WhatsApp, email, push) has a per-organization cap on how many notifications can fire in 60 seconds. If the cap is exceeded, further notifications on that channel are held and a single summary message is delivered telling you how many were suppressed. Keeps Discord and Slack channels usable during any kind of widespread incident.
• ImprovedPicking the Free plan no longer starts a 7-day trial clock the moment you sign up. You can take your time setting up your first monitor without watching a trial expire in the background. The full-feature trial offer will surface later, at the moment you actually need it (when you hit a Free-tier limit or click on a paid feature).

• FixWhen you invite a teammate and they sign up, they no longer get a phantom personal workspace before joining yours. They land directly in your organization.
• FixFree plan details on the website-monitoring overview page now match what you actually get on the Free plan: three monitors, HTTP and SSL checks, email and push alerts, EU and US regions, no time limit.
• ImprovedComparison pages updated for accuracy. We tightened the wedge against other tools to focus on what is genuinely different (visual regression, content change detection, real-browser checks) rather than feature gaps that no longer exist.

Detection of registrar parking pages and hosting-suspended landings, introduced one release earlier, now applies to checks from every region rather than only some. Multi-region checks classify the same situation the same way regardless of which region observes it.

• FixParking-page and hosting-suspended classification now applies uniformly across all check regions. Previously the new detection only ran in some regions, which could produce a partial-outage state on a domain that was actually parked everywhere.

When your domain stops pointing at your hosting (lapsed domain billing, transferred away, parked at the registrar), Visual Sentinel now classifies the situation correctly at the uptime layer instead of firing a confusing visual-difference alert with a misleading "all metrics normal" diagnosis.

• FixWhen a domain redirects to a parking, suspended, expired, or maintenance landing page, the uptime check now flags the monitor as down and the alert clearly states the cause (e.g. "Domain redirects to a parking/suspended page"). Previously these situations could fire a misleading visual-difference alert with a server-health diagnosis that did not reflect the real cause.
• ImprovedVisual checks no longer run when the underlying page has been replaced by a registrar parking page or a hosting-suspended notice. This avoids comparing the wrong page against your baseline and saves resources for the actual sites you are monitoring.

Two mobile fixes from real reports. The top navigation now stays accessible while scrolling on iPhone Safari, and the support chat icon is calmer and smaller on small phones.

• FixTop navigation now stays in place while scrolling on iPhone Safari. The hamburger menu is reachable from anywhere on the page, not just the top.
• ImprovedSupport chat icon on small phones is now smaller, with a calmer animation. The "Hi!" greeting pops up much less often, and reduced-motion preferences are now respected fully.

Audit log entries for password and admin actions now record reliably. Refreshed brand mark and favicon for sharper rendering on light and dark themes.

• FixSuccessful password resets, password changes, and admin actions now record in the account audit log reliably.
• FixForm submissions opened just before a release no longer fail when submitted after the release completes.
• ImprovedRefreshed brand mark and favicon. The owl logo now adapts to light and dark themes consistently across the marketing site, dashboard, and browser tabs.

SSL certificate expiry alerts are now tuned for less noise on healthy auto-renewing certificates while preserving early warning for actual renewal failures. Plan, channel, and feature descriptions across the marketing site, blog posts, and AI-agent documentation now exactly match what each tier offers.

• ImprovedSSL certificate expiry alerts now default to 13, 3, and 1 day before expiry. Optional 20 and 6 day tiers remain available per monitor for users who want extra cushion. Existing monitors keep whatever tiers they already had selected.
• ImprovedPlan, channel, layer-coverage, and retention descriptions across the homepage, pricing, blog, and AI-agent documentation now exactly reflect what each tier includes. Several legacy claims that overstated the Free tier or understated the Business tier have been corrected.
• ImprovedWeb Push is now visible alongside the other alert channels on the homepage so its availability is obvious at a glance. Web Push is enabled per browser with a single click and lands directly on the operator device.
• ImprovedAI-agent documentation files (/llms.txt and /llms-full.txt) restructured with verified customer incident write-ups, a canonical positioning section, and per-section indexes at /tools/llms.txt, /compare/llms.txt, and /blog/llms.txt.
• FixMonthly product update email subject now correctly references the month being summarized (the previous month) rather than the month it sends in.
• ImprovedBeta environment network reliability improved (transport and routing changes on the beta host).

Added two new comparison pages, two new long-form blog posts, and deeper coverage on the visual monitoring and server monitoring pages. Homepage and pricing copy now describe each plan in plainer language so you can pick the right tier faster.

• NewTwo new comparison pages added under /compare.
• NewTwo new long-form blog posts added under /blog.
• ImprovedHomepage now describes the typical visitor types in clearer language so each reader recognises themselves earlier.
• ImprovedPricing tier descriptions are now plainer about who each plan fits.
• ImprovedVisual Monitoring page expanded with additional context on continuous change detection.
• ImprovedServer Monitoring page expanded with additional context for common server stacks.

Refreshed the public documentation file at /llms.txt with the latest pages and product surface so it stays a faithful summary of what is on the site.

• ImprovedPublic documentation file refreshed.

Updated the top navigation and footer to expose recently added pages so they are one click from anywhere on the site.

• ImprovedTop navigation now includes a direct link to the MCP server install page on both desktop and mobile menus.
• ImprovedFooter expanded with links to recently added pages.
• ImprovedAPI documentation page links to the MCP install page and the public OpenAPI repository.

Added a new side-by-side comparison page and a new /website-monitoring overview that walks through all six monitoring layers and how a check runs end to end.

• NewNew comparison page added under /compare.
• NewNew /website-monitoring overview page covering the six monitoring layers and how a check runs end to end.

Visual Sentinel is now installable in Claude Desktop, Claude Code, Cline, Cursor, and Continue via the public @visualsentinel/mcp-server package on npm. Ask your AI assistant what monitors are down, triage an incident, run a free SSL or DNS check, or onboard a new monitor by description, all from inside the conversation.

• NewVisual Sentinel is now installable in Claude Desktop, Claude Code, Cline, Cursor, and Continue. Install snippets are at /mcp.
• NewSixteen tools available, including five that work without an account.
• NewOptional Claude Code plugin bundle with task-focused skills and slash commands.

Tightened the rules that decide when a slow-response alert fires, so a brief blip during a check no longer trips the alert. Your configured slow-response threshold is now respected exactly as set, and slow checks are counted per region instead of pooled across regions, which removes a noise pattern where a single transient hiccup could fire alerts for several monitors at once.

• FixSlow-response alerts now require the full number of consecutive slow checks you set on the monitor before firing, instead of half that count.
• FixSlow-check streaks are now counted per check region, so a brief transient slowness across multiple regions no longer counts as multiple slow checks against the same monitor.
• ImprovedRecovery alerts that paired with these false slow-response incidents will also stop, giving you a quieter alert inbox.

Added a new side-by-side comparison page under /compare. Also published the public OpenAPI specification on GitHub so developers and AI agents can integrate with the Visual Sentinel API directly from a canonical source.

• NewNew comparison page added under /compare.
• NewPublic OpenAPI specification published at github.com/VisualSentinel/openapi with curl, JavaScript, and Python quick-start examples.

New blog posts and changelog entries now notify search engines the moment they go live, so they show up in search results in hours instead of days. Previously, a freshly published post had to wait for the next natural crawl cycle.

• ImprovedNew blog posts are pushed to indexing endpoints automatically on publish.
• ImprovedTidier brand metadata across the site.

The Add Monitors and Add Servers dialogs on a status page now have a search box and a Select All checkbox. Search by name or URL, then click Select All to pick the entire matching set in one go. The previous one-click-per-row workflow still works for picking individual entries.

• NewAdd Monitors / Add Servers dialog now has a search box and a Select All checkbox so you can bulk-link many entries to a status page in one click.
• ImprovedSelect All operates on the currently filtered set, so typing a search term then clicking Select All picks just the matching entries.

If you manage many monitors, the Monitors page used to slow down once the list grew large because every card was rendered up front. The list and grid views now render only what is on screen, so scrolling, searching, and filtering stay snappy regardless of how many monitors you have. Smaller accounts continue to render exactly as before.

• ImprovedMonitors page list and grid views now render only the cards visible on screen, keeping scrolling and filtering smooth on large accounts.

Bespoke Enterprise customers were being capped at the standard Agency monitor limit even when their account carried a higher per-customer ceiling. The plan-limits resolver now correctly honors per-customer overrides for Enterprise accounts.

• FixEnterprise customers with custom monitor / team / status-page / data-retention ceilings on their account now have those limits enforced correctly at gate-check time, instead of falling back to standard Agency limits.

Status pages now support two access controls. Add a password to protect any status page, set an IP allowlist to restrict access to specific IP addresses or ranges, or combine both. The IP allowlist requires a verified custom domain. Existing public status pages render exactly as before unless you turn on a control in Settings.

• NewPassword-protect any status page with a single password that visitors enter to view it.
• NewIP allowlist for status pages on a verified custom domain. Add IPv4 or IPv6 addresses, or CIDR ranges. Visitors outside the allowlist see an access-denied message.
• NewBulk-import IPs by pasting a comma, semicolon, space, or newline separated list, or by uploading a CSV / TXT file (up to 200 KB). Lines starting with # are comments.
• NewAdd IPs one at a time with inline validation, plus a removable list view of every entry.
• ImprovedNew Privacy & Access section in Status Page Settings ties everything together. Both controls can be combined.

Several feature gates were checking your subscription tier without taking your active trial into account, so trial customers were silently denied features they were entitled to during the trial. The DNS history snapshots, keyword content monitoring, status-page theme and SEO controls, and the AI usage allowance on the billing page all now honor the trial state correctly. Once your trial ends, normal plan limits apply as before.

• FixDNS history snapshots are now captured on schedule for trial customers, so the DNS tab populates without needing to open each monitor manually.
• FixKeyword and content-change monitoring now works during your trial without being silently downgraded to the Free-plan feature set.
• FixStatus-page theme, custom CSS, custom HTML, SEO meta fields, and OG image are editable during the trial window for plans that include those tiers at conversion.
• FixAI usage page on billing now shows the correct token allowance during your trial instead of the Free-plan zero allowance.
• ImprovedInternal audit added a recurring guard so any future feature gate that reads your plan also reads your trial state.

When a monitor wasn't actively checking during a report period (because it was disabled, paused, or newly created with no checks yet), reports used to show '100% uptime' on the headline stats. They now correctly show 'N/A' and the AI summary explains that monitoring was inactive instead of leading with a misleading score. Reports for active monitors are unchanged.

• FixReports for monitors that were inactive during the report window now display N/A for uptime, response time, and success rate, instead of a fabricated 100%.
• ImprovedAI report summaries no longer claim "achieved 100% uptime" for inactive monitors and now flag the monitoring gap as a configuration issue.
• ImprovedOrganization-wide weekly digest averages now exclude inactive monitors instead of letting their fabricated scores skew the rollup.

Tightened internal error reporting so common bot-probe traffic against the platform's homepage no longer surfaces as on-call alerts. No customer-facing change.

• ImprovedInternal alerting tuned to suppress noise from bot probes without affecting genuine error visibility.

If you started your trial with a card on file, the billing page now correctly shows your billing-start date and tells you can cancel anytime before then, instead of the generic 'subscribe below to keep your features' message. Customers without a card on file continue to see the 'subscribe to keep features' message as before.

• FixCard-on-file trials now show the correct billing-start date and cancellation language on the billing page.

Recovery (back online) alerts now fire when an incident actually closes, rather than relying on a fixed time window. This guarantees recovery alerts for genuine multi-day outages while still suppressing alerts from background state cleanup or brief check-time flaps that never crossed the alerting threshold.

• FixRecovery alerts now reliably fire for genuine multi-day outages, including those at the maximum repeat-alert cadence.
• ImprovedRecovery alerts are now keyed on the underlying incident lifecycle, so brief check-time flaps that did not generate a down alert no longer produce a recovery alert either.

Monitor recovery alerts now require a corresponding down alert within the last 24 hours. This prevents 'recovered' notifications from firing when no outage was ever surfaced to you, which could otherwise happen during background state cleanup after platform upgrades.

• FixRecovery alerts will only fire when there was a corresponding down alert in the last 24 hours, eliminating noise from background state-machine cleanup.

Down detection for monitors that check from multiple regions has been hardened. A subtle interaction between the database server's clock-zone setting and certain time-window queries could prevent the platform from recognising that recent checks had failed across regions. The fix is layered across the application code, the database connection, and the runtime environment so the issue cannot recur as we add more check regions and nodes.

• FixDown detection for multi-region monitors is now reliable regardless of the database server's clock-zone configuration.
• ImprovedHardened the platform end-to-end against clock-zone drift as we expand to new monitoring regions, so adding new check nodes cannot reintroduce this class of issue.

If your monitor went down and you got a 'monitor is down' alert, you should always get the matching 'monitor recovered' alert when it comes back. A subtle gap in the previous logic could occasionally drop the recovery alert when an outage resolved very quickly or affected only one region. Recovery alerts are now tied directly to the incident lifecycle, so every closed incident that originally alerted you also tells you when it's resolved.

• FixRecovery (back online) alerts now reliably fire whenever a previously-alerted incident resolves, including fast outages and single-region issues that did not always trigger a recovery alert before.
• ImprovedRecovery alerts are now strictly one-per-incident, so duplicate recovery messages are not possible even if multiple internal paths agree the monitor is healthy at the same time.

When a monitor had no explicit visual check cadence configured, the settings UI was showing 'Every 24 hours' regardless of the actual cadence. The display now reflects the cadence the system is really using for that monitor, taking your plan into account. Saving the form without changing the dropdown no longer writes a value, so your intent to 'use the plan default' is preserved across plan changes. No customer action required.

• FixMonitor settings now show the actual visual check cadence the system uses, instead of a generic 24-hour placeholder when no explicit value was set.
• ImprovedSaving visual settings without changing the cadence dropdown no longer locks in a value, so the cadence continues to follow your plan defaults if you upgrade or downgrade later.

We rewrote earlier changelog entries to be cleaner and more user-focused. Same shipped behavior, tidier copy.

• ImprovedRefreshed the wording on a number of historical changelog entries.

Background cleanup of stale visual-monitoring records now runs reliably. A pre-existing bug was causing the cleanup pass to abort early on high-traffic accounts, which over time could allow stale records to accumulate. No customer action required.

• FixBackground cleanup of stale visual-monitoring records now runs reliably on every restart. Prevents accumulation on high-traffic accounts.

Visual change detection now requires the same content drift to repeat across multiple checks before triggering a screenshot capture. Previously, any mismatch between checks counted toward the threshold, which could falsely trigger captures on pages with dynamic noise (timestamps, ad slots, dynamic markup) even when no real visual change had occurred. With this release, random per-request noise resets the counter; only stable, repeated changes lead to a screenshot. Once a screenshot is taken for a particular changed state, that exact state is suppressed from re-capture until either the page recovers to baseline or the periodic safety window elapses (default 12 hours, configurable). The result is dramatically fewer wasted captures on dynamic pages and a much higher signal ratio in alerts. No customer action required.

• ImprovedVisual change detection now requires the same content drift to repeat before triggering a screenshot. Random per-request page noise no longer accumulates toward false-positive captures.
• ImprovedOnce a screenshot is captured for a particular changed state, that exact state is suppressed from re-capture until the page recovers or the periodic safety window elapses (default 12 hours).

Foundation work for running visual monitoring at much higher monitor counts. Adds centralized rate limiting (per-minute global and per-host), smart prioritization (manual checks beat scheduled ones), backpressure-aware delay when the queue is hot, and deduplication so the same capture can't queue twice. Also adds an opt-in scanning mode that replaces per-monitor scheduled jobs with a single periodic scan, drastically lowering background overhead. The new mode is opt-in; existing accounts continue to use the previous behavior. No customer action required.

• ImprovedVisual capture pipeline now enforces global and per-host rate limits with smart prioritization, deduplication, and queue-aware backpressure. Reduces wasted captures and improves responsiveness under load.
• ImprovedNew opt-in eligibility scanner replaces per-monitor scheduled jobs with a single periodic scan, foundational for running visual monitoring at much higher account sizes. Existing behavior is unchanged unless explicitly switched on.
• ImprovedVisual change detection threshold can now be configured per monitor (including zero for instant-trigger), and respects the configuration on slow monitors that previously overrode it.

Visual monitoring now ignores transient HTML noise (timestamps, ad slots, dynamic class hashes, etc.) instead of triggering a screenshot capture on every minor content drift. Fast-cadence monitors now wait for several consecutive content mismatches before enqueueing a screenshot, and once a screenshot is enqueued there is a cooldown window before the next one can fire. Customers running noisy sites (e-commerce, news, dashboards) will see far fewer false-positive captures and far less alert noise. Slow-cadence monitors (one-hour-plus intervals) still react to the first mismatch since each check is more significant. The threshold is configurable per monitor.

• ImprovedVisual monitoring now waits for several consecutive content drifts before queueing a screenshot capture, then sits in a cooldown window before the next one. Cuts false-positive captures on dynamic pages substantially, configurable per monitor.
• ImprovedReduced memory usage of one-shot screenshot captures used by the HTTP checker.

When an active or recently-resolved visual change incident is opened, the before/after/difference screenshots now stay viewable for at least 30 days. Previously, on monitors with frequent UI changes, the comparison images could be cleaned up the same day an incident closed (sometimes while the incident was still open) leaving the dashboard with placeholder boxes instead of the actual evidence. No customer action required. The deeper architectural fix that stores incident evidence completely separately from the rolling screenshot pool is planned for a future release.

• FixThe before, current, and difference images shown on a UI change incident now stay viewable while the incident is open and for 30 days after it closes. Previously, on monitors with frequent UI changes, those images could disappear within hours.

Two small fixes. First, the per-service status pages (e.g. visualsentinel.com/tools/status/playstation) no longer crash for mobile users whose browser auto-translates the page into another language. Now they render cleanly across translation modes. Second, when the visual monitor detects a UI change, it now only reopens a previously-resolved incident if the prior incident closed within the last hour (was 24 hours). Practical effect: a fresh UI change the next day opens a fresh incident with a fresh detection timestamp instead of re-attaching to yesterday's incident and showing yesterday's date on the alert.

• FixPer-service status pages (e.g. /tools/status/playstation) no longer crash on mobile browsers when the page is auto-translated from English into another language.
• FixWhen a visual change is detected, the system now only reopens a previously-resolved incident if it closed within the last hour. Was 24 hours. New changes the next day get a fresh incident with a fresh detection timestamp on the alert.

Restored visual capture reliability after a regression in the previous release. No customer action required.

• FixVisual captures are reliable again.

Tiny visual fix. The β beta badge next to the Content tab was rendering as a plain capital B because of an inherited CSS uppercase rule. Now it correctly shows the lowercase Greek beta character.

• FixThe β beta badge on the Content tab now renders as the intended lowercase Greek letter instead of a capital B.

Internal build reliability fix. Builds now complete in their normal time again. No customer-visible behavior change.

• FixInternal build reliability fix.

Internal startup cleanup hardened against an edge case that could halt it early. No customer-visible behavior change for monitoring.

• FixInternal startup cleanup is more resilient.

Added a small β badge next to the Content tab inside the single-monitor view. Content monitoring is the most volatile of the six layers (the underlying detection is hash-based and there is no restored-state notification yet), and we want customers to know it is still under active iteration before they wire alert rules around it. No change to any monitoring behavior.

• ImprovedA β (beta) badge now appears next to the Content tab inside individual monitor views, so customers can see at a glance that content monitoring is still under active iteration.

When a monitor recovers from a DOWN state, Discord and Slack alerts now include how long the monitor was offline (matching what email and WhatsApp already showed). Same shape of fix as the previous release's UI Restored duration improvement, applied to the DOWN to UP recovery path.

• FixDiscord back online alerts now include a "Was down for" field showing the downtime duration.
• FixSlack back online messages now include the downtime duration in parentheses.

When a UI Restored alert fires after a visual change has cleared, Discord and Slack now show how long the page was off baseline (matching what WhatsApp and email already showed). Server Recovery alerts in Slack also now include the offline duration and the previous issue label, matching the Discord embed.

• FixDiscord UI Restored alerts now include a "Was changed for" field showing the duration the page was off baseline.
• FixSlack UI Restored messages now include the change duration in parentheses.
• ImprovedSlack Server Recovery messages now include the offline duration and the previous issue label, matching Discord.

Additional network-layer protections for visual monitoring captures. Monitors of CDN-fronted, multi-host, and certificate-pinned sites continue to work unchanged. No customer action required.

• SecurityEnhanced security hardening for visual monitoring captures.

Cleaner error reporting in visual monitoring when a target site is extremely slow to render. Same screenshot budget, same outcome for slow sites, just a tidier alert trail. No customer-visible behavior change for monitors that complete normally.

• ImprovedCleaner error reporting when a visual monitor screenshot exceeds its 30-second budget. Underlying screenshot timeout behavior is unchanged.

Fixed an internal bug where the daily NPS Day-14 lifecycle email could not run. Other lifecycle emails (welcome, day-3, day-7, weekly digests, monthly product updates, milestone emails) were unaffected. NPS Day-14 emails resume on the next daily cycle. No customer action required.

• FixNPS Day-14 lifecycle email is delivering again.

Additional network-layer protections for HTTP and HTTPS monitor checks. Monitors of CDN-fronted, multi-host, and certificate-pinned sites continue to work unchanged. No customer action required.

• SecurityEnhanced security hardening for HTTP and HTTPS monitor checks.

Additional protections for the server monitoring agent install and report paths. No customer-visible behavior change. Existing agents continue to work unchanged.

• SecurityEnhanced security hardening for the server monitoring agent installer and report endpoints.

Two threads in one release. First, a new server alert type for the server monitoring agent: high load average. CPU% on its own can stay under your threshold even when a server is being hammered (a common pattern under fork-bombs, runaway processes, and heavy I/O wait, where cores look idle while work piles up). The new Load alert watches the 5-minute load average normalized against the server's CPU count and pages you when work is queueing faster than the box can process it. Defaults are calibrated against industry references (warn at 2x cores, critical at 4x cores) and every server's thresholds are tunable from the alert configuration drawer. The alert message includes the 1m, 5m, and 15m load averages plus the per-core saturation percentage so you know at a glance whether load is climbing or settling. Second, a stability pack for the visual-monitoring pipeline: warm browser pool re-enabled, post-deploy ramp-up made instant instead of half an hour, scheduler clock no longer reset on every worker boot, and full-size visual evidence preserved on the dashboard for the most recent four resolved incidents per monitor in addition to the open ones.

• NewNew server alert: High Load Average. Fires when work queueing per CPU core crosses your warn or critical ratio, even if individual-core CPU% never crosses the legacy threshold.
• NewPer-server tunable warn and critical ratios in the alert configuration drawer. Defaults of 2.0x and 4.0x cores match the industry consensus (Brendan Gregg, Netdata, Datadog system.load.norm.5).
• ImprovedServer status pill on the dashboard now flips to Degraded on sustained high load too, not just on CPU/Memory/Disk breaches.
• FixVisual monitoring browser pooling re-enabled. Previous-release stability issue resolved and pinned with regression tests; visual checks now reuse warm browsers across captures as designed.
• FixPost-deploy ramp-up for visual checks is now instant instead of taking up to an hour. Coverage is full immediately after a release without a thundering herd.
• FixBackground restarts no longer reset the next-check clock on healthy live monitors, so 5-minute uptime monitors keep their cadence across deploys.
• FixDashboard "Recent visual incidents" no longer loses the full-size capture, baseline, and diff images for the four most recent resolved incidents per monitor.
• FixServer status pill no longer resets on every background restart for monitors whose state was healthy before the restart.
• ImprovedVisual monitoring baselines now capture within seconds of becoming eligible. Whether you start a free trial, a paid trial, or upgrade to a paid plan, your existing monitors get their first baseline screenshot immediately instead of waiting up to a full cadence cycle.

A focused performance release for visual monitoring. Three changes compound: a warm browser pool that keeps browsers alive across checks instead of relaunching each time, an adaptive page-load wait that skips the slow wait after a monitor has had 5 clean checks in a row, and an expanded content-change filter that ignores common dynamic page noise so more checks exit on the fast path without launching a browser at all. The result is roughly 10x more monitors serviceable at the same compute cost.

• ImprovedVisual monitoring is dramatically faster per check. Stable monitors now skip heavy browser launches and page-load waits that are not needed.
• ImprovedSmarter content-change detection: more dynamic page noise (session IDs, cache-busters, generated class names, tracking tokens) is filtered before comparison, reducing false positives.
• ImprovedIdentical screenshots are now detected in milliseconds instead of going through the full pixel-by-pixel comparison.
• ImprovedVisual monitoring concurrency ceiling increased. More captures now run in parallel automatically.

A focused reliability release for visual monitoring. We found that some visual-enabled monitors were silently missing their scheduled comparison captures, meaning a real UI change could go undetected and (more importantly) a fix never got picked up as a restoration. This release rebuilds the scheduling layer to never reset a live monitor's clock, prunes accumulated stale state, and lifts the visual monitoring throughput ceiling by 2x to match the available headroom. On the incident side, restoration now fires correctly when a visual-only incident is still open but the monitor's uptime status has already flipped back to Operational, and posting a Postmortem update on an un-resolved incident now atomically marks it resolved (the Postmortem is conceptually one step beyond Resolved, so it shouldn't need a separate click).

• FixVisual monitors that went quiet after worker restarts now fire reliably again. Newly-added visual monitors register and start comparing on their configured cadence without gaps.
• FixWhen your site visually returns to the baseline, the open UI Changed incident now auto-resolves and you get the restoration notification, even when the monitor's uptime has already flipped back to Operational first.
• FixPosting a Postmortem update directly on an un-resolved incident now also marks the incident as resolved at that moment, so the public status page and your MTTR numbers reflect reality instead of a still-open incident with a postmortem written.
• ImprovedVisual worker throughput ceiling lifted from 12 to 24 concurrent captures per host (IO-bound, not CPU-bound). You keep visual monitoring keeping up as you add more visual-enabled monitors.

A small but visible fix to internal error noise. When a monitor is deleted while a check for it is mid-flight (the external HTTP + render can run for 30+ seconds), the final step that saves the check row would fail and raise an alert. The delete is the normal expected behaviour, so we now skip the write silently instead of treating it as an error.

• FixDeleting a monitor while one of its checks is mid-flight no longer surfaces an internal error. Check writes that fail because the monitor is gone are now silently dropped, as intended.

Two user-visible fixes and one visual overhaul. The auto-resolve toggle now actually holds the incident open when you switch it off (it was leaking through four other recovery paths we missed). The incident drawer now shows the full update timeline, matching the detail page. And the Past Incidents section on your public status page has been rebuilt to match the layout industry-standard status pages use, date headers grouping the incidents of each day, each incident's full update timeline flat-rendered inline, and the day's wall-clock time shown in your organization's timezone.

• FixAuto-resolve toggle actually works now. Flipping it off prevents every recovery path from closing the incident (previously four of them leaked).
• FixThe incident drawer on the Incidents list now shows the full update timeline (same as the detail page). Previously it only rendered an empty section because the underlying API never returned the updates.
• ImprovedPast Incidents on your public status page is redesigned to a date-grouped timeline matching the layout used by status.claude.com and similar sites. Each day lists its incidents with the full update log inline.
• ImprovedEvery automatic resolution (slow response recovered, SSL renewed, PageSpeed score improved, 1-hour stale cleanup, orphan cleanup) now leaves an explicit System entry in the incident timeline explaining why.

Two changes to how Visual Sentinel closes incidents when a monitor recovers. First, auto-resolutions now leave an explicit 'System' entry in the incident's Updates Timeline so the dashboard and public status page show what happened instead of silently flipping the status. Second, every incident now has an Auto-resolve toggle in the drawer and detail page. Leave it ON (default) for the pipeline to close the incident automatically when the monitor is healthy again. Flip it OFF for incidents where you want to keep the incident open until a team member posts a Resolved update themselves, e.g. while you finish writing the postmortem.

• NewNew Auto-resolve toggle on every incident. ON by default (existing behavior). Flip to OFF to keep the incident open until you manually close it, even if the monitor recovers.
• ImprovedEvery automatic incident resolution now writes a 'System' entry to the update timeline noting that the monitor is back online, so your dashboard and public status page show a clear audit trail instead of a silent status flip.

Three fixes to how your public status page renders incident updates. Your full update timeline now shows on every active and past incident (previously newer updates would push older ones off-screen once you had more than three). Each update now renders with a bold status tag (Investigating, Identified, Monitoring, Resolved, Postmortem) before the message, matching the layout used by the incident-status pages your viewers are used to. Timestamps now display in your organization's timezone instead of the viewer's browser timezone, with the zone abbreviation shown so international viewers can orient themselves.

• FixEvery update on every incident (active and resolved) now shows on your public status page. Previously only the latest three updates per active incident were visible, and resolved incidents showed no updates at all.
• ImprovedEach update now renders with a bold status label (Investigating / Identified / Monitoring / Resolved / Postmortem) before the message, matching standard status-page conventions.
• ImprovedPast Incidents section is now expandable. Click any past incident to drop down its full update timeline, including the final postmortem or resolution note.
• ImprovedTimestamps on the public status page now use your organization's timezone from Settings, with the timezone abbreviation shown next to each time so viewers know what zone they're reading.

The new Post Update form now also appears inside the incident drawer that opens from the Incidents list, so you can post a status update without clicking through to the full details page. We also restyled the form with color-coded status pills (Investigating, Identified, Monitoring, Resolved, Postmortem) matching the badges used elsewhere, an integrated character counter in the message field, and tighter padding that fits the drawer properly.

• ImprovedPost an update directly from the incident drawer on the Incidents list, no need to navigate to the full details page first.
• ImprovedStatus is now a set of color-coded pills (one per lifecycle stage) instead of a plain dropdown, matching the badge styling used across the dashboard.
• ImprovedCharacter counter is integrated into the message field and turns red if you exceed the 2,000-character limit.

Lifecycle emails (Day 1 onboarding, Day 3 visual-monitoring nudge, Day 14 NPS, re-engagement, weekly summary, milestones, monthly product update) are sending again after a delivery regression in a recent release. Transactional mail (alerts, incidents, billing, password reset) was not affected. Lifecycle sends resume on the next scheduled run.

• FixLifecycle emails are back. If you signed up recently and have not received our Day-1 or Day-3 onboarding notes, that is this bug. Emails still due (NPS, milestones, weekly summary) will land on their next scheduled send.
• SecurityOne-click unsubscribe headers (List-Unsubscribe / List-Unsubscribe-Post) are now delivered to your mailbox provider as designed, so the native "Unsubscribe" button in Gmail and Outlook works without a login round-trip.

You can now post status updates directly on any incident and they appear on your public status page in real time. Choose from Investigating, Identified, Monitoring, Resolved, or Postmortem, write a short note for your users, and hit Post. The incident's top-line status moves with it, so your status page tells a clear story from 'we noticed something' through to 'all resolved'. Anyone with Admin or Owner role in the organization can post updates.

• NewNew 'Post an update' card on every incident detail page (Admin or Owner role required). Pick a status, write a message (up to 2,000 characters), and it's live on your public status page immediately.
• NewDashboard incident timeline now shows who posted each update and when, alongside the status label and the message. Posts made automatically by the monitoring pipeline show up as System.
• ImprovedPublic status page continues to show updates chronologically without exposing which staff member posted, keeping the internal and public boundary clean.

Previously only the Owner could save changes to the Organization Settings form, even though Admins could already swap the logo through a separate flow. That was an inconsistency. Admins on the Organization Settings page can now save the form (name, slug, description, website, timezone, billing email, logos) and update whitelabel branding (colors, fonts, email footer, 'Powered by' toggle). Deleting the entire organization and changing outbound SMTP credentials still require the Owner role, because both are either destructive or security-sensitive and not something an Admin should be able to change unilaterally.

• FixAdmins can now save the Organization Settings form. Previously Admins saw an 'Insufficient permissions. Required role: OWNER' banner on Save, while still being able to upload logos separately through a different flow. Both paths are now Admin-accessible.
• ImprovedAdmins can also update whitelabel branding (primary/secondary/accent colors, font family, email footer, the Powered by toggle) and reset branding to defaults. Business plan or higher is still required for the whitelabel feature itself.
• SecurityOrganization deletion and outbound SMTP credentials remain restricted to the Owner role. Both touch destructive or security-sensitive territory where a single-step admin change would be inappropriate.

Monitor Settings → Content Checking lets you flag a monitor as DOWN when required keywords (mustContain) are missing or forbidden keywords (mustNotContain) appear in the response body. The UI accepted your rules and saved them correctly, but the HTTP check pipeline was reading them from the wrong place, so the rules were silently never evaluated. The toggle now works as described. If your saved rules would have been violated by your site's current response, your monitor will correctly flip to a failure state on its next check.

• FixContent Checking rules (mustContain / mustNotContain keywords) are now actually evaluated on every HTTP check. If your site response has ever violated the rules you configured, the monitor will correctly register a failure on the next check (it was silently ignoring violations before). Visual-monitoring keyword checks on the rendered page were unaffected and continue to work as before.

Saving a monitor's Reports settings (include charts, include incidents) was silently failing for some accounts. The save now persists correctly with existing defaults preserved.

• FixMonitor Settings → Reports accordion now saves correctly. The 'Include charts' and 'Include incidents' toggles were sending the right data but failing to persist; defaults preserved so existing monitors behave exactly the same.

A complete rework of which emails you get from us and when. Six distinct drip and engagement flows, all gated by a single one-click unsubscribe link in every footer. Transactional mail (trial reminders, alerts, billing, password reset) stays on separate settings and is never affected. If a flow isn't useful for you, the unsubscribe link flips a flag and every lifecycle email stops.

• NewDay 1 onboarding nudge: if you haven't added a monitor yet, one short email walks you through the 60-second setup. Skipped entirely if you're already monitoring something.
• NewDay 3 visual-monitoring nudge: if you have a monitor but haven't turned on visual monitoring, one email explains what it catches and links to the setting.
• NewDay 14 honest check-in: two weeks in, one email asks whether Visual Sentinel is earning its keep and (if TrustPilot is live for the brand) invites a short review. Detractor path is just 'reply to this email'. The inbox is watched.
• NewDormant re-engagement at 2-3 weeks: if you signed up but never added a monitor, one last soft nudge asking what blocked you. If we can help, reply. If not, the one-click unsubscribe is in the footer.
• NewLapsed re-engagement at 30 days: if you haven't logged in for a month but have monitors running, you get a 30-day activity recap (checks run, incidents detected, uptime, next SSL expiry). No pitch, just the numbers.
• NewFree-tier weekly summary (Monday mornings): seven-day rollup with a context-aware upgrade pitch picked by the engine, not a generic "upgrade now" banner. Incident this week? WhatsApp pitch. Never tried visual monitoring? Visual pitch. Slow site? Performance pitch. Everything in order? No pitch.
• NewMilestones: emails when you catch your first incident, cross 100 and 1,000 checks, and hit your 30-day anniversary. Small dopamine hits with actionable next steps.
• NewMonthly product update digest (1st of each month): summary of what shipped in the last 30 days, pulled directly from this changelog. Skipped automatically if nothing new shipped (no empty digests).
• ImprovedEvery lifecycle email has a one-click unsubscribe link in the footer AND an RFC 8058 header so Gmail and Outlook show their native "Unsubscribe" button right in the inbox. No login required, one click flips a flag server-side.

Sign up with Google, start your 7-day trial, get every feature unlocked. That was already the promise, but a cluster of gating bugs was making the product look like a Free plan with some upsells sprinkled in. This release cleans that up end to end (monitor tabs, schedule step, sidebar badge, billing copy, integrations page).

• FixMonitor detail pages now open Performance, Visual, Content, and DNS History tabs during the trial instead of showing "Unlock with Free Trial" to users who are already on the trial.
• FixSchedule step on the New Monitor wizard now offers 1-minute check frequency during the trial (was capped at 5 minutes).
• FixStatus page limit during the trial now shows the correct allowance instead of being capped at 1.
• FixSidebar plan badge now shows "Trial · Xd" in green during the trial, so you can see your remaining days at a glance. It used to just say "Free".
• FixThe "You're on the Free plan" top banner no longer shows to trial users. It was misleading because the trial already unlocks visual monitoring, WhatsApp/Slack alerts, and everything else on the banner.
• FixBilling page no longer says "billing starts on DATE" for the no-card trial. The no-card trial is truly free: your account simply drops back to the Free plan after 7 days (we email you a reminder before and a recap after, nothing is charged).
• FixCloudflare integration card no longer shows a phantom "Connected · 0 zones" state to users who never linked their Cloudflare account.
• FixAI Insights page loads again instead of erroring out. A stale database field reference was making the page crash on first load.

Narrowing the unified-auth rollout: API keys can no longer reach AI-powered endpoints. Your AI chat assistant, AI insights, incident summarizer, and monitoring digest stay behind your browser session only. This is about preventing token-cost abuse from a leaked key, not a feature regression. Your existing integration work with API keys is unchanged for everything else (monitors, incidents, status pages, teams, etc.).

• SecurityAI endpoints (/api/chat/*, /api/ai/insights, /api/incidents/[id]/summarize, /api/reports/digest) now require a cookie-based session. API keys cannot invoke these features. Reason: AI calls cost money per request and are attractive targets for abuse with a leaked key.
• ImprovedPre-login AI chat widget (/api/chat/public) is unaffected, still publicly available and rate-limited per IP.
• FixInternal build reliability fix bundled with the AI carve-out.

The unified-auth rollout that started in 2.24.0 is now complete. Every tenant-facing API endpoint accepts both session cookies and Bearer API keys. Six endpoints stay session-only by design (auth flows, billing checkout, OAuth init, invitation-accept, account-delete, org-switch). The API docs at /docs now reflect the final state with a dedicated mobile-app section.

• NewBatch 5 migrated 35 more endpoints: all integrations (Discord, Slack, PagerDuty, Webhooks, Google Analytics), chat and support, notification channels read, team member lists, server alerts, AI usage billing, email-tracking stats, report generation, monitor-URL test, incident summaries, and more. API keys with the matching scope can now hit them.
• NewAPI docs at /docs refreshed with a dedicated Mobile Apps section, the full list of session-only exceptions, per-key rate-limit documentation, and a clearer bearer-token authentication walkthrough.
• ImprovedSix endpoints kept session-only by design: auth flows, billing checkout (supports anonymous signup), Slack OAuth init, organization invitation-accept (email-link flow), account deletion (blast-radius guardrail), and organization-switching (cookie mutation).
• ImprovedExisting API keys keep working unchanged. Wildcard (*) scope and matching resource scopes (monitors, channels, organization, analytics, maintenance, user, etc.) now reach every unified endpoint.

Fourth batch of the unified-auth rollout. API keys can now drive onboarding flows (auto-setup, save-step, select-plan, start-no-card-trial, complete, status) and track analytics events (journeys, subscription lifecycle). The API key scope picker now exposes three new resources in the UI: Analytics, Maintenance Windows, and a clearer description for User Profile.

• NewAPI keys can now run the onboarding endpoints (/api/onboarding/auto-setup, /complete, /save-step, /select-plan, /start-no-card-trial, /status) and the analytics endpoints (/api/analytics/journeys, /api/analytics/subscription-events).
• NewAPI key scope picker in Settings -> API Keys now lists three new resources: Analytics (journey + subscription-event tracking), Maintenance Windows (scheduled maintenance), and the User Profile entry description now mentions onboarding.
• ImprovedExisting API keys keep working unchanged. A key with the matching resource scope (analytics, maintenance, user) can hit the newly unified endpoints immediately.
• SecurityAccount deletion (/api/user/delete-account) stays session-only by design. API keys cannot delete the account they belong to.

Third batch of the unified-auth rollout. API keys can now list and read your status pages, read their details, list and read maintenance windows, fetch AI-generated monitoring digests, and check whether all alerts are paused. Your existing keys gain access immediately based on the scopes they already have.

• NewAPI keys can now list and read status pages (/api/status-pages and /api/status-pages/[id]), list and read maintenance windows (/api/maintenance and /api/maintenance/[id]), fetch AI monitoring digests (/api/reports/digest), and check the current alerts-paused state (/api/alerts/pause-all GET).
• ImprovedReport endpoints now map to the "monitors" scope, since reports are derived from monitor data. A key with monitors:read can fetch your digests.
• ImprovedExisting API keys keep working unchanged. A key with a wildcard (*) scope, or the matching resource scope (status-pages, maintenance, monitors, alerts), can hit the newly unified endpoints immediately.

Second batch of the unified-auth rollout. Your API keys can now read your bell-icon notifications, your notification preferences (quiet hours, digest cadence), your digest settings, upload or remove your avatar, and read your current plan + limits + usage. Mobile apps and integrations no longer have to fall back to cookie-based auth for these.

• NewAPI keys can now reach /api/notifications (bell-icon inbox), /api/notification-preferences (quiet hours, grouping, digest), /api/user/digest-preferences, /api/user/profile/avatar (upload + delete), and /api/plan.
• ImprovedAPI key scope mapping tightened: push-subscription endpoints now correctly map to "channels" scope (was falling through to a generic default), plan endpoint maps to "organization" scope, and notification-preferences map to "user" scope.
• ImprovedExisting API keys keep working unchanged. A key with a wildcard (*) scope, or the matching resource scope, can hit the newly unified endpoints immediately.

The first batch of routes that were previously session-only now accept Bearer API keys too. That means integrations can now read your organization, teams, user profile, SMTP settings, and more using the same API key they use for monitor data. Admin endpoints (platform-level) stay session-only. Two new scopes are available: "user" and expanded "organization".

• NewAPI keys can now reach 8 admin endpoints that were previously session-only, including /api/user/profile, /api/organization, /api/teams, /api/organization/smtp, and /api/api-keys list.
• NewNew "user" scope for API keys (read/write) gives access to your profile and preferences without exposing organization-wide data.
• ImprovedThe "organization" scope description in the API key creation dialog now clearly lists what it covers: org settings, teams, members, SMTP, and API-key management.
• ImprovedExisting API keys keep working exactly as before. Integrations with a wildcard (*) scope key, or an "organization" or "user" scoped key, automatically gain access to the newly unified endpoints.

Fixed a subtle bug that affected anyone belonging to multiple organizations. API keys are now locked to the organization you were switched to when you created them, instead of silently resolving to an older org in your account. If you create a key while in Org A, it will always act on Org A data.

• SecurityAPI keys are now tied to the organization they were created in. Previously, if you belonged to multiple organizations, a new key could silently authenticate against a different (usually older) organization than the one you were switched to when you created it.
• FixThe API Keys list page now only shows keys that belong to the currently selected organization. Before, a user in multiple organizations would see the same keys appear under every organization they were a member of.
• ImprovedExisting keys continue to work exactly as they did before, resolving to the same organization they already resolved to. No action required from integrators.

Small SEO polish. The homepage meta description was a few characters over the ideal length used by search engines, so it was getting flagged by Bing. Shortened from 176 to 157 characters.

• ImprovedHomepage meta description shortened to 157 characters, within the 150-160 range recommended by Bing and Google for full display in search results.

Three real visual bugs squashed, plus a silent email bug fix. Your monitor charts no longer dive to 50% uptime on the rightmost data point (that was a partially-sampled current bucket, not a real outage). Y-axis labels no longer get their leading digit clipped on the left. And the weekly / monthly report emails now show a real average response time computed from your checks, not 0ms.

• FixThe "Uptime & Response Time" chart no longer shows a cliff at the rightmost point. The currently-filling 15-minute bucket is now excluded until it has a full sample, so you can stop squinting at "is my site actually 50% down or is that just the chart?".
• FixY-axis labels on every chart across the app no longer get their leading digit clipped (labels like "3600ms" that read as "6600ms"). Affected the overview page, monitor detail, performance tab, server metrics, incident root-cause timeline, and API monitor views.
• FixWeekly organization digest emails and monthly report emails now compute the real average response time from your checks, instead of always showing 0ms. If you have ever looked at those emails and wondered why response time was always zero, this is why.
• ImprovedUnused database column on every monitor dropped. Zero user-visible impact, the column was never populated, just cleanup.

Small polish on the API key creation flow. The modal that shows you your new key once it is generated is no longer cramped, the copy button now actually sits next to the key (with a clear "Copied" confirmation), the key auto-selects on click, and a small usage snippet with a curl example is now shown so the next step is obvious.

• FixThe "API Key Created" modal copy button now sits inline next to the key input with a proper "Copy" / "Copied" state, instead of a tiny floating clipboard icon that could land outside the input.
• ImprovedClicking the key field now auto-selects the whole key so Cmd+C / Ctrl+C works instantly without reaching for the button.
• ImprovedModal now includes a curl example showing how to send the key as a Bearer token, with a link to the API docs.

Two small but annoying things fixed. Blog posts no longer show a brief hydration flicker on the published date for readers outside UTC, and the US check region now always returns a proper, actionable error code instead of ever appearing to hang.

• FixBlog post and blog list pages now render the published date in UTC regardless of your timezone, so the date stays consistent and no longer triggers a client-side rendering warning in the console.
• ImprovedUS region checks are now more resilient: if DNS or a specific request phase stalls, the region returns a clear error (DNS_ERROR / TIMEOUT) within seconds instead of ever getting stuck. Your incident timelines from the US node are now strictly more accurate.

Extending yesterday’s response-time correctness fix. The /monitors list page and its uptime / performance sub-views were still showing each monitor’s last single check in the response-time column. They now show the same rolling 24-hour average as the detail page, so the numbers are consistent wherever you look.

• FixThe response-time column on the /monitors list, /monitors/uptime, and /monitors/performance pages now shows each monitor’s rolling 24-hour average instead of its last single check, matching the detail page.
• ImprovedOrg-wide averages, fastest/slowest picks, and the response-time histogram on /monitors/performance now reflect 24-hour aggregates per monitor rather than a single-moment snapshot.

Follow-up to yesterday’s response-time fix. The Response pill in the header row next to Uptime and SSL now reads the same rolling 24-hour average as the "Avg Response (24h)" stat card below it, so the two numbers agree and the whole header row is consistently showing aggregates rather than the pill breaking from the pattern.

• FixThe Response pill in the monitor header now matches the "Avg Response (24h)" stat card value, so a single recent check no longer makes the header pill disagree with the card.

The "Avg Response" number on each monitor detail page was silently showing the response time of the most recent check, not an average, so it would swing between refreshes. It is now a real rolling 24-hour average computed from every check in the window, and the header pill next to your uptime shows the current-health "last response" separately.

• FixThe "Avg Response" stat on a monitor's detail page is now a true rolling 24-hour average, labelled "Avg Response (24h)" so the time window is explicit.
• FixThe header health pill now shows the response time of the most recent check, separate from the 24-hour average, so you can see the current health signal without it moving the historical number.
• ImprovedManual check, queue re-check, and auto-test after creating a monitor all update the right field now: the "last response" pill moves on a single check, the 24-hour average only updates when fresh monitor data is fetched.

Maintenance times entered in the form are now interpreted in your organization timezone, not your browser timezone, so 7:49 AM means 7:49 AM to you regardless of where you are sitting. The create dialog shows the active timezone plainly, and cards render every timestamp with an explicit offset suffix.

• FixMaintenance start and end times are now interpreted in your organization timezone on submit, fixing a silent offset shift that affected any org not set to UTC.
• ImprovedThe "Schedule Maintenance" dialog now shows the active organization timezone clearly (e.g. "America/New_York (EDT, GMT-4)") with a link to Settings if you need to change it.
• ImprovedMaintenance cards now render Starts and Ends in the timezone the record was created in, with an explicit GMT offset, so timestamps stay stable even if the org timezone is changed later.

Broader follow-up to 2.23.1. Maintenance windows now suppress every notification type during the active window, not just UI Changed. SSL expiry, DNS change, content change, performance degraded, and slow response alerts all respect the window. History (DNS snapshots, screenshots, content hashes) is still captured so you can review exactly what happened during maintenance once it ends.

• FixEvery alert type (SSL, DNS, content, performance, slow response, visual) is now suppressed during active maintenance windows, not just UI Changed.
• FixData collection (DNS snapshots, content hashes, screenshots) continues during maintenance so your change history stays accurate, only the notifications are muted.

A fix and a polish. Scheduled maintenance windows now correctly suppress visual-change (UI Changed) alerts, not just uptime alerts, so a planned site update does not flood your channels. The Maintenance page card is also redesigned with clear Starts / Ends / Duration cells, timezone, live countdown, and clickable affected-monitor links.

• FixVisual change (UI Changed) alerts are now suppressed during active maintenance windows, matching the existing behavior for uptime alerts.
• ImprovedMaintenance page card redesigned: explicit Starts, Ends, and Duration cells with timezone, live countdown ("Starts in 4h 12m" / "Ends in 32m" / "Ended 3d ago"), and clickable affected-monitor links.
• ImprovedIn-progress maintenance windows now visually stand out with an amber border and pulse indicator so it is obvious which window is live.

The fourth guide in the error-diagnosis cluster lands in the Knowledge Hub. A plain-language explanation of what DNS errors actually are, what the Chrome error messages really mean under the hood, how a DNS problem can surface as "your connection is not private," and step-by-step fixes for visitors, site owners, and gaming consoles (PS5, Xbox).

• NewNew Knowledge Hub guide: "What Is a DNS Error? Meaning, Causes, and How to Fix It." Covers the six DNS response codes you actually see (NOERROR, NXDOMAIN, SERVFAIL, REFUSED, FORMERR, NOTIMP), the Chrome error surface (DNS_PROBE_FINISHED_NXDOMAIN, ERR_NAME_NOT_RESOLVED, and friends), how DNS problems can look like SSL warnings, and a six-step fix tree for visitors.
• NewSide-by-side PS5 and Xbox DNS-error fix instructions with exact menu paths and recommended DNS servers.
• ImprovedThe existing "DNS server not responding" guide and the new "What is a DNS error" pillar now cross-link: the pillar covers the broad category, the narrower guide drills into the resolver-unreachable case.

A focused pass on visual change detection after a customer report showed the same underlying change being split into two separate incidents with fragmented timing. The lifecycle is now end-to-end accurate: an incident stays open until the page really returns to baseline or you accept a new one, duration reflects the real change window, and the incident record itself carries the server correlation that the alerts already showed.

• FixVisual incidents no longer auto-close after 4 hours. A visual incident now stays open until the page actually returns to baseline, you accept a new baseline, or you resolve it manually.
• FixIf a visual change persists after an incident was resolved (against the same baseline, within 24 hours), the previous incident is reopened instead of a new one being created. "Detected at" and "Was changed for" stay anchored to the original detection time.
• FixVisual incident records now include linked server name, server health snapshot, and the diagnosis phrase, matching what the alert channels (email, WhatsApp, Slack, Discord) already show.
• FixRecovery emails now always include a "Was changed for" row, falling back to "Unknown" when the original detection time is not available, matching WhatsApp behavior.
• FixResolved visual incidents now persist their total duration to the database, so historical reporting and incident views show the correct "Was changed for" value.

Shipped two more Knowledge Hub guides (504 Gateway Timeout, SSL Errors) to round out the core error-diagnosis cluster, and refreshed the three highest-traffic comparison and explainer posts with first-party data sourced from our live monitoring.

• NewNew Knowledge Hub guide: "What Is 504 Gateway Timeout (Meaning, Causes, and Fix)." Covers the timeout trio of 504 vs 502 vs 408, platform-specific diagnosis on nginx, Cloudflare, AWS, and Vercel, and the Cloudflare 504 vs 524 distinction.
• NewNew Knowledge Hub guide: "What Is an SSL Error and How to Fix It." Decodes the 10 most common SSL error messages, platform-specific diagnosis across Chrome, Safari, Firefox, Edge, and major web servers, with openssl diagnostic patterns.
• ImprovedTop three comparison and explainer posts now carry first-party data from our own monitoring instead of generic claims.

A deep 502 Bad Gateway troubleshooting guide written from a DevOps engineer’s perspective lands in the Knowledge Hub, plus mobile polish on the blog and better tap targets on tools and compare pages. Homepage caching also got a cleanup behind the scenes so return visits feel snappier.

• NewNew Knowledge Hub guide: "What Is 502 Bad Gateway and How to Fix It." Covers root causes, diagnosis on nginx, Cloudflare, AWS and Vercel, and how to prevent 502s reaching users.
• ImprovedBlog landing page on mobile now shows the latest two posts above the category filter so real content is above the fold.
• ImprovedHeader "Start Monitoring" button on free tools and comparison pages now meets the 44px touch-target minimum on phones.
• ImprovedHomepage caching policy is now applied cleanly at the edge, so return visits benefit from the stale-while-revalidate policy added in 2.19.1.
• FixProduction deployments now refresh the background worker container reliably when worker code changes.

An internal deploy fix. The previous release (2.19.2) had all the features (five new live-status pages, better content, performance and design) built and staged, but did not reach production due to an internal release-pipeline issue. This release ensures everything that was waiting now ships. No functional difference from 2.19.2; this is the version that actually reaches you.

• FixThe 2.19.2 release payload now deploys to production. An internal release-pipeline issue had held it back.

Added Venmo, Apple Pay, Apple Music, Apple TV+, and Rockstar Games (GTA Online servers) to the live-status page set after keyword research confirmed high demand and low competition in their SERPs. Total live-status pages now at 79.

• NewNew live status page at /tools/status/venmo for Venmo payments, sign-in, and bank transfers.
• NewNew live status page at /tools/status/apple-pay for Apple Pay in-store, checkout, Apple Cash and Express Transit.
• NewNew live status page at /tools/status/apple-music for Apple Music streaming, library sync, and iCloud Music Library.
• NewNew live status page at /tools/status/apple-tv for Apple TV+ streaming, MLS Season Pass, and live events.
• NewNew live status page at /tools/status/rockstar for Rockstar Games servers including GTA Online and Red Dead Online.

A focused pass following a full SEO audit. Every live-status page now carries genuinely unique per-service content (not just a template). Mobile pages load and render better. Marketing copy is honest about what Visual Sentinel actually is (built by a DevOps engineer, not a generic full-stack developer). Compare pages no longer confusingly imply that we sell our competitors.

• NewEvery one of the 74 live-status pages at /tools/status/[service] now carries a unique "About" paragraph and 2 service-specific FAQ answers, written by hand, instead of sharing one template.
• ImprovedStatus pages stopped jumping around at load. The live status card now renders in a reserved height so there is no visible shift when the check completes.
• ImprovedHomepage hero title resized on phones so it no longer wraps to 6 lines and hides the value prop below the fold.
• ImprovedPaddle checkout script no longer loads on pages that do not need it (homepage, blog, tools, compare). About a second faster first paint on those pages.
• ImprovedImages site-wide now serve AVIF first, smaller and sharper than WebP on modern browsers.
• ImprovedBrowser back-button navigation is now instant again. Previous cache-control settings were forcing a full re-render on every back press.
• FixAbout page now correctly describes the founder as a DevOps engineer and sysadmin, not a generic full-stack developer.
• FixBlog post meta author tag now matches the schema (Acefina LLC) on every post.
• FixCompetitor comparison page titles fixed a stray space before the comma that read as a typo.
• FixPricing page title shortened to "Simple, Transparent Pricing" so the keyword sits at the front.
• Fix/blog/<missing-slug> 404 page no longer renders the header twice.

We scaled the free live status checkers from 27 services to 74 with AI platforms (ChatGPT, Claude, Gemini, Perplexity, Midjourney), consumer tier 1 (YouTube, Netflix, Instagram, Facebook, Twitter, Gmail, TikTok, Roblox), and cloud / dev infrastructure (Cloudflare, AWS, Azure, Google Cloud, Zoom, Slack, Dropbox, Heroku, Netlify, DigitalOcean, Jira, GitLab, Firebase, and more). Every status page ships with real-time checks from our EU and US nodes, a proper FAQ block, and a one-click "Monitor this yourself" CTA. Blog URLs are now year-free so the same post can be refreshed across years without breaking any inbound links.

• NewNew live status pages for ChatGPT, Claude, Gemini, Perplexity, Midjourney, GitHub Copilot, and Cursor. Check if any of them are down right now at visualsentinel.com/tools/status/<service>.
• NewNew live status pages for YouTube, Netflix, Instagram, Facebook, Twitter, Gmail, Amazon, TikTok, Snapchat, Roblox, Xbox, PlayStation, Minecraft, Twitch, Steam, PayPal, Outlook, Hulu, Pinterest.
• NewNew live status pages for Cloudflare, AWS, Google Cloud, Azure, Zoom, Slack, Dropbox, iCloud, Disney+, Max, Heroku, Notion, Netlify, DigitalOcean, Jira, Zendesk, Trello, Telegram, GitLab, Firebase.
• ImprovedBlog URLs are now year-free. Same post, refreshable across years, no broken backlinks.
• ImprovedDuplicate blog posts consolidated into single canonical URLs so the best version of each guide is the one that ranks.

A focused release on making the product tell the truth. Monitors with DNS problems now correctly show as down (they were being silently marked operational). Cloudflare imports skip zones with no origin. Competitor comparison tables were rebalanced to credit the competition fairly. New /cookies, /accessibility, and /bot pages published. Em-dashes removed from user-facing copy per house style.

• FixMonitors whose domain has no DNS records (parked, freshly-imported Cloudflare zones, expired domains) now correctly show as "Down: DNS resolution failed" instead of "Operational, 100% uptime, 0 ms".
• FixCloudflare import now pre-checks each zone for an A or AAAA record and skips zones with no origin, surfacing them in the import summary with a specific notice so you can fix DNS in Cloudflare before retrying.
• NewMonitor detail page now shows a clear amber warning if the monitor has no alert channels attached, with one-click access to the settings tab.
• FixSetup-progress gauge now counts email as a valid alert channel. Accounts that used only email were previously stuck below 100% indefinitely.
• FixMonitor list headers now break down the status counts (X operational, Y down, Z degraded, W paused) instead of showing only the operational number.
• NewNew /cookies page lists every first- and third-party tracker we use, why we use it, and how to manage your preferences.
• NewNew /accessibility page stating our WCAG 2.1 AA commitment, known limitations, and how to report issues.
• NewNew /bot page with our stable monitoring User-Agent and ready-to-paste WAF/firewall rules for Cloudflare, AWS, and Nginx so customers can whitelist our checks reliably.
• ImprovedCompetitor comparison pages rebalanced. The UptimeRobot table now credits UptimeRobot for keyword monitoring, port monitoring, and SMS/voice alerts that were previously omitted.
• ImprovedNotification channel count reconciled to 11 across every mention on the site (homepage, plan cards, FAQ, notification-channels page).
• ImprovedRegion claims corrected from "3 global regions (EU, US, Asia)" to "2 regions (EU + US)" across the site. Asia coming soon.
• ImprovedLimited-time discount banner renamed to "Launch Offer" with the real combined discount percentage shown explicitly, so the banner does not contradict the actual checkout price.
• SecurityClickjacking protection restored sitewide. Public status pages remain embeddable; the dashboard and marketing site no longer are.
• SecurityPublished a dedicated security contact at /.well-known/security.txt for responsible disclosure.
• FixWorker no longer rebuilds every monitor scheduler on every restart. Reduces the window where monitors could go dark during a worker crash.
• FixAPI 404 responses are now JSON for API routes instead of a 25 KB HTML page. Clients integrating with our API will no longer crash on JSON parse errors.

A sweep of marketing copy, trial-state emails, and conversion UX. Stats and reviews now show only what is real. New monitors are live immediately (instead of waiting for a worker restart). Free plan users no longer see a paywall.

• ImprovedPublic stats and review counts now reflect reality. Any inflated numbers and unverified rating schema have been removed.
• ImprovedTrial expiry now keeps you on the Free plan with your 3 most recent monitors running, without any paywall. Existing trial emails have been rewritten to match.
• FixNew monitors now receive recurring checks immediately after creation (previously only an initial check fired, and recurring checks started on the next worker restart).
• FixBroken dashboard links across the server alert banner, incident detail, AI insights, and monitor-form flows now resolve correctly.
• FixWelcome email now shows the correct monitor limits for Business (60) and Agency (300).
• Fix"Live chat" banner, "3 regions (EU, US, Asia)" claim, and the stale 14-day trial references across blog posts, the AI chat assistant, and API error messages have been corrected.
• SecurityMeta Pixel now fires only after explicit opt-in on EU traffic. Enhanced security hardening on a few mutation endpoints.

• FixThe Free plan CTA on the pricing page and billing settings was sending logged-in users to a 404. Now opens the dashboard overview as intended.
• FixThe "Welcome to the Free plan" email button was pointing at a non-existent /dashboard URL. Fixed.

The onboarding plan-selection page now shows the Free plan alongside paid tiers and uses the new single-story trial messaging.

• ImprovedPlan selection page now shows a Free plan card next to the paid tiers. Pick Free to start a 7-day full-feature trial with no card, or pick a paid plan for a 10-day trial with a card on file.
• FixRemoved the stale trial-mode toggle and old "card saved, not charged until day 15" copy that was left over from the earlier trial model.

Cleaner SSL expiry alerts: no spurious "first threshold" alert when a monitor is added for a cert that was already past that threshold, and the expiry date now renders in your organization's locale instead of a raw GMT dump.

• FixSSL expiring alerts no longer fire the top-threshold warning when a monitor is added for a certificate that was already below that threshold. For example, a cert with 21 days remaining on a [29, 6, 1] configuration will no longer trigger a 29-day warning, alerts only fire when the cert actually crosses a threshold under our watch.
• FixSSL expiry dates in WhatsApp alerts now render in your organization's timezone, date format, and time format (e.g. "May 10th, 2026, 4:16 AM GMT+5") instead of the raw Date output.
• ImprovedInternal test reliability and CI hygiene improvements.

Every account now has a permanent home on the Free plan (3 monitors, HTTP + SSL, EU + US, 10-minute checks) plus a clearer trial story: start free for 7 days with every paid feature unlocked (no card), or pick a paid plan for a 10-day trial with a card on file.

• NewNew Free plan with 3 monitors (HTTP uptime + SSL cert validation), EU + US check locations, 10-minute check intervals, 1 status page, and email + push notifications. Free forever, no credit card.
• NewStart free with 7 days of every paid feature unlocked (visual monitoring, DNS history, content change detection, AI insights, 1-minute checks, every notification channel). On day 8 you keep the Free plan automatically, no surprises, no pauses, your 3 oldest monitors keep running.
• ImprovedPaid plan free trials shortened from 14 to 10 days. Same card-on-file verification, same full access, just a tighter window.
• ImprovedTrial end email rewritten: instead of "monitors paused", you now get a "Welcome to Free" email with a clear feature summary and a list of which monitors are active.
• ImprovedPricing page now shows the Free plan card alongside the paid tiers, with the unified trial messaging front and center.
• ImprovedRefund policy and terms updated to reflect the new Free plan + dual-trial options.

• FixFixed a bug that caused monitor checks to fail with a database encoding error when a target site returned binary data with embedded null bytes.
• FixFixed a React hydration warning on the free Website Checker tool page.
• ImprovedPerformance tests that cannot reach an external URL (firewall/blocklist) and transient Google PageSpeed outages no longer trigger internal alerts.

Fixed the "Avg. Uptime" card on the Overview dashboard so paused monitors no longer drag down your fleet average. Paused monitors also no longer clutter the Monitor Health table.

• FixOverview "Avg. Uptime" now averages across active monitors only. Previously, paused monitors were being counted at their stale uptime value, which could incorrectly push the fleet below your SLA target even when every active monitor was healthy.
• FixThe Monitor Health table on Overview now hides paused monitors. Paused monitors still appear on the full monitors list and stay visible if you have pinned them explicitly.
• FixAI chat and daily/weekly digest emails use the same corrected calculation, so "your fleet is healthy" conclusions no longer include paused monitors in the math.
• ImprovedInternal test reliability improvements to reduce deploy pipeline flakiness.

Alerts on Discord, Slack, Telegram, and webhooks now carry the full picture (response time, threshold, URL, region, linked server health, and a root-cause hint) in a consistent format. Timestamps now respect your organization's timezone and date/time format preferences on every channel.

• FixDiscord alerts are no longer two-liners. Every alert now shows the right fields for its type (response time for slow, days remaining for SSL, diff percent for visual, etc.) plus server health and a root-cause hint when a linked server is attached.
• FixSlack alerts now pull details from structured event data instead of trying to parse the message body, so response time, threshold, and SSL days always appear correctly.
• FixTelegram alerts rebuilt with a clean per-event format, proper emoji per alert type, and key:value fields instead of a wall of prose.
• FixWebhook payloads are now structured: top-level event, severity, monitor, details, linkedServer fields. The original metadata block is still included for backwards compatibility. Template variables expanded to include alertType, threshold, daysRemaining, issuer, region, duration, server fields, and more.
• FixNotifications on every channel now respect your organization's timezone and date/time format preferences. Timestamps no longer fall back to server locale or raw ISO for slow response, visual, SSL, DNS, content, anomaly, or performance alerts.
• FixCleaned up error phrasing across all channels. SSL errors now read "SSL handshake failed (server rejected the secure connection)" instead of the old hyphenated format. Same cleanup applied to email subjects and incident descriptions.
• ImprovedInternal build reliability improvements covering the visual monitoring pipeline.

Fixed a class of WhatsApp alerts that were rendering as "DOWN" for events that were not actual outages (anomalies, content changes, DNS changes, performance degradation). Now every alert type, including visual restored, SSL renewed, and anomaly resolved, uses its own properly-framed template with server context when available.

• FixNo more false "DOWN" WhatsApps for anomaly, content change, DNS change, or performance degradation events. Each event now uses its own template with the correct framing and severity.
• NewVisual restored, DNS restored, content change, SSL renewed, anomaly detected, anomaly resolved, and performance degradation now each have their own WhatsApp template with linked-server context where applicable.
• ImprovedSimplified WhatsApp delivery pipeline. Single render path, no fallback to deleted templates, clear log entries when an unknown event type is received.

Every alert across every channel now tells you WHY something is wrong, not just that it broke. Unified notifications with linked-server health, root-cause diagnosis, and consistent formatting across WhatsApp, Slack, Discord, Teams, Telegram, and email.

• NewSmart Diagnostics in every channel, when a monitor is slow or down and has a linked server, the alert now includes one-line diagnosis: "CPU 94%, likely root cause" or "All metrics normal, likely app-level (deploy, DB, API, traffic, attack)". Same sentence goes to WhatsApp, Slack, Discord, Teams, Telegram, email, and webhooks so your team reads the same signal everywhere.
• NewLinked server context on every alert, when a monitor has a confirmed server link, the alert renders the server name, current CPU/RAM/disk, and a deep-link to the server detail page. Healthy servers get a "likely app-level" hint instead of just a silent line.
• NewUnified WhatsApp templates, fresh set of 13 templates replacing the old drift-prone batch. Consistent emoji, consistent layout, dedicated rows for Server health and Diagnosis on linked variants. Shorter, cleaner, no redundant footer.
• NewBulk link monitors to a server, new "Link to server" option in the monitors list bulk-actions dropdown. Pick a server, pick the monitors, pair them in one click. Replaces the old flow that required opening each server detail page.
• NewPer-monitor Google Analytics + Search Console in digest emails, weekly and monthly reports now show traffic and top queries per linked monitor, not just org-wide. AI executive summary in the digest also accounts for traffic trends alongside uptime.
• NewHomepage and pricing page updated, the full 2.12–2.14 feature set (Google integration, Cloudflare one-click import, server correlation, smart diagnostics) is now visible on the marketing pages and in the plan comparison matrix.
• NewLinked-monitors count on server alerts, "4 sites on this server may be affected" / "4 sites on this server are back online" renders in server-offline and server-recovery emails so you instantly see blast radius.
• NewServer recovery tells you what went wrong, "Previous issue: High CPU usage" instead of "Previous Issue: Unknown". Duration since going offline included automatically.
• FixCorrelation bug on slow-response alerts, monitors with a healthy linked server used to send alerts with only the server name and no diagnosis context. Now every linked monitor sends CPU/RAM/disk and a root-cause hint, and the incident record is correlated retroactively.
• FixBackfilled 869 historical incidents on production to show their linked server. Prior incidents will now display server correlation in the UI even for events that fired before this release.
• FixMonitors disappearing after Cloudflare import, the monitors list no longer goes empty after importing CF-proxied domains. Cache is invalidated the moment the import completes, so the new monitors show up immediately without a hard reload.
• FixReadable error messages, raw OpenSSL and Node networking errors like "write EPROTO 008D3985017F0000:error:0A000438:SSL routines:ssl3_read_bytes:tls..." now render as "SSL handshake failed (server rejected the secure connection)". Same normalization applies across every channel.
• FixPowered-by footer defaults corrected for whitelabel agencies. Turning on whitelabel mode now hides our branding by default instead of requiring a second click to remove it.
• FixCloudflare modal no longer shows a 404 in the browser console when you haven't connected yet. The check-if-connected probe returns a clean state instead of an error.
• FixBulk edit in the monitors list is faster, fixed a scale issue that would slow the list query on orgs with thousands of monitors.
• ImprovedFaster Cloudflare origin lookups, DNS record calls cached per zone for 5 minutes so server-site correlation doesn't hit the Cloudflare API on every check.
• ImprovedWildcard DNS record support in server correlation, if you have a `*.example.com` wildcard in Cloudflare, monitors under subdomains now correctly resolve to the origin server.
• ImprovedTimestamp consistency across alerts, every timestamp now renders in your organization's timezone instead of drifting to UTC on certain alert types.
• SecurityEnhanced tenant isolation on mutation endpoints and hardened email open-tracking protections.

Connect Google Search Console and Analytics, import domains from Cloudflare, and a round of critical reliability fixes for multi-region monitoring and server offline incidents.

• NewGoogle integration (Phase 1), connect Google Search Console and Analytics 4 from one place. Unified sign-in with your Google account, sites picker, and automatic sync of the last 7 days on connect to compensate for Search Console's indexing delay.
• NewCloudflare integration, import all your Cloudflare-proxied domains as monitors in one click. Visual Sentinel automatically wires a proxy-bypass CNAME so you monitor the origin (not Cloudflare's cached edge) for accurate uptime.
• NewAuto-Link All servers, one button to connect every monitor to its matching server via DNS resolution. Automatic server links are refreshed daily and on monitor URL changes.
• New8 new status pages, Reddit, LinkedIn, WhatsApp, ESPN, Walmart, SoundCloud, Indeed, Expedia. All with real-time multi-region checks.
• NewInstall the server agent without sudo, the setup modal now shows both sudo and non-sudo install commands, so you can monitor managed or shared servers where root access isn't available.
• NewPer-region response times on status pages, public status pages now show response-time capsules per region (EU / US), so visitors see geographic performance at a glance.
• FixMulti-region outage detection, fixed a critical bug where monitors checked from multiple regions could stay "Operational" during genuine outages. Region checks now correctly record failures when a check node is unreachable.
• FixEU and US checks no longer block each other, during outages, a slow check in one region no longer delays or skips scheduled checks in the other region.
• FixServer offline now creates an incident, when a server agent stops reporting, Visual Sentinel now opens a "Server Offline" incident in your incidents timeline instead of only sending a one-off alert. The incident auto-resolves when the server comes back.
• FixServer detail page now shows the correct last alert, "Last alert" no longer sticks to a stale CPU/memory breach when the server is currently offline.
• FixSSL expiry alerts no longer spam, each expiry threshold (30/14/7/3/1 days) fires exactly once per certificate. Previously, once a threshold was crossed, the alert re-fired every check cycle.
• FixIn-app bell notifications no longer duplicate, one bell per incident, with updates landing in the incident timeline rather than flooding the bell.
• FixEmail deliverability: org logos now resolve correctly in emails, automatic retry on transient email-provider errors, and SSL alert WhatsApp templates with buttons render correctly.
• FixStatus page polish, removed duplicate headers, improved HTTP status detection, and paused monitors are now excluded from uptime calculations.
• ImprovedCross-region outage confirmation now logs full diagnostic context (response time, status code) for audit when investigating incidents.
• SecurityEnhanced security hardening across integrations and credential handling.

When your website goes down, Visual Sentinel now tells you WHY. Notifications include server health context, incidents auto-link to servers, and a root cause timeline shows exactly what happened.

• NewSmart notifications, when a monitor goes down and the linked server is under load, the alert includes server CPU, RAM, and disk usage so you know the root cause instantly
• NewGrouped server outage incidents, when multiple websites on the same server go down, Visual Sentinel automatically groups them into one "Server Outage" incident instead of flooding you with alerts
• NewRoot cause timeline, a visual chart in the incident detail view showing server metrics alongside website response time, with markers for when things went wrong
• NewDashboard alert banner, a warning banner appears on the dashboard when a server is stressed, showing how many websites may be affected
• NewServer alert enrichment, server CPU/RAM/disk alerts now mention how many linked websites may be impacted
• ImprovedWebhook payloads now include server context data when available for deeper automation integrations
• ImprovedIncident API responses include server data and parent/child relationships for grouped outages

Link your monitors to servers for instant root cause diagnosis. See server CPU, RAM, and disk metrics right alongside your website performance data.

• NewServer-Site Correlation, link monitors to the servers they run on. When your site slows down, instantly see if the server is under load with live CPU, RAM, and disk gauges on the monitor detail page
• NewAuto-detection, Visual Sentinel automatically suggests server matches based on IP address and hostname when you create a monitor. Confirm with one click.
• NewServer metrics mini-chart, toggle a time-synced CPU and memory chart below the response time graph to visually correlate website slowdowns with server resource spikes
• NewHosted websites view, see all monitors linked to a server in one place on the server detail page
• NewPer-region response time capsules, status pages now show separate color-coded response times for each monitoring region (EU, US)
• FixPaused monitors no longer affect status page health or uptime calculations
• FixVisual monitoring no longer crashes on slow-loading websites due to premature timeout detection
• FixWhatsApp notifications now send correctly even when monitor details are unavailable
• FixBlog pages no longer show brief content flicker on load
• FixPlan downgrade now properly cleans up background monitoring jobs
• SecurityEnhanced server security hardening

Three new monitoring landing pages, 35 new comparison FAQs, corrected pricing data across the entire site, and instant indexing via IndexNow.

• NewNew Endpoint Monitoring landing page, learn how Visual Sentinel monitors APIs, webhooks, and HTTP endpoints with 6-layer checks
• NewNew Synthetic Monitoring landing page, proactive website checks from multiple global regions before real users hit problems
• NewNew Server Monitoring landing page, CPU, RAM, disk, and network monitoring alongside your websites in one dashboard
• New35 new FAQs across all 7 comparison pages, honest, detailed answers about how Visual Sentinel compares to each competitor
• NewIndexNow integration, new and updated pages are instantly submitted to Bing and Yandex for faster indexing
• ImprovedSSL, DNS, and API monitoring pages now include deeper explanations and additional FAQs covering common questions like certificate chains, DNS record types, and API monitoring best practices
• ImprovedComparison pages now show accurate pricing, correct feature availability, and descriptive trial/tier information for each competitor
• ImprovedProfitWell Retain integration, improved subscription recovery for failed payments
• FixCorrected pricing data across all pages, consistent plan details everywhere
• FixStatus pages correctly shown as available on all comparison pages (previously showed "Coming soon")
• FixTrial messaging clarified: 7-day free trial (no card) or trial with card on all paid plans. Trial-with-card length has since changed to 10 days.
• FixRemoved duplicate text in homepage call-to-action section

Self-hosted US monitoring from Ashburn, VA with full performance data. Multi-region response time charts. Redesigned API key permissions.

• NewUS region monitoring now runs from a dedicated server in Ashburn, Virginia, faster, more reliable, and with full performance waterfall data (DNS, TLS, TTFB) matching EU quality
• NewPer-region response time chart, monitors with multiple regions now show separate colored lines for each location (EU, US) so you can compare performance across regions
• NewEdit permissions on existing API keys, no need to regenerate keys when you want to change access levels. New Stripe-style permissions table with Read/Write columns and select-all headers
• NewAPI keys are now organization-scoped, admins can see, edit, and revoke keys created by any team member
• NewVisual check interval configurable from Alert Settings page, set per-monitor or bulk-edit across all monitors
• NewCustom domain status pages now show proper SEO metadata (title, description, OG tags) instead of generic defaults
• ImprovedVisual monitoring restoration detection is now much faster, checks for recovery every visual cycle instead of waiting up to 60 minutes
• ImprovedBilling webhook handling expanded, better tracking of payment failures, subscription status transitions, and trial conversions
• FixAlerts API now accessible with API keys, previously required an unavailable scope
• FixAPI keys page now updates correctly when switching organizations
• FixRegion changes via dashboard now properly clean up old monitoring schedules, prevents duplicate checks from previous regions
• FixDialog modals no longer clip behind the navigation header

Critical fix for visual monitoring baselines reverting, plus incident dashboard improvements.

• FixVisual monitoring baselines no longer revert to old screenshots after being accepted, baselines now persist reliably across all check cycles
• FixIncident count now displays correctly in the sidebar navigation
• FixScreenshot preview in incident details can now be closed properly, clicking the X or backdrop dismisses the image as expected
• FixEmail verification button now appears on all notification channels, including those created before email verification was added

SSL alerts that actually escalate, automatic incidents for slow performance and expired certificates, and configurable SLA targets.

• NewConfigurable SLA target and response time thresholds in Settings > Preferences, set your own uptime goal and define what "degraded" and "critical" mean for your services
• NewAutomatic incidents for slow response times, creates a DEGRADED incident when response time consistently exceeds your threshold, auto-resolves when performance recovers
• NewAutomatic incidents for SSL certificate expiry, creates an incident when your SSL cert is about to expire or has expired, auto-resolves when renewed
• NewResponse time color coding across the dashboard, green, amber, and red based on your configured thresholds
• ImprovedSSL expiry alerts now escalate properly, each threshold (29d, 13d, 6d, 3d, 1d) fires independently instead of being blocked by a flat cooldown
• ImprovedBell icon notifications now appear for all alert types (slow response, SSL expiring, DNS changes), previously only showed for downtime events
• ImprovedNotification bell shows type-specific icons (lock for SSL, clock for slow, globe for DNS) with compact timestamps
• FixFixed DNS refresh button stuck in permanent "Refreshing..." state on monitor detail page
• FixFixed SSL and DNS notification links pointing to wrong tab
• FixFixed clicking notifications from a different organization showing "Error Loading Monitor", now auto-switches to the correct organization

Cleaner organization switcher, improved onboarding flow, and pricing page updates.

• ImprovedOrganization switcher redesigned, your org logo in the sidebar header is now the switcher with a clean dropdown
• ImprovedPricing page updated to reflect current trial options
• FixFixed dashboard flashing briefly before redirecting to plan selection for new accounts
• FixFixed promotional banner showing incorrect discount percentage
• FixFixed third-party scripts being blocked by Content Security Policy on dashboard

Faster status pages, lighter database, smarter data retention.

• ImprovedStatus pages now load instantly, switched from querying millions of individual checks to pre-computed daily summaries
• ImprovedResponse time and uptime charts use aggregated data for 7-day and 30-day views, significantly faster rendering
• ImprovedSmarter data retention, raw check data kept for recent debugging, daily summaries preserved for long-term trends
• NewIncident limits per plan with automatic cleanup of old resolved incidents

Choose your trial path, get notified about incidents on status pages, and improved onboarding experience.

• NewTwo trial paths: a paid trial with card, or a 7-day free trial without card. Choose what works for you. (Trial-with-card length has since changed to 10 days.)
• NewStatus page subscriber notifications, subscribers now receive email updates when incidents are created, updated, or resolved
• NewLeave organization, non-owner members can now leave an organization
• ImprovedSetup wizard redesigned, guides you through monitors, visual monitoring, alerts, timezone, and status pages
• ImprovedOrganization switcher redesigned with cleaner look
• ImprovedInvitation flow improved, auto-accepts after login, no extra click needed
• ImprovedBilling, Alerts, and Organization added to top navigation for quick access
• ImprovedNew accounts get smart organization naming from your email domain
• FixFixed login redirect not returning to invitation page after authentication
• SecurityEnhanced security across authentication, session management, and content security policies

Upload your profile photo, control your branding on status pages, and accurate incident scoping.

• NewProfile photo upload, click your avatar to upload a custom photo (JPEG, PNG, WebP, GIF). Google OAuth users now see their Google photo automatically.
• NewWhitelabel status pages, Agency plan users can now hide "Powered by Visual Sentinel" branding from their public status pages
• NewWhitelabel settings accessible to Business plan users (email branding, custom colors, org logo)
• ImprovedProfile page redesigned with compact name field and color-coded role badges
• ImprovedDashboard health indicator now reflects actual monitor status across all pages
• FixFixed status pages showing incidents from unrelated monitors, now scoped to assigned monitors only
• FixFixed status page uptime percentage not matching the daily history bars
• FixFixed custom domain not appearing in the status pages list

Accurate uptime display, custom domain reliability, and plan-specific branding.

• NewCustom domains and custom SMTP now available on Business plan (previously Agency only)
• NewOrganization logo displayed on status pages for Business+ plans
• ImprovedStatus page uptime percentage now matches the daily bars, both calculated from the same data
• ImprovedDashboard status indicator reflects actual monitor health instead of always showing green
• FixFixed custom domains not saving when re-adding a previously configured domain
• FixFixed status pages list not showing custom domain URL for pages that have one
• FixFixed refresh button on public status pages not responding to clicks
• FixFixed country flags showing globe emoji instead of actual flags for monitor locations

Browser push alerts on all plans, smarter alert delivery, and 50+ reliability improvements.

• NewBrowser push notifications, get instant native OS alerts when your sites go down, available on all plans including Free
• NewNotification fallback, if all your external channels fail (email, Slack, etc.), you still get notified in the dashboard for visual, SSL, DNS, and content alerts
• NewAutomatic data cleanup, old incidents, alerts, DNS records, and logs are now cleaned up on schedule to keep your dashboard fast
• SecurityEnhanced security across authentication, access controls, and data protection
• ImprovedMid-tier plan downgrades now properly enforce monitor and feature limits
• ImprovedAccount deletion is now comprehensive, all associated data is fully removed
• ImprovedMonitor settings (slow response threshold, alert delay, report options) now save correctly
• ImprovedVisual check intervals aligned per plan, Solo: 30min, Starter: 15min, Business/Agency: 5min
• ImprovedCountry flags now display correctly for monitor locations
• FixFixed AI chatbot showing incorrect plan prices
• FixFixed notification channel plan labels, Solo plan gets all 10 channels
• FixFixed play/pause buttons on notification channels appearing disabled
• FixFixed server alert spam, breach counter now resets properly after firing
• FixFixed SSL expiry reminders, now escalate at 29, 13, 6, 3, and 1 day before expiry
• FixCorrected plan naming across all pages (billing, terms, contact, pricing)

Instant data updates after changes, reliable alert delivery with automatic fallbacks, and clear timezone controls.

• NewIn-app fallback alerts, if all your notification channels fail (email, Slack, etc.), you still get notified inside the dashboard
• NewOrganization timezone now controls all alert and notification timestamps, set once, consistent everywhere
• NewEmail notifications now respect your organization's date and time format preferences
• ImprovedChanges reflect instantly, creating monitors, updating profiles, acknowledging alerts, and switching orgs no longer show stale data
• ImprovedMonitor status updates appear within 10 seconds instead of 30
• ImprovedAlert threshold behavior clearly explained, early warning fires at half the configured failure count
• ImprovedProfile page links to Organization Settings for configuring alert timezone
• FixFixed API monitoring authentication not working for multi-region checks, Basic Auth and Bearer Token now work globally
• FixFixed SSL certificate badge showing outdated "valid" status after certificate errors, now correctly shows invalid
• FixFixed timezone falling back to a different user's settings in some cases, organization timezone is now always used for alerts

New visual monitoring capabilities, improved plan enforcement, and critical bug fixes.

• NewElement capture for visual monitoring, screenshot a specific page section instead of the full page using a CSS selector
• NewGoogle profile pictures now display in the navigation bar for OAuth users
• NewSetup progress widget redesigned, click to open, shows all steps with completion status
• ImprovedAI Chat and AI Insights now properly gated by plan, Starter and above
• ImprovedScheduled Reports gated to Business plan and above
• ImprovedCustom domains gated to Business plan and above
• ImprovedTrial users now get correct feature access during their trial period. (Trial length has since changed.)
• ImprovedSidebar footer (plan badge, theme toggle) stays pinned at the bottom while navigation scrolls
• ImprovedPublic chat now renders formatted responses with bold text, links, and lists
• ImprovedPricing page no longer shows a "Downgrade" button on the Free plan for paid users
• FixFixed monitors getting stuck in "Under Maintenance" after a maintenance window was deleted
• FixFixed maintenance window deletion not checking for overlapping active windows before resetting monitors
• FixFixed visual screenshot exclusion selectors being ignored on manual captures due to stale cached config
• FixFixed sidebar horizontal scrollbar appearing on some screen sizes
• FixOnboarding now correctly completes only after successful checkout, not before

Major release focused on security hardening, bug fixes from a comprehensive codebase audit, and SEO infrastructure.

• SecurityEnhanced security hardening across webhook notification channels.
• SecurityHardened cross-organization data isolation on notification channel linking.
• SecurityTightened plan-limit enforcement on monitor updates.
• NewMonitor status now shows specific error reasons, Connection Refused, DNS Failed, Timed Out, Blocked (403), Cloudflare Error (520-524)
• NewContextual "Unblock Guide" link appears when Cloudflare blocks monitoring
• NewCloudflare monitoring troubleshooting guide with IP whitelisting instructions
• NewServer offline detection, alerts when servers stop reporting for 5+ minutes
• NewAnomaly notifications now sent for medium+ severity AI-detected anomalies
• NewSEO content engine, topic clusters, internal link auto-injection, cluster-aware breadcrumbs
• NewChangelog page for tracking product updates
• FixFixed monitor refresh showing "Down (200)" for operational sites
• FixFixed MAJOR_OUTAGE and PARTIAL_OUTAGE displaying as "Operational" in UI
• FixFixed status mapping bugs across 7 files, missing states silently fell to wrong display
• FixFixed settings form fields (Method, Expected Status, Follow Redirects) not rendering on first open
• FixFixed 5-second middleware timeouts from session DB query on every request, added 5-minute cache
• FixFixed incident detail page unreadable in light mode (hardcoded dark-mode colors)
• FixAdded error boundary for dashboard, component crashes no longer remove navigation
• ImprovedReplaced all 20 native browser confirm() dialogs with styled React modals
• ImprovedReplaced all native alert() calls with auto-dismissing toast notifications
• ImprovedAdmin users table: dedicated Plan column + inline action buttons
• ImprovedPage timeouts and connection errors logged as warnings instead of errors (reduces Discord noise)
• ImprovedRemoved 11 dead code files (3,994 lines), cleaner codebase
• ImprovedDNS and performance tables now scroll horizontally on mobile instead of crushing

• NewAI-powered monitoring keyword positioning across homepage and meta tags
• NewGitHub OAuth authentication for login and signup
• NewCollapsible sidebar with localStorage persistence
• NewBlog featured images generated with AI image models
• FixDNS SOA records excluded from change detection (too noisy)
• FixDNS alert wording improved, Added/Removed/Updated instead of New/Old
• ImprovedOnboarding URL field: hardcoded https:// prefix, auto-strips protocol on paste
• ImprovedOAuth buttons side-by-side in grid layout
• ImprovedHero section spacing improved with natural breathing room

• NewPlan rename: Professional → Business, Enterprise → Agency
• NewServer alert system with CPU/memory/disk threshold monitoring
• NewPer-server alert configuration with notification channel overrides
• NewWhatsApp templates for server alerts (CPU, memory, disk, offline, recovery)
• NewFree plan: check interval 1hr → 5min, Starter: 10 → 15 monitors
• ImprovedServer alert evaluator with consecutive breach counting and cooldown logic

• NewContent change detection with CSS selector-based monitoring
• NewContent freshness monitoring with configurable staleness thresholds
• NewKeyword checking in visual screenshots
• NewBlog pipeline for AI-generated SEO content
• ImprovedVisual monitoring sub-pages for monitoring multiple URLs under one monitor

Visual Sentinel is officially out of beta. Scaled-up production infrastructure, automated deploys, and proactive incident detection on the platform itself.

• NewScaled-up production infrastructure with dedicated capacity for visual monitoring workloads.
• NewAutomated continuous-deployment pipeline for beta and production environments.
• NewInternal container watchdog with proactive alerts on unexpected restarts.
• SecurityProduction traffic served over automatically-renewed TLS certificates.