Connect with us

News

Tesla “whistleblower’s” lawyer opens up about Martin Tripp’s sudden Twitter departure

Published

on

Less than a day after posting images supposedly supporting his case against Tesla, alleged saboteur and self-proclaimed “whistleblower” Martin Tripp has opted to leave Twitter. Tripp’s departure from the social media platform comes amid the aftermath of his posts yesterday, which allegedly depicted flawed battery packs that Tesla installed on some Model 3.

Apart from photos taken inside Gigafactory 1, Tripp also released a list of Model 3 VINs which he claimed were equipped with damaged battery packs. The former employee shared screenshots of emails he sent to Elon Musk about Tesla’s operations as well. These images were quickly picked up by several media outlets.

Unfortunately for Tripp, his account was slapped with a 12-hour suspension by Twitter, due to one of his tweets containing an email address listing Elon Musk’s name. In a statement to Gizmodo, Tripp noted that Twitter warned him that he “may not publish or post other people’s private information without their express authorization and permission.”

Stuart D. Meissner, Tripp’s lawyer in his countersuit against Tesla, also contacted Linette Lopez, one of the reporters who covered the former Tesla employee’s tweets. It was not long before Martin Tripp opted to depart from Twitter completely.

https://twitter.com/StuartMeissner/status/1029905643208101889

In a series of recent tweets, Meissner announced that Tripp decided to take down his Twitter page on his advice. The lawyer also denied reports that Tripp’s Twitter account was suspended earlier today. Meissner maintained that Tripp’s departure from the social media platform was voluntary, so that there will not be any more confusion about his case against Tesla. Furthermore, the lawyer also claimed that a number of his client’s social media pages were hacked.

Advertisement
-

Following are Meissner’s updates explaining why Tripp opted to leave Twitter. 

https://twitter.com/StuartMeissner/status/1030138369840500736

https://twitter.com/StuartMeissner/status/1030139433276846081

https://twitter.com/StuartMeissner/status/1030142208572358657

Martin Tripp, a former Tesla engineer working at Gigafactory 1, was accused by the electric car maker of sabotage last June. A lawsuit filed by the company against Tripp alleged that the former employee hacked into Tesla’s Manufacturing Operating System, sent confidential data to external sources, and misreported to the media. Among Tripp’s contacts in the press was Business Insider reporter Linette Lopez, who, in turn, published a number of articles based on information provided by the former Tesla engineer. Lopez confirmed this when she was featured in a segment at CNBC’s Halftime Report last month.

Interestingly, Lopez’s comment on CNBC was a bit different from Tripp’s statement immediately after he received a lawsuit from Tesla. Tripp claimed to CNN Money that he contacted several media outlets about his allegations against the company, and that he had spoken at length with one of them, but the news outlet was yet to do a story about his revelations. During this time, Lopez had already published articles that included information seemingly provided by Tripp.

Advertisement
-

Tesla, for its part, has denied Tripp’s claims. In response to the release of Model 3 VINs that were allegedly equipped with damaged battery packs, the electric car maker was firm in the notion that the former Tesla engineer’s allegations were false.

“As we’ve said before, these claims are false, and Mr. Tripp does not even have personal knowledge about the safety claims that he is making. No punctured cells have ever been used in any Model 3 vehicles in any way, and all VINs that have been identified have safe batteries. Notably, there have been zero battery safety issues in any Model 3.”

Simon is an experienced automotive reporter with a passion for electric cars and clean energy. Fascinated by the world envisioned by Elon Musk, he hopes to make it to Mars (at least as a tourist) someday. For stories or tips--or even to just say a simple hello--send a message to his email, simon@teslarati.com or his handle on X, @ResidentSponge.

Advertisement
Comments

News

Tesla crosses major Unsupervised Self-Driving milestone

Published

on

Credit: Tesla

Tesla has reached a notable benchmark in its autonomous driving program after its Robotaxi fleet surpassed one million miles of unsupervised operation. The company made the announcement during its Cybercab event in Austin on September 3.

Tesla Vice President of AI Ashok Elluswamy told attendees he was happy to report the fleet had achieved one million miles of unsupervised Robotaxi operation as a testament to safety.

The new total marked a sharp increase from the 380,000 unsupervised miles Tesla disclosed during its second-quarter 2026 earnings update in late July.

In roughly six weeks, the company added about 620,000 miles. That acceleration followed Tesla’s decision to remove in-vehicle safety monitors from most of its operations outside the San Francisco Bay Area.

Credit: Tesla

Tesla first launched Robotaxi service in Austin in June 2025 with safety drivers present. It later began fully unsupervised rides and expanded into Dallas, Houston, Miami, Orlando, and Tampa. The San Francisco Bay Area remains the exception, where a safety monitor still rides in the vehicle under California permitting rules.

The company has not released a city-by-city breakdown of the one million unsupervised miles.

The milestone arrived as Tesla began offering public Cybercab rides in Austin. The purpose-built vehicle has no steering wheel or pedals and is designed only for autonomous ride-hailing. Production versions joined the existing fleet of modified Tesla vehicles already operating in the service.

Advertisement
-

Tesla’s unsupervised mileage is growing at a double-digit weekly rate according to earlier company comments, yet its fleet size remains modest compared with established competitors. Waymo has accumulated more than 200 million fully autonomous rider-only miles. Tesla has described its own unsupervised operations as having recorded zero notable incidents in the period leading up to the July update.

