🇸🇦 اقرأ بالعربية

Internet Monitor is a free, open-source tool that captures proof of every internet drop — so you can stop arguing from memory and start attaching evidence to your support ticket.

It logs each outage with per-layer detail (TCP / HTTP / DNS) — so you can prove things like "DNS failed while the link was up" — with exact timestamps and durations, and exports a clean monthly report (PDF) or CSV you can hand to your provider. 100% local: no account, no cloud, no telemetry.

It's also an excellent everyday connectivity monitor — live dashboard, latency/jitter trends, speed tests, and Discord/Slack/Telegram alerts.

Most "my internet is down" complaints fail because you have no proof — no timestamps, no causes, no durations. Internet Monitor produces that evidence:

• Per-layer logging (TCP / HTTP / DNS) — prove which layer failed, not just "it was slow". (e.g. "DNS resolution failed while the link itself was reachable.")
• Exact timestamps + durations for every disconnection, plus monthly availability %.
• Exportable evidence — one-click monthly outage report (PDF) and JSONL / CSV you can attach to a ticket.
• LAN-vs-ISP diagnosis (optional ICMP) — distinguish "my router is down" from "my ISP is down".

1. Run it in the background (system tray or standalone window) — it checks every few seconds, 24/7.
2. Let it capture the drops — each outage is logged with its cause (TCP/HTTP/DNS), exact start time and duration.
3. Generate the monthly report — open the dashboard → Logs → Monthly report (PDF), pick the month, then Print / Save as PDF.
4. Attach it to your ticket/complaint. The report is neutral by default (reads as your own document); an opt-in "shareable" toggle can add a small footer if you want.

Tip: enable scheduled speed tests and ICMP/LAN-vs-ISP diagnosis to back your case with latency, jitter, and throughput history.

Windows SmartScreen warning? Click "More info" → "Run anyway". The binary is unsigned — the source code is fully auditable above.

Download the latest pre-built binary from Releases:

Windows — run once, then right-click the tray icon → Open Dashboard:

internet-monitor-windows.exe

Windows — install to run automatically at startup:

scripts\install.cmd

macOS / Linux:

chmod +x internet-monitor-*
./internet-monitor-macos-arm64

Open the dashboard at http://localhost:8765

git clone https://github.com/FutureSolutionDev/internet-monitor.git
cd internet-monitor
go mod tidy
go run .

# Install air
go install github.com/air-verse/air@latest

# Run with live reload
air

Air watches .go, .html, .js, and .css files and rebuilds automatically.

Open the dashboard at http://localhost:8765 — edit any source file and the binary reloads.

The native window (GUI) version requires GCC — see Build from Source below.

git clone https://github.com/FutureSolutionDev/internet-monitor.git
cd internet-monitor
go mod tidy
CGO_ENABLED=0 go build -ldflags="-H=windowsgui -s -w" -o internet-monitor.exe .

Windows — auto-installs TDM-GCC if missing:

scripts\build-gui.cmd

macOS / Linux — GCC is pre-installed:

go build -ldflags="-s -w" -o internet-monitor-gui ./cmd/gui/

scripts\build.cmd        Build tray exe
scripts\build-gui.cmd    Build native window (auto-installs GCC if missing)
scripts\build-debug.cmd  Build with visible console (debugging)
scripts\run.cmd          Build and run (tray)
scripts\run-gui.cmd      Build and run (native window — requires GCC)
scripts\stop.cmd         Stop running instance
scripts\install.cmd      Install to Windows Startup
scripts\uninstall.cmd    Remove from Startup
scripts\logs.cmd         Open logs folder

Every push to master triggers automatic builds for all platforms:

Windows Tray  →  cross-compiled on Linux (CGO disabled)
Windows GUI   →  windows-latest runner
macOS         →  macos-latest (arm64 native + intel cross-compile)
Linux         →  ubuntu-22.04 (WebKitGTK 4.0)

config.json is created automatically on first run with sensible defaults. Edit it directly or use the Settings tab in the dashboard.

{
  "check_interval_sec": 5,
  "ping_targets":  ["8.8.8.8:53", "1.1.1.1:53"],
  "http_targets":  ["https://connectivitycheck.gstatic.com/generate_204"],
  "dns_targets":   ["www.google.com", "www.cloudflare.com"],
  "fail_threshold": 3,
  "packet_loss_threshold": 20.0,
  "latency_threshold_ms": 500,
  "log_dir": "logs",
  "webhook_url": "",
  "dashboard_port": 8765,
  "speed_test": {
    "download_targets": ["https://speed.cloudflare.com/__down"],
    "parallel_connections": 4,
    "timeout_seconds": 30,
    "upload_target": "https://speed.cloudflare.com/__up",
    "schedule_minutes": 0,
    "alert_threshold_mbps": 0
  }
}

