March combined a substantial refresh of Globalping’s public network experience with a push to make probe adoption and large-result delivery more reliable. The API also received several targeted performance improvements aimed at reducing Redis pressure and response-processing overhead under concurrent load.

A richer network explorer

The network page received a significant design update, including better behavior when results aren’t grouped, clearer network names on ASN pages, and dedicated provider pages. The website also began refreshing probe data periodically so the network view stays current without requiring a full reload. (globalping.io#82, globalping.io#101, globalping.io#110, globalping.io#117, globalping.io#122)

Easier hardware probe adoption

Hardware-probe adoption gained a more direct browser-based flow: the dashboard can request local-network access and redirect users to the probe’s local adoption server, while the probe and account backend gained the endpoints needed to complete the process. Several follow-up fixes made the flow more reliable when browser permissions or local connectivity are limited. (globalping-dash#181, globalping-dash#184, globalping-probe#352, globalping-dash-directus#154, globalping-dash#185, globalping-dash#186)

Faster measurement retrieval under load

The API now avoids repeating identical concurrent Redis reads when the same measurement is requested by many clients. ETag generation was also moved to a much faster hash implementation, while unnecessary string encoding was removed from hot paths. These changes are particularly relevant for large measurement responses and popular shared-result URLs. (globalping#817, globalping#820, globalping#821)

Better probe quality and IP ownership handling

Probe QA was expanded to better detect unstable probes, including a new status for probes that disconnect too often. IP ownership handling was also tightened so offline and alternative-address scenarios are represented more accurately across the API and dashboard. (globalping-probe#350, globalping#805, globalping-dash#180, globalping#804, globalping-dash-directus#153, globalping#816)

A new community leaderboard

The website gained a dedicated leaderboard highlighting Globalping users and probe contributors, making participation in the network more visible. (globalping.io#112)

Better mobile measurement results

Mobile users now see measurement information immediately when opening a result, improving the initial experience on smaller screens. (globalping.io#95)

Clearer credit and API-limit messaging

The website and API documentation were updated to better explain how Globalping credits and request limits work, including clarifying that authenticated API requests are not capped at the displayed hourly credit allowance. (globalping.io#100, globalping#807)

Full Changelog

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

globalping

• feat: improve probe IP ownership handling – globalping#804
• feat: add too-many-disconnects status – globalping#805
• feat: detect client IPs behind Fastly – globalping#814
• fix: search duplicate IPs in altIps too – globalping#816
• perf: avoid duplicate concurrent redis calls – globalping#817
• perf: capture spans in single-flight – globalping#818
• perf: capture spans for selected middleware – globalping#819
• perf: use xxhash-based etags – globalping#820
• perf: avoid unnecessary string encoding – globalping#821
• docs: improve API limits text – globalping#807

globalping.io

• feat: add Datapacket to platinum sponsors – globalping.io#90
• feat: update the Datapacket sponsor description – globalping.io#94
• feat: show measurement info for mobile users on load – globalping.io#95
• feat: change credits plans text – globalping.io#100
• feat: update network page design with groupBy disabled – globalping.io#101
• feat: add organization structured data – globalping.io#109
• feat: add the providers page – globalping.io#110
• feat: add the leaderboard page – globalping.io#112
• feat: update probe data periodically – globalping.io#117
• feat: add network name to network tools ASN pages – globalping.io#122
• feat: remove newsletter – globalping.io#123
• fix: broken livereload – globalping.io#89
• fix: revert groupBy on browser navigation on the network page – globalping.io#97
• fix: remove incorrect header class – globalping.io#103
• fix: use fixed width fields for numerical values on the about page – globalping.io#114
• fix: set network domain in a deterministic manner – globalping.io#115
• fix: email link – globalping.io#119

globalping-probe

• feat: improve QA tests – globalping-probe#350
• feat: add the /adopt endpoint to local adoption server – globalping-probe#352
• fix: treat 0 packet loss as successful even if execaError – globalping-probe#351
• fix: improve mtr error handling – globalping-probe#353

globalping-dash

• feat: add too-many-disconnects status – globalping-dash#180
• feat: add local network access popup and permission handling – globalping-dash#181
• feat: support local adoption via a link redirect – globalping-dash#184
• feat: improve automatic hw adoption on failure – globalping-dash#188
• feat: remove error toast from the probe logs component – globalping-dash#193
• fix: template composable usage – globalping-dash#182
• fix: set network access using all valid permission names – globalping-dash#185
• fix: only use ips for adoption if we have local network access – globalping-dash#186
• fix: refresh all nuxt data on hw probe adoption – globalping-dash#191
• fix: homepage location overflow – globalping-dash#194

globalping-dash-directus

• feat: allow NULL IP for offline probes – globalping-dash-directus#153
• feat: merge local adoption endpoint GET / into GET / – globalping-dash-directus#154

globalping-mcp-server

• fix: return full origin with port in CORS headers for localhost – globalping-mcp-server#30