Bullion Price Check

We may earn a commission when you buy through links on this site. How we earn money.

Compare › Methodology › Operating record

Operating record: how reliably the hourly refresh runs

Over the last 7 days, 169 of 179 refresh runs completed and deployed (94.4%), and 75.4% of clock hours had at least one completed refresh. The live price snapshot was more than 120 minutes old for 1,243 minutes in that time, by our refresh log. A market-data benchmark is only as good as its record, so we publish ours. These numbers come only from our own logs and are recomputed at every build; we do not show figures we do not log.

Refresh runs

From logs/refresh.log on the build machine, as of Nov 11, 2026 9:03 AM ET. Log starts Oct 15, 2026 3:15 AM ET. Hourly coverage counts every clock hour in the window, including any hour when no refresh was scheduled.
WindowRuns completedHours with a completed refreshMinutes the live snapshot was over 120 min oldLink check failures
Last 1 day37 of 41 (90.2%)21 of 23 (91.3%)14 (1 episode)0 of 38
Last 7 days169 of 179 (94.4%)126 of 167 (75.4%)1,243 (8 episodes)0 of 171
Last 30 days495 of 523 (94.7%)352 of 653 (53.9%)12,708 (49 episodes)0 of 500

Failed runs in the last 30 days by stage: wrangler deploy (rc=1): 5; build_site: 3. A failed run does not deploy; the previous build stays live and its prices age out under the 120-minute rule.

Tests

Pre-deploy test suite: 5 of 5 full runs passed every suite (155 of 155 suite runs passed), recorded from Nov 10, 2026 9:10 PM ET to Nov 11, 2026 5:08 AM ET. We only started logging these runs on November 10, 2026; earlier runs are not counted.

Every hourly run also checks every internal link and stops the deploy on a broken one. It also checks that the premium index served by the API belongs to that build and logs a warning if it does not.

What these numbers do not show

Machine-readable: /data/operating-record.json. Live freshness per dealer: data quality.