Web Server Access Log Analyzer

How it works

Each pasted line is matched against a single regular expression built for the nginx/Apache combined log format — capturing the client IP, timestamp, HTTP method and path, status code, and response size — entirely in your browser. Lines that don't match that format are counted as "not parsed" rather than causing an error, and the matched requests are then tallied into IP, path, status-code, and hour-of-day counts.

FAQ

Why do some of my log lines show up as "not parsed"?

The parser expects the standard nginx/Apache combined log format; lines in a custom log format, JSON logs, or with extra or missing fields won't match its regex and are skipped rather than guessed at.

Does the hour-of-day chart account for timezones?

No — it buckets by the hour digits parsed directly out of each line's own timestamp text, without converting for the timezone offset also present in that timestamp, so mixed-timezone logs still bucket by whatever hour each server originally wrote down.