The Globalping blog
Learn how to diagnose routing and latency issues, automate tests across your workflows, and follow what we’re building with our open-source community.
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,
Want to add Globalping’s global network testing capabilities to your tool, or build a new tool on top of it using a coding agent? Then this guide is for you (and your agent). The first part explains how to use this guide and what you, the human, need to know. Below, you'll find the agent brief, which
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
Many SaaS monitoring tools are built for large or specialized teams and offer many features for different requirements and workflows. But small teams and solo devs often don't need all of that. They prefer tools with only the features they'll actually use, that they can host themselves, and, ideally, that are open-source. Unfortunately, that often means
After moving your website to a new domain or switching hosting providers, the next step is usually to wait for the updated domain settings to take effect; in other words, you are waiting for DNS propagation to complete globally. The tricky part is that without special tools, you can’t know whether DNS propagation has concluded everywhere. Do your users
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
