Skip to main content

Server latency, GPU temperature, this month's power bill.

After your agent ships or a model starts running, the server page logs every machine’s latency and failures, with traffic for bound VPS instances; the hardware page puts CPU and GPU temperature and power in the tray and works out the electricity cost from your rate.

Monitoring in 77Fox is a server page that tracks latency, health and VPS traffic cycles, and a hardware page that shows CPU and GPU temperature, power and energy cost with up to 365 days of history.

Download for Windowsv6.9.2 · 426 MB · Windows 10 / 11 · 64-bitWhat this page covers

Server monitor

Sample data

NetworkUpdated 04:30:00 AM
Domestic exit203.0.113.24Austin · direct
International exit198.51.100.7Frankfurt · via proxy
Local IP192.168.1.24
Latency (HTTP)6 fast · 2 slow · 2 poor
Tencent18msBaidu24msDouyin31msCloudflare86msGoogle142msYouTube168msStripe212msNetflix238msTikTok655msFacebook1180ms
Server monitor5/6 online · Updated 04:30:00 AM · 3 bound
Frankfurt · webhk.example.net
38ms
Tokyo · relaytyo.example.net
72ms
Los Angeles · buildlax.example.net
168ms
United States · Google Public DNS8.8.8.8
38ms
Germany · Frankfurtfra.example.net
118ms
Australia · Telstrasyd.example.net
-1

Real interface, sample data. Click around.

Server monitoring

On Windows desktop, each completed server check adds one cell to the status strip. History retains individual records for the last 30 days, showing exact times, latency and success or failure, with a failures-only filter. Use the wheel, dragging or pinch gestures to move between long-term trends and individual checks; zoomed-out views preserve latency peaks and failures. ICMP loss shows lost checks out of all ICMP checks, while TCP connection failures are counted separately, helping multi-server operators find intermittent faults. Older minute summaries remain available but cannot be reconstructed as individual records.

Ping is off by default when adding a server. Select it and save to enable it; resource monitoring works independently.

Bind VPS traffic with one command

Server monitoring can bind a Linux VPS to your account and track traffic per billing cycle. Binding is light: run a single install command on the target machine, and inbound and outbound traffic accumulates from there without any manual bookkeeping.

This is what stops the classic "throttled at the end of the month before you notice you went over" — usage stays visible instead of arriving with the bill.

Cycles, reset dates and provider calibration

Billing cycles differ per provider, so reset rules are configurable: choose monthly or yearly resets and set the reset month and day. More usefully, calibration lets you align the current cycle to the number shown in your provider's panel when the two drift apart, so later figures track the real bill instead of restarting from zero.

What the status colours mean

Latency colours were redefined to avoid alert fatigue from a wall of red: high latency is orange, and dark red is reserved for genuinely unreachable servers. VPS cards use a denser layout with details and actions moved into hover hints and the context menu, keeping long lists readable. Country flags make regions easy to scan.

Hardware monitoring (Windows desktop)

Hardware monitoring reads your CPU and graphics card temperature and power. It detects Intel and AMD CPUs and NVIDIA, AMD and Intel graphics, integrated or dedicated, and with several GPUs you choose which ones to show. Hover the tray icon and a card lists each device’s short model name, temperature and power; a dashboard widget opens the full monitoring page, where history goes back 365 days.

One-time administrator approval

The first time, hardware monitoring needs one administrator approval: click Authorize hardware monitoring and Windows shows a single UAC prompt. That registers an on-demand helper task for the low-level sensors; 77Fox itself keeps running with normal rights, and no further UAC prompts appear.

Reading low-level CPU sensors needs an officially signed driver. 77Fox verifies the driver’s version, hash and digital signature before enabling it, and once you’ve approved, installed builds take care of this on first launch or after an upgrade.

If low-level sensors can’t be enabled, the app says so plainly and offers Re-detect and repair CPU monitoring. Missing readings show as “—”, never as 0 or an estimate. GPU monitoring is unaffected, and the web console doesn’t run local hardware monitoring.

History and electricity cost

The full page charts temperature, power and energy over 1 hour, 6 hours, 24 hours, 7 days or 30 days, with 60, 90, 180 and 365 days under More. Temperature shows the minimum, average and maximum; energy switches between Wh and kWh automatically; the CPU, each GPU and the total are listed separately. Minute-level data is kept for 30 days and hourly summaries for a year, all stored only on your PC and never synced.

Set your electricity price in any major currency (right-click the cost card) and the energy and cost of the selected range are worked out directly, all the way to 365 days; without a price the cost shows “—”.

Monitors, memory, drives and fans have no power sensor, so you can add them by hand as estimates: monitors from size, resolution, refresh rate and brightness, everything else as quantity × typical wattage. Estimates are kept apart from measured values and drawn as a separate gray dashed line.

77Fox counts the measured energy of your CPU and graphics card, plus any peripherals you add as estimates. It leaves out power supply losses, the motherboard and the like, so it reads lower than a wall-socket meter. Only time when the PC was on and sampling counts; sleep and shutdown aren’t filled in. For an exact figure for the whole PC, check against a plug-in power meter.

Remote control

Two Windows PCs running 77Fox can control each other with a 9-character connection code, once the other person clicks Allow or you enter the password. Connection methods, quality, audio and safety tips are on the remote control page.

Why "refresh on demand" matters

The usual failing of monitoring tools is that they cost more than they save. 77Fox schedules background work centrally, starts heavy services only when needed and loads pages on demand, which keeps idle memory and process counts low. The hardware sampling interval is adjustable too, so the trade-off between immediacy and overhead stays yours.

Blog

Frequently asked questions

What needs installing on the VPS?

A single install command, provided by 77Fox and hosted on its own domain. Once bound, traffic accumulates from inbound and outbound deltas into a cycle total.

What if the traffic total disagrees with my provider panel?

You can calibrate the current cycle against the provider figure so later numbers track the real bill, without resetting to zero. Reset month and day are configurable monthly or yearly.

Why does hardware monitoring ask for administrator approval?

Reading CPU and other low-level sensors goes through a small helper that needs elevated rights. The first time, click Authorize hardware monitoring in Settings and approve one Windows UAC prompt; after that, 77Fox itself keeps running with normal rights. Any driver it uses is checked for an official signature, version and hash before it is enabled.

Can I see hardware monitoring on the web?

No. Local hardware monitoring runs only in the Windows desktop app. Server monitoring is available on both desktop and web.

Is monitoring resource-hungry?

Refreshes happen on demand and tray updates slow themselves down automatically. Background work is centrally scheduled, heavy services start only when needed, idle memory and process counts stay modest, and the refresh interval is adjustable in settings.

Are server monitoring and hardware monitoring the same page?

No, they are two separate pages: server monitoring watches remote nodes for latency, health and cycle traffic, while hardware monitoring watches local CPU and GPU temperature and power. Dashboard widgets can put the key readings from both on one screen.

Give it a try.

Bring your most-used prompts in first, then connect your AI agent.