What's new — November 2026

We've shipped a major update to InfraNest with a complete redesign of how problems reach you, a home page that shows what matters first, and new ways to catch issues before they bite.

✨ New

• Teams can now get their daily or weekly needs you list in Slack or Teams, posted in the morning only when something new appears.
• Home now warns weeks early if a Let's Encrypt, ZeroSSL or Google certificate stops renewing itself, showing the renewal date, expiry date and urgency.
• Home now suggests things InfraNest can do for you in one click — watching an unwatched site, turning on DNSSEC, or showing GitHub deploys on a monitor — with no confirmation needed and the option to undo for 24 hours.
• When Slack, Teams or another alert destination refuses an alert, it is now emailed to whoever looks after that destination straight away, with the alerts it missed kept for a week so you can resend them once it works again.
• InfraNest now opens on Home showing what needs you and what is fine, with the most important thing getting its own card and the rest in a short list; dashboards are unchanged and can be set as your default under Preferences.
• When a site goes down minutes after a deploy, the incident now shows the deploy with a link, and GitHub deploys also appear as markers on response-time and server charts when you link a repository to Integrations → GitHub.
• New accounts now start by showing where a domain is registered and hosted, who handles its mail, whether SPF and DMARC are set and when the certificate expires, with one click to watch the site and alerts, and the option to connect a provider later.
• The Services tab on servers with the agent now lists Docker and Podman containers with restart counts, and a new alert under Monitoring → Alert defaults warns when one restarts three times within fifteen minutes. (details)
• A new alert under Monitoring → Alert defaults warns when a service restarts three times within fifteen minutes on servers with the agent installed, with the service name and restart count. (details)
• A new alert under Monitoring → Alert defaults warns when an Ubuntu server with the agent loses its Ubuntu Pro attachment or subscription, and the System card now shows whether Livepatch and ESM are on. (details)
• A new alert under Monitoring → Alert defaults warns when a server with the agent runs out of memory and stops a program to stay running, with an all-clear once nothing more has been stopped for an hour. (details)
• Every Monday you get one email with what needs you this week, what renewed or fixed itself, what changed at your DNS provider, and one suggestion, with domain renewals batched into it instead of arriving one by one.
• Choose a delay under My account → Notifications and a monitor that is still down with nobody on it is pushed to your browser as a push notification, even if push is off for monitoring.
• Turn on push notifications under My account → Notifications and your browser shows urgent problems like a monitor going down even when InfraNest is closed, with the option to choose per kind what it shows.
• Three new automations fix known failures on their own after showing you what they would do: take a failing server out of its load balancer, reboot a frozen server at most once a day, and grow a volume before it fills.
• Settings → Branding now puts your icon, logo and colour on one page next to a live preview of a real alert, with the option to give buttons their own colour and send yourself a test email.
• Pick a status page or tag and get a monthly report with uptime, every incident with its cause, response time and maintenance done, sent to your client as a PDF on the 1st or downloaded.
• After a production deploy, monitors are checked more often for an hour and compared with the hour before from each location, showing response-time changes and failed-check rates on the deploy's page and charts.
• A monitor that fails because its address won't resolve now tells you why — the domain expired, lost its nameservers, has broken DNSSEC, the record was removed, or the problem was on our side.
• InfraNest now checks Google Web Risk about every domain you hold roughly weekly, and if Google lists one as suspected phishing or malware it appears on Home and in Domains with what to do and your alert destinations hear it.
• Drop catch now has a Discover tab to search names the .uk registry will release by word, drop date and length, with the option to watch one or save the search for new names by email each morning, and each watch says what happens once the name is yours.
• Drop catch now opens on an Overview showing what needs you, where your watches are in their expiry, how catching has gone and what it cost, plus a Results tab with the full history of each watched domain.
• When a name you watch becomes free, every alert opens a page built for your phone with the name, how long it has been free, and the price at the cheapest registrar you have connected, with one tap to register it.
• When an incident is over, one click says whether it was a real problem, a false alarm or expected, and each resolved incident gets a summary drafted from what was recorded that you can edit and copy as text or Markdown.
• The incident, monitor page and alert now say Likely not you when the problem is something only InfraNest can see, like one of our probes having trouble or servers at many workspaces in one provider location failing at once.
• Switch on one automation and every new domain, server and status page component is watched as it arrives with the frequency and locations you choose, without adding a second monitor or going past your plan.
• The Metrics graphs and server tiles now shade the range each reading normally falls in at that hour of the week learned from the server's last weeks, so unusual readings for that time of day show as normal and never send an alert.
• A website, API or keyword monitor now splits its response time into looking up the name, connecting, the secure handshake, waiting for your server and downloading the page for each location with a sentence on what makes the difference.
• Every server now says what it is — web server, database, cache, queue worker, backup host and more — recognised from what runs on it and what connects to it, and automations that reboot servers now leave a database alone unless you allow it.
• InfraNest now spots three slow problems before they bite: memory that climbs until every restart with the service or container named, processes killed for lack of memory again and again in a week, and a volume that will be full within two weeks.
• When someone signs in with an address on one of your verified domains they can now ask to join and an administrator decides, instead of being added automatically.
• Set the uptime you promise on a monitor or status page and the monitor page shows this calendar month's downtime allowance and whether you will make it at your current pace, with alerts only when the allowance is being spent fast enough to miss the target.

