Robo Tracker currently shows Waymo at 1,108 mi² across seven qualifying cities, with city-level entries of Phoenix 302, San Francisco Bay Area 278, Miami 154, Austin 133, Los Angeles 122, Atlanta 61, and Orlando 58. The same page also says the leaderboard was last updated on May 14, 2026. That matters because the market’s fine print switches to official Waymo / credible-tech-reporting evidence if Robo Tracker has not updated for more than 7 days, so stale-data risk is central to the forecast. (robotracker.app)

The key inclusion issue is the no-waitlist rule. Waymo officially said on April 15 that Miami and Orlando were open to everyone. But on February 24 it said Dallas, Houston, and San Antonio were only admitting select riders on a rolling basis, with broad opening planned “later this year”; Nashville’s April 7 launch likewise began with rolling invites rather than fully open access. Under Robo Tracker’s own rules, those texts make Dallas, Houston, San Antonio, and Nashville materially less likely to count by June 30 unless Waymo changes access terms very soon. (waymo.com)

The bullish evidence is Waymo’s May 13 statement that Miami was expanding immediately, with Austin, Atlanta, Houston, and the San Francisco Bay Area “following close behind,” and that over the next few weeks Waymo would cover more than 1,400 square miles across 11 cities. Local reporting quantified at least two of those moves: NBC Bay Area reported roughly +60 square miles, taking the Bay Area above 330 square miles, and Axios Houston reported Houston rising to about 50 square miles. The catch is that Houston still appears to be early-access/invite-based, so its extra area does not automatically qualify for this specific market. (waymo.com)

My base case is therefore: start from the current seven-city qualifying total of 1,108 mi², assume the Bay Area expansion does count, and then add modest Austin/Atlanta increases that I infer from Waymo’s May 13 statement but could not directly quantify from primary sources. A simple additive model of about +57 Bay Area, +15 Austin, and +8 Atlanta gives about 1,188 mi². That 1,188 figure is my inference, not a reported number, but it is consistent with the official expansion language and with the idea that the 11-city 1,400+ figure mixes fully open markets with invite-only ones. (robotracker.app)

The main way this resolves above 1,200 is if one early-access city becomes open enough to satisfy the no-waitlist/public-availability standard before June 30. Houston is the clearest upside candidate because its announced footprint is about 50 mi²; adding that to the 1,188-mi² base gets roughly 1,238. Dallas, Nashville, or San Antonio could create similar upside, but the official wording for Dallas/Houston/San Antonio still points to broader opening later in 2026, Nashville also started with rolling invites, and San Antonio has faced service-pause issues. So I treat >1,200 as a meaningful but minority scenario rather than the base case. (waymo.com)

Bottom line: I center the distribution in the upper 1180s, with the highest mass around 1188-1192. Most of my probability is on a result where the seven already-qualifying markets absorb announced expansions, while a smaller but real chunk is on at least one currently invite-only city qualifying in time and pushing the answer into the >1200 top bin. I put only a tiny tail on very low outcomes because the currently qualifying total is already 1,108 mi². (robotracker.app)

I start from Robo Tracker because it is the primary resolution source unless the site is stale. Its current leaderboard shows Waymo at 1,108 mi² across seven public cities, last updated on May 14, 2026: Phoenix 302, San Francisco Bay Area 278, Miami 154, Austin 133, Los Angeles 122, Atlanta 61, and Orlando 58. Because that timestamp is already more than 7 days old on June 14, the question’s fallback clause is a real possibility by June 30 if Robo Tracker does not refresh again. (robotracker.app)

Waymo’s own FAQ now separates cities where anyone can take a fully autonomous ride right away from cities where it is only welcoming riders. As of June 14, the open-now bucket is Los Angeles, Metro Phoenix, Miami, Orlando, and San Francisco, plus Austin and Atlanta via Uber; Dallas, Houston, Nashville, and San Antonio are still in the softer early-access bucket. That makes it hard for me to count those four as clearly public/no-waitlist today. (waymo.com)

The bullish evidence is on expansion inside the already-public network. On May 13, Waymo said Miami was expanding immediately and Austin, Atlanta, Houston, and the San Francisco Bay Area would follow over the next few weeks, taking Waymo to over 1,400 square miles across 11 cities. The next day, NBC Bay Area reported the Bay Area expansion alone would add roughly 60 square miles and put that footprint at over 330 square miles, while Axios Houston reported Houston would nearly double to 50 square miles and also said Austin and Atlanta had expanded. My inference is that, even with no new city graduating from early access, the public/no-waitlist total is likely to move from 1,108 into the high-1,100s once those public-city expansions are fully reflected. (waymo.com)

For timing/base rates, Miami moved from limited public access on January 22, 2026 to open-to-everyone on April 15, 2026, and Orlando moved from limited access on February 24, 2026 to open-to-everyone on April 15, 2026. Dallas, Houston, and San Antonio have been in limited rollout since February 24, 2026, and Nashville since April 7, 2026, so an additional city opening by July 1 is plausible. But it is not my base case, because Waymo still had those cities in the early-access bucket on June 14, and late-May weather/flood issues created extra friction: AP reported temporary pauses in Atlanta and Texas, Atlanta later resumed, and KSAT reported San Antonio’s cars had resumed autonomous driving but were still not transporting passengers there at that time. (waymo.com)

So my modal case is that Bay Area plus Austin/Atlanta growth gets recognized, but Dallas/Houston/Nashville/San Antonio do not all become clearly no-waitlist public before resolution. That puts the highest probability mass in the low 1190s. I still leave a material above-1200 tail, mainly for the possibility that Houston or another early-access city becomes clearly open to everyone, or that Robo Tracker/fallback sourcing captures more of Waymo’s May-June footprint changes than the current leaderboard does. The distribution below implements that view as a three-scenario mixture centered on roughly 1108 for the stale/current case, roughly 1192 for the existing-public-city expansion case, and roughly 1260 for the at-least-one-additional-city-becomes-fully-public case. (waymo.com)

As of June 14, 2026, Robo Tracker shows Waymo at 1,108 square miles across 7 active public cities, with the city breakdown listed as Phoenix 302, San Francisco Bay Area 278, Miami 154, Austin 133, Los Angeles 122, Atlanta 61, and Orlando 58; the same page says the leaderboard was last updated on May 14, 2026. (robotracker.app)

Waymo’s own FAQ is the key cross-check on what should count under the question’s no-waitlist/public-access standard. As of today, Waymo says anyone can ride right away in Los Angeles, Metro Phoenix, Miami, Orlando, and San Francisco, while Dallas, Houston, Nashville, and San Antonio are still in the weaker welcoming-riders status; Austin and Atlanta are publicly available through Uber. That lines up closely with Robo Tracker’s current 7-city active tally. (waymo.com)

The main upside comes from two places. First, Robo Tracker’s updates page shows the currently limited-access footprints are already material: Dallas 48 square miles, Houston 22, San Antonio 53, and Nashville 50. Second, Waymo said on May 13 that over the next few weeks it would cover more than 1,400 square miles across 11 cities, with expansions in Miami already underway and Austin, Atlanta, Houston, and the San Francisco Bay Area following close behind. (robotracker.app)

The most concrete documented public-area expansion after Robo Tracker’s May 14 snapshot is the Bay Area: NBC Bay Area reported on May 14 that Waymo planned to add roughly 60 square miles there, taking the Bay Area footprint to more than 330 square miles. Separately, Axios Houston reported Houston’s limited-access area nearly doubled to 50 square miles ahead of the World Cup. Austin, by contrast, was already reported at about 130 square miles in late April, which is very close to Robo Tracker’s current 133 figure, so I do not assume much additional Austin upside beyond what is already on the leaderboard. (nbcbayarea.com)

