Throughput, straight from the kernel
Download and upload come from the interface byte counters macOS keeps itself — no polling of other apps, no estimates. A live sparkline in the status bar, the full chart in the dashboard.
Live download and upload speed, the country your traffic actually exits from, and — unusually — the location of every VPN tunnel separately. Split routing is visible at a glance.
macOS 14 or later · Apple silicon · one-time purchase, no subscription
What it does
Everything is read locally and updates the moment it changes — no background service, no calls home, no waiting for a refresh.
Download and upload come from the interface byte counters macOS keeps itself — no polling of other apps, no estimates. A live sparkline in the status bar, the full chart in the dashboard.
utun, WireGuard, IPsec — each active tunnel is geolocated over that interface, not over the default route. Split routing is flagged the moment part of your traffic leaves the country you expect.
Country, city, ISP and ASN, with the flag in the status bar. Recent IP history, and your own labels: tag an exit as Home or Office VPN by country, city, ISP, ASN or IP.
Live up and down per app, session totals, connection counts and remote endpoints. Top five in the popover, a sortable table in the dashboard. It runs on a macOS content-filter extension you add from Settings.
Round-trip time and jitter for hosts you choose, plus an on-demand Cloudflare speed test with configurable duration, parallel streams and a data cap per phase.
Network name, signal, channel, 802.11 standard, security and transmit rate — next to your local IP, MAC address and the DNS servers actually in use.
Cumulative totals for received and sent, with automatic resets — daily, weekly, monthly or never — and a manual reset whenever you want a clean count.
Three key-less providers by default — each editable, switchable or removable. Add your own HTTPS endpoint by URL and JSON key paths, and pick which one is authoritative.
Screen by screen
The dashboard stacks everything that matters into a single scroll: what you are connected through, where it comes out, how fast it is right now, and what a proper test says.
Every app that touches the network is listed live — with connection counts and the endpoints it talks to. It runs on a macOS content-filter system extension, installed from the app's own settings.
Monitoring settings keep the controls together: how data usage resets, whether Wi-Fi details are read, and whether traffic is counted per app.
Show a live sparkline, the two speeds, a compact label — with or without the flag of the country you are exiting from. It is a menu-bar app: no dock icon, no window in the way.
Privacy
Ohayo Network has no account, no sign-in and no backend — everything it shows is measured on your Mac, by your Mac.
Throughput, per-app traffic, Wi-Fi details and your history of exits are computed and kept locally, in your own preferences.
Geolocation, latency probes, the speed test and the map reach only the services you enable, always over HTTPS. Disable one and it is never contacted again.
The content-filter extension allows every flow untouched, never inspects payload, and writes nothing to disk. It only counts bytes per app, in memory.
At a glance
FAQ
No. Without a tunnel you get live speed, your exit IP and region, latency, Wi-Fi details, data usage and the speed test. If you do use one, each active tunnel is geolocated separately — that is what sets it apart from most menu-bar monitors.
Per-app traffic is the only feature that needs it, and it is entirely optional — everything else works without it. It is a macOS content-filter extension: read-only, never blocking, never inspecting payload. You install it yourself, approve it in System Settings, and can uninstall it from the same panel at any time.
No — Ohayo Network is built for Apple silicon and requires macOS 14 Sonoma or later. If you need an Intel build, write to feedback@ohayo.by.
No. It is a one-time purchase on the Mac App Store, and updates to the version you bought arrive the usual way.
No. Speed is read from counters the kernel already maintains, once a second. The content filter allows every flow immediately and only asks the kernel for cumulative byte counts — your traffic never routes through user space.
English and Russian, following your system language. If you need another language, write to feedback@ohayo.by.