A Barapullah traffic jam stretching close to two kilometres on the Phase-3 elevated stretch forced Delhi Traffic Police to divert vehicles onto the DND Flyway this week, with officers publicly blaming Google Maps for routing confusion that worsened the gridlock.
Key Takeaways
- The Barapullah Phase-3 corridor saw a jam of roughly 2 km, confirmed by on-ground commuter footage and police traffic advisories.
- Delhi Traffic Police diverted traffic toward the DND Flyway to ease the bottleneck near the Barapullah stretch.
- Police pointed to Google Maps’ routing suggestions as a factor that pushed extra vehicle load onto an already congested corridor.
- The incident went viral on social media within hours, with commuters posting videos and venting about lost time.
What Exactly Happened On The Barapullah Stretch?
Commuters heading toward Sarai Kale Khan and the Ring Road side of South Delhi found themselves stuck for well over an hour. The jam wasn’t a one-lane slowdown — it ran close to two kilometres, swallowing up the Phase-3 flyover approach and spilling onto feeder roads below.
Traffic marshals on duty told local reporters the snarl built up fast, within about 30-40 minutes of the morning rush starting. That’s the part that matters here: this wasn’t a slow-building Monday-morning crawl. It was sudden, and it caught both commuters and the police off guard.
Why Did Police Divert Vehicles To DND?
Once the Phase-3 stretch choked up, the standard playbook kicked in — push traffic to an alternate corridor. DND Flyway, connecting Delhi to Noida, became the fallback route for vehicles that would otherwise have queued through Barapullah.
Three things stack up here, and they’re worth separating:
- A traffic advisory went out asking commuters to use DND as an alternate route.
- Marshals were deployed at key junctions to physically redirect vehicles.
- Police said the diversion was meant to be temporary, pending the jam easing on Barapullah.
None of this is unusual procedure. Delhi’s traffic department has used DND as an overflow valve before, especially when VIP movement or construction work chokes the Ring Road network. What made this instance different was the next step — the public blame placed on a navigation app.
Why Are Police Blaming Google Maps?
This is where the story gets its edge. Officers on the ground said a chunk of the jam built up because Google Maps kept rerouting drivers through the same narrow stretch, rather than spreading the load across available roads. Drivers trusting the app blindly followed its suggested path, deepening the bottleneck instead of avoiding it.
It’s a familiar complaint, not a new one. Traffic police in several Indian cities have flagged similar issues — apps optimising for individual travel time without accounting for what happens when a few thousand drivers get the same suggestion in the same ten-minute window. For context on how such navigation-app congestion patterns have been studied elsewhere, see this report on how cities are managing app-driven congestion, which lays out why bulk rerouting by GPS apps can backfire during peak hours.
Whether Google Maps was the primary cause, or just the tool that revealed a structural bottleneck already baked into Barapullah Phase-3’s design, is something only a formal review will settle. Right now, it’s one side’s version — the police’s — and that’s worth remembering before anyone treats it as the full picture.
Has This Happened Before On Barapullah?
Barapullah Phase-3 isn’t new to congestion complaints. Commuters have flagged bottlenecks near the Sarai Kale Khan merge point for months, particularly during construction-linked lane closures. What’s new is the scale of this particular jam and the public finger-pointing at a navigation platform.
How Did Commuters React?
Social media did what it does — it turned a traffic jam into a trending topic within hours. Videos of bumper-to-bumper vehicles, honking match-ups, and exasperated commuters narrating their commute delays spread across X and Instagram reels through the morning.
| Detail | Reported Figure |
| Jam length | Approx. 2 km |
| Diversion route | DND Flyway |
| Primary cause cited by police | Google Maps routing + existing bottleneck |
| Commuter delay reported | 45-90 minutes, per on-ground accounts |
None of these numbers are official government data — they’re drawn from commuter accounts and local reporting, and should be read as estimates, not verified statistics.
The India Angle: Why This Keeps Happening
Here’s the original point worth making. Delhi isn’t short on elevated corridors built to cut congestion — Barapullah itself was meant to be one of those fixes. But every new flyover phase tends to shift the bottleneck rather than remove it, because the merge points at either end rarely get widened at the same pace as the flyover itself.
Add a navigation app into that mix, one that’s optimising purely for the fastest individual route, and you get a feedback loop: the app sends more cars down the “faster” path, that path chokes, and the app has no real-time signal to course-correct fast enough. It’s less a Google Maps problem and more a classic case of infrastructure lagging behind traffic-app adoption — a pattern several Indian metros are quietly wrestling with as GPS-based routing becomes the default for daily commutes.
FAQ
What caused the Barapullah traffic jam?
Police cite a mix of an existing bottleneck on the Phase-3 stretch and Google Maps routing a surge of vehicles through the same narrow section during peak hours.
Where were vehicles diverted?
Traffic was redirected toward the DND Flyway, the alternate corridor linking Delhi and Noida.
How long did the jam last?
Commuter accounts put the delay between 45 minutes and roughly 90 minutes, though there’s no official police figure confirming an exact duration.
Is this a recurring problem on Barapullah Phase-3?
Yes, commuters have flagged congestion near the Sarai Kale Khan merge for months; this incident stood out mainly for its scale and the public blame directed at a navigation app.
Has Google responded to the police’s claim?
No official statement from Google had surfaced as of this report. That silence itself is notable, and it’s the kind of gap that needs a second source before anyone calls this settled.
Bottom line: a two-kilometre jam, a DND diversion, and a navigation app taking public blame from the police — that’s confirmed. What isn’t confirmed yet is whether Google Maps actually caused it or just exposed a bottleneck Delhi’s traffic planners hadn’t fixed. Until there’s a second, independent account — from Google, from an independent traffic study, or from Delhi’s PWD — that distinction stays open.