Manual · chapter 7 of 10
Internet check
myNetWorking checks your connection for two reasons. First, so that it doesn’t blame a service when it’s you who has lost the Internet. Second — if you want — to notify you separately when the Internet goes down and comes back.
Verification before an alarm
When a service does not answer, the app proceeds as follows:
It asks the reference servers about the state of the connection. If the connection doesn’t work or is unstable, the service gets the “No network” status.
If the connection works, it connects to the service a second time, straight away. If that succeeds — “Online”.
After the second failure, it checks the connection once more, from scratch. If the connection is not fully working, or if there was trouble with it in the last 30 seconds — “No network”.
If a host name that used to resolve did not resolve this time — “No network”, because DNS is to blame.
In all other cases — “DOWN”.
Throughout this time, the service shows the “Checking…” status. A connection refused by a running host gives a result almost immediately. A host that does not answer at all can take up to roughly 20 seconds with the default 5-second timeout.
How the app assesses the connection
The app connects to all the reference servers in parallel. Only servers that have answered at least once since the app started count:
connection works — all such servers answered;
connection unstable — some answered and some did not;
no connection — none of them answered.
When the device has no network connection at all (airplane mode, an unplugged cable), the app knows immediately. Every “unstable” or “no connection” verdict starts a 30-second grace period during which failing services get the “No network” status. A single connection verdict applies to all services for 3 seconds, so services that stop answering at the same time get a consistent result.
New in 1.1.0: agreement between the servers (quorum), a second connection check after the second failed attempt, the 30-second grace period, the DNS rule and immediate recognition of a missing network connection. Version 1.0.0 considered the connection to be working when even one server answered.
You’ll find an example with times on the How it works page.
Reference servers
You can change the list of servers in Settings → Reference servers. By default, it contains three public DNS servers from different operators:
| Server | Operator |
|---|---|
1.1.1.1:53 | Cloudflare |
8.8.8.8:53 | |
9.9.9.9:53 | Quad9 |
The app only establishes a TCP connection with them on port 53 — it does not send DNS queries or any other data. It connects to them only when a service check fails, or regularly while the Internet connection watch is turned on: every 30 seconds, and during an Internet outage every 10 seconds (the default value of the Re-check interval when down setting).
To add a server:
Click Add server.
Enter a host or IP address and a port (the port field is pre-filled with 53).
Click Save.
You remove a server with the trash icon next to it. The last server can’t be removed. Restore defaults immediately restores the three servers from the table, without asking.
Tip: some corporate networks and VPN connections block traffic on port 53 to external servers. In that case, no server answers and every service that fails shows “No network”. Add servers that you know are reachable from your network, and remove the ones that don’t answer. Ideally, use at least two independent servers.
No-Internet notifications
Settings → Internet connection has two switches, both turned off by default:
| Switch | What it does |
|---|---|
| Alert when the Internet is down | a separate notification and log entry when the device loses Internet access — independently of the monitored services |
| Record Internet outages as incidents | every loss of Internet access also goes on the incident list as “No Internet access” |
When either of them is turned on, the app checks the connection every 30 seconds, and during an outage at the interval set in Re-check interval when down (10 seconds by default). Service checks also update the connection state.
When the Internet connection is lost:
the log shows the entry “No Internet access”;
if recording is turned on, a “No Internet access” incident is created;
if alerts are turned on, the notification “📡 No Internet access” appears — always with sound, and once per outage, without repeating.
When the Internet comes back, the incident closes, the log shows the entry “Internet access restored after…” with the length of the outage, and the notification “✅ Internet is back” appears — but only if the no-Internet notification was shown before.
An “unstable connection” verdict counts neither as an outage nor as a recovery. If you turn on a switch during an outage, the app reports the outage right away.
New in 1.1.0: notifications, log entries and incidents about losing the Internet connection.
myNetWorking 1.1.0 · Features added in 1.1.0 are marked in the text.