Starlink said there appeared to be “no new risk” to other space operations and did not use the word “explosion.” But it seems that something caused a Starlink broadband satellite to break apart into at least tens of pieces. LeoLabs, which operates a radar network that can track objects in low Earth orbit, said in an X post that it “detected a fragment creation event involving SpaceX Starlink 34343,” one of the 10,000 or so Starlink satellites in orbit.
“LeoLabs Global Radar Network immediately detected tens of objects in the vicinity of the satellite after the event, with a first pass over our radar site in the Azores, Portugal,” LeoLabs said. “Additional fragments may have been produced—analysis is ongoing.”
LeoLabs said the breakup was “likely caused by an internal energetic source rather than a collision with space debris or another object.” Because of “the low altitude of the event, fragments from this anomaly will likely de-orbit within a few weeks,” it said. [...]
LeoLabs said yesterday that the new event is similar to one from December 17, 2025, which also produced “tens of objects in the vicinity of the satellite” and appeared to be “caused by an internal energetic source” rather than a crash with another object. LeoLabs said it wants more information on the anomalies.
“These events illustrate the need for rapid characterization of anomalous events to enable clarity of the operating environment,” it said.
Starlink provided a few details shortly after the December 2025 incident, saying on December 18 that an “anomaly led to venting of the propulsion tank, a rapid decay in semi-major axis by about 4 km, and the release of a small number of trackable low relative velocity objects.” Starlink added that the satellite was “largely intact” but “tumbling,” and would reenter the Earth’s atmosphere and “fully demise” within weeks.
In December, Starlink seemed confident that it could prevent future anomalies. “Our engineers are rapidly working to [identify the] root cause and mitigate the source of the anomaly and are already in the process of deploying software to our vehicles that increases protections against this type of event,” Starlink said in the December 18 post.
We asked SpaceX today whether it has determined the cause of the December anomaly or the one on Sunday, and will update this article if we get a response.
by Jon Brodkin, Ars Technica | Read more:
Image: Aurich Lawson | Getty Images