That creates a split forecast. In my base case, no additional limited city fully opens to everyone by June 30, but at least some of the documented public-area expansions are reflected by resolution; that pushes the likely total above the stale 1,108 reading and into the mid-to-high 1100s. In the upside case, if even one of Dallas, Houston, Nashville, or San Antonio converts from limited access to true no-waitlist public access, the total likely jumps to roughly 1,210 or higher once combined with the Bay Area expansion, which is why the >1200 overflow bin gets meaningful probability in my uncensored distribution. (waymo.com)

I keep that upside below 50% because Waymo’s own FAQ still does not list Dallas, Houston, Nashville, or San Antonio as ride-right-away cities on June 14, and there is also evidence of operational friction: Reuters/TechCrunch reported pauses tied to flooding and construction-zone issues, and San Antonio in particular was paused after a flood incident in April. Those facts make a rapid no-waitlist conversion in the next 16 days plausible, but far from assured. (waymo.com)

So my final distribution is a three-scenario mixture: a conservative case centered near 1,112, a main case centered near 1,172, and an upside case centered near 1,232. Intuitively, that corresponds to roughly: stale/under-reflected public-area reporting; public expansions without a new city fully opening; and at least one limited city crossing into full public eligibility before resolution. The resulting forecast has its center of mass in the high 1100s, with a substantial but not dominant chance that the latent total ends up above 1,200.

First, the client’s starting point is stale. On June 14, 2026, Robo Tracker’s leaderboard shows Waymo at 1,108 mi² across seven public cities, not about 1,044. The city breakdown shown there is Phoenix 302, San Francisco Bay Area 278, Miami 154, Austin 133, Los Angeles 122, Atlanta 61, and Orlando 58; Robo Tracker also says the leaderboard was last updated on May 14, 2026. (robotracker.app)

That last-update date matters because the market’s fine print says a stale Robo Tracker page can trigger fallback resolution using official Waymo announcements or consensus reporting. Since the leaderboard is already more than 7 days stale as of June 14, I gave meaningful weight to official Waymo statements and local reporting instead of anchoring mechanically on 1,108. (robotracker.app)

The main upside signal is Waymo’s official May 13, 2026 update. Waymo said Miami was expanding immediately, with Austin, Atlanta, Houston, and the San Francisco Bay Area ‘following close behind,’ and that ‘over the next few weeks’ it would cover over 1,400 square miles across 11 cities. Local reporting adds two concrete figures: Bay Area coverage would rise by roughly 60 square miles to more than 330, and Houston would nearly double to 50 square miles. (waymo.com)

But the key catch is the market’s public/no-waitlist rule. As of June 14, Waymo’s FAQ still distinguishes between places where anyone can ride right away and places that are merely ‘welcoming riders.’ The FAQ lists immediate open access only for Los Angeles, Metro Phoenix, Miami, Orlando, and San Francisco, while Austin and Atlanta are available publicly through Uber; Dallas, Houston, Nashville, and San Antonio are phrased as cities where users can download the app ‘to be among the first to ride.’ That matches Waymo’s February 24 launch post for Dallas/Houston/San Antonio/Orlando, which said select invited riders would start first and broader opening would come later in 2026, and Waymo’s April 7 Nashville post, which launched service but did not describe it as open-to-everyone. So I do not simply import the company’s 1,400+ mi² figure into this market; some of those miles may still fail the market’s no-waitlist standard on June 30. (waymo.com)

Recent flood-related disruptions are another reason to discount a very fast public ramp in the South. Reuters and TechCrunch reported late-May pauses in Atlanta and Texas tied to flooding and roadway-safety fixes, and KSAT reported that in San Antonio Waymo vehicles had resumed autonomous driving but were still not transporting passengers. That makes San Antonio especially unlikely to become newly countable by July 1, and it also modestly reduces my odds that Dallas or Houston suddenly move to fully open public access before resolution. (ca.investing.com)

My base case is therefore: Bay Area expansion counts; Austin and Atlanta receive modest counted expansion; Miami and Orlando have some smaller upside; but Houston, Dallas, Nashville, and San Antonio mostly remain outside the market’s public/no-waitlist definition by June 30. That lands the resolved value close to, but usually still below, the upper cap. The main upside scenario is that Houston becomes countable under the fallback interpretation or one of Dallas/Nashville opens broadly enough to qualify, which would push the market into the >1200 top bin. This is an inference from combining the current 1,108 mi² base, the announced Bay Area/Houston deltas, and Waymo’s still-limited-access language for the newer cities. (robotracker.app)

So my distribution is centered just under 1,200 mi², with most of the mass in the high-1100s and a substantial but not dominant top-bin tail above 1,200. In words: I think the market is more likely than not to resolve above today’s 1,108, very likely to be near 1,200, and still has a meaningful chance to clip into the >1200 bin if one additional city or a larger-than-expected public expansion becomes countable before June 30. (robotracker.app)

Robo Tracker currently lists Waymo at 1,108 mi² across 7 public cities, broken down as Phoenix 302, San Francisco Bay Area 278, Miami 154, Austin 133, Los Angeles 122, Atlanta 61, and Orlando 58. The leaderboard page also says it was last updated on May 14, 2026. (robotracker.app)

Waymo’s growth signal is clearly positive. On February 24, 2026, Waymo launched Dallas, Houston, San Antonio, and Orlando to rolling invited riders ahead of opening to everyone later in 2026. On April 7, 2026, it did the same in Nashville with an initial 60-square-mile area. On April 15, 2026, it opened Miami and Orlando to everyone. On May 13, 2026, Waymo then said Miami was expanding immediately and Austin, Atlanta, Houston, and the Bay Area would follow, taking it to over 1,400 square miles across 11 cities in the next few weeks. (waymo.com)

The key resolution nuance is that Robo Tracker counts only truly public service with no waitlist and reasonable availability. As of June 14, 2026, Waymo’s FAQ still separates cities where anyone can ride right away from Dallas, Houston, Nashville, and San Antonio, where Waymo says it is still welcoming riders and that users should download the app to be among the first. That is the biggest reason I do not simply import the full 11-city, 1,400+-square-mile Waymo figure into the resolving number. (waymo.com)

Even so, the active-city footprint probably rises materially before resolution. NBC Bay Area reported on May 14, 2026 that the South Bay expansion would add roughly 60 square miles and bring Bay Area coverage to over 330 square miles, and Waymo’s Bay Area ride page now describes service running from the Sunset to San Jose, which is consistent with that expansion being live or nearly live. Houston reporting the same week said Houston would nearly double to about 50 square miles and that Austin, Atlanta, and Miami had also expanded, with Waymo above 1,400 square miles across 11 cities. My inference from those pieces is that the no-new-city case is already around the high 1180s to low 1190s once the Bay Area change and some Austin/Atlanta growth are reflected. (nbcbayarea.com)

I trim the odds that San Antonio contributes much by June 30 because service was still halted for weeks after the April flooding incident, while Atlanta had to pause and then resume after its own flooding episode. Those weather-related interruptions also make a fresh no-waitlist opening in Houston or Dallas somewhat less certain on this short horizon. (techcrunch.com)

Putting it together, my central estimate is 1194 mi². The modal mass is just below 1200: I think the likeliest path is that Bay Area growth is counted, Austin and Atlanta are somewhat larger than the stale Robo Tracker numbers, and Dallas/Houston/Nashville/San Antonio mostly still fail the no-waitlist test by June 30. I still leave a meaningful upside tail above 1200 because a single additional city becoming countable public service would likely add roughly 50 to 60 square miles by itself. The code implements that view as a 4-scenario mixture: a conservative recognition case, a main case clustered just below 1200, a one-new-city-open case, and a more aggressive multi-open case.

