Logo

Sample Web Server Log CSV File — Free Download

A web server access log flattened into CSV — timestamp, IP, method, path, status, bytes, response time and user agent — for practising traffic analysis, error-rate monitoring and bot filtering.

Download the sample file

CSV · 800 rows · 79.7 KB · synthetic data, free for any use

Download CSV sample

Preview

timestampipmethodpathstatusbytesresponse_msuser_agent
2026-01-01T00:01:00Z111.1.5.85GET/login2003083542Mozilla/5.0 (iPhone; CPU iPhone OS 17_2) Mobile Safari
2026-01-01T00:03:00Z216.164.231.77HEAD/compress/4049202150Googlebot/2.1
2026-01-01T00:05:00Z5.199.229.64POST/200807114Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15) Safari/17
2026-01-01T00:06:00Z193.249.121.9POST/pricing20041368397Mozilla/5.0 (iPhone; CPU iPhone OS 17_2) Mobile Safari
2026-01-01T00:10:00Z153.181.72.5HEAD/assets/app.js20031793266Googlebot/2.1
2026-01-01T00:10:00Z145.54.77.221GET/compress/20014263879Mozilla/5.0 (iPhone; CPU iPhone OS 17_2) Mobile Safari

Showing the first 6 of 800 rows.

Columns

ColumnTypeDescription
timestampdatetime (ISO 8601)Request time
ipstringClient IPv4 address
methodstringGET, POST, HEAD
pathstringRequested URL path
statusintegerHTTP status (mostly 200, some 3xx/4xx/5xx)
bytesintegerResponse size
response_msintegerServer response time, ms
user_agentstringBrowser or bot UA string

What makes this file useful

  • About 14% of rows are non-200, spread across 301, 304, 404, 403, 500 and 502 — enough of each to chart.
  • 304 responses correctly have bytes = 0, so byte totals are not inflated by cache hits.
  • user_agent includes a Googlebot string and curl, so you can practise separating bots from browsers.

Use cases

  • Break traffic down by status code and find the error rate
  • Rank the most-requested paths
  • Filter out Googlebot / curl to isolate human traffic
  • Look at the response_ms distribution and its slow tail

Open it in a tool

Load this sample — or your own file — into a real tool. Everything runs client-side.

Related guides

More sample datasets

Browse all sample CSV files →

Frequently asked questions

Is this a real access log?

No. IPs, paths and timings are generated. The path list references real site sections for realism only.

Why CSV instead of the raw log format?

Raw Apache/Nginx logs need parsing first. This file is already tabular so you can go straight to analysis — or use it to check your parser output.

How many rows?

800 request rows plus the header.

Turn this into a saved workflow

Create a free account to save the steps from this guide as a reusable workflow and re-run it on any file, from any device.

Sign in for free

Follow HowToCSV on Google

Add us as a preferred source on Google Search so our latest CSV guides and tutorials surface more often in your Top stories.

Add HowToCSV as a preferred source