host-09 is copying, and cannot be controlled
Its agent refused the last call. The caller’s address is not on that agent’s allowlist — on a host 2.4.0 against 2.4.1, that is almost always the dispatcher added on 4 Sep never reaching it. Its 3 terminals keep copying — the agent’s trade connection to the Hub is outbound and untouched, which is also how we know the machine is alive. What is lost is the ability to restart, move or drain them from here.
host-13 is waiting to enrol
The one-time token was minted when the host record was created and is shown once. If it was not captured then it cannot be recovered — revoke the record and create it again.
Hosts96 online
Slots used15 / 3615 can be placed into today
Agents behind3current is 2.4.1
Not answering24 terminals on them
Host registry
9 hosts across 3 regions
| Host | Region | State | Capacity | Agent | Agent API | Last answered | |
|---|---|---|---|---|---|---|---|
| host-01 | eu-west-1 es-vm-eu-01 | Online | 4 / 6 2 free | 2.4.1 | 10.60.1.11:8443 Answering22 ms | 14 Sep 13:41:00 1m ago | |
| host-02 | eu-west-1 es-vm-eu-02 | Online | 1 / 6 5 free | 2.4.1 | 10.60.1.12:8443 Answering24 ms | 14 Sep 13:41:00 1m ago | |
| host-04 | eu-west-1 es-vm-eu-04 | Online | 2 / 2 0 free | 2.4.1 | 10.60.1.14:8443 Answering25 ms | 14 Sep 13:40:00 2m ago | |
| host-07 | ap-south-1 es-vm-ap-07 | Online | 2 / 6 4 free | 2.4.1 | 10.62.3.7:8443 Answering41 ms | 14 Sep 13:41:00 1m ago | |
| host-09 | ap-south-1 es-vm-ap-09 | Online | 3 / 4 1 free | 2.4.0 behind | 10.62.3.9:8443 Refused | 14 Sep 13:39:00 3m ago | |
| host-11 | us-east-1 es-vm-us-11 | Online | 2 / 6 4 free | 2.4.1 | 10.64.2.11:8443 Answering30 ms | 14 Sep 13:41:00 1m ago | |
| host-12 | us-east-1 es-vm-us-12 | Draining | 1 / 6 5 free | 2.3.8 behind | 10.64.2.12:8443 Slow610 ms | 14 Sep 11:42:00 2h ago | |
| host-13 | eu-west-1 es-vm-eu-13 | Enrolling | 0 / 6 6 free | 2.4.1 | 10.60.1.13:8443 Not enrolled | Never | |
| host-06 | ap-south-1 es-vm-ap-06 | Offline | 1 / 6 5 free | 2.3.8 behind | 10.62.3.6:8443 Unreachable | 13 Sep 07:42:00 1d ago |
How a host enrols
Per-host secrets, never a fleet-wide one
1 · Create the record
Host id, region, VM name, capacity and the address the agent will listen on. Saving mints a one-time enrolment token, displayed once — not stored in a form you can reopen, not emailed, not recoverable.
2 · The agent presents it
On first boot, and it must come from the address on the record. An enrolment from anywhere else is refused, which is what stops a token redeemed on somebody else’s machine from becoming a host.
3 · Pinned, and given the allowlist
The token is spent. The agent receives its own per-host credential, its fingerprint is pinned, and it is handed the list of addresses it will accept calls from. Nothing fleet-wide is ever handed out.
4 · Two planes from then on
The agent dials out to the Hub for trades — one connection per host — and answers inbound on its own address for control: placing a terminal, dispatching a credential, restarting, draining, upgrading. Losing one does not lose the other, and the pair is how a refused caller is told apart from a dead VM.
Who may call an agent
The allowlist every agent enforces
| Address | Region | What calls from it |
|---|---|---|
| 52.18.44.10 | eu-west-1 | Signal Server — primary |
| 52.18.44.11 | eu-west-1 | Signal Server — standby |
| 3.108.72.4 | ap-south-1 | Regional dispatcher — added 4 Sep |
- Every agent refuses an inbound call whose source is not on this list, and it refuses before authenticating. An allowlist checked after auth narrows who can be attacked, not how often.
- Adding an address here is a fleet-wide change. It has to reach every agent before anything calls from it. Until it does, each agent refuses the new caller one at a time — which is what host-09 on the table above is, not a fault on the host.
- The addresses are private. An agent API reachable from the internet is a credential dispatcher reachable from the internet, and no allowlist is worth relying on as the only thing between those two facts.