September focused heavily on correctness and reliability across the Globalping stack. The CLI gained two-target comparisons, probe-side DNS and timeout handling was substantially strengthened, HTTP testing became safer and more transparent, and probe notifications were improved across the dashboard.

The CLI can compare two targets in one measurement

Globalping CLI now supports running measurements against two targets at once, making side-by-side comparisons directly from the terminal much easier. The same release also handles individual probe failures without losing the rest of a measurement, improves error reporting throughout the CLI, and presents HTTP timing phases in the same order as the website. (globalping-cli#202, globalping-cli#203, globalping-cli#201, globalping-cli#200)

DNS handling is now more predictable across network tests

Ping, traceroute, and MTR now share centralized target resolution inside the probe instead of relying on the individual native commands. This gives Globalping direct control over DNS deadlines and produces more consistent resolved addresses, hostnames, and failure sources. We also started caching missing PTR and ASN records and improved the distinction between DNS resolution deadlines and command execution timeouts. (globalping-probe#407, globalping-probe#417, globalping-probe#418)

HTTP measurements preserve more useful information when things go wrong

Timed-out HTTP measurements can now return timings from phases that completed before the timeout, together with the phase that was active when the deadline was reached. DNS is also prevented from consuming the whole HTTP measurement budget, leaving enough time for TCP, TLS, and the actual response. A separate fix keeps paths and query strings distinct so special characters and unusual paths are sent exactly as requested. (globalping-probe#409, globalping-probe#414, globalping-probe#420)

HTTP testing now blocks common sensitive paths

The API gained an HTTP request blacklist for common sensitive files and directories, initially based on CrowdSec's sensitive-data list. The website now surfaces these request validation errors instead of silently hiding them, making it clear why a measurement was rejected. (globalping#914, globalping.io#201)

DNS answers are visible directly in website table results

DNS measurements in table mode now show their returned answers, making it possible to inspect and compare DNS responses across probes without opening each individual result. (globalping.io#196)

Probe notifications are clearer and more reliable

Location-change notifications now include probe names in their titles, making messages much easier to identify when an account has several probes. We also fixed notification delivery so one user disabling a notification does not prevent it from being sent to other eligible users, and kept the unread indicator visually attached to its notification title in the dashboard. (globalping#908, globalping-dash-directus#186, globalping-dash-directus#185, globalping-dash#227)

Full Changelog

Below is the complete monthly changelog for Globalping repositories, grouped by project. Maintenance-only changes are omitted.

globalping

globalping-probe

globalping-cli

globalping.io

globalping-dash

globalping-dash-directus

globalping-mcp-server