Know the pipeline
slipped before your
customers do.
A monitor that lives in your toolbar. It pings the API, reads live status for Great Britain, Australia and Ireland, tracks what your key is spending, and raises a desktop alert the moment results start arriving late.
Regions
Last recorded result
A results feed rarely dies. It drifts.
Nothing 500s. The endpoint answers, the JSON parses, and your app keeps serving cards that settled forty minutes ago. You find out when a customer asks why a race that ran at 19:46 still shows no winner. This extension watches the two numbers that catch that early, on every region you take data from, and tells your desktop rather than waiting for you to open a dashboard.
What it actually watches
Six things, each of which would otherwise mean opening a tab and reading a dashboard.
Toolbar badge
Green when everything is inside your thresholds, amber with a count when something slips, red when the API cannot be reached at all.
visible without clickingThree regions, separately
Great Britain, Australia and Ireland each carry their own sync age, races awaiting results and median delay, so a quiet region cannot hide behind a busy one.
GB · AU · IEPing, with its own history
Round-trip time to the server with a sparkline of recent checks, and a refresh button on the card itself. The ping endpoint takes no key, so it costs you nothing.
free of your rate limitWhat your key is spending
Calls this minute against your rate limit, the day's running total, and the month against your plan, so a runaway loop shows up before the 429s do.
reads /v1/usageDesktop alerts that shut up
One notification per new issue, not one per check. A problem that persists stays on the badge quietly; clearing it re-arms the alert for next time.
once, not every minuteYour thresholds, not ours
Check interval, how stale a sync may get, how many races may sit awaiting results, the ping ceiling and the median-delay limit. All saved locally.
six dialsThree tabs, no hunting
Status for the pipeline, Usage for the key, Settings for the dials. The window is 380 pixels wide and everything fits without scrolling past it.
Regions
Status
Ping and sync age up top, then a row per region carrying the day's card and what is still outstanding. The last recorded result sits underneath, so you can see the pipeline moving rather than infer it.
Usage
The minute window, the day and the month, straight from your key's own allowance. Useful the first time a new integration goes out and starts polling far harder than anyone intended.
Settings
Paste the key once. Pick how often it checks, which regions matter to you, and the point at which each number stops being normal. Everything is stored in the browser, nowhere else.
What the four numbers mean
The same fields the API publishes at /v1/status, in the order they usually go wrong.
Server ping
Round trip to the edge. It moves with your own connection as much as ours, which is why the sparkline matters more than any single reading.
Last sync
How long since the pipeline last wrote anything at all. The first number to go wrong when ingest stops, and it goes wrong for every region at once.
Awaiting results
Races that have run and have no result yet. A handful during an evening card is normal; a climbing count is the early warning.
Median delay
The middle gap between a race going off and its result landing, over 24 hours. Rising means results are arriving, just later than they should.
Installed in under a minute
- Download the zip and unzip it somewhere permanent. The browser loads the extension from that folder, so it needs to stay put.
- Open
chrome://extensions. - Turn on Developer mode, top right.
- Click Load unpacked and choose the unzipped
chromeextfolder. - Pin it, open it, and paste your key into Settings.
No key yet?
The free key is enough to run the monitor: it reads status, ping and usage, which are all outside the metered endpoints. You can watch the pipeline before you ever pull a race card.
Get a free keyPrefer to build your own?
Everything the extension shows comes from three documented endpoints. If you would rather put it on a wallboard or in Slack, the same fields are yours.
Read the status docsBefore you ask
The things people write in about, answered here instead.
Does it eat my rate limit?
Barely. One status call and one usage call per check, plus a ping that needs no key at all. At the default minute interval that is under three thousand calls a day, and you can slow it to fifteen minutes.
Why is it not on the Chrome Web Store?
Store review adds days to every change, and this thing tracks an API that moves weekly. Loading it unpacked keeps the two in step.
Does it work with a free key?
Yes. Status, ping and usage are all available on the free tier, so the monitor works from the day you sign up.
What happens when my laptop sleeps?
Checks stop and resume when it wakes, and the first check after waking refreshes everything. The countdown in the footer always shows when the next one is due.
Can I watch one region only?
Yes. Untick the others in Settings and both the rows and the alerts follow, so an Irish evening card cannot set off an alert if you only take GB data.
Does it phone home?
No. There is no analytics, no account and no server of ours involved beyond the API calls your key makes. Everything it stores stays in your browser.
Put it in your toolbar and forget it
It will stay green and say nothing until the day it matters, which is exactly the point. Twenty-odd kilobytes, three regions, and one fewer dashboard to remember to open.