How to Prove Your Internet Connection is Slow and Avoid Arguments with Your ISP

By /

Listen to this Post

When dealing with a slow internet connection, standard speed tests may not capture intermittent issues. To effectively document and report problems to your ISP, follow these steps to create a detailed connection log.

Step-by-Step Guide to Log Connection Issues

1️⃣ Open Command Prompt (CMD)

  • Windows: Press Win + R, type cmd, and hit Enter.
  • Linux/macOS: Open Terminal.

2️⃣ Log the Current Date

[cmd]
date /t >> connection_log.txt
[/cmd]

**Linux/macOS:**

date >> connection_log.txt

#### **3️⃣ Log the Current Time**

time /t >> connection_log.txt

**Linux/macOS:**

date +%T >> connection_log.txt

#### **4️⃣ Run a Continuous Ping Test**

ping -t 8.8.8.8 >> connection_log.txt

**Linux/macOS:**

ping 8.8.8.8 >> connection_log.txt

– Press Ctrl + C to stop after several minutes.

#### **5️⃣ Perform a Traceroute**

tracert 8.8.8.8 >> connection_log.txt

**Linux/macOS:**

traceroute 8.8.8.8 >> connection_log.txt

#### **6️⃣ Check Packet Loss with MTR (Linux/macOS)**

mtr -rw 8.8.8.8 >> connection_log.txt

#### **7️⃣ Analyze Traffic with Wireshark (Optional)**

  • Capture network traffic for deeper analysis.

#### **8️⃣ Send the Log to Your ISP**

  • Attach `connection_log.txt` to your support ticket.

### **You Should Know: Advanced Network Diagnostics**

#### **🔹 Check Latency with `tcping` (Windows)**

tcping -t 8.8.8.8 80 >> connection_log.txt

#### **🔹 Test DNS Resolution**

nslookup google.com >> connection_log.txt

**Linux/macOS:**

dig google.com >> connection_log.txt

#### **🔹 Monitor Bandwidth Usage**

**Windows:**

netstat -e 60 >> bandwidth_log.txt

**Linux:**

iftop -i eth0

#### **🔹 Check for ISP Throttling**

speedtest-cli --simple >> speedtest_log.txt

#### **🔹 Analyze Jitter (Linux)**

ping -c 100 8.8.8.8 | awk -F'=' '/rtt/ {print $2}' | cut -d'/' -f4

### **What Undercode Say**

A slow internet connection can stem from various issues—ISP throttling, network congestion, or faulty hardware. Using ping, traceroute, and `MTR` helps pinpoint the problem. For deeper insights, tools like Wireshark and iftop provide real-time traffic analysis.

#### **Expected Output:**

A structured log file (`connection_log.txt`) containing:

  • Timestamp
  • Ping statistics (latency, packet loss)
  • Traceroute hops
  • DNS resolution results
  • Bandwidth usage

By providing this data, you force your ISP to address the issue objectively. 🚀

**URLs for Reference:**

References:

Reported By: Leandro M – Hackers Feeds
Extra Hub: Undercode MoN
Basic Verification: Pass ✅

Join Our Cyber World:

💬 Whatsapp | 💬 TelegramFeatured Image

Related Posts: