The Network — How a Packet Actually Finds Its Way Home

A Sunday morning in Coimbatore

Priya had been on call for the grocery delivery startup for exactly six weeks when the Sunday morning happened. The team was eight engineers, working out of a small office near the Coimbatore railway station, serving a customer base that had grown from two thousand to forty thousand in a year. Sunday mornings were the busiest hours of the week. Orders started pouring in at seven and did not slow down until lunch.

At eight-fifteen, the support inbox started filling up with complaints from one specific area of the city — a neighbourhood called Saibaba Colony. The app was loading for users there, but the moment they tried to place an order, the screen went blank. Other neighbourhoods were fine. The company's own dashboards showed everything green. The backend was healthy. The mobile app team had not pushed any changes in three days.

Priya spent the next hour doing what any second-year engineer would do. She looked at her code. She looked at the API logs. She looked at the database. She looked at the third-party payment service. Everything was working. The bug was real. The code was fine. By nine-thirty, with the WhatsApp group from the support team getting steadily angrier, she did the thing that she would later describe as the moment her career changed. She stopped looking at her code, and she started looking at the network.

It took her another forty minutes to find it. The DNS server at one specific ISP in Coimbatore had gone bad that morning. For customers whose internet ran through that ISP, the app's API server name was failing to resolve to an actual address. Their phones were trying to send orders to a name that, for them, was pointing nowhere. The bug was not in her code. The bug was not in her company. The bug was in the postal address book of one ISP, three layers removed from anything she could touch.