Author
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
August was largely a follow-through month: July’s timeout and failure-source model moved from API capability into day-to-day use, while the rollout exposed DNS and timeout edge cases that we tightened across probes and clients. The Go SDK aligns with the current measurement API The Go SDK now models measurement status separately from individual probe-result status, supports the current location-selection
July pushed Globalping toward faster, more diagnosable measurements: large result sets became dramatically more responsive, while new failure-source reporting and configurable timeouts make it much easier to understand when and why a test fails. The same month also brought a series of backend scalability improvements and tighter controls around probe quality and discovery. Faster, richer measurement results The Globalping website’
June’s standout change was a major overhaul of how Globalping presents raw measurement results, paired with substantial performance work to keep those results responsive as they stream in. Behind that visible refresh, we also strengthened measurement completion under load and improved several supporting parts of the platform, from probe efficiency and account handling to authentication and deployments. A redesigned
May laid the groundwork for one of Globalping’s bigger capabilities: scheduled measurements, with the API gaining the first pieces needed to run recurring tests and export their results as time-series data. The month also introduced account notifications and credit alerts, while improving sponsorship accounting and hardening probe and API behavior. Scheduled measurements take shape Globalping gained the first backend
April made Globalping noticeably better at handling large measurements, both in the backend and in the browser. Measurement storage and delivery were optimized to reduce memory and CPU overhead, while the website gained better controls, cleaner raw output, and the ability to stop running measurements directly from the UI. Faster handling of large measurements The API introduced several optimizations around
