Changelog 2025.05

Improvements

• Made the monitoring location appear for each monitor cycle (on hover) when viewing historical monitoring results, so you can easily tell which location a cycle ran from. This can help in diagnosing regional or location-specific problems or differences in performance between regions.
• Added a breakdown of fuel usage by recent test to the Billing page, so you can see how much fuel each individual test consumed.
• Optimized query performance for several fuel-related queries, mainly affecting customers with lots of high-frequency monitors.

Bug Fixes

• Fixed a problem with graph legend column sorting being lost on refresh during a load test.
• Fixed an issue that sometimes caused a browser tab to crash when multiple users viewed the same test simultaneously when the final test report was being generated.

Further Reading

Loadster’s Site & API Monitoring feature runs your scripts on a schedule from multiple locations around the world. When something goes wrong, knowing which location flagged the issue is important – a failure from one region but not others can point to a regional CDN problem, DNS routing issue, or a data center outage rather than a global incident. The location-on-hover improvement makes that information immediately accessible without digging through logs.

The fuel usage breakdown on the Billing page gives you visibility into how your Loadster fuel is being consumed across individual tests. Fuel powers your load testing and monitoring, so understanding which tests use the most can help you plan and budget more effectively.