Status

Ingest health. This page reads the ingest run log in D1 directly and renders even when the snapshot store is empty. The weekly indexation report is built by the same worker.

Snapshot age

1 min

2026-09-30 09:12 UTC

Snapshot store

readable

55 contracts cached

Last ingest

5896 ms · 2026-09-30 09:12 UTC

Minute tick, last hour

clean · 60 of 60

Hyperliquid mark and funding · every tick records, so one that never ran shows here

Failures in last 24 runs

24 runs recorded

Bindings and worker version

Three deploy steps the build cannot see, all checked here. A missing KV binding SNAPSHOT fails loudly, on purpose: pages answer 503. The other two fail quietly: every page still renders.

Check	State	What a wrong value means
KV binding `SNAPSHOT`	attached	Pages would serve 503 rather than fall back to the upstream API — deliberately, so a missing binding cannot hide behind a working-looking site.
D1 binding `DB`	attached	Pages still render, and the ingest worker still writes through its own binding, but nothing on the site can read what it wrote: the “Last ingest”, “Minute tick, last hour” and “Failures in last 24 runs” cards above say “unreadable”, “Per-venue coverage, last run” prints “—” for every venue, “Recent runs” below says “Run log unreadable”, and /open-interest cannot say how much of its open interest is new.
Ingest worker version	current	Deployed `3f775d930f91`, site expects `3f775d930f91`. The bundle is pasted into the dashboard by hand, so it can sit behind this repository with nothing to say so — whatever the newer worker was meant to write is simply absent.

External corroboration

What a signed-out reader gets when they follow the one external link this site would publish about itself. It is published only while this says published: a link that does not resolve is worse corroboration than none, and nothing here has to be edited either way.

URL	State	Last anonymous GET
`https://github.com/coinliqui/coinliqui`	unreachable	HTTP 429, checked 16h ago

Series coverage

A published contract with no series behind it renders a page-shaped hole: the chart panel is simply absent, every other figure is fine, and nothing above this line would notice. The counts are against the 55 contracts currently published.

Series	Covered	Refresh interval	Missing or stale
15-minute candles drives the 15m and 30m charts	55 / 55	2 h last full refresh 2026-09-30 08:52 UTC	none
Hourly candles drives the liquidation map and the 1H/4H charts	55 / 55	2 h last full refresh 2026-09-30 07:27 UTC	none
Daily candles drives the 1D/1W charts and leverage survival	55 / 55	12 h last full refresh 2026-09-30 06:02 UTC	none
Funding history drives the funding chart and 30-day standing on each contract page	55 / 55	6 h last full refresh 2026-09-30 08:37 UTC	none

Per-venue coverage, last run

A venue silently dropping out of the upstream response looks like success: the run still writes rows, just fewer. A count at zero here is that failure.

Venue	Rows last run
Hyperliquid `HlPerp`	55
Binance `BinPerp`	52
Bybit `BybitPerp`	51

Recent runs

When	Source	Status	ms	Result
2026-09-30 09:12 UTC	hyperliquid	200	5896	ok
2026-09-30 09:07 UTC	hyperliquid	200	6528	ok
2026-09-30 09:02 UTC	hyperliquid	200	6631	ok
2026-09-30 08:57 UTC	hyperliquid	200	6504	ok
2026-09-30 08:52 UTC	hyperliquid	200	7819	ok
2026-09-30 08:47 UTC	hyperliquid	200	8575	ok
2026-09-30 08:42 UTC	hyperliquid	200	7633	ok
2026-09-30 08:37 UTC	hyperliquid	200	7771	ok
2026-09-30 08:32 UTC	hyperliquid	200	8853	ok
2026-09-30 08:27 UTC	hyperliquid	200	9249	ok
2026-09-30 08:22 UTC	hyperliquid	200	8466	ok
2026-09-30 08:17 UTC	hyperliquid	200	6096	ok
2026-09-30 08:12 UTC	hyperliquid	200	6454	ok
2026-09-30 08:07 UTC	hyperliquid	200	5909	ok
2026-09-30 08:02 UTC	hyperliquid	200	7030	ok
2026-09-30 07:57 UTC	hyperliquid	200	6382	ok
2026-09-30 07:52 UTC	hyperliquid	200	5772	ok
2026-09-30 07:47 UTC	hyperliquid	200	5895	ok
2026-09-30 07:42 UTC	hyperliquid	200	6600	ok
2026-09-30 07:37 UTC	hyperliquid	200	6294	ok
2026-09-30 07:32 UTC	hyperliquid	200	6518	ok
2026-09-30 07:27 UTC	hyperliquid	200	7206	ok
2026-09-30 07:22 UTC	hyperliquid	200	7644	ok
2026-09-30 07:17 UTC	hyperliquid	200	7754	ok

Announcement channel

IndexNow is the only route from this site into the indexes that are not Google, and it needs no account. A URL is announced once, when it first appears — never on a price change. The Worker submits to all five endpoints rather than trusting the aggregator's fan-out, so a backlog against one of them is that endpoint's refusal rather than a site fault. Consecutive failures against the two Microsoft-run endpoints mean the shared Cloudflare egress is being throttled; the fix is npm run indexnow:drain, which sends the same backlog from somewhere else.

Endpoint	URLs owed	Consecutive refusals	Next attempt
api.indexnow.org	12	35	held until 2026-09-30 18:52 UTC
bing.com	18	58	held until 2026-09-30 10:22 UTC
yandex.com	0	—	next pass
search.seznam.cz	0	—	next pass
searchadvisor.naver.com	0	—	next pass

143 URLs recorded as published. Last accepted by any endpoint 2026-09-28 08:17 UTC.

2 endpoints are refusing. api.indexnow.org (35x, 12 owed), bing.com (58x, 18 owed). The retry rate decays from five minutes to a twelve-hour cap, so a URL owed here is not lost — it is waiting. What it is not is announced.

Contact route

The published address is hello@coinliqui.com, protected from edge rewriting. Directly below is the same address deliberately left unprotected, as a live test of whether the rewriting is switched on at all: hello@coinliqui.com. If those two differ, the edge is rewriting and the protection on every other page is what is keeping the site reachable.