Tesla Robotaxi: 40 Min for 2 Blocks in Houston [2026]

A Tesla Robotaxi trip estimate in downtown Houston quoted about 40 minutes to cover two blocks, according to a Martin Cid Magazine report that traces the claim to Ethan McKanna, the creator of Robotaxi Tracker and a former Tesla employee. He posted the screenshot on October 26, 2026. Gadget Review ran the story under a headline that asked why riders were baffled, and Yahoo Autos, AZ Family and Information Age (ACS) have covered the same episode.

The app itinerary showed a 2:05 p.m. pickup and a 2:48 p.m. drop-off at Houston Police Department headquarters on Travis Street. Instead of heading straight across downtown, the proposed path ran south through Midtown and the Museum District toward the Texas Medical Center, then looped back north. That detour is the whole story, and it lands days after our look at the Tesla Houston Robotaxi expansion.

This analysis separates what the reporting confirms from what it only suggests. Two things stay unproven. Tesla has not explained the routing, and no outlet has measured how riders in general feel. We file the story under hardware because robotaxi service quality depends on the vehicle, its maps and its fleet software working as one system. That framing is ours, and the facts below come from the named outlets.

What Happened With the Tesla Robotaxi in Houston

The Tesla Robotaxi Houston episode started with a single screenshot. McKanna, who runs Robotaxi Tracker, posted an app itinerary for a downtown trip that spans only two blocks. The reporting we reviewed mentions no out-of-range notice. The itinerary simply described a ride that would run for most of an hour.

McKanna summarized the result in a post that read “40 min ride to cross 2 blocks downtown.” Reports then fanned out across trade and local outlets. Gadget Review framed the trip as a puzzle, while Martin Cid Magazine focused on the shape of the service map and the gap where downtown should sit. The reporting we reviewed does not say that anyone actually rode the 43-minute itinerary. It describes the quote shown in the app.

That distinction matters. A quote on screen is a prediction, not a completed trip. It still counts as evidence, because the same software that produced the estimate also decides where a car would drive if a rider tapped confirm. A routing engine that prices a two-block hop at 40 minutes is telling you something about the roads it is willing to use.

The Trip Timeline in Numbers

The itinerary data is short, and every figure below comes from the reported app screen. We list the details side by side so readers can check the arithmetic themselves.

Detail	Reported value
Date of the quoted trip	October 26, 2026
City	Houston, Texas
Straight-line distance	Two blocks downtown
Pickup time in the app	2:05 p.m.
Drop-off time in the app	2:48 p.m.
Destination	Houston Police Department headquarters, Travis Street
Headline estimate	About 40 minutes
Route described	South via Midtown and the Museum District toward the Texas Medical Center, then north

The clock times work out to 43 minutes, so the “about 40 minutes” figure is a fair rounding. At the speed of a slow walk, two downtown blocks would take a pedestrian a few minutes. The gap between that and the quoted drive is what made the screenshot travel.

Why the Route Looks So Strange

A route that heads toward the Texas Medical Center to reach a destination two blocks away looks like a sign that the direct path is closed to the vehicle. Several explanations fit that picture, and the reporting confirms none of them. The service may block certain streets, intersections or turns. The map data may mark parts of downtown as unavailable for driving. Or the geofence may contain an interior boundary that forces cars to leave and re-enter.

The railway crossing theory

McKanna offered one reading. He suggested the service might be steering around downtown railway crossings. Tesla has not confirmed that, and the available reporting treats it as his interpretation. We flag it for what it is, a plausible guess from someone who tracks these fleets closely. If true, it would mean Tesla chose to accept absurd detours rather than let cars cross tracks, which is a safety-first trade that the company could explain in one sentence if it wished.

What the app showed

The coverage describes an itinerary with a pickup time, a drop-off time and a long route, and it mentions no warning attached to it. From a product design view, that is the sharpest problem. A rider who is offered a trip assumes the service can do the job, and only the clock says otherwise. A plain error message would cost Tesla less goodwill than a 43-minute quote for a two-block trip.

Ethan McKanna’s Case Against the Service Area

McKanna has not limited his criticism to one screenshot. In comments reported by Electrek, he called the Houston map “by far the most egregious” example of a “fake” autonomous vehicle service area he has seen. His broader point, as Electrek relays it, is that advertised robotaxi maps often promise more than the cars deliver, because the polygon on the website does not match the places where the app accepts pickups.

Business Insider reported his view on why the zone looks the way it does. McKanna said he understood Tesla drew the area in a starship shape. In the same breath he called the resulting layout “another poor experience point,” as Business Insider quoted him. Electrek’s own headline describes the map as rocket-shaped and partly fake.

He is not an outside agitator hunting for flaws. Martin Cid Magazine reports that McKanna also praised the Houston service, saying “it feels really good in Houston” when it comes to the driving and the waits. That mix matters. The driving itself drew praise while the map and the routing drew the fire, which points the finger at service design, not at the car’s basic ability to drive.

A Second Rider’s 13-Mile Trip: Hy Luu

