DU Meter measures network traffic that crosses selected adapters on one Windows computer. It shows current transfer rates and stores traffic totals. Reports and alerts use those totals. DU Meter observes bytes at the IP layer.
The real-time graph answers what the computer sends or receives now. Reports answer how much DU Meter accumulated over a longer period. A monthly-limit setting compares that history with an allowance that the user enters; it cannot read the provider’s billing plan automatically.
The adapter list defines the measurement boundary
A computer can have physical Ethernet or Wi-Fi adapters alongside VPN and other virtual interfaces. DU Meter counts traffic on the adapters selected for monitoring. Choosing the wrong adapter can omit the connection that matters.
A VPN can expose the same transfer on its virtual interface after the physical adapter carries the encrypted packets. DU Meter counts the transfer twice when both interfaces remain selected. A total that suddenly doubles after VPN setup may describe overlapping observation points rather than twice as much Internet use.
DU Meter counts IP headers and data above them while excluding lower-level link data. This technical boundary also prevents exact comparison with a counter taken elsewhere on the route.
The provider and the computer see different packets
An Internet provider can count inbound packets before a router or local firewall drops them. DU Meter never sees packets that fail to reach the monitored computer. In the other direction, DU Meter can count local broadcast traffic or communication with another machine on the LAN even though that traffic never reaches the provider.
Lost or discarded packets create another difference between the two locations. The totals can remain useful for trends and limits without matching the provider to the last byte.
A monthly limit needs the real billing date
The monthly transfer limit asks for an allowance and the billing-cycle start date. Separate warning thresholds control when DU Meter sends a notice. DU Meter then compares accumulated traffic with those values and can notify the user at the selected points.
A calendar-month start entered for an account that renews mid-month divides traffic into the wrong periods. The graph can look accurate while the allowance comparison answers a different question. The limit also remains a local alert; reaching it does not ask the provider to stop service or prevent another transfer.
A moving graph does not prove that reports are recording
DU Meter can suspend report accumulation separately from the live traffic display. A red dot in the taskbar icon identifies that state. Current traffic may continue moving across the graph while historical totals remain unchanged.
This separation helps when the user intentionally excludes a session from reports, but it can also create a gap that becomes visible only later. Checking the icon matters before a measurement period begins. Resuming reports starts accumulation again. The suspended period remains a gap in the stored totals.
