Contact NIM Stats
How to reach the operator of NIM Stats — corrections, endpoint requests, data questions, and bug reports.
How to reach us
NIM Stats is operated by a single maintainer, Aathil Felix. There is no support desk and no ticket queue; messages go directly to the person who runs the collector. The fastest channel for anything technical is a GitHub issue — it is public, it keeps the context attached to the code, and other people hitting the same problem can find the answer.
Open an issue: https://github.com/AathilFelix/nim-stats/issues. For anything that is not a bug — a question about how a metric is derived, a request to track an additional endpoint, a correction to something the site reports — the same tracker is the right place, or reach the maintainer through the profiles linked from https://aathil.com.
What to include
For a data question, name the model ID exactly as the dashboard shows it and the approximate time in UTC. Probe samples are timestamped, so a model ID plus a timestamp is usually enough to reconstruct what the collector saw and explain the discrepancy. For a rendering or accessibility problem, the browser and viewport width help.
If you believe a published measurement is wrong, say what you observed instead and how you measured it. Measurements taken from a different network, region, or prompt shape legitimately differ from the collector's; those differences are interesting and worth reporting, not disputes.
Response expectations
This is an unpaid side project. Issues are read, but there is no response-time commitment and no on-call rotation. Outages of the site itself are usually visible on the public status page before a report arrives. If the dashboard is stale, the collector — not the web front end — is generally the thing that stopped.
A direct email address is not published yet. Until one is, the channels above are the supported way to get in touch.