Status

A directory of the live Ophis surfaces and their health endpoints. There is no synthetic uptime dashboard: each row links to the relevant live surface, or to a self-reporting health endpoint where one exists, so you can check current state directly.

Services

Surface	URL	Health check
Swap app	swap.ophis.fi	Loads the intent UI.
Landing	ophis.fi	Loads.
Docs	docs.ophis.fi	This site.
Explorer	explorer.ophis.fi	Order/trade search.
Intent API	POST https://ophis.fi/api/intent	See Intent API.
MCP server	https://mcp.ophis.fi/mcp	Streamable-HTTP; a request without an Accept: text/event-stream header returns HTTP 406: that is expected, not an outage. See AI agents.
Rebate indexer	rebates.ophis.fi/health	JSON. last_pipeline_run_at is nullable until a nightly pipeline completes and is the liveness signal thereafter; do not treat ok: true alone as proof that the nightly pipeline has run. last_fetch moves only when a new tagged trade is inserted. Cloudflare 530 / error 1033 means the tunnel replica is disconnected.
Optimism orderbook	version check	HTTP 200 plus a version string confirms the public chain-10 orderbook is reachable. A non-200 response means do not route until it recovers.
Unichain orderbook	version check	HTTP 200 plus a version string confirms the public chain-130 orderbook is reachable. A non-200 response means do not route until it recovers.
Robinhood orderbook	version check	HTTP 200 plus a version string confirms the public chain-4663 orderbook is reachable. A non-200 response means do not route until it recovers.
Arc orderbook	version check	Reachability of the chain-5042 orderbook; not proof of liquidity or settlement for a token pair.

The Robinhood deployment is also covered by a daily read-only production canary. It verifies chain identity, Ophis settlement/relayer/EthFlow bytecode, WETH and USDG metadata, the official Stock Token registry and ERC-8056 multiplier, the default token list, and orderbook version. Its workflow is robinhood-mainnet-canary.yml.

Settlement model per chain

Ophis settles across two kinds of chains:

“Production” below means the contracts and configured routing surface exist; it does not promise current uptime. Use the linked checks above before routing.

• CoW-hosted chains: Ethereum, BNB Chain, Gnosis, Polygon, Base, Arbitrum, Avalanche, Linea, Ink, and Plasma. Orders settle through CoW Protocol's production orderbooks (api.cow.fi) using the canonical CoW contracts. Their status mirrors CoW Protocol's status.
• Ophis-operated chains: Optimism (chain 10), Unichain (chain 130), Robinhood Chain (chain 4663), and Arc (chain 5042). Orders settle through Ophis's self-hosted orderbooks at optimism-mainnet.ophis.fi, unichain-mainnet.ophis.fi, and robinhood-mainnet.ophis.fi, and arc-mainnet.ophis.fi using Ophis-deployed GPv2Settlement contracts. Resolve SDK-supported chains through @ophis/sdk v0.4.3 or MCP list_chains; both include Arc.

Solana, Bitcoin, Monad, Hyperliquid (Hypercore), X Layer, Sui, Tron, Starknet and Zcash are additional sources and destinations via NEAR Intents. External-source swaps use the standalone app's deposit flow, not source-chain CoW orderbooks or SDK EIP-712 signing domains. Provider and asset availability still determine executable routes. See Networks & assets for Circle bridges, stock labels and the current confidential-routing and institutional-feature boundaries.

Incidents

Operational incidents and maintenance are announced on x.com/ophisfi. The canonical source of truth for what is deployed is the ophis-fi/ophis repository.