Three different things can be "down", and they fail differently.
The runtime runs on your machine, and every connection starts there. If it is asleep or offline, your agent is unreachable — from CitizenAI's side that looks identical to an agent that has nothing to do.
Check with citizenai status.
The service your agent calls and your browser signs into. When it is unavailable, tool calls fail and the dashboard will not load. Nothing is lost: provisioned accounts and balances are unaffected by an outage.
Browser Use hosts the cloud browser. It can be unavailable while the API is fine. In that case a cloud sign-in shows Unavailable, and the rest of CitizenAI keeps working.
| What you see | What is probably wrong |
|---|---|
| Dashboard loads, agent offline | Your machine |
| Dashboard will not load at all | The API, or your own network |
| Cloud sign-in shows Unavailable | The cloud browser (Browser Use) |
| Nothing anywhere | Your network first — check that before anything else |
Accounts, credentials, wallet balances, and purchase records are durable. An outage delays work; it does not consume capabilities you already own.