Loading…
Pre-openThe market has not opened yet. Showing Wed 23 Sept's close, 16:00 ET. These numbers start moving again when it opens today at 09:30 ET.
Loading…
Every scheduled job, when it last succeeded, and whether anything is behind.
1 of 16 jobs is behind or has never run.
Green means the job wrote something inside its own window, not that what it wrote was correct. A job can succeed and still store a bad number; this page cannot tell you about that, only about silence.
/api/breadth/refresh
every minute, 13:00-21:59 UTC, Mon-Fri
/api/retest/refresh
every minute, 13:00-21:59 UTC, Mon-Fri
/api/scanner/gamma
12:30 and 13:30 UTC, Mon-Fri
/api/scanner/run
13:35 and 14:35 UTC, Mon-Fri
/api/trackrecord/log
20:15 and 21:15 UTC, Mon-Fri
/api/trackrecord/settle
20:20 and 21:20 UTC, Mon-Fri
/api/post
13:00 UTC, Mon-Fri
/api/log/snapshot
14:45 UTC, Mon-Fri
/api/log/settle
21:15 UTC, Mon-Fri
/api/flow/refresh
21:40 UTC, Mon-Fri
/api/velocity/refresh
21:50 UTC, Mon-Fri
/api/groups/refresh
22:00 UTC, Mon-Fri
/api/sectors/refresh
22:10 UTC, Mon-Fri
/api/digest
22:20 UTC, Mon-Fri
/api/rs/refresh
23:00, 01:00, 03:00 and 05:00 UTC
/api/rs/members
22:30 UTC, Saturdays
When the live feed cannot be reached, pages serve this stored snapshot with a warning banner above it rather than failing. Recovered data is never presented as current — it keeps its own timestamp, and the banner is not dismissible.
Which credentials this deployment can actually see is reported by /api/health, as presence only — no value is ever returned or displayed.
Reading the limits. Most of these run on weekdays only, so the “late past” figure is set wide enough to cover a long weekend. That means a job which died on Monday will not show red until Thursday. The tradeoff is deliberate: a page that turns red every Saturday is a page that gets ignored by the following Tuesday.
The machine-readable version. /api/health returns the same readings as JSON, alongside the storage and environment checks. Both are built from one helper, so they cannot disagree.