The /api/servers/monitored endpoint returns statistics nested within the server statistics object, but the statistics[] data payload is not ordered chronologically. Time-based keys (e.g. 01:02, 06:02, 07:02) appear in an inconsistent order, even within a single statistics object (such as Disk or RAM).

Because the timestamps are keys rather than structured values, API consumers cannot reliably determine the most recent metric update without additional client-side sorting or assumptions. This is further complicated by the fact that the current response format does not align with the API documentation example.

The resource should return statistics data in a predictable, documented order (or include explicit timestamps) so consumers can safely identify the latest values.