Independent ownership research on U.S.-listed companiesMethodology  ·  Disclosures

SpaceX company research

SpaceX & xAI Daily Briefing — 2026-11-16

Sources checked: 2026-11-16 08:35 EST (America/New_York)

Developments after the November 15 morning edition, written as of this Monday morning check: United Launch Alliance's Vulcan Leo 1 launched on November 15 and failed to deliver 40 Amazon Leo satellites to orbit; further press reporting on possible SpaceX–Tesla merger talks, including previously disclosed special committees, an unconfirmed December timing report, comments from Texas's attorney general-elect, and an earlier analyst view; official posts folding Grok Imagine image and video creation into the Grok app; a correction that a limited Grok 4.8 soft rollout to Bot users had already been described on November 13; SpaceX's reported explanation of a “technical issue” in the Starshield dispute; and the November 13 Shaheen–Coons document-preservation letter, with a November 30 reply date. This is a selective briefing, not an exhaustive daily news feed. As of this morning, SpaceX had still not announced a Flight 16 date. Share prices are omitted.

Official company statements · cause not yet identified

Vulcan Leo 1 fails about 10 minutes after liftoff; ULA says 40 Amazon satellites were not delivered to orbit

United Launch Alliance's Vulcan Leo 1 lifted off from Space Launch Complex 41 at Cape Canaveral on November 15. Press accounts, including Space.com, put liftoff at 12:40 p.m. Eastern, later than the 12:11 p.m. window recorded in the November 15 morning edition. In a statement posted about 50 minutes after launch and quoted by Space.com, ULA said: “Based on data received by our Launch Director, we confirm that the Vulcan vehicle launched from Space Launch Complex 41 suffered an anomaly 10 minutes into the flight and failed to deliver the Amazon mission to orbit.” The company added that it did not yet have specific data to explain what occurred. A longer company statement, quoted by Via Satellite, said, “Today, we did not meet that standard,” and that ULA would work with its customer and other organizations to find the cause, determine corrective action, and return to flight. The mission carried 40 Amazon Leo satellites, the first of 38 Vulcan flights Amazon has purchased. Amazon Leo, in a statement also quoted by Via Satellite and local reports, called ULA a trusted partner and said there is risk with any launch, “especially true for inaugural missions like LV-01.” ULA has not identified the failed system. Some accounts noted that solid-rocket boosters and first-stage flight appeared to proceed, and that the upper stage had ignited, before an anomaly at about 10 minutes — earlier than the planned first Centaur main-engine cutoff around 17 minutes. Those observations support describing the failure as occurring during upper-stage flight, but they are not the same as an official finding that the Centaur stage was at fault. Press reports, including Via Satellite, called this ULA's first full launch failure; that characterization is the press's, not a statement in the ULA excerpts reviewed here. Space Force use of Vulcan had already been paused after earlier solid-rocket-booster nozzle problems; this anomaly, on a commercial return-to-flight, is a separate event from those nozzle issues.

Analysis · opportunity and risk
Opportunity: official, near-term statements from ULA and Amazon confirm the loss of the payload and a promised investigation, which is clearer than unofficial countdown chatter. Risk: the cause is not yet identified, a redesigned-nozzle return-to-flight ended in a different failure, and the Space Force pause now sits alongside a commercial total loss rather than being resolved by this mission.

Source: Space.com — Vulcan Centaur rocket fails during return-to-flight launch, 40 Amazon satellites lost (updated November 15, 2026). Longer ULA and Amazon statements as quoted by Via Satellite, November 15, 2026.

Press and analyst reporting · no announced deal; December timing unconfirmed

Press reports say SpaceX–Tesla merger talks are continuing; a December announcement is unconfirmed

Teslarati, reporting on November 12, said Bloomberg, citing people familiar with the matter, had reported that SpaceX and Tesla were working through deal terms and governance, that an announcement could come as soon as December, and that a slip into early 2027 had also been discussed. Neither company commented, according to that report. The December timing is unconfirmed third-party reporting, not a company notice. Special committees of independent directors were not a new November disclosure: Elon Musk said on SpaceX's October 20 third-quarter earnings call, as reported then by Yahoo Finance and later recounted by Teslarati, that both boards had formed such committees at the request of shareholders, that he is a conflicted party and cannot take part in those discussions, and that a merger should not be assumed as a certainty even though he thinks it would be a good idea. Teslarati also said Tesla's December 3 annual meeting ballot does not include a merger proposal. Separately, USA Today reported on November 13 that Texas Attorney General-elect Nathan Johnson, in a November 12 Bloomberg interview, said “any merger of companies of that consequence warrants tremendous scrutiny,” and that his transition team had not been in touch with Musk. An earlier Barclays note, reported by Yahoo Finance on October 21, had described an all-stock combination with SpaceX as the acquirer as the analyst's expected structure; that is an analyst opinion, not a company plan, and it predates this edition. Share prices, valuations and exchange-ratio estimates that appeared in some of this coverage are omitted here.

Analysis · opportunity and risk
Opportunity: the existence of independent-director committees, as described on the October earnings call, is a firmer fact than a timing rumor. Risk: no deal has been announced, the December date is unconfirmed, regulatory and political review has already been previewed, and analyst structure opinions should not be read as terms.

Source: Teslarati — Tesla and SpaceX merger talks hit a new stage, and one hurdle remains (November 12, 2026), citing Bloomberg. Special-committee remarks from the October 20 earnings call as reported by Yahoo Finance, October 21, 2026. Texas AG-elect comments from USA Today, November 13, 2026.

Company social posts · product location change, details limited

Official posts say Grok Imagine image and video creation now live in the Grok app

