How ISP helped a BitTorrent user get faster downloads

In short

A few heavy BitTorrent users degraded internet for a whole town. Instead of blocking anyone, the ISP agreed on a connection limit, and downloads got faster for everyone, including the BitTorrent user.

Situation

During regular traffic analysis, a small regional operator noticed irregular numbers of active connections in one of its regions.

Internet worked for most households, but in one town the radio connection struggled. Customers saw short interruptions, slow domain resolution and a generally worse internet experience.

Irregular number of active connections in one region

Challenge

Technical support often lacks tools to troubleshoot anomalies caused by how customers use the internet. Without easy root cause analysis, it is tempting to leave such problems alone, until they pile up into something serious.

In this case, the cause was a few customers who used BitTorrent heavily.

Solution

The solution had two steps: find the root cause, then mitigate it.

With user-friendly dashboards in FLOWCUTTER, the technician found the IP address behind the anomaly.

Customer IP behind the anomaly in Top Conversations

Its traffic showed heavy torrent use, with most connections on port 6881 over UDP.

BitTorrent user traffic on port 6881 over UDP in FLOWCUTTER

Results

The ISP's support called the customer. Instead of blaming him, they agreed to limit active connections to about 20.

The result was a surprise. It solved the problem and also gave the customer faster downloads, because the freed connections improved bandwidth utilization for the whole town.

Faster downloads after limiting the BitTorrent user's active connections

Resources

Takeaway

With traffic context at hand, the support line became a source of positive change. One friendly call gave the BitTorrent user and the whole town a better internet experience.

Seeing this in your network?

Describe what you see. An engineer replies with clear next steps within one business day.

Talk to an engineer

Real cases. Real networks.

More network problem solved.

DDoS

A distributed DDoS attack slipped past scrubbing. Flow data let the ISP cut each wave down until the attacks finally stopped.

9

DNS & IP reputation

A shared blacklisted IP kept getting flagged while NetFlow looked normal. The cause: botnets on the ISP’s own backbone devices.

9

DDoS

A UK ISP faced 20 DDoS attacks in two days. Flow data showed the vector, and DDoS mitigation via upstream BGP ended the outages.

9