When an Akash provider looks offline, separate unknown, unlisted, and a directory flag

“Not online” in the directory is that check’s flag, not an outage invoice. After you open the provider address on the Akash monitor, look at two things first: whether the online flag has a value, and whether the check time is present. Say “the directory marked this provider not online at this time” only when the flag is no and a time is present. A blank flag is unknown. An address the directory cannot find is unlisted or the wrong identifier. Do not call that offline.

What the flag, the time, and capacity each say

The online flag comes from the directory record. This page does not run its own probe. Check time is the moment the directory wrote down. Without it, you do not know how old that “no” is. GPU total and allocated count are still the provider’s advertised capacity. When the directory marks that provider not online, the allocated count does not turn into a loss amount by itself. The official site expects someone running a provider to have a host, networking, and ongoing maintenance. Restarting the service happens on the provider’s infrastructure, and the address is not necessarily one host.

What to inspect in each case

• Flag is no: note the check time, then on the provider’s infrastructure inspect the provider process, the network, and the operations items in the getting-started guide. This monitor cannot power it on for you.
• Flag is blank: leave it unknown. Return to the provider directory and see whether the original row later has a flag.
• There is no row at all: use provider address versus wallet and check that you did not paste a tenant wallet or a deployment id.
• Flag is yes, but you believe there is no order: online only restates the directory mark. It does not mean a lease exists. Read leases in the console, as in capacity and income.

What to do next

• If you are the provider: handle the service and the network on your provider infrastructure. Saving the record only lets you view the directory card. It uses account quota: five saved records per project on Free, 50 on Pro, not a physical host count.
• If you are the tenant: when the directory flag is no, do not assume the workload is still billing on that provider. Open your own deployment and lease page and confirm whether that workload is still open and whether you need another provider.
• On either side, do not multiply an offline duration by an hourly rate and call it a loss already taken. Without an official settlement or a lease window, the loss stays unknown.

Illustrative case (not a real outage)

The card name is North shed. First: online flag no, check time written as 09:00 on a given day. Read that as the directory marking not online at that moment, not as “offline for 9 hours,” unless you have a separate record measured from that moment. Second: the flag is blank. Read unknown. Third: a directory search does not find North shed. Read unlisted or wrong address. Do not fill any of the three in as 0 GPUs or 0 income.

Limits

One directory check is not continuous monitoring and not an infrastructure log. An availability line on the marketing site does not replace this directory record’s check time.