[ad_1]
\n<\/p>\n
Waymo is now available<\/a> for anyone in San Francisco to fire up the app and hail a robotaxi. The Alphabet-owned company has had government approval to operate paid driverless cars<\/a> in the city since last August but had been working its way through a waitlist in the months since. Following Cruise\u2019s unceremonious exit from California<\/a> (after dragging a pedestrian 20 feet<\/a> and concealing evidence from regulators<\/a>), Waymo is now the only company with autonomous commercial cars in the state.<\/p>\n Waymo says its cars have logged over 3.8 million driverless miles in San Francisco, and the company claims its vehicles tally \u201ctens of thousands of weekly trips\u201d there. The San Francisco Chronicle<\/em> reports<\/a> that Waymo\u2019s fleet in the city has about 300 cars, up from around 250 in January. However, despite the wider availability, it reportedly doesn\u2019t plan to aggressively expand its San Francisco lineup in the near future.<\/p>\n San Francisco is Waymo\u2019s second city to offer rides to the general public, following Phoenix. The service was exclusive to Waymo One members (and their invitees) starting in 2020<\/a>, and expanded to anyone in the city<\/a> two years later.<\/p>\n Cruise may have flamed out spectacularly<\/a>, but Waymo hasn’t been without its own troubles. Earlier this month, it pushed a software update for its fleet after one of its driverless cars hit a telephone pole in Phoenix<\/a>. That followed a bizarre incident earlier this year when two Waymo robotaxis \u201cmade contact\u201d with the same backward-facing pickup truck<\/a> being towed. The company later said its software had incorrectly predicted the truck\u2019s movements due to a \u201cpersistent orientation mismatch\u201d between the towed vehicle and the one pulling it.<\/p>\n If you\u2019re in San Francisco (or Phoenix), you can book a Waymo ride through the iOS<\/a> or Android<\/a> app.<\/p>\n<\/div>\n