What will be the total square mileage of Waymo’s public service area on July 1, 2026?

• My most likely prediction for Waymo’s total square mileage on July 1, 2026, is 1,107.50, with a 50% chance of falling between 1,100.50 and 1,118.50.
• The current baseline is 1,108 square miles as reported by Robo Tracker in mid-May 2026, which remains the strongest anchor for the forecast given the proximity to the resolution date.
• Recent software recalls and service suspensions due to flooding in Texas and Georgia have likely delayed the transition of invitation-only cities to full public access.
• There is a secondary possibility of expansion to approximately 1,165 square miles if a single city, such as Houston or Nashville, removes its waitlist before June 30.
• A value exceeding 1,200 square miles is considered unlikely (roughly 10-15% chance) because it would require multiple major cities to transition to public status simultaneously despite current safety pauses.
• Financial data indicates Alphabet has ample cash reserves ($126B+) to fund expansion, but operational safety and mapping updates are currently the limiting factors.

Key figures

Historical context

• Waymo’s public footprint grew significantly in early 2026, reaching 1,108 square miles by May after opening Miami and Orlando to the public on April 15, 2026.
• The company previously tripled its annual ride volume in 2025 to 15 million rides, demonstrating a pattern of aggressive scaling.
• In February 2026, Waymo secured $16 billion in funding, primarily from Alphabet, to support expansion into 20+ additional cities.
• Historically, Waymo has utilized an “invitation-only” phase lasting several months before removing waitlists for the general public in new markets.
• Previous software recalls occurred in 2025 (1,200 vehicles) following collisions and issues with school bus detection, briefly impacting expansion timelines.

Tailwinds

• Waymo’s “World Cup” expansion plans in Houston aim to double the service area to 50 square miles, which may include a public launch.
• The company has already established infrastructure and invitation-only riders in Nashville, Dallas, and San Antonio, making them “launch-ready.”
• Alphabet’s record-high R&D spending ($17B in Q1 2026) and massive cash position support rapid recovery from the software recall.
• Competitive pressure from Tesla’s robotaxi ambitions may push Waymo to maintain its public expansion lead.

Headwinds

• A voluntary software recall of approximately 3,800 vehicles in May 2026 has slowed the pace of new public launches.
• Recent flooding incidents in San Antonio and Atlanta led to service pauses and increased safety scrutiny from the NHTSA.
• Waymo’s temporary suspension of highway operations nationwide reduces the effective utility and potential “reasonable wait time” coverage required by Robo Tracker.
• The transition from invitation-only to “no-waitlist” status is currently delayed in high-growth Texas markets (Houston, Dallas, San Antonio).

Detailed reasoning

My analysis is anchored by the most recent reliable data from Robo Tracker, which reported Waymo’s public service area at 1,108 square miles as of May 14, 2026. This area is distributed across seven cities: Phoenix (302), San Francisco Bay Area (278), Miami (154), Austin (133), Los Angeles (122), Atlanta (61), and Orlando (58). While Waymo officially operates in 11 metropolitan hubs, the four additional cities (Dallas, Houston, San Antonio, and Nashville) are currently restricted to invitation-only or waitlisted riders. For the purposes of this forecast, only “no-waitlist” public service areas qualify.

The transition from invitation-only to public status has historically been the primary driver of rapid acreage growth. However, significant headwinds emerged in late May 2026. A series of flooding incidents in Texas and Georgia resulted in an unoccupied robotaxi being swept away in San Antonio and another stalling in Atlanta. These events triggered a voluntary software recall of Waymo’s entire 3,800-vehicle fleet and a temporary suspension of highway operations nationwide to address “untraversable flooded lanes” and construction zone navigation. Consequently, the aggressive timeline for opening Texas cities like Houston and Dallas to the general public was explicitly delayed.

In weighting the forecast, I assigned the highest probability (approximately 65%) to a status-quo scenario where the total area remains near 1,108 square miles. With only 16 days remaining until the resolution date, the regulatory and safety scrutiny following the recall makes a major public launch highly unlikely within this narrow window. I allowed for minor fluctuations (±10 square miles) due to Robo Tracker’s polygon mapping adjustments or small expansions in mature markets like Phoenix or Los Angeles.

A secondary scenario (approximately 25% weight) considers the possibility of a single city, most likely Houston (50 sq mi) or Nashville (60 sq mi), transitioning to public status just before the deadline. Houston is a particularly strong candidate due to the “World Cup expansion” plans mentioned in May reports, which aimed to double its footprint ahead of the tournament. If this occurs, the total would likely land between 1,160 and 1,175 square miles.

A low-probability “upside” scenario (10% weight) accounts for a rapid, multi-city rollout that would push the value above the 1,200 square mile threshold. While Waymo has the capital (following a $16 billion round) and the fleet size to do so, the current “wait-and-see” safety posture makes this less probable. Overall, the forecast reflects a heavily anchored baseline with a moderate right-skewed tail representing potential last-minute expansions.

Key uncertainties

• The exact timing of the “no-waitlist” status change for cities like Houston and Nashville is at the discretion of Waymo management.
• Robo Tracker’s polygon mapping methodology can lead to minor area fluctuations even without city-wide launches.
• The duration of the highway service suspension could affect whether Robo Tracker considers certain zones as having “reasonable wait times.”
• Regulatory intervention from the NHTSA following the San Antonio flooding incident could force a longer pause on geographic growth.

Conclusion

• Waymo’s public service area is expected to remain near its May 2026 baseline of 1,108 square miles, as recent operational setbacks and software recalls likely delay the transition of invitation-only cities to full public access.
• Decision-makers should monitor Houston and Nashville; a sudden “no-waitlist” launch in either city would trigger an immediate 50-60 square mile increase, potentially pushing the total toward the 1,200 square mile upper threshold.

Question: will Waymo’s public/no-waitlist, no-safety-driver service area per Robo Tracker exceed 1,200.5 mi² by 2026-06-30? Robo Tracker currently shows 1,108 mi² across seven active cities, so the top bin needs roughly +92 mi²; forecasters unanimously anchor on Robo Tracker’s stricter metric rather than Waymo’s May 13 “over 1,400 mi²” headline, which likely includes invitation-only or testing areas. The most plausible in-range increase is a reported SF Bay/South Bay expansion of ~50–60 mi² (pushing the total to ~1,160–1,170), while promotion of testing/future areas (Dallas, Houston, San Antonio, Nashville — ~174 mi² total) could alone push the total over 1,200 if Robo Tracker reclassifies them as open-to-everyone. Historical evidence (Miami/Orlando) suggests Robo Tracker waits for explicit “open to everyone” language, so rolling-invite launches are less likely to be counted quickly; teams therefore put substantial mass on little or moderate change and a smaller but real tail probability that the broader May expansion or fallback to press reports yields >1,200. A resolution-source wrinkle is a possible Robo Tracker timestamp/staleness issue: if the site is deemed stale or unavailable, fallback to Waymo/journalism could favor the higher headline total, which is the main disagreement driver. Overall, forecasters see top-bin outcomes as plausible but not the default, with only a modest probability assigned to surpassing 1,200.5 by the deadline.

Forecast and Reasoning

Forecast: Probability distribution:

• 1.00% chance of value below 1046.0
• 5.00% chance of value below 1102.0
• 10.00% chance of value below 1115.0
• 20.00% chance of value below 1128.0
• 30.00% chance of value below 1143.0
• 40.00% chance of value below 1157.0
• 50.00% chance of value below 1168.0
• 60.00% chance of value below 1179.0
• 70.00% chance of value below 1191.0
• 80.00% chance of value below 1203.0
• 90.00% chance of value below 1218.0
• 95.00% chance of value below 1228.0
• 99.00% chance of value below 1237.0