McKanna’s two-block quote is not the only odd data point. The Next Web and Business Insider both carried the account of Hy Luu, who documented a 13-mile Robotaxi ride in Houston. According to The Next Web, the ride took about 80 minutes once the vehicle arrived, and the vehicle itself needed about 25 minutes to reach him. His usual commute in his own Tesla takes about 45 minutes.

Measure	Robotaxi trip	Own-car commute
Distance	About 13 miles	Same commute
Time in the vehicle	About 80 minutes	About 45 minutes
Wait for the vehicle	About 25 minutes	None
Gap versus own car (ride only)	About 35 minutes longer	Baseline

The 35-minute gap is our arithmetic from the reported figures, not a number any outlet published. Add the 25-minute wait and the Robotaxi option cost this rider roughly an hour more than driving himself, though he gave up the effort of driving. Luu’s account and McKanna’s screenshot share a theme. Both describe trips whose length does not match the map distance.

What Is Confirmed and What Is Not

A story that spreads this fast needs a clean separation of fact and inference. The table below sorts each claim by the strength of its support in the reporting we reviewed.

Claim	Status	Basis
Quote of about 40 minutes for two downtown blocks	Reported	McKanna’s screenshot, carried by multiple outlets
2:05 p.m. pickup and 2:48 p.m. drop-off	Reported	App itinerary as described in coverage
Route south through Midtown and the Museum District	Reported	Description of the app’s proposed path
Hy Luu’s 13-mile ride took about 80 minutes	Reported	Rider account in The Next Web and others
Tesla avoids downtown railway crossings	Unconfirmed	McKanna’s interpretation, no Tesla statement
Riders broadly baffled	Unconfirmed	Individual complaints only, no survey

Two lines in that table deserve emphasis. First, no outlet has quantified rider sentiment, so “baffled” describes a handful of public complaints. Second, Tesla has not publicly explained the routing, which leaves every theory open. We will update this piece if the company responds.

Why Geofences and Routing Matter for Robotaxi Hardware

A robotaxi is not just a car. It is a vehicle, a set of sensors, onboard computing, a map, a dispatch system and a rider app, all tuned together. When the output looks absurd, the cause can sit in any layer. In the Houston case, the evidence points toward the map and dispatch layers, because the car’s driving drew praise while the routes and pickup availability drew complaints.

That reading fits what we have seen in other Tesla coverage. Our piece on whether the Cybercab can truly run unsupervised explains why the label hides a lot of operational detail, including how much human oversight sits behind a driverless ride. Routing restrictions are part of that hidden detail. Operators often keep cars out of tricky areas and let the map absorb the cost.

For buyers of vehicles and for investors, the lesson is that vehicle specs alone do not predict service quality. Two fleets with similar hardware can feel completely different to riders if one maps its city well and the other does not. Readers who follow the hardware side can browse our hardware coverage for the vehicle and chip stories that sit underneath the service.

Market Impact: Trust Is the Real Cost

We found no reporting that ties the Houston episode to ride volumes, revenue or Tesla’s share price, and we will not invent such a link. The likely impact is quieter. Robotaxi demand rests on trust that the service will get you there in reasonable time, and a viral two-block screenshot erodes that trust in a way an ordinary traffic jam does not.

Marketing exposure is the second cost. When a company publishes a large service map, it invites riders and analysts to test the edges. McKanna did exactly that. If testers keep finding pickup pins that the app rejects inside the published boundary, the map itself becomes the story, which is the dynamic Electrek’s headline captured.

We have no evidence of any regulatory action tied to the Houston routing, and we do not suggest one is coming. Still, a gap between advertised coverage and real access is the kind of detail that invites questions from watchers of the sector. Our report on Cybercab deliveries and the NHTSA deadline shows how closely federal timelines already track Tesla’s robotaxi plans.

Competitive Comparison: How Rivals Handle Service Areas

Tesla’s competitors face the same tension between a big map and a usable one. Our comparison of Tesla and Waymo mileage in Austin shows how far apart the two operators were on road experience, and the Houston routing stories add a service-quality angle to that gap.

We do not have a matched Houston benchmark for the rivals, so we avoid ranking them on wait times or trip lengths here. What we can say is that trackers and local reporters now test these services in public, and every operator’s map will face the same scrutiny. A fair test would compare identical origin and destination pairs across services at the same hour, something no outlet has published for Houston.

Ownership and data questions shape the contest too. Our analysis of Waymo’s Ojai vans and the privacy debate shows that competitors carry their own controversies. Houston riders choosing between services weigh convenience, price, wait time and trust, and the two-block story hits the first and last of those.

Historical Context: Marketed Maps Versus Usable Maps

The gap between a published service area and the places a robotaxi really serves is not new. McKanna’s own point, as Electrek relays it, is that advertised autonomous service maps are often partly fake across the industry, because providers publish a polygon that cars do not fully cover. Houston is his worst example, but he places it on a spectrum.