On November 14, the official Grok Imagine account posted, “Image and video creation now live in Grok. Just open Grok and start creating,” as quoted in contemporaneous reports including TeslaNorth. The main Grok account added that more SpaceXSI products were being brought together “into one Grok experience.” The posts did not state plan prices, regional availability, or whether a standalone Imagine interface was being withdrawn for every user. A report that about 60 Imagine-related jobs were cut was not verified from a primary company announcement in this review and is omitted. A claim that Grok Studio had been retired was likewise not independently confirmed here and is omitted.

Analysis · opportunity and risk
Opportunity: an official, dated statement that image and video creation lives inside Grok is a clear product-location change. Risk: the posts are short, they do not define plans or regions, and staffing rumors should not be treated as confirmed.

Source: TeslaNorth — Grok Brings Imagine Image and Video Creation Into One App (November 15, 2026), quoting official @imagine and @grok posts of November 14, 2026

Correction · limited soft rollout described November 13; not a general or API release

Correction: a limited Grok 4.8 soft rollout to Bot users was already described on November 13

The November 15 edition correctly said a broader official launch of Grok 4.8, as a general or API release, remained unconfirmed that morning. It should also have recorded, as of that morning, that the official Grok account had posted on November 13 that a “soft rollout of Grok 4.8 to Bot users is underway this week after the full C/C++ stack rewrite,” as quoted in contemporaneous reports. That post, dated two days before the November 15 check, describes a limited rollout to Bot users, not general consumer availability and not an API launch. This review did not open the original post and relies on those quotations. As of this Monday morning, no official Flight-style model card or public API identifier for Grok 4.8 was confirmed here, and the limited-rollout description should not be read as a full release.

Analysis · opportunity and risk
Opportunity: a dated official-account description of a Bot-user soft rollout is a narrower, more accurate status than “not released.” Risk: eligibility, access instructions and capability claims were not published in the materials reviewed here, so the rollout remains limited and unmeasured in this briefing.

Source: Zeniteq — Grok 4.8 Begins a Limited Rollout to Bot Users, quoting the official Grok account post of November 13, 2026. This review did not open the original post.

Reported company explanation · still disputed, and not a technical finding

SpaceX has told Ukraine the Starshield disruption is a “technical issue,” a diplomat says

Hromadske reported on November 16 that SpaceX had told Ukraine the renewed Starshield restrictions were the result of a technical issue, without a further public explanation. The article cited PBS journalist Nick Schifrin, quoting Denys Sienik, Ukraine's chargé d'affaires in the United States, as saying Kyiv had received no additional clarification about why restrictions had persisted in occupied territory for five consecutive days. Hromadske also said sources in Ukraine's Defense Ministry told the outlet on November 13 that a 161 kilometer-per-hour threshold applied to the speed at which a terminal can travel while maintaining service over Russian-occupied territory, not to data-transfer speed, and that a comparable limit had not been observed over Ukrainian-controlled areas. Those ministry-source details are attributed to Hromadske and were not independently confirmed here. President Zelenskyy's disagreement with a purely technical explanation was recorded in the November 15 edition. A Financial Times report that some Ukrainian officials suspected a link to peace negotiations is noted by Hromadske as not independently established, and is not treated here as a finding.

Analysis · opportunity and risk
Opportunity: a reported company explanation, even a brief one, is more specific than the November 12 denial alone. Risk: Kyiv says it still lacks a detailed account, the travel-speed description rests on attributed ministry sources, and the dispute is not resolved.

Source: Hromadske — SpaceX blames 'technical issue' for renewed Starshield restrictions affecting Ukraine (November 16, 2026)

Congressional request · preservation letter, not a finding of fact

Senators Shaheen and Coons ask SpaceX to preserve Starlink and Starshield records and to reply by November 30

In a November 13 letter released by the Senate Foreign Relations Committee's Democratic office, Senators Jeanne Shaheen and Chris Coons asked Elon Musk and SpaceX to preserve documents, communications and electronically stored information relating to Starlink or Starshield in Ukraine, including records from September 1, 2026, to the present. The senators asked for written confirmation no later than November 30, 2026, that preservation measures have been implemented, and for answers by the same date to questions about how any restrictions since October 1 were communicated, approved or directed, whether SpaceX assessed the consequences, and which restrictions remain in effect. The letter is an oversight request and a preservation demand, not an adjudicated finding. It notes conflicting public statements about who has authority to impose limits. This review opened the official Senate release and the letter text.

Analysis · opportunity and risk
Opportunity: a dated official letter with a specific reply deadline is a concrete oversight step, independent of the still-unresolved operational dispute. Risk: a preservation demand is not a determination of who imposed any limits, and no SpaceX reply was confirmed in this morning's check.

Source: U.S. Senate Committee on Foreign Relations (Democratic office) — Shaheen, Coons letter to Elon Musk (November 13, 2026)

Calendar check · no official Flight 16 date as of this morning

SpaceX has still not announced a date for Starship Flight 16

As of this Monday morning check, SpaceX's Flight 15 recap remains dated November 13–14 and does not name a follow-on flight date. A November 15 Space.com preview of work still ahead — including reuse of a caught ship, eventual off-Earth refueling, and longer-term cadence comments from Elon Musk — likewise does not state a Flight 16 date. Those longer-term comments are not a schedule. This item confirms the calendar gap already noted in the November 15 edition.

Analysis · opportunity and risk
Opportunity: none beyond a clear public calendar fact. Risk: unofficial speculation about the next flight should wait for a company date.

Source: Space.com — What's next for SpaceX's Starship after epic Flight 15 chopsticks catch? (November 15, 2026); SpaceX Flight 15 recap also checked this morning.

Latest briefing and full archive