01
Why did signups move?
Tie conversion changes to landing pages, referrers, errors, geography, and deploy windows.
ask across the bay
Ask your traffic anything, then see the request trail.
knockstat turns access logs into an answer layer. Ask what moved, why it moved, and which routes, referrers, crawlers, countries, or status codes explain it.
answer layer / sf node
Which pages got cleaner human traffic after the deploy?
Docs and pricing gained the cleanest human lift. Bot share stayed flat, but organic visitors from US west and Canada spent more time on setup pages.
/docs/server-logs+31%
/pricing+18%
known crawler shareflat
san francisco signal
Question types that operators actually ask
From launch-day spikes to crawler floods, every answer keeps a link back to the underlying request patterns.
02
Which crawlers are here?
Separate useful bots from noisy crawlers and watch crawl behavior by route.
03
What broke?
Find status clusters, latency pockets, and failure windows without spelunking raw logs.
answer evidence
Answers with evidence, not vibes
Every answer is grounded in the rows behind it, so the assistant can explain confidence, outliers, and the trace it followed.
trace / request evidence
Show the evidence behind that answer.
The conclusion came from a 24-hour route comparison, filtered to human traffic and grouped by referrer.
sample window24h
rows checked214k
bot filteron
launch from the pier
Start with one site. Ask the first question.
Point knockstat at a log source and get a readable traffic layer in minutes.