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
3 min
2026-11-22 20:37 UTC
Snapshot store
readable
54 contracts cached
Last ingest
ok
5080 ms · 2026-11-22 20:37 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
0
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.

CheckStateWhat a wrong value means
KV binding SNAPSHOTattachedPages 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 DBattachedPages 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 versioncurrent Deployed 9a6441648add, site expects 9a6441648add. 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.

URLStateLast anonymous GET
https://github.com/coinliqui/coinliquipublishedHTTP 200, checked 23h 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 54 contracts currently published.

SeriesCoveredRefresh intervalMissing or stale
15-minute candles
drives the 15m and 30m charts
54 / 542 h
last full refresh 2026-11-22 19:57 UTC
none
Hourly candles
drives the liquidation map and the 1H/4H charts
54 / 542 h
last full refresh 2026-11-22 19:07 UTC
none
Daily candles
drives the 1D/1W charts and leverage survival
54 / 5412 h
last full refresh 2026-11-22 17:12 UTC
none
Funding history
drives the funding chart and 30-day standing on each contract page
54 / 546 h
last full refresh 2026-11-22 16:22 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.

VenueRows last run
Hyperliquid HlPerp54
Binance BinPerp51
Bybit BybitPerp51

Recent runs

WhenSourceStatusmsResult
2026-11-22 20:37 UTChyperliquid2005080ok
2026-11-22 20:32 UTChyperliquid2001600ok
2026-11-22 20:27 UTChyperliquid2003806ok
2026-11-22 20:22 UTChyperliquid2003743ok
2026-11-22 20:17 UTChyperliquid2003642ok
2026-11-22 20:12 UTChyperliquid2007462ok
2026-11-22 20:07 UTChyperliquid2004166ok
2026-11-22 20:02 UTChyperliquid2009402ok
2026-11-22 19:57 UTChyperliquid2005681ok
2026-11-22 19:52 UTChyperliquid2005011ok
2026-11-22 19:47 UTChyperliquid2004395ok
2026-11-22 19:42 UTChyperliquid2007356ok
2026-11-22 19:37 UTChyperliquid20010139ok
2026-11-22 19:32 UTChyperliquid2002515ok
2026-11-22 19:27 UTChyperliquid2007247ok
2026-11-22 19:22 UTChyperliquid2007932ok
2026-11-22 19:17 UTChyperliquid2004086ok
2026-11-22 19:12 UTChyperliquid2004465ok
2026-11-22 19:07 UTChyperliquid2009859ok
2026-11-22 19:02 UTChyperliquid2008196ok
2026-11-22 18:57 UTChyperliquid20010384ok
2026-11-22 18:52 UTChyperliquid2004233ok
2026-11-22 18:47 UTChyperliquid20010581ok
2026-11-22 18:42 UTChyperliquid2005078ok

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.

EndpointURLs owedConsecutive refusalsNext attempt
api.indexnow.org0—next pass
bing.com20165held until 2026-11-23 03:52 UTC
yandex.com0—next pass
search.seznam.cz0—next pass
searchadvisor.naver.com0—next pass

141 URLs recorded as published. Last accepted by any endpoint 2026-11-18 00:12 UTC.

1 endpoint is refusing. bing.com (165x, 20 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.