Sample Web Server Log and Telecom Subscriber Data for Testing and Practice
Log analysis and telecom reporting both need lots of rows with timestamps, codes and usage numbers. Generate web server logs and telecom subscribers in your browser, free, with no real traffic or customers.
Two datasets
Web server logs has a timestamp, client IP, HTTP method, request path, status code, response time in milliseconds, bytes sent, browser user agent and log level. Telecom subscribers has a subscriber id, name, phone number, IMEI, mobile plan, monthly data usage in GB, monthly bill, status and activation date.
Realistic proportions
Most requests are GET and most status codes are 200, with a smaller share of 304, 404 and 500, so error-rate calculations have something to find. Log levels are mostly INFO with a few WARN and ERROR rows. Data usage follows a skewed curve, so many subscribers use a few GB and a few use far more, as in real plans. Subscriber status is mostly Active, with some Suspended and Churned.
IMEI numbers have 15 digits and a correct check digit, so they pass an IMEI validator. They are random and do not identify real devices.
Questions to answer with it
For logs, find the error rate and the slowest paths: SELECT path, COUNT(*) AS requests, ROUND(AVG(response_ms)) AS avg_ms, SUM(CASE WHEN status >= 500 THEN 1 ELSE 0 END) AS server_errors FROM server_logs GROUP BY path ORDER BY avg_ms DESC; For subscribers, calculate churn by plan and average data usage per plan. Run both in SQL on Your Files, or load the CSV into any database.
What to use it for
Use the logs to practise log analysis, test a parser or dashboard, and check how your tool handles 100,000 rows. Use the subscribers to build a churn or usage report and test a billing import. Both work as Parquet for a data lake test. To check a file for problems after you load it, run it through the Data Profiler.
What it is not
All rows are random. The IP addresses are not real visitors, the user agents are a handful of common browser strings, and phone numbers and IMEIs do not belong to real subscribers.
Related tool pages
- Fake Data Generator: Generate realistic fake data online: names, emails, addresses, dates and more, up to 500,000 rows, as CSV, JSON, Parquet or Excel. Free.
- Test Data Generator: Generate test data for databases and apps: names, emails, addresses, dates and numbers, up to 500,000 rows, as CSV, JSON, Parquet or Excel. Free.
- Student Data Generator: Fake Student Records: Generate fake student data for class projects: IDs, names, courses, marks and attendance. Download CSV, Excel, JSON or Parquet. Free.
- Student Marks Dataset Generator: Create a student marks dataset by student, subject and exam for SQL, Excel pivot tables and charts. Free, in your browser.
- Sample Data for SQL Practice: Generate sample tables for SQL practice (students, orders, employees), download CSV and query it in your browser. Free.
- Dummy Data for Excel Practice: Generate dummy sales, student or employee data and download Excel to practise filters, pivot tables and VLOOKUP. Free.
Also try
How to use the Data Generator: step by step
- Open the Data Generator and pick Web server logs or Telecom subscribers.
- Choose the number of rows.
- Pick CSV, Excel, JSON or Parquet.
- Download the file and load it into your tool.
When to use the Data Generator
- Practise log analysis in SQL
- Test a log parser or dashboard
- Build a telecom churn report
- Load-test an import with 100,000 rows
Example
Input: Dataset: Customers, 3 rows
Output: id,name,email 1,Maya Patel,maya.patel@example.com 2,Leo Fischer,leo.fischer@example.com
Frequently asked questions
Are these real server logs?
No. They are random rows shaped like web server logs, with weighted methods and status codes. No IP address or request belongs to real traffic.
Is the log in a standard format such as Apache or Nginx?
No. It is a table with one column per field, which you can load as CSV, JSON or Parquet. It is not a raw text log line format.
Do the IMEI numbers pass validation?
Yes. They have 15 digits and a correct Luhn check digit, but they are random and do not match real devices.
Tip: For a log that covers a full week, set the timestamp From and To dates in the generator to that week.