What changed in 2026 is the scale of public tracking. Community tools such as Robotaxi Tracker give any rider a way to log pickup failures, wait times and odd routes, and outlets now pick those logs up within a day or two. A decade ago, a routing quirk like this would have stayed in a few forum threads. Today a screenshot reaches several newsrooms within hours.

The open question for Tesla is how long a gap persists before the company closes it or labels it clearly. Neither the reports nor Tesla’s own announcements give a timeline, so any estimate would be guesswork.

How to Measure Robotaxi Service Quality

The Houston screenshots show why a single headline metric, such as the number of square miles on a map, tells riders little. Three simple measures would say more. We propose them as an analytical frame, not as an industry standard.

Metric	What it captures	Houston signal in the reporting
Pickup acceptance rate	Share of in-map pins the app accepts	McKanna reports mismatches between the shown boundary and accepted pickups
Detour ratio	Quoted drive time against direct distance	Two blocks quoted at about 40 minutes
Wait-to-ride ratio	Time waiting for the car against time riding	About 25 minutes of waiting before an 80-minute ride
Door-to-door time against own car	Total trip versus the rider’s usual commute	About 80 minutes against about 45 minutes

Each of these can be gathered by riders and trackers without any help from the operator. That is the reason a tool like Robotaxi Tracker matters. It turns anecdotes into a log, and a log is harder for a company to dismiss than a single complaint. If a few dozen riders logged the same four numbers every week, Houston would have a public scorecard within a month.

The detour ratio is the sharpest of the four. A trip that needs a long drive to cover a short distance is usually safe from a pure arithmetic standpoint, since the car is not breaking any rule. It fails the rider anyway. The industry has little incentive to publish it, which is why outside testers fill the gap.

What Tesla Could Do Next

The fixes here are mostly software and communication, not new vehicles. We outline the options below as our own suggestions, and Tesla has announced none of them.

Show unavailable zones on the in-app map so riders see the gap before they request a trip.
Block or flag itineraries where the estimated drive time far exceeds the direct distance.
Publish a plain-language note on any areas, such as railway crossings, that the fleet avoids.
Offer a walking or alternative-transport prompt when a short trip would take a long time.

The second item is the cheapest. A single sanity check on trip time against distance would have stopped the downtown screenshot before it reached a rider. It would not fix the underlying map, but it would turn a viral embarrassment into a routine error message.

Five Predictions for Tesla Robotaxi Houston

These are our forecasts based on the reporting, not facts and not statements from Tesla or any named person.

Tesla patches the app first. A warning or a block for absurd itineraries is the lowest-cost response and the most likely first step.
The downtown gap narrows. If a railway or map constraint causes the detour, expect incremental changes that open more downtown streets over the coming months.
Trackers keep testing the edges. Community tools will keep logging pickup failures, so more screenshots will follow.
Service area claims face tougher scrutiny. Reporters will compare published polygons with real pickup coverage for every operator, not only Tesla.
The Cybercab arrives into the same map. Whatever hardware Tesla fields next will inherit this routing and geofence layer, so fixing it matters beyond Houston, as the Miami and Tampa expansion plans suggest.

What Riders Should Check Before Booking

If you ride a robotaxi in Houston or any new market, a few habits protect your time. Look at the estimated arrival and trip duration before you confirm. Compare the duration with the distance, and cancel if the pair looks off. Check whether the pickup pin is accepted, since McKanna’s testing found mismatches between the displayed boundary and available pickups.

Allow extra time for the vehicle to reach you. Luu’s reported 25-minute wait is one rider’s experience, not a rule, yet it shows that arrival time can dominate a trip. For short downtown hops, walking may beat any vehicle. Finally, screenshot the itinerary if it looks wrong, because documented cases are what push operators to respond.

Frequently Asked Questions

How long did the Tesla Robotaxi quote say the two-block trip would take?

The app quoted about 40 minutes. The itinerary ran from a 2:05 p.m. pickup to a 2:48 p.m. drop-off, which is 43 minutes on the clock.

Where did the trip end?

The destination was Houston Police Department headquarters on Travis Street in downtown Houston, according to the reporting.

Who reported it?

Ethan McKanna, the creator of Robotaxi Tracker and a former Tesla employee, posted the screenshot on October 26, 2026. Gadget Review, Martin Cid Magazine, Electrek and others carried it.

Does Tesla avoid railway crossings in downtown Houston?

That is unconfirmed. It was McKanna’s interpretation of the routing, and Tesla has not given an explanation.

What happened on Hy Luu’s ride?

Luu reported a 13-mile ride that took about 80 minutes after the vehicle arrived. The vehicle needed about 25 minutes to reach him, and his usual commute in his own Tesla takes about 45 minutes.

Are Houston riders broadly baffled by the service?

No survey backs that. The reporting confirms individual complaints and unusual routing, but nobody has measured rider reaction across the service.

Did McKanna have anything positive to say?

Yes. Martin Cid Magazine reports he said it feels really good in Houston, praising the driving experience and wait times while criticizing the map and routing.

Has Tesla responded?

The reporting we reviewed contains no Tesla explanation of the routing. We will update this article if the company comments.