⚡ Improved

• The Start here card on Home now shows why something is wrong and what InfraNest did about it, with a second action where it helps, and lets you assign problems to teammates or take them back.
• Problem emails now split by urgency: something urgent like a site going down arrives at once, while slower issues like a domain expiring in weeks goes into your daily or weekly needs you email that reaches everyone in the workspace.
• Home now lists when you have monitors or servers but no alert destination, and tips now appear on the pages they are about instead of above Home.
• The notifications bell now knows when problems are fixed, dims them with a timestamp and stops counting them, and on Telegram and Discord the original alert updates when the problem ends.
• Domains and DNS zones now only come from a connected provider; POST requests to create them without a provider_credential_id are no longer supported.
• Domains, DNS zones and servers now show Not syncing with the sync date and a button to fix it when their integration is disabled or needs reconnecting, and expiry warnings say the date may be out of date and why.
• Home now shows what needs you in the same cards as Certificates, Domains and DNS overviews using one shared list, and you can snooze or mark items intentional on any of these pages to set them aside on all of them.
• Select the ? in the bottom-right corner for the help article about the page you are on, a search of every article and chat with support, and the ? that used to sit in page headers is gone.
• With PagerDuty connected, its page now suggests automations you can review and save in a few clicks, such as opening an incident before a certificate expires or paging on-call when a GitHub workflow fails. (details)
• Free now includes up to 3 cloud, DNS, registrar and certificate connections and one Slack, Teams, Discord or Telegram destination; Pro allows 5 connections and includes PagerDuty, Jira, Linear, Notion and GitHub, with connections made before 14 October 2026 grandfathered on Free. (details)
• The Monitors list now switches its bars between days and hours, with each domain or server row showing its worst monitor.
• The drop-catch Overview now offers the fix beside each finding, such as showing where to register a free name and for how much, or getting a backup registrar when another registrar you connected sells the ending.
• A monitor added this morning no longer reads 100% for the last 30 days, paused time no longer counts toward uptime, new monitors are marked New in the list, and status pages say how many days their uptime covers.
• When a keyword check fails its page now shows a short piece of what the page said instead, a ping monitor shows packet loss and reply time variation, a DNS monitor shows the answer each location got, and a redirect monitor lists every step it followed.
• What was called an organization in some places and a workspace in others is now a workspace everywhere, and settings are now grouped by what you came to change with payment details and invoices on one page.
• Monitor pages now open in a few tens of milliseconds even when checked every 30 seconds from several regions, down from over a second.
• You can now paste a full URL like https://example.com/page into a ping, port or DNS monitor and only the hostname is kept.
• Each monitoring location now checks that its own DNS works, so DNS failures it reports are recorded as ours and do not open incidents or alert you.

🐛 Fixed

• Archived domains no longer appear in renewal reminders, the sidebar count, dashboards or attention emails, and return if you unarchive them. (details)
• A monitor that ended up down without an open incident, such as after it was restored from the recycle bin or went down during a maintenance window, now opens an incident on its next check dated from when it actually went down.
• The embedded status page widget now shows its uptime figure and history bar again.