Skip to main content

Notifications

No notifications yet

Changelog

Release history and version notes

0.41.1 Current
2026-10-17
  • Packet-loss threshold per ping check. A ping fails when more than 20% of the replies are lost. For a link that always drops a few packets you can raise this per check, from 0 to 100%, through the API setting `max_packet_loss`.
0.41.0
2026-10-17
  • The 0.39 and 0.40 improvements are live. Everything listed under 0.39.0 to 0.40.0 is now in production: incidents opened and closed by a majority of regions, paired alerts with retries, clearer status pages, downtime checks from the regional pollers, and the billing fixes.
  • Faster result processing. Results from the regional pollers are processed within seconds, also during busy periods.
0.40.0 Rolled back
2026-10-15
  • Not live. 0.40.0 was rolled back on the day it was released. The changes listed under 0.39.0 to 0.39.4 are not in production yet; they will return in a later release.
0.39.4 Rolled back
2026-10-11
  • Not live. 0.39.4 was rolled back on the day it was deployed. The changes listed under 0.39.0 to 0.39.4 are not in production yet; they will return in a later release.
0.39.3 Rolled back
2026-09-25
  • Not live. 0.39.3 was rolled back on the day it was released. The changes listed under 0.39.0 to 0.39.3 are not in production yet; they will return in a later release.
0.39.2 Not in production
2026-09-25
  • Faster result processing (not live). Results from the regional pollers are processed in the background, so a busy period no longer holds them up.
  • Plainer email layout (not live). Alert and account emails look the same in every mail client.
0.39.1 Rolled back
2026-09-23
  • Not live. 0.39.1 was rolled back on the day it was released. The changes listed under 0.39.0 are not in production yet.
0.39.0 Not in production
2026-09-23
  • Incidents (not live). An incident starts at the first failed check. Maintenance windows and paused time do not count toward its start. Regions open and close an incident by the same majority vote, and an incident closes when you stop monitoring the check or site.
  • Alerts (not live). A failed alert channel is retried for hours instead of being dropped. Every DOWN alert is paired with its UP alert on the same channel, and certificate and DNS issues are paired with their recoveries.
  • Status pages (not live). Public status pages and subscriber emails show a short failure category such as "Connection failed" instead of the monitored URL or raw error text. The 90-day uptime figure is weighted by time, and a site with an expiring certificate shows as degraded instead of down.
  • Downtime checks (not live). A site with an "Expect offline" check is checked only from the regional pollers.
  • Billing (not live). A partial refund no longer suspends a team. When a prepaid term ends, checkout is offered again, and a running term can be renewed before it ends. An owner can cancel a stale pending checkout.
  • Public API (not live). Every `/api/v1` route answers in JSON. A `per_page` or `limit` above the maximum (100 and 200) is reduced to the maximum instead of rejected. The API applies the same trial and subscription rules as the web app, and check settings can be updated partially.
0.38.16
2026-10-17
  • API token expiry you can see. You choose how long a new API token lives: 30, 90 or 365 days, or never. The API Tokens page shows when each token expires. Before, every token stopped working after 90 days without warning.
0.38.15
2026-10-15
  • Faster recovery alerts. When most monitoring regions see a site come back, the incident closes and the recovery alert is sent at once.
  • Faster results. Monitoring results are processed sooner, and results from our busiest monitoring location are no longer lost.
0.38.14
2026-10-11
  • Faster outage and recovery alerts. While a site is down or looks down, it is checked every 30 seconds for the first hour, whatever its interval. Recovery is now seen within about a minute.
  • Fewer false alarms. A single failed check from each region no longer opens an incident; the failure must last at least a minute.
0.38.12
2026-09-29
  • Steady performance. Housekeeping of processed monitoring results now runs every hour, so result processing stays fast.
0.38.11
2026-09-29
  • Account deletion confirmation. After you delete your account, the login page now confirms that the deletion was requested.
0.38.10
2026-09-29
  • Phone layout. The top bar fits on one line, the sites list shows as cards on small screens, and tables for channels, alerts and API tokens stack neatly.
  • Clearer filters. Monitoring-mode and region filters only appear when your team uses them.
  • Wording. Counts read "1 site" and "1 incident" instead of "1 sites".
  • Uptime figures update reliably in the background.
0.38.9
2026-09-29
  • Clearer alert emails. Down and up emails now lead with "🟥 DOWN" or "🟩 UP", say what failed or how long the outage lasted, and link straight to the incident.
  • Email links work. The help link in every email opens the help center, and every email now has a readable plain-text version.
  • Faster first alert. The site you add during signup is checked every minute.
0.38.8
2026-09-29
  • Faster result processing. Check results from our monitoring nodes are processed many times faster, so status and alerts stay current during busy periods.
0.38.7
2026-09-29
  • Checks run on time again. Our monitoring nodes could not fetch their check lists in time, so many checks ran late. They now get the list quickly.
  • Verification email arrives right after signup instead of minutes later, and the login page now shows the "email verified" and other confirmation messages.
  • Paused monitoring closes its open incident with a "Monitoring paused" note and no alert. Resuming starts fresh.
  • Public status pages show plain wording instead of technical error text, a failing SSL check no longer marks a site down there, and the 90-day figure is time-weighted.
  • Account deletion works after a trial ends.
  • Checkout shows a clear message when the payment provider is unreachable.
  • Help search handles unusual queries.
  • Security fixes.
