ZadeNor AI
Back to Blog
AI

Waymo explains why its robotaxis got stuck during the SF blackout

December 27, 2025
5 min
1,928 views
By ZadeNor AI Team
Waymo explains why its robotaxis got stuck during the SF blackout

Waymo explains why its robotaxis got stuck during the SF blackout

Waymo's Robotaxis Get Stuck During SF Blackout: What Went Wrong and What's Next

In a recent blog post, Waymo explained why its self-driving robotaxis got stuck at intersections during a massive power outage in San Francisco over the weekend. The company's vehicles, which are designed to navigate through complex traffic scenarios, were unable to operate normally due to the widespread outage. This incident highlights the challenges that autonomous technology faces in real-world scenarios and the need for continuous improvement.

The Problem: Confusion Over Dead Stop Lights

Waymo's self-driving system treats dead stop lights as four-way stops, just like humans are supposed to. This should have allowed the robotaxis to operate normally in spite of the massive outage. However, many of the vehicles requested a "confirmation check" from Waymo's fleet response team to make sure what they were doing was correct. This confirmation check system was built "out of an abundance of caution during our early deployment" but has now become a bottleneck in situations like the recent power outage.

The Bottleneck: Confirmation Requests

With a widespread outage on Saturday, there was a "concentrated spike" in these confirmation requests, which helped create all the congestion caught on video. Waymo's fleet response team was overwhelmed with requests, and the company's software was unable to navigate the situation decisively. This highlights the need for Waymo to refine its confirmation request system to match its current scale.

The Solution: Software Update and Improved Emergency Response

Waymo is shipping a software update that will add "even more context about regional outages" to the company's self-driving software. This update will allow the software to navigate more decisively in situations like the recent power outage. Additionally, Waymo is improving its emergency response protocols by incorporating lessons from this event. This includes better communication with its fleet response team and more efficient handling of confirmation requests.

Lessons Learned and Implications

This incident highlights the challenges that autonomous technology faces in real-world scenarios. It also underscores the need for continuous improvement and refinement of autonomous systems. Waymo's response to this incident demonstrates its commitment to safety and its willingness to learn from its mistakes. As autonomous technology continues to evolve, it is essential to address these challenges and improve the reliability and efficiency of self-driving systems.

Forward-Looking Thoughts

The recent power outage in San Francisco serves as a reminder of the importance of robust and reliable autonomous systems. As Waymo continues to refine its technology and improve its emergency response protocols, it is essential to consider the broader implications of autonomous technology on transportation and society. The successful deployment of autonomous systems will require a multidisciplinary approach, involving experts from various fields, including computer science, engineering, and social sciences.

Conclusion

Waymo's robotaxis got stuck during the SF blackout due to a combination of factors, including confusion over dead stop lights and a bottleneck in confirmation requests. However, the company's response to this incident demonstrates its commitment to safety and its willingness to learn from its mistakes. As autonomous technology continues to evolve, it is essential to address these challenges and improve the reliability and efficiency of self-driving systems.


Source: https://techcrunch.com/2025/12/24/waymo-explains-why-its-robotaxis-got-stuck-during-the-sf-blackout/

About the Author

ZadeNor AI Team is a leading expert in AI, contributing to cutting-edge research and development in the field.