Same Call, Different Router: an interactive explainer of a €48,000 sales call on Teams when a digger cuts the office fibre. On an ordinary load-balancing router the customer freezes and the deal slips; with bonding nobody notices. Includes traffic ribbons for the whole office and a calculator for what one line failure costs a year. Made by Munir Kotadia. Full description, screenshots and options: All the work, described.
Anna is closing a €48,000 contract on a Teams call. Her office has fibre, 4G and 5G. Halfway through the customer's sentence, a digger cuts the fibre in the street. Two offices, identical except for the router.
Each ribbon is one person's traffic, and every thin line is a packet that arrived. Holes are time when nothing got through. Anna is on the call, Ben is uploading a 2.4 GB file to Dropbox, Clara is working in Salesforce.
Anna's call goes silent for 9 s. Ben's upload stalls for 5.5 s, then sends part of the file again.
A few voice packets are lost at the moment of the cut, too few to hear. Ben's upload slows down until the fibre is repaired.
Enter your own figures. The example values are placeholders, so replace them with yours.
failures × people × minutes ÷ 60 × hourly cost
With bonding, connections on the lines that are still working carry on, so these interruptions are avoided as long as the remaining lines have enough capacity for the work.
Illustrative simulation. The conversation, timings and packet counts are a representative example, not a measurement. Voice packet counts assume a typical 50 packets a second in each direction. Call uptime is the share of the call so far, about seven minutes, during which audio was getting through. Real behaviour depends on router configuration, carrier conditions and how each application handles a network change. Microsoft Teams, Dropbox, Salesforce, Telekom, Vodafone, O2 and Hansen Logistik are used only to make the example concrete. The cost calculator uses only the figures you enter.