Excessive Network Usage in Rider

Problem

One might notice Rider sends and receives packets over the network. The data activity observed appears to be disproportionately high for an IDE. The total amount might be counted in GB: It might happen user might face the network connection slows down, suspecting it is Rider consuming the bandwidth.

Cause

Most of the network activity in Rider is due to internal communication between its frontend and backend over the local loopback interface (localhost). Such inter-process communication is normal for Rider and does not necessarily indicate external network usage or bandwidth consumption. The total bytes sent and received are expected to grow over time. If there is a huge number of bytes, that means Rider processes interchanged that amount of data during its work. This is perfectly fine and doesn't consume external bandwidth.

If one notices the network connection slowdown and suspects it is a Rider fault, one might verify that. Be aware that external factors—such as operating system or network stack issues, drivers, VPNs, or other processes—may cause apparent slowdowns. While it might coincide with visible Rider network counters in Activity Monitor, Rider is unlikely to be responsible for the external bandwidth slowdown.

Meantime Rider might consume network bandwidth for the following purposes:

• restore NuGet packages;
• install updates;
• use AI Assistant;
• download symbols or tools;

If the issue happens when IDE performs such an operation, the slowdown might be expected depending on machine network setup.

How to verify if Rider consumes the external bandwidth at the moment?

Use tools like nettop or the following console command to verify Rider’s network activity: bash:

lsof -n -i | grep -e LISTEN -e ESTABLISHED | grep -e rider -e dotnet

Powershell:

Get-NetTCPConnection | 
    Where-Object { $_.State -in 'Listen', 'Established' } | 
    Select-Object LocalAddress, LocalPort, RemoteAddress, RemotePort, State, OwningProcess, 
                  @{ Name = "ProcessName"; Expression = { (Get-Process -Id $_.OwningProcess -ErrorAction SilentlyContinue).ProcessName } } | 
    Where-Object { $_.ProcessName -match 'rider|dotnet' }

This should primarily show local (127.0.0.1) connections, guaranteeing no external bandwidth is consumed. If so, investigate the network slowdown without suspecting Rider.