lagcheck answers one question: is this your connection, or is it them? It measures
your own line for the things that actually break games and calls — latency under load,
jitter, upload headroom — and reads the published status of 28 services so the
two halves of the answer sit on one screen.
If you are here because you saw our user-agent
You are probably looking at a request like this in your logs:
lagcheck.com status reader (+https://lagcheck.com/about)
What we fetch. Your public status endpoint only — usually
/api/v2/summary.json on Statuspage, or whatever machine-readable feed you
publish. Nothing else on your domain. We do not crawl your site.
How often. Once every five minutes at most, and less if we are rationing
requests. One request per cycle per feed.
What we do with it. Report your status as you published it. We never
re-word your incident titles, and when we could not read your feed we say so rather than
assuming you are healthy.
Where we measure from. A Cloudflare Worker, so the source addresses are
Cloudflare's.
If you would rather we did not. Say so and we will stop. Contact is below.
A handful of services publish no status feed at all. For those we make a single ordinary
request to a documented public API endpoint and time it. That result is labelled in our
interface as our own measurement, never as a statement from you — because a slow or refused
response tells us about the path between us, not about your service.
What we cannot see
This is the part most tools leave out.
Your home network. A browser cannot see your router, your radio, or the hop to it.
Real game traffic. We load a line with HTTP; games use small constant UDP. Different
shapes, and we do not pretend otherwise.
Whether your account is affected. Vendor feeds describe the service, not you.
How long an outage will last. Nobody publishes that, and we will not guess.
Microsoft 365. Their machine-readable feed requires a tenant credential, so there is no
honest way for us to report it. If Teams is down, nothing here will tell you.
What we will not build
Crowdsourced outage reports would make us faster at spotting problems that vendors have
not admitted yet. They would also mean collecting reports from people on a server, and the
promise that nothing leaves your browser would become conditional. We would rather keep the
promise and be a little slower.
Contact
Status feed corrections, crawler questions, or a request to be removed:
hello@lagcheck.com.