Docs · For traders
Status and the network
What is checked
| Service | Up when |
|---|---|
| Indexer and API | It has read the chain in the last 60 seconds and is no more than 300 blocks behind the tip |
| Zero RPC | At least one of the nodes the indexer reads through answers with a block number |
| Keeper | Its last round, filling orders and running copies and buybacks, finished in the last 120 seconds |
| Website | The terminal answers without a server error |
Each check has 10 seconds to answer, 5 for the keeper. Nothing is guessed: a service that hasn't been checked lately shows as not checked, not as up.
What each state means
| State | Means |
|---|---|
| Up | The last check, in the last 3 minutes, passed |
| Down | The last check failed, with the reason it gave |
| Not checked lately | No check in the last 3 minutes |
| Everything is working | Every service is up |
| Something is down | At least one service is down |
| Partly checked | Nothing is down, but not everything was checked lately |
Uptime and incidents
Each service shows its uptime over 24 hours, 7 days and 90 days, and a bar for each of the last 90 days. A service down for two checks in a row opens an incident, dated from the first of them; one failed check alone is a blip. The first check that passes closes it. The page lists the 50 latest incidents and how long each lasted.
Your money doesn't depend on any of these. Tokens, orders, the copy vault and staking live in the contracts, which you can use without the site. See Keepers and the site.
Picking your RPC
The site reads the chain and sends your trades through an RPC. Click the network's name in the top bar to see how each one is doing and pick another:
- Submarine's RPC, the default, reached through this site.
- Zero's public RPC, when there is one.
- Your own: any https RPC for this network. The site checks that it answers and is on the right chain before it switches.
The dot by the network's name shows how the RPC in use is doing against the indexer. If it falls about 20 seconds of blocks behind, at least 5, a banner says prices and balances lag, and Fix network tries every RPC on offer and moves to the one furthest ahead, the faster one on a tie. If none answers, the problem is likely your own connection.
From code
GET /api/v1/status answers with overall, each service's state, last check, note, uptimes and days, and the incidents. It is kept for 15 seconds between everyone asking. See Public API.