What it does

myNetWorking features

myNetWorking checks whether services on your network and on the Internet accept connections: servers, routers, NAS devices, printers and websites. Below is the full list of features in version 1.1.0; what was added in version 1.1.0 is marked in each group.

Monitoring

  • Any TCP service. A service is a host — a name, an IPv4 or an IPv6 address — and a port from 1 to 65535. The app checks whether the port accepts a TCP connection, so it works with any service that listens on a port.

  • Web addresses. You can paste an address that starts with http:// or https://. The app takes the host name from it, and you enter the port separately, e.g. 443.

  • Response time. With the “Online” status you can see how many milliseconds it took to establish the connection. For host names, this time also includes the DNS lookup.

  • A check interval for each service. Every 30 seconds by default, and no more often than every 5 seconds. When a service is not working, it is checked more often — every 10 seconds by default. The connection timeout is 5 seconds by default (from 1 to 60).

  • Checked right away. After you save a service, the app checks it immediately, without waiting for the next cycle.

  • Pausing. When you turn off the Monitoring enabled switch, the service shows “Paused” and is not checked.

  • The name is optional. A service without a name is shown by its address, e.g. 192.168.1.1:80.

New in 1.1.0: pasting http(s):// addresses, validation of host names and IPv4/IPv6 addresses with clear messages, and the optional service name.

What the app does not do: it does not use ping (ICMP) or UDP, does not check page content, HTTP status codes or TLS certificates, does not draw charts and does not send alerts by email, SMS or webhooks. The service list cannot be imported or exported.

Reliable outage verification

A failed connection does not mean the service is down yet. Before myNetWorking shows the “DOWN” status, it checks whether the problem lies with your own connection.

  • Two attempts. A service that does not answer is checked a second time right away.

  • Reference servers. The app connects in parallel to independent servers — by default 1.1.1.1:53 (Cloudflare), 8.8.8.8:53 (Google) and 9.9.9.9:53 (Quad9). This is only a TCP connection attempt, with no DNS queries. You can change the list in the settings.

  • The servers must agree. When some reference servers answer and others do not, the connection is treated as unstable and no service is blamed for an outage.

  • A second connection check. The connection is checked again after the second failed attempt too, not just before it.

  • A 30-second grace period. For 30 seconds after any connection trouble, failing services show “No network” instead of “DOWN”.

  • Airplane mode and unplugged cables. When the device has no active network connection at all, the app knows immediately, without waiting for timeouts.

  • DNS is a network matter. When a host name that used to resolve suddenly stops resolving, the problem lies with DNS, not with the monitored service.

  • Only proven servers count. A reference server that has never answered is not taken into account, so a single blocked server does not skew the verdict.

New in 1.1.0: agreement between the reference servers, the second connection check, the 30-second grace period, detection of a missing network connection and the DNS rule. Version 1.0.0 considered the Internet to be working when even one server answered — on unstable Wi-Fi, that led to false alarms.

For details and a step-by-step example, see How it works.

Alerts and notifications

  • Outage and recovery notifications. When a service goes down, a system notification appears, and when it comes back, a second one tells you the connection has been restored.

  • Sound. You set the Play sound switch separately for each service.

  • An alarm until acknowledged. With Repeat alarm until acknowledged turned on, the notification comes back every 60 seconds (or at an interval you set, no shorter than 5 seconds) until you click the crossed-out bell, Acknowledge alarm. The alarm also goes quiet on its own when the service is back up, and it resumes if the app is restarted during an outage.

  • No-Internet notification. Optional and independent of the services: a separate message when the device loses Internet access, and another when it gets it back.

  • Linux: outage notifications have the highest priority, so in GNOME and KDE they usually stay on screen until you dismiss them. Clicking a notification brings the app window to the front.

  • Windows: an outage notification plays the Windows reminder sound, which stands out from ordinary notifications. Clicking a notification brings the app window back, even from the system tray.

System notifications work on macOS, Windows, Linux, iPhone, iPad and Android. They are generated on your device, with no intermediary server.

New in 1.1.0: system notifications on Windows and Linux, and a separate notification when the device loses Internet access.

