My services

My services answers one question: is my hosting all right, and if not, what do I press? You will find it in the sidebar, in the slot an administrator has Servers in. That is not a coincidence — that slot used to show the machines your hosting runs on, which is an answer to a question you never asked. This page is about your hosting, not about our hardware.

It opens with one sentence about everything you have: Everything is in order, or 3 item(s) want attention, or 1 critical item, 2 to look at. There is deliberately no percentage. "Your hosting is 82% healthy" is not something you can act on; "one thing is broken and this is it" is.

What each service shows

Every hosting account in your name is one block. The block carries the account's name, the plan underneath it, and a label naming the worst finding of that service. If everything runs the way it should, it says This service runs without remarks and that is the whole story.

If there is something, the findings sit on top and the checks that were run sit underneath. That order is deliberate: the item you have to do something about is what you came for, and the list of passing checks is what you read afterwards to watch the row you just fixed go green. A page that hid the passing checks could not show you that.

What you see here, and what you do not

The rows come out of the same check your administrator sees, but you do not get all of them. You see a row when it is critical, or when it is something you can fix yourself. That is why an address on a blocklist does reach you — your mail is bouncing, and that is yours to deal with — and a warning about the machine's own disk does not: there is nothing you could do about it, and your administrator already has it.

If you are a reseller the line sits elsewhere: you see the rows about your own customers' hosting, because that is your work and not somebody else's.

What a button beside a row does

Some findings carry a button. It does exactly what the screen behind that row would have done — same operation, same server, same check on whether you are allowed. There is no second, faster path behind it. If it goes wrong you get that operation's own error, not a generic one.

There is also a Check again button. Every measurement has its own shelf life; that button asks for everything that is due to be measured now. Straight afterwards nothing may have changed yet — an address you had delisted this morning can still be travelling through the list keeper's own systems.

When there is nothing to show

If no hosting is in your name yet the page says so, and that is the right message — not an empty grid and not a zero. If the check could not be fetched the page says that instead of reporting "all well" about a list it never managed to read. The difference between "nothing is wrong" and "I do not know" is the whole point of this screen.

The same answer from a terminal

If you would rather run your hosting from a terminal, the public API returns the same list. You need an API key for it (see API keys):

# The findings of one hosting account, the way this screen shows them
curl -sS -H "Authorization: Bearer corecp_<prefix>_<secret>" \
  https://panel.example.com/api/v1/accounts/myaccount/advisor

See also

• What needs attention — the same principle, for the overview the panel opens with.
• Usage and limits — where a row about throttling or a refused process points.
• Reading your notifications — how the same events reach you without your having to look.
• What you can arrange yourself — everything you can change about a hosting account.