The one-million-mile figure reflects Tesla’s shift from supervised testing to broader driverless service in multiple states. It also highlights the company’s strategy of using both existing Model Y vehicles and the new Cybercab to scale its network.

Credit: Tesla

Whether the rapid recent growth continues will depend on further city expansions, regulatory approvals, and the performance of the purpose-built Cybercab in everyday paid rides. Tesla has not specified how many of the latest miles involved the new vehicle versus the rest of the fleet.

The announcement underscores Tesla’s progress toward a larger robotaxi network while illustrating the remaining gap in total autonomous experience relative to longer-operating rivals.

Continue Reading

News

Tesla Robotaxi will be a 24/7 service: here’s when

Published

on

Credit: @AdanGuajardo/X

Tesla AI lead Ashok Elluswamy said this week that 24-hour Robotaxi service is close. Replying on X to a rider who wanted Cybercab trips all night, he wrote that the capability would arrive “next month or so” once “the next tech to merge on the v15 plan” is ready.

The comment landed on September 4, one day after Tesla opened public Cybercab rides in Austin. It is the clearest near-term timeline yet for overnight unsupervised operation. Tesla’s paid Robotaxi network currently runs from 6 a.m. to 10 p.m. seven days a week across Austin, Dallas, Houston, Miami, Orlando, and Tampa.

That 16-hour window is shorter than the 6 a.m. to 2 a.m. schedule the company used for much of the prior year.

Elluswamy did not name the specific feature or say whether the change would apply first to purpose-built Cybercabs, the existing Model Y fleet, or both. He also offered no city-by-city rollout list. The link to Full Self-Driving v15 is nevertheless significant.

Advertisement
-

Tesla has described v15 as a step-change architecture with seven parallel improvement tracks and roughly ten times more parameters than earlier builds. Early versions of that software already operate on the Robotaxi fleet and contain about 40 percent of the planned gains.

By July 2026, the unsupervised fleet had logged more than 380,000 miles across six cities in two states with what the company called an impeccable safety record and no notable incidents caused by the vehicles themselves. Tesla has repeatedly argued that camera-based end-to-end neural networks, rather than extra sensors, are the core of the solution.

Overnight service would test that claim in lower-light conditions and would also raise vehicle utilization, a key variable for Robotaxi unit economics. The company has already begun using public Superchargers at night and is building dedicated Robotaxi charging sites.

Riders have asked why software must change if the cars already drive in the dark. The practical answer appears to be reliability and scale: Tesla has held back mass expansion until more of the v15 stack is merged, citing the need for higher confidence before putting thousands of unoccupied vehicles on streets around the clock.

If the next module arrives on the timetable Elluswamy sketched, 24-hour service could begin in October 2026 in at least some markets.

That would mark a shift from a daytime-bounded pilot to a service that can run whenever demand exists, including the late-night hours that have so far remained out of reach.

Advertisement
-
Continue Reading

News

Tesla Full Self-Driving will now overtake manual driving to avoid disaster

Published

on

Credit: Tesla

Tesla is beginning to roll out Full Self-Driving Supervised v14.3.9 with a new active safety layer that can take control even when the driver is operating the car manually.

Tesla AI said the software can activate FSD on the driver’s behalf when an imminent collision is detected and Automatic Emergency Braking may not be enough. It may also engage if the system detects heavy distraction or an accidental FSD disengagement.

Advertisement
-

The capability is essentially Automatic Collision Evasion. However, unlike conventional AEB, which mainly applies the brakes in a straight line, this feature can use steering, braking, and acceleration together if the car calculates that stopping alone will not prevent impact and a safer path exists. The system may change lanes or move toward a shoulder when conditions allow, then continue driving after the immediate threat is handled rather than simply coming to a stop.

The intervention is meant as a last-resort safety net, not a replacement for attentive driving.

Tesla Full Self-Driving v14.3.7 early review: FSD saved me from an accident

Tesla’s own description still frames FSD as supervised assistance. Secondary reports on internal release notes say the feature can fire while the car is being driven manually if cabin-camera monitoring suggests the driver is not sufficiently attentive, such as reaching toward the back seat, or if FSD appears to have been turned off unintentionally.

After the emergency maneuver, the car is expected to alert the driver and request a return to manual control.

The safety case is straightforward. Many collisions happen in the last second because a driver is looking away, fumbles a control, or faces an obstacle that braking cannot fully solve. A system that can both recognize that AEB is insufficient and execute a coordinated evasive path can reduce those remaining high-severity events.

Advertisement
-

Re-engaging after accidental disengagement also addresses a practical failure mode: a small steering nudge that drops FSD at the worst moment. The advantage is a background safety net that uses the same vision stack already running in v14, instead of leaving the car solely to emergency braking once the driver is no longer in command.

The feature still depends on FSD being enabled and, according to reports, an active FSD purchase or subscription. It does not make the vehicle unsupervised. Drivers remain responsible, and Tesla has not published how often the system is expected to intervene or how it will handle false positives.

If the rollout is conservative and the false-alarm rate stays low, the update is a meaningful step: FSD is no longer only a feature the driver turns on. In the rare moments when disaster is already forming, it can step in.

Continue Reading