Incidents

  • Every outage is an incident with a start, an end and a duration, e.g. 1h 12m 5s. An incident in progress is marked “ongoing”.

  • An incident closes by itself when the service is “Online” again — even if “No network” appeared in between.

  • “Current” and “Archive” tabs. You move finished incidents to the archive and restore them from it.

  • Acknowledging incidents. The Acknowledge incident command in the incident menu marks it as reviewed. You can see this from the badge next to the incident and in the CSV export.

  • Deleting single incidents, with confirmation. Clear incidents removes the finished incidents from the open tab.

  • Internet outages as incidents — optional, under the name “No Internet access”.

  • The history covers up to the last 300 incidents.

New in 1.1.0: the incident archive, acknowledging incidents, deleting single incidents and no-Internet incidents. “Clear incidents” now clears only the open tab.

Event log and CSV export

  • An event log on the Logs tab: service outages and recoveries, changes to “No network”, loss and return of the Internet, and every start of monitoring — newest first.

  • The log in your language. Entries are translated when they are displayed, so after you change the app language, older entries change language too.

  • Up to 500 entries. The oldest ones are removed automatically.

  • CSV export of the log and the incident history with the Export to CSV button. The file uses a semicolon as the separator, UTF-8 encoding with a BOM and dates in the format 2026-09-30 14:32:05, so Excel with Polish regional settings opens it straight into columns, and LibreOffice and Numbers detect the separator automatically.

New in 1.1.0: exporting the log and the incident history to a CSV file.

Views and ordering

  • List or icons. The List / Icons switch in the Services toolbar. Tiles come in three sizes: Small, Medium and Large.

  • Sorting: Manual order, Name or Last incident, ascending or descending. When you sort by last incident, services that have not had one yet always come last.

  • Dragging. In manual order, you drag the ⋮⋮ handle in the list, or drag a tile onto another tile in the icons view. On a touch screen, touch and hold a tile, then drag it.

  • Remembered layout. The view, icon size and sorting stay the same after a restart.

  • Comfortable on a big screen. From a window width of 720 pixels, navigation moves to a sidebar, and from 1100 pixels the labels sit next to the icons. The window has a minimum size of 560 × 480 pixels.

New in 1.1.0: the icons view, sorting, dragging, the navigation sidebar, the Add service button in the toolbar and the minimum window size.

Running in the background on every platform

PlatformAfter you close the windowLaunch at startupGood to know
macOSthe window hides, the icon stays in the menu barfrom macOS 13to quit: the icon menu or ⌘Q
Windowsthe window hides in the system trayyesonly one copy of the app runs at a time
Linuxthe window is minimizedyesto quit: Settings or Ctrl+Q
Androidmonitoring continues in the background–permanent notification; after restarting the phone, open the app
iPhone, iPadfull monitoring only while the app is open–in the background, checks roughly every 15 minutes, not guaranteed

New in 1.1.0: launch at startup on macOS 13+, Windows and Linux, a single copy of the app on Windows, and on Android a special-use foreground service — without the 6-hour daily limit that Android 15 places on data sync services.

More in the Running in the background chapter.

Languages and appearance

  • Four languages: Polish, English, German and Spanish. The app uses the system language, and when the system uses a different language, English. You change the language in Settings → General → Language.

  • Light and dark appearance that follows the system setting, with no separate switch in the app. On desktop computers, scrollbars are always visible.

Privacy

  • No account, sign-in, ads, analytics, telemetry or crash reports.

  • The service list, settings, incidents and log stay on your device.

  • The app connects only to the services you add and to the reference servers. Versions downloaded from this site contact nci.pl only when you click Check for updates.

The details are in the privacy policy.

Platforms and requirements

PlatformWhere to get itMinimum systemNotes
macOSMac App Store or a .dmg file from this sitemacOS 12.0menu bar icon; launch at startup from macOS 13
WindowsMicrosoft StoreWindows 10 (1809)x64 and ARM64
Ubuntu, Debian.deb package from this siteUbuntu 22.04 / Debian 12x64 and ARM64
Fedora.rpm package from this siteFedora 40x64 and ARM64
iPhone, iPadApp StoreiOS and iPadOS 15.0only periodic checks in the background
AndroidGoogle PlayAndroid 7.0foreground service with a permanent notification

Store versions are updated by the store, and the files from this site have a Check for updates button in the app. You can check current availability on the Installation page.