Status
Status
0.9.53Degraded: see below. Everything below is read from our own node, its ord index, the scheduled jobs that keep this dashboard current, and the web server itself (uptime and release) -- nothing here is a marketplace's uptime, only ours.
At a glance
- Dashboard uptime
- 13m
- Release
- 0.9.53
- Bitcoin node
- unreachable (last answered 2026-10-21 01:51 UTC)
- Last block seen
- 972,401 at 2026-10-21
- Our ord index
- reachable
- Ord caught up with the node
- yes
- Ord features live
- Inscriptions, Runes, Sat ranges, Addresses
- Scheduled jobs watched
- 103
- Scheduled jobs failing
- 17
Jobs failing
| Job | Failures in a row | Last error |
|---|---|---|
| rune_claim_sweep | 48 | OperationalError: cannot start a transaction within a transaction |
| inscription_sales_history | 47 | OperationalError: cannot start a transaction within a transaction |
| clusters_backfill | 42 | OperationalError: cannot start a transaction within a transaction |
| offer_alerts | 34 | OperationalError: cannot start a transaction within a transaction |
| signed_outpoints | 32 | OperationalError: cannot start a transaction within a transaction |
| marketplace_open_offers_expire | 16 | OperationalError: cannot start a transaction within a transaction |
| onchain_price | 16 | OperationalError: cannot start a transaction within a transaction |
| collection_radar | 15 | OperationalError: cannot start a transaction within a transaction |
| listing_expiry | 15 | OperationalError: cannot start a transaction within a transaction |
| marketplace_offers_expire | 15 | OperationalError: cannot start a transaction within a transaction |
| subscription_expiry | 14 | OperationalError: cannot start a transaction within a transaction |
| showcase_refresh | 13 | RuntimeError: showcase refresh failed for 1A1zP1eP: /address/<address>: ReadTimeout: timed out |
| pnl | 9 | OperationalError: cannot start a transaction within a transaction |
| collection_holders | 7 | OperationalError: cannot start a transaction within a transaction |
| collection_index | 6 | OperationalError: cannot start a transaction within a transaction |
| wash_trades | 6 | OperationalError: cannot start a transaction within a transaction |
| ord_holdings | 4 | OperationalError: cannot start a transaction within a transaction |
Jobs running long
| Job | Last run | Expected interval |
|---|---|---|
| lab_fair_launch | 1238s | 60s |
Checking this automatically?
Poll /api/health for a plain "status": "ok" and an uptime counter -- it answers in milliseconds and carries no HTML. This page is the human-readable version of the same facts, plus /api/ord/status and the job_health section of /api/snapshot.
Last updated