Forecast Reasoning

Key fact from multiple analysts is that Robo Tracker’s latest reported Waymo “Total Service Area (mi²)” is about 1,108 mi² (higher than the ~1,044 mentioned in the prompt background). With only ~16 days until the June 30, 2026 snapshot, the forecast is dominated by (a) whether Robo Tracker updates already-public geofences (especially SF Bay Area) in time, and (b) whether any additional cities meaningfully change status under Robo Tracker’s strict “public / no waitlist / no safety driver / reasonable wait times” criteria.

I put most probability on moderate near-term increases (tens of square miles, potentially ~50+ if a reported Bay Area expansion is incorporated), yielding a median in the high-1100s. Reaching the ≥1,200 threshold by June 30 requires a relatively large net jump from ~1,108 (roughly +90 mi²), which seems plausible but not the default given the short window and the possibility that some announced expansions remain limited rollout and thus excluded. Downside risk (falling to ≤1,050) exists mainly through reclassification/pauses or measurement revisions, but appears low versus the short-term expansion momentum and the already-above-1,050 baseline.

An amateur forecast is likely to anchor either on the prompt’s stale ~1,044 figure (understating current size) or on the “>1,400 mi² across 11 cities” headline (overstating what will qualify as fully public on Robo Tracker by the cutoff). This forecast re-anchors on the ~1,108 Robo Tracker baseline reported by multiple analysts, explicitly accounts for Robo Tracker’s stricter inclusion rules and the very short time-to-resolution, and represents the remaining uncertainty by assigning a meaningful (but not dominant) chance of landing in the ≥1,200 top bin and a small chance of dropping to the ≤1,050 bottom bin. Confidence: medium, with most uncertainty coming from Robo Tracker update timing and how it classifies borderline rollouts.

Forecast rationale (numeric):

— Iteration 1 — Across these forecasts, the dominant reasoning pattern is that Waymo’s July 1, 2026 public service area is likely to be above the current ~1,044 sq mi baseline, but the exact result depends on how much of Waymo’s announced expansion is actually reflected in the measurement source.

Key factors driving the forecasts

• Current tracker baseline: Robo Tracker’s stricter “public service” definition starts around 1,044 sq mi.
• Waymo’s announced expansion: Recent press coverage suggests 1,400+ sq mi across 11 cities, which creates strong upside pressure on the estimate.
• Measurement-definition mismatch: The largest uncertainty is whether the final value will follow:
  • the stricter tracker criteria,
  • delayed tracker updates,
  • or fallback to Waymo’s official announcements if the tracker is stale.
• Rollout pace and waitlist status: Whether additional cities/areas fully drop waitlists and become publicly usable is treated as the main determinant of whether the estimate stays near the baseline or moves substantially higher.
• Market/rollout signals: Prediction-market style signals are used to bracket outcomes, with modest expansion seen as the most likely path.

Areas of consensus

• All forecasts agree that some increase beyond 1,044 sq mi is plausible and likely.
• They also agree that the “public service area” definition matters more than the marketing headline, so the final number may lag Waymo’s announced figure.
• The most probable outcomes are in the middle-to-upper range, not a sharp drop or a dramatic surprise below baseline.

Main disagreement

• The forecasts differ mainly on how far the expansion will be reflected by July 1:
  • a conservative view expects only modest growth if tracker updates lag,
  • a more bullish view expects the top-bin outcome if Waymo’s 1,400+ sq mi rollout is fully recognized.

Unified takeaway

The collective reasoning points to moderate-to-strong expansion from the current baseline, with outcomes shaped by the tension between Waymo’s rapid announced growth and Robo Tracker’s stricter, slower-moving public-service accounting.

— Iteration 2 — Across the rationales, the forecast is driven mainly by Waymo’s current reported public-area footprint and how much can change before the June 30 cutoff.

Main factors considered

• Current baseline is about 1,044 sq mi, which is just under the 1,050 lower resolution floor.
• The biggest uncertainty is whether Waymo will:
  • make only small incremental public additions, or
  • remove waitlists / expand to additional cities, which could push the reported area toward or above the 1,200 upper cap.
• Several rationales note a gap between the Robo Tracker figure (~7 cities / 1,044 sq mi) and Waymo’s broader operational footprint of 1,400+ sq mi across 11 cities, implying the resolution could jump substantially if more areas become publicly counted.

Shared reasoning pattern

• The forecasts are heavily shaped by the binning structure:
  • outcomes at or below the current level tend to resolve to 1,050,
  • outcomes near the broader expansion scenario cluster at 1,200,
  • and intermediate outcomes land somewhere in between.
• This creates a bimodal or skewed distribution, with strong mass at the lower bound and meaningful tail risk at the upper bound.

Consensus

• Most reasoning converges on a modest increase from the current tracker value, with a central expectation around 1,100–1,125 sq mi.
• There is broad agreement that large expansion is possible but not certain.

Main disagreement

• The models differ mostly on how likely a jump to the top bin is:
  • one emphasizes a substantial chance of staying near 1,050,
  • another places more weight on a broader expansion to 1,200,
  • while another sees the middle range as most likely but still assigns notable probability to both extremes.

Overall, the collective view is that Waymo’s July 1, 2026 public service area is likely to be somewhat above today’s tracker value, with outcomes constrained by the resolution bins and sensitive to near-term public expansion updates.

— Iteration 3 — The forecasts largely agree that the answer will be driven by a tension between Waymo’s announced expansion plans and what the public tracking source is likely to count by July 1, 2026.

Core reasoning pattern

• Current baseline is around 1,044 square miles.
• Waymo has announced a much larger eventual footprint, above 1,400 square miles, but that does not necessarily translate into the metric used for the question.
• Robo Tracker’s public-service definition appears restrictive, likely counting only areas without a waitlist, which means newly announced cities may not be included right away.
• Given the short time horizon, the most plausible change is incremental expansion within existing cities, not full inclusion of the announced multi-city rollout.

Areas of consensus

• Most weight should remain near the current level or modestly above it, rather than jumping immediately to the full 1,400+ square-mile target.
• Existing-city expansions are the main expected source of near-term growth.
• There is a meaningful lag between Waymo’s headline footprint and the tracker’s reported figure.

Main disagreements

• One view puts substantial probability on the top bin, arguing that the official footprint target could be reflected more quickly than expected.
• The more cautious views expect most probability mass in the bottom to middle bins, with only a smaller tail reaching the highest range.

Overall synthesis

The collective reasoning suggests a mostly modest increase from the current ~1,044 square miles, with the strongest probabilities concentrated around roughly 1,050–1,150 square miles, and a smaller chance of a larger jump if Robo Tracker incorporates a broader share of Waymo’s announced service area.

Baseline and Resolution Mechanics The rationales broadly agree that Waymo’s current waitlist-free service area sits at a baseline of roughly 1,044 square miles. Because the resolution criteria dictate that any final value at or below 1,050 resolves to the bottom bin, the service area must physically grow—and be recorded by the tracker—within a very tight 16-day window to result in a different outcome.

Headwinds to Near-Term Expansion Forecasters highlight several major constraints making a sudden, un-waitlisted expansion before the deadline unlikely:

• Waitlist Monetization: Waymo recently launched “Waymo Premier,” a subscription tier that allows users to bypass virtual queues. Monetizing the waitlist creates a strong financial disincentive to completely remove waitlists in newer, high-demand markets like Houston, Dallas, or Atlanta.
• Safety and Operational Pauses: Recent severe weather events led to a voluntary NHTSA software recall and operational pauses in several markets. Rectifying these issues diverts the company’s focus toward safety validations rather than immediate geographic scaling.
• Regulatory Delays: Approvals for new markets and territorial expansions in California currently face ongoing regulatory scrutiny and protests.

