UMBRAE/ STATUS Open platform ↗
System status · Base mainnet Live · next check in 60s

Checking

Checking services

Waiting for the first status report.

 

Loading current availability…

What these checks cover — and what they don't

Network checks use the production routes that connect Umbrae to Ethereum L1 and Base L2, including any configured fallback, verifying the network and the latest block time. Contract addresses come from the platform's shared configuration and link to their block explorer. Data checks probe the two subgraphs that index trading history (indexing errors and lag behind Base), the database and the shared cache. App checks exercise the platform's own API. Public API checks read the OpenAPI specification and the latest indexed block from every market-data adapter it publishes, and confirm the API-key gate refuses a missing or unknown key — no credential is used or exposed.

A readable contract is not a guarantee that trading is enabled or that a transaction will succeed. The contract directory covers the DLMM core, the U1 token and lock vault, and the Ignis Elite NFT contracts — not every pool or retired deployment. The cache is reported as degraded, not down, when unreachable: the platform runs without it.

This page reports current observations, not historical uptime. It shares hosting with the platform; a hosting outage can also prevent this page from loading.