October brought more context to troubleshooting: probe logs are easier to search, and failed measurements retain more of the information collected before the failure. We also laid the foundations for organization accounts and improved the handoff from website comparisons to the CLI.

Search probe logs and browse more history

Probe owners can now filter logs by component and message text, load older entries as they scroll, and follow new messages when viewing the latest entries. We expanded storage from roughly 1,000 entries to around 100,000 per probe, with a maximum history of 30 days. The log view keeps your place while you inspect older messages and resumes following new entries when you return to the bottom. (globalping-dash#218, globalping#896, globalping-dash#233)

More diagnostic detail when measurements fail

Following September’s improvements to HTTP timeouts, probes now retain known target IP addresses when ping, traceroute, MTR, or HTTP measurements fail. HTTP failures such as connection refusals and TLS errors also keep completed phase timings and total elapsed time. (globalping-probe#423)

Copy website comparisons into the CLI

The website’s “Replicate in CLI” action now produces commands for two-target comparisons, including the relevant HTTP URLs, headers, and DNS query types. We also corrected HTTP target parsing in the CLI: bare IPv6 targets and http2:// URLs are accepted, and encoded paths such as /a%2Fb stay encoded instead of becoming /a/b. (globalping.io#203, globalping-cli#205)

Preparing for organization accounts

We completed the first stages of organization support across the dashboard, API, and authentication service. Probes, credit balances, and credentials now belong to an account that can represent either a person or an organization, providing the ownership and permission model needed for shared resources. Organization management screens and the account picker for authorizing applications remain part of a later phase. (globalping-dash-directus#187, globalping#909, globalping-dash#228, globalping-auth#14)

Custom locations no longer prevent probe reattachment

An adopted probe with a custom city could fail to reconnect to its existing dashboard record after both its IP address and probe ID changed. We now match against its original detected city, allowing the probe to recover its association with the account. (globalping#931)

An Unraid community integration

Our community integrations directory now includes Globalping Probe for Unraid, contributed by joaogalaghar, for running a probe on an Unraid server. (globalping.io#206)

New sponsors and sponsorship tools

We welcomed is*hosting as a Gold sponsor and Synthient as a Bronze sponsor. For our operations team, a new admin view brings sponsorship statistics, payment history, and manual credit adjustments into the dashboard. (globalping.io#213, globalping.io#207, globalping-dash#229, globalping-dash-directus#190)

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-auth