Robo Tracker Lag and Fallback Scenarios A central theme across all rationales is the methodology of Robo Tracker itself. Because it is a crowdsourced, community-driven dashboard, it inherently lags behind official corporate announcements. Even if Waymo drops a waitlist or expands a geofence late in the month, the platform relies on user ride logs, meaning changes may not be mapped and validated before the deadline. Conversely, forecasters note a significant tail risk: if the tracker goes stale and fails to update for seven days, the resolution falls back to official Waymo press releases. Official figures report “gross” square mileage (which includes un-drivable areas like bodies of water), which would drastically elevate the final total.

Potential Catalysts for Growth Despite the overarching constraints, the rationales identify a few specific pathways for metric growth. The tracker’s total could naturally “creep” upward as users slowly finish mapping the remnants of Waymo’s massive mid-May expansion. Additionally, there is a possibility that Waymo abruptly drops waitlists in Texas cities to accommodate the influx of tourist demand for the 2026 FIFA World Cup, though this remains heavily weighed against the drag of recent safety recalls and subscription monetization.

SUMMARY

Question: What will be the total square mileage of Waymo’s public service area on July 1, 2026? Final Prediction: Probability distribution:

• 10.00% chance of value below 1108.005
• 20.00% chance of value below 1174.9
• 40.00% chance of value below 1217.305
• 60.00% chance of value below 1300.105
• 80.00% chance of value below 1355.005
• 90.00% chance of value below 1440.055

Total Cost: extra_metadata_in_explanation is disabled Time Spent: extra_metadata_in_explanation is disabled LLMs: extra_metadata_in_explanation is disabled Bot Name: extra_metadata_in_explanation is disabled

Report 1 Summary

Forecasts

Forecaster 1: Probability distribution:

• 10.00% chance of value below 1108.4
• 20.00% chance of value below 1166.4
• 40.00% chance of value below 1235.0
• 60.00% chance of value below 1400.4
• 80.00% chance of value below 1510.0
• 90.00% chance of value below 1680.0

Forecaster 2: Probability distribution:

• 10.00% chance of value below 1107.61
• 20.00% chance of value below 1183.4
• 40.00% chance of value below 1199.61
• 60.00% chance of value below 1199.81
• 80.00% chance of value below 1200.01
• 90.00% chance of value below 1200.11

Research Summary

The research summarizes that Waymo publicly announced a major service-area expansion on May 13, 2026 that raised its reported coverage to about 1,400 square miles across 11 U.S. cities (Phoenix, San Francisco, Los Angeles, Austin, Atlanta, Miami, Dallas, Houston, San Antonio, Orlando, Nashville). This 1,400 sq mi figure represents roughly a 27% increase (≈300 sq mi) from an earlier ~1,100 sq mi baseline in 2026; however, the question’s background cites a conflicting 1,044 sq mi figure, suggesting either an out-of-date Robo Tracker reading (last updated May 14, 2026), measurement differences, or a pre-expansion baseline. The research also catalogs the 2026 expansion timeline (Miami initial launch in January and highway expansion in April, Nashville launch in March at ~60 sq mi, May 13 multi-city expansion, and a June 11 Houston expansion announcement tied to the FIFA World Cup), notes a February 2026 $16 billion funding round at a $126 billion valuation with Alphabet contributing ≈$13 billion and stated goals of 20+ cities and 1 million weekly rides in 2026, and estimates a 6-month growth pace of ≈300 sq mi (≈27%).

The report highlights operational and regulatory constraints that could affect the public service-area tally by July 1, 2026: a large vehicle recall (≈3,700–3,800 vehicles) and multi-city service suspensions in April–May 2026, highway-ride suspensions, and a pending California Public Utilities Commission decision on June 27, 2026. Key uncertainties for the June 30/July 1 resolution include Robo Tracker’s update lag, the unspecified square mileage of the June 11 Houston expansion, whether suspended services reduce qualifying coverage, and measurement methodology (Robo Tracker counts only fully public, no-waitlist, no-safety-driver service with reasonable wait times). The research provides base-rate scenarios for July 1: minimal (0–5%) yielding ≈1,400–1,460 sq mi if only small additions occur, moderate (5–10%) ≈1,470–1,540 sq mi with further densification, and aggressive (15–20%) ≈1,610–1,680 sq mi if multiple large expansions materialize—while noting the short (≈16-day) window limits likely additional growth.

Sources used in the research (as named in the document; no URLs were provided in the research): Robo Tracker (leaderboard), Waymo press releases/announcements (May 13 expansion, June 11 Houston expansion), FutureSearch.ai analysis (May 27, 2026), California Public Utilities Commission (CPUC), reporting on the February 2026 funding round and on vehicle recalls/service suspensions (various news outlets), and mention of prediction-market platforms checked (Metaculus, Manifold, Kalshi, Polymarket).

RESEARCH

Report 1 Research

Waymo Service Area Forecast Research - June 14, 2026

Current State & Recent Developments

Most Recent Service Area Data: According to multiple sources from May 13, 2026, Waymo expanded its service area to approximately 1,400 square miles across 11 US cities [21][24][25]. This represents a 27% expansion from approximately 1,100 square miles earlier in 2026, adding roughly 300 square miles [24]. This coverage now exceeds Rhode Island’s size (1,034 sq mi).

However, the question’s background states Waymo “currently operates in approximately 1,044 square miles” as of June 14. This discrepancy suggests either:

• Robo Tracker hasn’t been updated since the May 13 expansion
• Different measurement methodologies between sources
• The background information predates the May expansion

Important Note: Robo Tracker’s leaderboard was last updated on May 14, 2026 [23], just one day after the major expansion announcement.

Cities Currently Operating (as of June 2026): Phoenix, San Francisco, Los Angeles, Austin, Atlanta, Miami, Dallas, Houston, San Antonio, Orlando, and Nashville [6][10][15][21]

Recent Expansion Timeline (2026)

• January: Miami launch (initial neighborhoods) [1]
• March: Nashville launch (60 sq mi service area) [15]
• April: Miami highway expansion announced [1]
• May 13: Major expansion to 1,400+ sq mi announced [21][24]
• May 18: Miami expanded to additional neighborhoods, highways (I-95, Dolphin/Palmetto Expressways) [7]
• June 11: Houston expansion for FIFA World Cup announced [3]

Funding & Strategic Context

February 2026 Funding Round:

• $16 billion raised at $126 billion valuation [11][12][13][15][17][18]
• Lead investors: Dragoneer Investment Group, DST Global, Sequoia Capital
• Alphabet contributed ~$13 billion [13]
• Stated goal: Expand to 20+ cities in 2026 [4][6][10][11]

Growth Targets:

• Aiming for 1 million weekly rides by end of 2026 (currently ~500,000) [6][10][13][15]
• International expansion planned: London and Tokyo [2][4][5][6]
• Launched “Waymo Premier” subscription June 11 targeting power users [6][10][18]

Historical Growth Patterns & Base Rates

2026 Growth Rate:

• From ~1,100 to ~1,400 sq mi over approximately 6 months = ~300 sq mi or 27% growth [24]
• This represents rapid expansion pace

Historical Reference:

• 2023 Phoenix expansion: 45 square miles added [20]
• Suggests variable expansion rates depending on city maturity and regulatory environment

Expansion Pattern: Recent expansions have focused on densifying existing cities rather than launching entirely new markets [24]. Miami, Austin, Atlanta, Houston, and San Francisco Bay Area all received expansions within existing footprints.

Recent Operational Challenges

