On March 29, SpaceX lost contact with a Starlink satellite designated 34343. The spacecraft was operating at roughly 560 kilometers above Earth. By March 30, SpaceX confirmed the anomaly, said it posed no threat to the International Space Station, the Artemis II crew, or a Falcon 9 rideshare mission that lifted off that morning, and said it was working to determine the root cause. LeoLabs was tracking tens of objects associated with the event. Reuters SpaceNews
This is the second Starlink anomaly in three months. The first was Starlink-35956, which suffered a propellant tank venting event on December 17, lost altitude rapidly, and reentered on January 17. In the aftermath, SpaceX identified an internal energetic source — a failure originating inside the spacecraft, not from an external collision — and said it was deploying software mitigations across the fleet. SpaceNews SpaceNews
Those mitigations did not prevent the second event.
The pattern is what makes this worth tracking. Two anomalies, both involving the same class of internal failure, both generating trackable debris, both occurring on Starlink v2 Mini satellites within three months of each other. The first prompted a three-week pause in Starlink launches. The second did not — SpaceX's Transporter-16 mission launched about six hours after confirming the 34343 anomaly. SpaceNews
SpaceX has not disclosed the specific cause of either event. Michael Nicolls, vice president of Starlink engineering, said in January that SpaceX was "rapidly working to identify the root cause and mitigate the source of the anomaly." The company said at the time it was deploying software updates to increase protections. In its March 30 statement, SpaceX said it would "rapidly implement any necessary corrective actions." SpaceNews Reuters
The v2 Mini question
The Starlink v2 Mini is a larger, higher-power design than its predecessor. It produces roughly twice the thrust per satellite, uses a different propulsion system configuration, and was introduced as SpaceX sought to increase constellation density in anticipation of higher-throughput demands. The December and March anomalies both involved v2 Mini satellites. Whether the design introduces failure modes that didn't exist in the earlier version — or whether two independent failures simply happened to occur close together — is a question SpaceX has not answered.
After the December incident, SpaceX announced a constellation-wide reconfiguration, lowering approximately 4,400 satellites from around 550 kilometers to 480 kilometers. The stated rationale was to reduce uncontrolled decay times from more than four years to a few months, making debris from any future anomaly less persistent. Nicolls said the maneuver would improve "space safety in several ways" and that SpaceX would coordinate with other operators, regulators, and U.S. Space Command. SpaceNews
That reconfiguration is still underway. Whether satellites at the lower altitude would have exhibited different failure behavior in a similar event is speculative. But the timing — a second anomaly before the reconfiguration was complete — is not.
The IPO in the context
SpaceX is preparing for a public listing that could value the company at up to $1.75 trillion, making it potentially the largest IPO in history. Reuters Starlink is the core asset. Its reliability record is central to the valuation case — the company markets Starlink as a mature, operational system serving millions of customers across aviation, maritime, residential, and government segments.
Two anomalies in three months is not disqualifying for a constellation of nearly 9,400 satellites. Failures happen. The question for the IPO narrative is whether the failure mode is understood, contained, and unlikely to recur at a rate that affects the constellation's economics — or whether there is a systemic issue with the v2 Mini that requires fleet-wide inspection, design changes, or operational restrictions.
SpaceX says it is investigating. That is the correct answer. It is also the answer that leaves the question open.
The orbital environment
Both the December and March anomalies occurred at altitudes where the International Space Station and the Chinese Tiangong space station operate, although at different orbital planes. At 560 kilometers, the collision risk from debris is lower than in dense operational bands, and both stations have maneuvered to avoid Starlink debris in the past. The US Space Force's 18th Space Defense Squadron is tracking the objects from the March event. SpaceNews
The debris from both events is expected to decay naturally within weeks, according to SpaceX. LeoLabs, which first characterized the December event as an internal energetic source rather than a collision, has said the same about the March objects. That is consistent with a propellant or battery-related failure — energetic, but finite.
The question is not whether the debris is dangerous. It appears not to be, on current analysis. The question is why the same class of failure is occurring twice in three months on a fleet that SpaceX operates with what it describes as continuous monitoring and rapid corrective capability. Software updates deployed in January were supposed to prevent this. The March event suggests either they didn't work, or the failure mode is different from what those updates addressed.
SpaceX will implement corrective actions. That is what it said after the first event. The test of those corrective actions is whether there is a third event — and whether it happens before or after the IPO roadshow begins.