Internet Monitor sends webhook notifications for three event types:

{
  "username": "Internet Monitor",
  "embeds": [{
    "title": "❌ Internet Disconnected",
    "color": 16007988,
    "fields": [
      {"name": "🔌 TCP Ping",    "value": "❌ Failed", "inline": true},
      {"name": "🌐 HTTP",        "value": "❌ Failed", "inline": true},
      {"name": "🔍 DNS",         "value": "✅ OK",     "inline": true},
      {"name": "📉 Packet Loss", "value": "85.0%",    "inline": true},
      {"name": "⏱️ Duration",    "value": "2m 15s",   "inline": true}
    ],
    "timestamp": "2026-05-11T14:30:00Z"
  }]
}

{
  "username": "Internet Monitor",
  "embeds": [{
    "title": "🚀 Speed Test Completed",
    "color": 2278718,
    "fields": [
      {"name": "📥 Download", "value": "94.3 Mbps", "inline": true},
      {"name": "⏱️ Duration", "value": "10.0s",     "inline": true},
      {"name": "📡 Latency",  "value": "12ms",       "inline": true}
    ]
  }]
}

The built-in speed test uses an adaptive HTTP download + upload approach, shown live on a speedtest.net-style circular gauge:

• Measures ping, then download, then upload — the gauge animates through each phase
• Starts with small payloads and increases chunk size over the configured duration
• Opens multiple parallel connections (default: 4) to saturate modern high-speed links
• Uses Cloudflare's speed endpoint (speed.cloudflare.com) by default — no account required
• Optional scheduled automatic tests (speed_test.schedule_minutes) build a throughput history unattended
• Results are stored in logs/speedtest_DATE.jsonl (separate from connectivity logs)
• History is viewable and exportable as CSV directly from the dashboard

Privacy: speed test payloads contain no device identifiers. Traffic goes only to the endpoint you configure in Settings → Speed Test.

internet-monitor/
├── main.go                   Entry point — Tray version
├── singleton_*.go            Single-instance guard (per OS)
├── cmd/gui/                  Native window version
│   ├── main.go
│   ├── gui_notifier.go       GUI-specific Notifier implementation
│   ├── tray_windows.go       Background systray in GUI mode
│   └── notify_*.go           OS notifications (Windows / Unix)
├── core/                     Shared monitoring engine
│   ├── engine.go             Engine struct + Notifier interface + MultiNotifier
│   └── doc.go
├── types/                    Shared data types (CheckResult, Status, Event)
├── speedtest/                Adaptive download speed test engine
├── config/                   Config struct, loading, migration
├── monitor/                  Check engine — TCP / HTTP / DNS
├── dashboard/                HTTP server, SSE stream, REST APIs, embedded assets
│   ├── server.go
│   ├── notifier.go           DashNotifier (core.Notifier implementation)
│   └── assets/               Embedded HTML / CSS / JS (Chart.js local)
├── logger/                   JSONL logging + Discord/Slack webhook formatting
├── tray/                     System tray icon, menu, OS notifications
│   └── notifier.go           TrayNotifier (core.Notifier implementation)
├── updater/                  GitHub Releases API + minio/selfupdate
├── startup/                  OS startup registration
├── .github/workflows/        build.yml — CI/CD for all platforms
└── scripts/                  Windows build / install / run helpers

logs/
  connectivity_2026-05-11.jsonl   Connectivity events (one JSON per line)
  speedtest_2026-05-11.jsonl      Speed test results (one JSON per line)
  app.log                          App errors and webhook status

Connectivity event:

{
  "timestamp": "2026-05-11T14:30:00Z",
  "event": "disconnected",
  "duration_seconds": 45.2,
  "reason": {
    "tcp_ping_failed": true,
    "http_failed": true,
    "dns_failed": false,
    "packet_loss_pct": 80.0,
    "avg_latency_ms": 0
  }
}

Speed test result:

{
  "timestamp": "2026-05-11T14:35:00Z",
  "event": "speed_test",
  "download_mbps": 94.3,
  "upload_mbps": 18.7,
  "latency_ms": 12,
  "duration_seconds": 9.8,
  "endpoints": ["https://speed.cloudflare.com/__down"],
  "parallel_connections": 4,
  "triggered_by": "user"
}

All contributions are welcome — bugs, features, translations, documentation.

git clone https://github.com/YOUR_USERNAME/internet-monitor.git
cd internet-monitor
go mod tidy

git checkout -b feature/your-feature-name

We use Conventional Commits — commit type drives auto-versioning:

• Describe the motivation clearly
• Attach a screenshot for any visual change
• Confirm go build ./... passes

• Windows ARM64 build support
• Mobile-responsive dashboard improvements
• macOS native menu bar integration
• Per-target latency history charts
• Additional language support

MIT — Free for personal and commercial use.

Built with ❤️ by FutureSolutionDev