Service Disruptions (April-May 2026):

• 3,700-3,800 vehicle recall due to flooding detection issues [1][7][8]
• Service suspensions in 6 cities (Atlanta, Nashville, Austin, Dallas, Houston, San Antonio) in May after vehicles entered flooded roads [8]
• Highway rides suspended across all cities in May over construction zone navigation issues [4][5][8]

Regulatory Delays:

• California Public Utilities Commission (CPUC) decision on fare authorization and expansion expected June 27, 2026 [4]
• This is 3 days after the resolution date, potentially limiting California expansion in the next 16 days

Prediction Markets & Expert Forecasts

FutureSearch.ai Analysis (May 27, 2026): [22]

• Projects 775,000 weekly rides by Q4 2026 (median), falling short of 1M target
• First Ojai public ride: ~October 1, 2026
• 18% probability of formal NHTSA enforcement before mid-2027
• 15% probability of federal action restricting Ojai imports before June 30, 2027
• Assessment: Growth is “industrial and regulatory-challenged rather than technological”

Note: I did not find active prediction markets on Metaculus, Manifold, Kalshi, or Polymarket specifically forecasting this service area metric with liquidity data.

Key Uncertainties for June 30 Resolution (16 Days Away)

Critical Considerations:

1. Robo Tracker Update Lag: Last confirmed update was May 14, 2026 [23]. Will it capture any June expansions before June 30?

2. Houston FIFA World Cup Expansion: Announced June 11 with expanded coverage including Heights, Downtown, EaDo, Montrose, and Texas Medical Center [3]. Size not specified - could add meaningful square mileage.

3. Service Resumptions: Six cities had suspended service in May [8]. Resumption timing and whether service areas were reduced is unclear.

4. Very Short Timeline: Only 16 days until resolution. Typical new city launches start small (Nashville was 60 sq mi [15]), limiting impact of any new launches.

5. Regulatory Constraints: CPUC decision comes after resolution date, potentially limiting California expansion in the immediate term.

6. Measurement Methodology: Robo Tracker only counts services “open to the public with no waitlist, no safety driver, and reasonable wait times” [23]. Cities with service disruptions or pilot phases wouldn’t qualify.

Relevant Base Rates & Benchmarks

Growth Scenarios:

• Minimal expansion (0-5%): If only Houston expansion materializes at ~30-60 sq mi: 1,400-1,460 sq mi
• Moderate expansion (5-10%): Additional city densification: 1,470-1,540 sq mi
• Continued aggressive expansion (15-20%): Multiple cities expand significantly: 1,610-1,680 sq mi

Historical Context:

• Single city expansion (Phoenix 2023): 45 sq mi [20]
• New city launch (Nashville): 60 sq mi [15]
• Major multi-city expansion (Q1 2026): ~300 sq mi over ~6 months [24]

Given only 16 days remain, the pace of expansion would need to dramatically accelerate from historical rates to add substantial coverage beyond the 1,400 sq mi reported May 13.

Key Question: Does the current 1,044 sq mi baseline in the question reflect an outdated Robo Tracker reading, or has there been a methodology change or service area reduction?

Summary for Forecasting

The superforecaster should weigh:

• Recent confirmed expansion to 1,400 sq mi as of May 13 [21][24]
• Very limited time (16 days) for additional meaningful expansion
• Recent operational challenges that may have slowed expansion or reduced qualifying service areas
• Houston expansion announced but size unspecified [3]
• Regulatory headwinds in California until after resolution date
• Historical growth rate suggests 25-50 sq mi per month during aggressive expansion phases

The resolution will likely fall well above the 1,200 top bin if the May 13 expansion to 1,400 sq mi is accurately reflected in Robo Tracker’s June 30 reading, but uncertainties about service suspensions, measurement methodology, and Robo Tracker’s update cadence create meaningful tail risks.

FORECASTS

R1: Forecaster 1 Reasoning

I agree with the critic’s main point: this is more about resolution mechanics than 16 days of organic expansion. Robo Tracker currently shows Waymo at 1,108 mi² across 7 active cities, with the leaderboard last updated May 14, 2026 and with strict criteria: public/no waitlist, no safety driver, reasonable wait times, and near-anywhere pickup/dropoff in the area. (robotracker.app) If that remains stale by more than 7 days at resolution, the fallback language plausibly shifts the answer toward Waymo/press reporting, where the >1,400 mi² across 11 cities claim is highly salient. (blog.waymo.com)

I also accept the critic’s point that the 1,200 threshold is low. From 1,108, Waymo needs only about +92 mi². The reported Bay Area expansion adds roughly 60 mi², and Houston is reported as expanding to 50 mi²; if both are counted, Waymo clears 1,200 without needing Dallas, San Antonio, Nashville, or much Austin/Atlanta. (nbcbayarea.com) A new insight from rechecking Robo Tracker is that its “testing” Waymo areas already total 174 mi² across Dallas, Houston, Nashville, and San Antonio; simply reclassifying some of those can move the total sharply. (robotracker.app)

Where I still resist the critic’s stronger version: the strict no-waitlist/public criterion remains a real obstacle. Waymo’s own February announcement for Dallas/Houston/San Antonio/Orlando said select riders would be invited on a rolling basis and that service would open to everyone later in 2026. (waymo.com) Nashville likewise launched with “first public riders,” rolling invitations, and access codes to skip the line, which is exactly the kind of ambiguity Robo Tracker may treat as non-active. (waymo.com) Robo Tracker’s current classification of Dallas/Houston/Nashville/San Antonio as not active is therefore not obviously wrong.

So I’m moving meaningfully upward, but not all the way to an 85–90% top-bin forecast. My rough decomposition now is:

• ~30–33% below 1,200: Robo Tracker updates strictly, counts Bay Area and maybe small Austin/Atlanta changes, but excludes Houston/Texas/Nashville; or operational/flood-related restrictions keep some areas non-qualifying.
• ~15–20% modestly above 1,200: Houston or a similar status change is counted, but not the full 11-city marketing footprint.
• ~40–45% around 1,400+: Robo Tracker remains stale enough to trigger fallback, or updates to reflect Waymo’s broader 11-city “serving riders” picture.
• Small high tail: additional expansions or a loose fallback interpretation.

Net: I now put about 68–70% on the top bin, up from my prior “slightly over half,” but with a substantial sub-1,200 shoulder.

Updated prediction:
Percentile 0.1: 935
Percentile 1: 1015
Percentile 5: 1066
Percentile 10: 1108.4
Percentile 20: 1166.4
Percentile 30: 1197.4
Percentile 40: 1235
Percentile 50: 1340
Percentile 60: 1400.4
Percentile 70: 1435
Percentile 80: 1510
Percentile 90: 1680
Percentile 95: 1820
Percentile 99: 2200
Percentile 99.9: 2700

R1: Forecaster 2 Reasoning

Conditioning on no annulment.

I think the critic’s main point is valid: I underweighted the stale-site fallback clause. Robo Tracker currently shows 1,108 mi² across 7 active Waymo cities and says the leaderboard was last updated May 14, 2026; if that is still true on June 30, the question’s own fallback language is plausibly triggered rather than simply resolving to 1,108. (robotracker.app)

I also accept the critic’s point that Waymo’s May 13 announcement is a strong top-bin signal: Waymo said it was expanding Miami immediately, with Austin, Atlanta, Houston, and the SF Bay Area “following close behind,” and that “over the next few weeks” it would cover over 1,400 square miles across 11 cities. June 30 is far enough after that that at least some of those expansions should be in force. (waymo.com)

