Story perspectives

Google Maps Blamed as Delhi Barapullah Phase III Jam Hits

By Drooid · Oct 7, 2026, 7:02 PM UTC · How we work

Center

Google Maps Blamed

On Monday, 5 October 2026, traffic on Delhi’s newly opened Barapullah Phase-III flyover formed a multi-kilometre jam.
Delhi Traffic Police later replaced its lane-merge warning with an alert that blamed Google Maps for the congestion.
Officials cited a bottleneck at the old Barapullah flyover as a cause.
They also noted Google Maps failed to display real-time traffic, worsening the jam.

Right

Flyover Design Fault

A multi-kilometre traffic jam formed on Delhi’s newly opened Barapullah Phase-III flyover on Monday, October 5, 2026.
BJP minister Parvesh Verma blamed the AAP-designed flyover for the congestion and said inaccurate Google Maps traffic data amplified the jam.
Delhi Traffic Police said merging two three-lane sections into one near Sundial Park caused the jam.
Authorities diverted traffic to NH-24 and the DND Flyway and deployed personnel to regulate flow.

History

Historical Context

After buying ZipDash in 2004, Google embedded its real-time traffic analysis into Maps in 2007, using anonymous mobile-phone locations to color-code congestion. The system, later relied on by commuters in Delhi, became a focal point of the October 5 2026 Barapullah Phase-III flyover jam, which Delhi Traffic Police and BJP minister Parvesh Verma blamed on Google Maps guidance. The episode highlights the need for coordinated traffic-management policies.

1 of 3

Google Maps Blamed

On Monday, 5 October 2026, traffic on Delhi’s newly opened Barapullah Phase-III flyover formed a multi-kilometre jam.
Delhi Traffic Police later replaced its lane-merge warning with an alert that blamed Google Maps for the congestion.
Officials cited a bottleneck at the old Barapullah flyover as a cause.
They also noted Google Maps failed to display real-time traffic, worsening the jam.

1 / 3