Service statuses — myNetWorking manual

Every service has a status — the result of the last check. You can see it on the right side of the row (or on the tile) as a bold label in the color of the status, and on the left as a colored dot.

Statuses

Status	Color	Meaning
Online	green	the last TCP connection succeeded; the response time in ms is shown next to it
DOWN	red	two connection attempts failed, and the Internet connection was checked and works; an incident is in progress
No network	orange	the connection failed, but the problem is on the side of the network or the device; the service is not blamed
Checking…	teal, animated	a check is in progress, including the outage verification
Paused	gray	Monitoring enabled is turned off
Unknown	gray	there is no result yet

“DOWN” or “No network”?

This is the most important distinction in the app. “DOWN” appears only when the service fails to answer twice in a row and the reference servers confirm that your connection works — before the second attempt and after it.

“No network” means one of these situations on your side:

the device has no Internet or network connection (e.g. airplane mode, an unplugged cable);
the connection is unstable — some reference servers answer and some do not;
30 seconds have not yet passed since the last connection trouble;
a host name that used to resolve has suddenly stopped resolving — DNS is to blame.

With “No network”, the app does not open an incident or turn on the alarm. The Internet check chapter describes the verification process in detail.

New in 1.1.0: the “No network” status now also covers an unstable connection, the 30 seconds after connection trouble, and DNS problems. Previously, it meant only that none of the reference servers had answered.

What happens when the status changes

Change	Log	Incident	Notification and alarm
to “DOWN” (when the service has no ongoing incident)	an outage entry	a new incident	an outage notification (with sound, if turned on) and a repeating alarm, if turned on
“DOWN” → “Online”	an entry with the outage duration	the incident is closed	a recovery notification; the alarm stops
to “No network”	an entry about a network problem, without blaming the service	no new incident	no notification; the repeating alarm stops
to “Paused”	with an ongoing incident: an entry about the pause, with the duration	the ongoing incident is closed	no notification; the alarm stops

An incident closes when the service is “Online” again — even if there was a “No network” period between the outage and the recovery. Pausing the service also closes it; if the service is still down when you turn monitoring back on, a new incident starts. If a service with an ongoing incident gets the “No network” status and then “DOWN” again, it is still the same incident: no new outage entry and no new notification, and an unacknowledged repeating alarm resumes.

Response time and last check

Response time (e.g. 12 ms) is the time it took to establish the TCP connection. For host names, it also includes the DNS lookup. It is shown only with the “Online” status.
Last check shows the date and time of the most recent check, e.g. 9/30/2026 14:32:05.

After a restart

After it starts, the app shows the last saved status of each service until a new check finishes — and the check starts right away. A “Checking…” status that was saved when the app closed changes to “Unknown”.

Tip: the app has no separate indicator for the state of the Internet connection. You see a lost connection as “No network” on services that do not answer, in the log and — if you turn them on — in separate notifications and incidents. The Internet check chapter describes this.