Is an io.net GPU idle or hired? What the monitor can show

Direct answer

The monitor cannot tell you whether this GPU is idle or hired right now. After the io.net monitor reads successfully, what it reliably shows is the hardware name, the GPU count, and that device’s block rewards for the UTC day. Job status from official device details is not turned into an idle or hired label.

The official endpoint describes device details as covering status, connectivity, job activity, rewards earned and hire rate. Each job in the documented payload can include compute_minutes_hired, compute_minutes_served, status, earned, total_hire_rate and uptime_percent. Those are the fields that speak to a hire. Read them in the official response, not by guessing from today’s IO.

How to read the fields

Minutes hired is the hired duration recorded on that job. Minutes served is the served duration recorded on it. Status is that job’s status, such as pending in the documentation sample. Earned is the accounted figure on that job. Hire rate is that job’s rate field. They describe the job. They are not today’s IO on the monitor.

Documentation sample dated 2023-09-12, not your machine: one job has 300 minutes hired, 0 minutes served, status pending, earned 0, hire rate 10.8 and uptime percent 100. When minutes served are 0 and status is still pending, 100% does not mean “hired and online at this moment.” Uptime on a job is not proof of current connectivity.

What to inspect

• Open the job list on official device details and read status, minutes hired and minutes served on each row.
• If status is pending and minutes served are 0, treat that job as not yet recording served time. Do not call the monitor offline because of it.
• If earned has a number, it is still job accounting. Do not add it to today’s IO. Today’s IO comes only from the UTC-day block-reward summary for the same device ID.
• Back on the monitor, check that the hardware name and GPU count match this device. If they do not, stop and recheck the UUID.

Action branch

• If you need to know whether someone hired it, use official job status and minutes served. The monitor has no such column.
• If you need today’s block rewards, use today’s IO. Blank is not zero and it is not “not hired.”
• If hardware shows but the job does not match, trust the device_id on the official details and confirm the monitor has that same UUID.

Worked case (illustrative, not measured income)

A schematic device has a job in the same shape as the documentation sample: hired 300, served 0, pending, earned 0, uptime 100%. At the same moment the monitor shows a hardware name, GPU quantity 2 and a blank today’s IO. Read it this way: the model is known, this read has no block-reward figure, and whether a hire is being served depends on minutes served on that pending job (here, 0). Do not describe blank IO or 100% as “earning from an active hire.”

This page cannot accept a hire or power the machine down for you. Continue with today’s IO versus uptime and how to connect.