Testnet on Base Sepolia: 1 ZRO here is 0.0001 test ETH.
Docs · Status and the network

Docs · For traders

Status and the network

The Status page checks every service Submarine runs on once a minute and keeps the answers for 90 days. If something seems off, look there first. If the network itself is slow from where you are, you can switch to another RPC.

What is checked

ServiceUp when
Indexer and APIIt has read the chain in the last 60 seconds and is no more than 300 blocks behind the tip
Zero RPCAt least one of the nodes the indexer reads through answers with a block number
KeeperIts last round, filling orders and running copies and buybacks, finished in the last 120 seconds
WebsiteThe 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

StateMeans
UpThe last check, in the last 3 minutes, passed
DownThe last check failed, with the reason it gave
Not checked latelyNo check in the last 3 minutes
Everything is workingEvery service is up
Something is downAt least one service is down
Partly checkedNothing 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.