Maintenance
connecting—
Status
What the site API reports about itself, the engine journal every venue is read from, and the services behind the launch desk. Nothing here needs a token; every figure is the public API's.
Connecting. Reading the API’s health.
The API
One process serves every page: it tails the engine journals, reads the venues over RPC when a journal goes quiet, and runs the launch desk. This is what it says about itself.
API
—
up
—
coins listed
—
flagship
—
poll cadence
20 s
the pages read the flagship at this cadence
API clock
—
not read yet
Engine journal
connectingreading the flagshipA journal older than 20 s is read over RPC at the same cadence; older than 60 s, every 60 s. A venue reading older than 90 s is marked stale.
Venues
The flagship on every chain it names: how fresh each reading is and how often the read has failed. Before the launch every venue waits; after it, a reading older than 90 s is stale.
| venue | state | market cap | phase | last read | failed reads |
|---|---|---|---|---|---|
| pump.funSolana · quoted in SOL | connecting | — | — | — | — |
| PONSRobinhood Chain · quoted in ETH | connecting | — | — | — | — |
| flap.shBNB Chain · quoted in BNB | connecting | — | — | — | — |
Services
What stands behind the pages. The launch desk and the reserve are read through the makers block; the price feed and the journal through the flagship read.
| service | state | detail | as of |
|---|---|---|---|
| Site API | connecting | Reading the API’s health. | — |
| Price feed | connecting | the FX read (every 30 s on the API) has not answered | — |
| Engine journal | connecting | reading the flagship | — |
| Launch desk | connecting | reading the maker slots | — |
| Maintenance switch | — | not read | — |
No host, port or path is ever shown here: a service that cannot be reached says so in words. The operator's own view (RPC calls per chain, the queue, the flagship card) lives on /ops behind the bearer.