0.38.6
2026-09-28
  • Down alerts are no longer lost. An alert could be dropped when a site went down during a busy moment. Alerts are now sent once the incident is saved.
  • Alert routing. A notification rule for one site no longer silences alerts for your other sites, and a second outage soon after the first still alerts.
  • Sites whose DNS stops resolving now alert instead of going quiet.
  • Slack and Discord channels save the URL you enter.
  • Resolved updates close the incident. Posting a "Resolved" status update now closes it.
  • Onboarding. Pressing Enter on the first-site step adds the site, and the first check runs at once. An empty sites list now shows how to add your first site.
  • Help. Search works, and the channel setup guides open.
  • Maintenance windows show times in UTC.
  • Billing form is readable in the dark theme.
  • Security fixes.
  • New channels can be email, Slack, Discord, webhook or Telegram. Existing channels of other types keep working.
0.38.5
2026-09-28
  • Email verification links work again. Verification links opened an "Invalid signature" page, so new accounts could not be confirmed.
  • Secure redirects. Redirects such as the one to the login page now stay on https.
  • Telegram setup. The link command is shown after you save a Telegram channel, so the bot links your chat on the first try.
  • Public changelog. This page is now open without logging in.
0.38.4
2026-09-28
  • Signup works again. The signup page showed no email field, so new accounts could not be created. The field is back.
  • Background tasks run on time again. Verification emails, billing and other scheduled tasks ran late for part of 2026-09-28. They run on schedule again.
0.38.3
2026-09-25
  • Downtime checks. A site with an "Expect offline" check could report a false failure. It is now checked only from the regional pollers.
0.38.0
2026-09-22
  • Faster dashboard under load. A burst of monitoring traffic no longer slows down the dashboard.
0.37.7
2026-09-22
  • Better availability at peak times. Pages no longer become briefly unavailable when the service is busy.
0.37.6
2026-09-22
  • Fewer false DNS alerts. A DNS check now watches the record your zone declares. For a host that points to a CDN, it compares that record, not the CDN addresses that change on every lookup.
0.37.5
2026-09-21
  • Pages load their styles and scripts correctly again.
0.37.0
2026-09-21
  • Open signup. Anyone can create an account from the signup page.
  • CSV exports. Download SLA figures from Reports and a site's incident list from Incidents as CSV files.
  • Status page branding. Set a logo, a primary color and a theme on a status page.
  • Invoices and receipts. Invoices are numbered in sequence and cannot be changed once issued; a correction is a credit note. Invoice emails link to the invoice in your account, and every payment has a printable receipt.
  • VAT and billing details. Checkout asks for your billing details, checks EU VAT numbers, and shows the net amount, VAT and total before you go to the payment page.
  • Regional evidence on incidents. An incident page shows which regions confirmed the outage.
  • Certificate and DNS alerts on every channel. Certificate expiry warnings and DNS changes go to all your notification channels.
  • API documentation. The API reference covers every public API route.
  • Email address changes need confirmation. Changing your email address asks for your current password. The new address becomes active after you follow the link sent to it, and the old address gets a notice.
  • API tokens belong to a team. A token works only for the team it was created in. Create a token in each team you automate.
  • New email design. Account and alert emails use a new branded layout.
  • Security fixes.
0.36.0
2026-09-14
  • Downtime checks ("Expect offline"). An HTTP check can verify that a target stays unreachable. The check passes while the target gives no response and fails as soon as it answers, with any status. Use it for a geo-blocked, firewalled or decommissioned endpoint.
0.35.1
2026-09-09
  • Telegram alerts redesigned. Each message is a short status line (DOWN, UP, SLOW, NORMAL) with the site name, one line of evidence, the time in UTC, and the incident number and team. Buttons read "Open incident", "Re-check now" and "Mute this site".
0.35.0
2026-09-08
  • New prices. €10.00 per month still covers five sites. Sites 6–25 cost €1.50 each, 26–100 €1.20, 101–250 €0.95 and 251–500 €0.70. You can buy any allowance up to 500 sites.
  • Prepaid terms. Next to monthly billing, you can prepay 6 or 12 months in one payment by card, iDEAL or bank transfer.
0.34.0
2026-09-08
  • Team invitations work for people without an account. An invitee who follows the link can sign up or log in and joins the team directly.
  • Security fixes.
0.33.0
2026-09-06
  • New uptimevanguard.com website.
  • The privacy policy and terms no longer name third parties that are not used.
0.32.3
2026-09-06
  • Check history API. `GET /api/v1/checks/{id}/history` returns timing, status and identity fields. Add `?with=headers` to include response headers.
0.32.2
2026-09-05
  • The check history API responds faster.
0.32.0
2026-09-05
  • Payments through Mollie. New subscriptions are paid through Mollie. Plan changes take effect at the next renewal, and cancelling keeps access until the paid period ends. Existing subscriptions keep working unchanged.
  • Reports page redesign. Daily downtime heatmap, downtime chart and a searchable site table. Overlapping incidents on one site no longer inflate downtime.
  • HTTP check assertions and request options. Set the method, headers, body, expected status codes, and body or header assertions on an HTTP check.
  • Faster pages. Site tabs, performance cards and charts load after the page appears.
  • Several reliability fixes for billing and site limits.
  • Security fixes.
0.31.0
2026-07-28
  • Platform components updated to current versions.
0.30.4
2026-07-27
  • Faster DNS tab. The site page's DNS tab opens in a fraction of a second.
  • Scheduled emails are sent again. Monthly uptime report emails and other scheduled work had stopped; they run again.
  • Faster site pages. A site with a long incident history opens quickly; the incidents tab shows the 20 most recent incidents and links to the full list.
  • Smaller logo files, so pages load faster.