That said, I still would not go to 85–90% top-bin. Robo Tracker’s criteria are stricter than Waymo marketing language: it requires no waitlist, no safety monitor, reasonable wait times, and near-anywhere pickup/dropoff. (robotracker.app) Waymo’s FAQ still distinguishes “ride right away” cities from Dallas, Houston, Nashville, and San Antonio, where riders are told to download the app “to be among the first to ride”; Austin and Atlanta are public via Uber. (waymo.com) So the 1,400+ mi² figure cannot be naively treated as identical to Robo Tracker-qualified area.

My new key calculation: starting from Robo Tracker’s 1,108, the known/likely active expansions put the strict no-waitlist total close to the threshold. SF Bay Area moving from 278 to over 330 adds about 50–60 mi²; Austin moving to “more than 140” adds maybe 7–15; Atlanta’s unspecified expansion is the swing factor. Houston expanding to 50 mi² helps only if it is counted as no-waitlist/public. Axios still described Houston’s prior launch as invitation/access-code based, while also saying access for everyone was expected soon. (axios.com)

So I now put the top bin around ~70–72%, up from my prior “a little over half.” The main remaining non-top cases are: (1) strict Robo Tracker update includes SF/Austin but not enough Atlanta/Houston to cross 1,200, landing roughly 1,165–1,199; (2) the resolver ignores or narrowly interprets the stale-site fallback and uses the visible 1,108; (3) temporary service pauses/removals, especially Atlanta, create a small bottom-bin risk.

Updated prediction:
Percentile 0.1: 1049.51
Percentile 1: 1049.61
Percentile 5: 1107.51
Percentile 10: 1107.61
Percentile 20: 1183.4
Percentile 30: 1199.51
Percentile 40: 1199.61
Percentile 50: 1199.71
Percentile 60: 1199.81
Percentile 70: 1199.91
Percentile 80: 1200.01
Percentile 90: 1200.11
Percentile 95: 1200.21
Percentile 99: 1200.41
Percentile 99.9: 1200.49

Frontier Forecast — Post 474

Modal: 1106-1125 (34.4%) • frontier aggregate • 5m27s

Interpret Summary

• Reading: strict
• Type: strict
• Window: Snapshot of Robo Tracker leaderboard value at 11:59 PM UTC on June 30, 2026

Resolution sources/checks:

• https://robotracker.app/leaderboard: https://robotracker.app/leaderboard - Resolver URL extracted mechanically from resolution criteria

Edge cases:

• If Robo Tracker is unavailable or stale (>7 days without update), the resolver switches to press releases or tech journalism consensus — which may yield a different figure than the
• The question title says ‘July 1, 2026’ but resolution criteria specify the snapshot is taken at 11:59 PM UTC on June 30, 2026 — these are effectively the same moment but could diff
• If Waymo launches in a new city between now and June 30 with a partial rollout (waitlist remaining), Robo Tracker may or may not count it depending on whether it meets the ‘no wait

Frontier Agents (4/4)

Adjudication

• frontier_2: flag_only/warning - Did not retrieve or cite the leaderboard snapshot directly; relies on city pages and corporate headlines to justify substantial mass above 1,125.
• frontier_4: discount/material - Ignored the directly-queryable resolver source (Robo Tracker leaderboard / city-sum evidence) and overweighted Waymo/press headlines — fallback rule only applies if Robo Tracker is

frontier_4 should be discounted: it ignores the named resolver (Robo Tracker leaderboard) and places all mass on >1200 based on press headlines, contrary to available leaderboard/city-sum evidence. frontier_2 should be reviewed/flagged: it reports inability to fetch the leaderboard snapshot and leans more heavily to higher bins than the direct Robo Tracker city-sum anchor supports — obtain the actual leaderboard snapshot or confirm Robo Tracker accessibility before weighting its map.

Key Sources / Checks

• Lists city service areas: Phoenix 302, SF Bay 278, Miami 154, Austin 133, LA 122, Atlanta 61, Orlando 58 mi²; sums to ~1,108 mi², anchoring the central estimate.
• Confirms city-level figures like Miami 154, Austin 133, LA 122, Atlanta 61, consistent with the operator-page totals.
• Sum of Waymo city service areas as of ~June 10-14, 2026: Phoenix 302, SF 278, Miami 154, Austin 133, LA 122, Atlanta 61, Orlando 58 = ~1,108 mi².
• Waymo announced expansion to 1,400+ sq mi across 11 cities, with rollout in Miami, then Austin, Atlanta, Houston, and SF Bay Area over the next few weeks. SF Bay Area expanding from 278 to 330+ mi².
• The most recent leaderboard data snippet retrieved unequivocally states: ‘Waymo · 7 · 1,108 mi² · 7.2M. 2.2 % of US pop.’.

Agent Agreement

Agreement: Aggregated 4 comparable prediction maps on the canonical bin space.

Disagreement: See per-agent rationales: Recent Robo Tracker city-level figures (Phoenix ~302, SF Bay ~278, Miami ~154, Austin ~133, LA ~122, Atlanta ~61, Orlando ~58) imply a current total near 1,108 mi², placing the snapshot in the 1106–1125 range absent further major expansions. Waymo’s June 11 update opening Miami and Orlando to everyone supports inclusion under the tracker’s ‘public/no waitlist’ criteria. With ~2.5 weeks to go, incremental expansions could add tens of square miles, creating upside risk into 1125–1144, while a material downward revision is less likely. Central mass is therefore on 1106–1125 with meaningful probability on the adjacent bins. / Research summed current RoboTracker city values to ~1,108 mi² as of mid-June 2026 (Phoenix 302 + SF 278 + Miami 154 + Austin 133 + LA 122 + Atlanta 61 + Orlando 58). Waymo announced May 13, 2026 a rollout to “over 1,400 sq mi across 11 cities” over the next few weeks, but a substantial portion of that figure includes cities (Houston, Dallas, San Antonio, Nashville) that RoboTracker does NOT count due to waitlist/safety monitor criteria. Backing out ~195 mi² from non-qualifying cities suggests qualifying public service area target ~1,205 mi² at full rollout. However, only some expansions will land on the RoboTracker leaderboard by June 30. Modal expectation: ~1,130–1,160 mi² as ongoing SF Bay Area (+60), Miami, Austin, Atlanta partial expansions get captured. Significant tail risk both higher (more cities cross no-waitlist threshold; RoboTracker fully captures expansion) and lower (RoboTracker lag in updating). Distribution centered around bins 5-6 with right skew given Waymo’s stated 1,400 mi² target and aggressive rollout pace. / As of mid-June 2026, the Robo Tracker leaderboard reports a ‘Total Service Area’ of 1,108 mi² across 7 cities for Waymo (meeting all criteria: no waitlist, open to the public). The question resolves based on this exact figure at 11:59 UTC on June 30, 2026. Only 16 days remain for the service area to grow. Considering Waymo recently concluded a massive, rapid sequence of operational expansions between late May and early June 2026 (Phoenix +83 mi², Miami +64 mi², an LA expansion on June 12, etc.), holding steady at the current 1,108 mi² (which places it comfortably in the 1106-1125 mi² bin) is the most probable scenario. However, due to Waymo’s aggressive expansion and massive February funding round, there is a meaningful probability (around 45%) of one or more additional increments of 20-80 mi² by late June.

Mechanical frontier aggregation via logit_mean across 4 successful agents.

(frontier_1) Recent Robo Tracker city-level figures (Phoenix ~302, SF Bay ~278, Miami ~154, Austin ~133, LA ~122, Atlanta ~61, Orlando ~58) imply a current total near 1,108 mi², placing the snapshot in the 1106–1125 range absent further major expansions. Waymo’s June 11 update opening Miami and Orlando to everyone supports inclusion under the tracker’s ‘public/no waitlist’ criteria. With ~2.5 weeks to go, incremental expansions could add tens of square miles, creating upside risk into 1125–1144, while a material downward revision is less likely. Central mass is therefore on 1106–1125 with meaningful probability on the adjacent bins.

