Questions, answered

It checks your connection every few seconds in three ways: it contacts well-known internet servers, opens a small web page, and looks up a website's name (DNS, the internet's address book). Every outage is saved with its exact start time, how long it lasted, and which part failed. You can then turn that into a report for your internet provider.

If you installed the background version, click the small icon next to the clock (on a Mac, the icon at the top of the screen) and choose “Open dashboard”. If you installed the regular-program version, open the program's window. Typing the address into the browser yourself shows a locked page, because the dashboard needs a key that changes every time the app starts.

Yes. There are builds for Windows, macOS and Linux. The “Start with Windows” option only exists on Windows.

Yes. It's free for personal and commercial use, and the source code is public under the Elastic License 2.0. There's no account and nothing to sign up for.

When checks fail 3 times in a row. With the default 5-second interval, that's about 15 seconds. This keeps a single lost check from counting as an outage. You can change both numbers in Settings → Monitoring.

You're online, but the connection is poor: more than 20% of the data you send gets lost on the way, or replies take longer than half a second (500 ms). Both limits can be changed in Settings → Monitoring.

A full outage means nothing gets through. A DNS problem means the line works but website names can't be looked up, so pages don't open. A website problem means names resolve but pages don't load. The History screen and the report show which one happened, which is useful when your provider says “the line was fine”.

The app also checks your router. If the router answers but the internet doesn't, the diagnosis points to your provider. If the router doesn't answer either, the problem is in your home network: Wi-Fi, cables, or the router itself.

Any router with UPnP turned on (a router feature that lets apps ask it for its status) gives the basics: whether the line is up, its speed and, on most routers, the data counters. If you also save the router's password in Settings → App, the app reads more from the router's own page, such as the noise margin and more reliable data counters. That works on Huawei home gateways (HG630, HG633, HG658, HG659 and DG8045), on routers that offer TR-064 (such as FRITZ!Box and some Zyxel models) and, as a trial, on newer ZTE routers (ZXHN and F6xx). The router card on the Overview says which reading is in use. Router not on the list? Turn on “Read the router's status” in the same place, then use “Help us support your router” to send us a report so we can add it.

Yes. Settings → Check targets has three lists: DNS servers (the internet's address books; 8.8.8.8 and 1.1.1.1 by default), web pages, and names to look up. Each list holds up to 10 entries, and you can test them before saving.

Regular checks are tiny: a connection, an empty web page and a name lookup. Speed tests are different. A test moves as much data as your line can in its time limit, so on a fast connection one test can use hundreds of megabytes. If your data is limited, don't schedule automatic speed tests.

From your router's own traffic counters, so it counts the whole house: every device on your network, downloads plus uploads, from your plan's renewal day. That's the 1st of the month unless you set another day under “Your internet line” in Complaints. Your provider counts on its side, so its meter can differ a little from the app's number. If your router shares no counters, there is no data tracking. On supported routers, saving the router's password in Settings → App can fix that.

As a system notification with a sound on this computer. You can also send them to a Discord or Slack channel with a webhook (a special link that lets an app post messages there), or to Telegram. Set these up in Settings → Alerts and use the test button to make sure they arrive.

Create a bot with @BotFather in Telegram and copy its token. Send your bot any message, then find your chat ID. Paste both into Settings → Alerts and press the test button.

Open Settings → Sound. It shows whether your own sound is in use and how long it is. Files must be MP3 or WAV, up to 30 seconds and 10 MB. “Play like a real alert” plays it exactly as an alert would. If you hear nothing, check that the computer isn't muted.

Windows hides notifications while Do not disturb or Focus is on, and it lets you turn them off per app. Check Settings → System → Notifications in Windows. The outage is still saved in History either way.

In Settings → Notifications, turn on Quiet hours and choose the times and days. You can mute only the sound or hold desktop alerts completely. A window that crosses midnight, like 22:00 to 07:00, counts for the day it starts. Webhook and Telegram messages are still sent, and every alert is still saved.

Yes. Set “Wait before alerting” in Settings → Notifications. Outages shorter than that are saved in History but don't alert you. “Remind while down” repeats the alert every few minutes until the connection comes back.

Click the bell at the top, or open Notifications in the menu. Each alert shows where it was sent and, if something was held back, the reason, such as quiet hours or a channel you turned off. The app keeps the latest 500.

In History, press “Monthly report” and choose “Print or save as PDF”. It lists every outage with its time, duration and cause. For all the detailed numbers, export a spreadsheet file (CSV, opens in Excel) from History for one day, 7 days or 30 days.

90 days. Older log files are deleted automatically. The logs live in the “logs” folder next to the app. To find them, click the small icon next to the clock and choose “Open logs folder”.

Cloudflare's speed test servers by default. You can point it at other servers in Settings → Speed test.

Yes. Set an interval in Settings → Speed test. You can also set a minimum speed. Results are sent to your Discord, Slack or Telegram alerts, and a result below that speed is marked as too slow.

No. There's no account, no tracking and no analytics. The only connections it makes are the checks themselves, speed tests, update checks on GitHub, and the Discord, Slack or Telegram alerts you set up. Reading your router stays on your home network. The Privacy page lists each one.

The app sends nothing. “Help us support your router” only makes a file on this computer that describes how your router answers: its make, model and software version, and which features and pages it offers. Private details are removed first: Wi-Fi names and passwords, serial numbers, MAC addresses, your public IP address, user names, passwords and the names of your devices. You can read all of it, then download it and attach it yourself to an issue on our GitHub page. It reaches us only if you submit that issue, and GitHub issues are public.

No. The dashboard only accepts connections from this computer, and even then it needs the key the app creates each time it starts.

In config.json next to the app. Your webhook URL and Telegram token are saved there as plain text, so don't share that file or that folder. The dashboard never sends them back to the browser.

The app checks GitHub for a new version every 6 hours, or right away when you press “Check for updates”. You can turn the automatic check off in Settings → App. Before installing, it checks that the downloaded file is exactly the one we published (using the release's checksums). Test (pre-release) versions are never offered automatically.

Open an issue on the project's GitHub page. Say what you expected, what happened, and your app version (shown at the bottom of the sidebar). Don't paste your config.json, since it may contain your webhook or token. You can also reach us on WhatsApp, Discord or email from the Contact page.