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 support for recurring measurements. The new scheduling model is designed to support both centrally managed monitoring and, eventually, custom user-created schedules, with efficient grouping of probe results and support for distributing measurements over time. Time-series export support was added alongside it. (globalping#797, globalping-dash-directus#166)

Account notifications and credit alerts

A new notification system now connects the API, account backend, and dashboard, providing the foundation for managing user notifications from one place. Credit notifications were one of the first concrete uses, giving users better visibility when their available Globalping credits need attention. (globalping#808, globalping-dash-directus#158, globalping-dash#189, globalping-dash-directus#168)

More reliable sponsorship credits

A bug affecting one-time sponsorships from users who already had an active monthly sponsorship was fixed, ensuring those contributions correctly generate their Globalping credits. (globalping-dash-directus#167)

Safer HTTP measurements

Probes now truncate excessively large HTTP response headers rather than allowing them to grow unchecked. The API documentation was updated alongside the probe behavior so clients can correctly identify when response data has been truncated. (globalping-probe#359, globalping#844)

More robust probe connections

The API now validates probe handshake parameters when a probe connects, rejecting malformed connection metadata earlier instead of allowing invalid state further into the system. (globalping#840)

More reliable notification delivery

The email notification pipeline was optimized to avoid database locking caused by broad scans during message processing. This reduces contention as notification volume grows. (globalping-dash-directus#169)

Full Changelog

globalping

• feat: initial support for scheduled measurements — globalping#797
• feat: send notifications using directus API — globalping#808
• feat: add handshake query validation — globalping#840
• docs: update truncated desc — globalping#844

globalping-probe

• feat: truncate HTTP response headers — globalping-probe#359

globalping-dash

• feat: notification management — globalping-dash#189
• fix: update user after unsubscribe — globalping-dash#199

globalping-dash-directus

• feat: notification management — globalping-dash-directus#158
• feat: add schedules schema — globalping-dash-directus#166
• feat: credits notification — globalping-dash-directus#168
• fix: no credits for one-time sponsorships of active monthly sponsors — globalping-dash-directus#167
• fix: email sending gap locks — globalping-dash-directus#169

globalping.io

• feat: add Digiturunc to bronze sponsors — globalping.io#156
• feat: add Perlot to bronze sponsors — globalping.io#158