(frontier_2) Research summed current RoboTracker city values to ~1,108 mi² as of mid-June 2026 (Phoenix 302 + SF 278 + Miami 154 + Austin 133 + LA 122 + Atlanta 61 + Orlando 58). Waymo announced May 13, 2026 a rollout to “over 1,400 sq mi across 11 cities” over the next few weeks, but a substantial portion of that figure includes cities (Houston, Dallas, San Antonio, Nashville) that RoboTracker does NOT count due to waitlist/safety monitor criteria. Backing out ~195 mi² from non-qualifying cities suggests qualifying public service area target ~1,205 mi² at full rollout. However, only some expansions will land on the RoboTracker leaderboard by June 30. Modal expectation: ~1,130–1,160 mi² as ongoing SF Bay Area (+60), Miami, Austin, Atlanta partial expansions get captured. Significant tail risk both higher (more cities cross no-waitlist threshold; RoboTracker fully captures expansion) and lower (RoboTracker lag in updating). Distribution centered around bins 5-6 with right skew given Waymo’s stated 1,400 mi² target and aggressive rollout pace.

(frontier_openrou…

Final Distribution

wooley_rhino • run 10b3ae90 • $3.34 • 5m27s

Extracted Percentile Values: {0.1: 1050, 1.0: 1050, 5.0: 1065, 10.0: 1105, 15.0: 1165, 20.0: 1200, 25.0: 1200, 30.0: 1200, 35.0: 1200, 40.0: 1200, 45.0: 1200, 46.0: 1200, 47.0: 1200, 48.0: 1200, 49.0: 1200, 50.0: 1200, 51.0: 1200, 52.0: 1200, 53.0: 1200, 54.0: 1200, 55.0: 1200, 60.0: 1200, 65.0: 1200, 70.0: 1200, 75.0: 1200, 80.0: 1200, 85.0: 1200, 90.0: 1200, 95.0: 1200, 99.0: 1200, 99.9: 1200}

Model’s Answer:

Forecasting Waymo’s Total Service Area on July 1, 2026

Understanding the Question

I need to forecast Waymo’s total public service area (in square miles) as reported by Robo Tracker at 11:59 PM UTC on June 30, 2026. The resolution bins values ≤1,050 to 1050 and values ≥1,200 to 1200.

Key Evidence Assessment

Most authoritative source: The Social Media Research provides a clear, recent, and specific data point: “As of mid-June 2026, Waymo’s publicly reported autonomous robotaxi service area stands at more than 1,400 square miles across 11 U.S. cities following a major expansion wave announced and rolled out in May 2026.”

This is corroborated by:

• Electrek article from May 13, 2026, confirming >1,400 sq mi
• Waymo’s official blog (around June 11, 2026) continuing to reference this figure
• Research noting this aligns with Robo Tracker methodologies

Baseline discrepancy: The background mentions ~1,044 sq mi, but this appears to be outdated pre-expansion data. The May 2026 expansion added approximately 300 square miles.

Critical Assumptions Analysis

Assumption 1: Robo Tracker’s measurement methodology produces results similar to Waymo’s reported >1,400 figure.

• Risk: Robo Tracker may use stricter “no waitlist/public” criteria
• Failure probability: ~15%
• Impact if wrong: Could drop value into 1,051-1,199 range

Assumption 2: No major service area contractions before June 30

• Risk: Regulatory actions, safety incidents, or technical issues
• Failure probability: ~3%
• Impact if wrong: Could reduce area significantly

Assumption 3: Data will be properly updated on Robo Tracker

• Failure probability: ~2%
• Impact: Backup resolution methods would apply

Scenario Analysis

Low outcome (≤1,050): Would require either a massive methodology discrepancy between Robo Tracker and public reports, or a significant service area pullback due to regulatory/safety issues. The California DMV regulations taking effect July 1, 2026, add compliance burden but don’t appear to force area reductions. Probability: ~3%

Mid-range outcome (1,051-1,199): Would occur if Robo Tracker’s strict “public/no-waitlist” criteria exclude portions of Waymo’s claimed footprint—perhaps newer cities like Houston or New Orleans still on waitlists, or if some expanded zones haven’t fully transitioned. Probability: ~14%

High outcome (≥1,200): Given multiple authoritative sources confirming >1,400 sq mi already achieved by May 2026, with continued expansion through June, this is the most likely outcome. Even with some methodological discount, staying above 1,200 is highly probable. Probability: ~83%

Time Until Resolution

Only ~16 days remain until June 30, 2026. This limits both upside expansion potential and downside contraction risk. The trajectory appears stable with incremental growth rather than dramatic changes expected.

Distribution Construction

Given the strong evidence for >1,200 sq mi and the binning rules:

• ~3% probability resolving to 1050 (bottom bin)
• ~14% probability in the 1051-1199 range
• ~83% probability resolving to 1200 (top bin)

The mid-range distribution should skew higher (toward 1150-1199) given partial methodology match is more likely than complete mismatch.

Percentile .1: 1050 Percentile 1: 1050 Percentile 5: 1065 Percentile 10: 1105 Percentile 15: 1165 Percentile 20: 1200 Percentile 25: 1200 Percentile 30: 1200 Percentile 35: 1200 Percentile 40: 1200 Percentile 45: 1200 Percentile 46: 1200 Percentile 47: 1200 Percentile 48: 1200 Percentile 49: 1200 Percentile 50: 1200 Percentile 51: 1200 Percentile 52: 1200 Percentile 53: 1200 Percentile 54: 1200 Percentile 55: 1200 Percentile 60: 1200 Percentile 65: 1200 Percentile 70: 1200 Percentile 75: 1200 Percentile 80: 1200 Percentile 85: 1200 Percentile 90: 1200 Percentile 95: 1200 Percentile 99: 1200 Percentile 99.9: 1200

Regulatory approvals, municipal boundaries, and available vehicle fleet define the slow-moving envelope of deployable service area.

A strict public-access requirement—service open without invitations or safety drivers—sets the operational counting rule at the cutoff.

Fresh capital and an explicit multi-city rollout program pressure expansion to add substantial square miles quickly.

Operational pauses for flood risk mitigation and phased invitations exert immediate downward pressure on counted area.

A handful of announced metro polygons flipping from invite-only to open would push the total above the 1,200‑mi² pivot before July 1.

Conversely, if those metros remain invite‑gated or resume slowly after pauses, coverage will cluster near current public figures.

Key unresolved uncertainties are the public-access status of specific large metros and the timing of resumed service after safety pauses.

The outcome is highly sensitive to a few polygon decisions—Bay Area expansions, Houston, or other multi‑dozen‑mile additions determine most of the probability mass.

Forecast (median): 1122.577 sq mi

• Hard baseline: Robo Tracker shows 1,108 sq mi as of May 14, 2026, and there’s no clear sign of any contraction—so the answer is unlikely to fall much below that.
• Big swing comes from “new public” cities: The main upside is whether one or more currently testing metro areas (e.g., Dallas/Houston/San Antonio/Nashville) become fully public without a waitlist before the June 30 cutoff.
• Robo Tracker might stay stale: Since the tracker hasn’t updated for weeks, a “no update” outcome would keep the total very close to the baseline.
• Less dramatic growth is still plausible: Even without new city launches, there’s room for incremental expansion in existing public areas (with Miami and other recently added cities being the most likely contributors).
• Result is right-skewed: Most of the probability mass clusters near the baseline, but there’s a thinner tail for a sharper jump if multiple city “graduations” happen in late June.